Tandem
Tandem was an iOS medication-adherence app that used reminders and SMS companion alerts to help people take regular medication.
View original storyProduct snapshot
What it was
Tandem sent medication reminders and SMS alerts to a user-selected companion when medication was missed.
Who it was for
Problem / value
Improve medication consistency through reminders, accountability, and social support.
Core workflow
- medication reminders
- companion accountability
- adherence support
Product form
Pricing model
Free to users; planned monetization through pharmaceutical companies and payers was not validated by revenue.
Competitors or alternatives
What happened
Summary
Tandem moved from a 120-person SMS pilot to a free iOS medication-adherence app, but adoption, retention, and distribution were weaker than expected.
Outcome
Tandem generated no revenue, the App Store listing was removed, and the team continued support only for existing users.
Core risk
A serious behavior-change problem did not create enough adoption, retention, or buyer proof for a free consumer health app.
Shutdown reason
The team stopped further development after seeing weak adoption, poor first-week retention, cost-prohibitive paid acquisition, and no deterministic growth channel.
Demand signal
The founder interview says pilot participants and forum outreach created interest, but real app adoption and retention did not reach expectations. Some users tried the app for only a few days, and the pilot enthusiasm did not generalize to normal usage.
Distribution issue
Paid acquisition was cost-prohibitive for a free app, disease-specific forums did not become a deterministic growth channel, and doctors said they did not have time to recommend or set up the product for patients.
Timeline
- 120-person SMS pilot
- MVP iOS app built around social support
- launch to pilot participants, disease forums, and companion-focused ads
- several hundred early users in the first few weeks
- further development stopped after about seven months
Before you build
Why it matters
Behavior-change products often have delayed rewards, so retention and distribution must be tested as early as the intervention itself.
Primary check
Validate a repeatable acquisition channel, first-week retention, and payer willingness before building a free health app around a delayed behavior-change benefit.
Checklist
- Run a landing-page or ad test before building the full app.
- Test retention with a lightweight SMS or concierge workflow.
- Ask target partners to commit to a real pilot workflow, not just express interest.
- Can users find value without compensation or study framing?
- What percentage of normal users are still active after the first week?
- Which channel can acquire users at a cost that fits the business model?
- Who has budget authority, and what proof would make them pay?
Relevant if
- You are building a health, wellness, productivity, or habit-change product.
- Your product has a delayed payoff and no immediate aha moment.
- Your monetization depends on a payer, employer, doctor, or partner who is not the daily user.
Less relevant if
- Your product already has repeat paid usage in normal conditions.
- The buyer and daily user are the same person and payment has been proven.
Pre-build tests
- Recruit users from the actual acquisition channel, not only a paid study.
- Measure setup completion and first-week usage before building a native app.
- Test payer or provider sponsorship with a concrete offer and price.
Transferable lessons
- Do not treat compensated pilot engagement as proof of organic demand.
- Measure first-week retention before building more features.
- Validate who pays before scaling a free user base.
- Test whether doctors or partners will actually add the workflow to their day.
If you build this today
Start with one condition or medication routine, run landing-page and ad tests before building, and prove either paid consumer intent or a provider/payer sponsor. A concierge SMS workflow can test adherence behavior before a full mobile app.