MWG Advisory · Thesis

Most subscription apps are leasing you a tool

A feature set billed monthly is a tool lease, and it gets re-decided every renewal. A service accrues. The difference is a loop — and the loop is what nobody finishes building.

01The thesis

Subscription pricing came from software that holds state

SaaS earned recurring revenue because the software did continuous work on the customer's behalf and held something that got more valuable the longer they stayed. Consumer apps adopted the pricing model and left the state behind.

Health and wellness is where this shows most plainly. What most of these apps ship is a set of features: a workout library, a plan generator, an assessment, a tracker, a daily score. Good features, often excellent ones. But a feature is a tool, and a tool's value lives in the moment you pick it up. Billing monthly for a tool isn't a service — it's a financing arrangement. You're leasing a thing that would otherwise be a one-time purchase, and the user works out the arithmetic eventually.

There's a single question that separates the two, and I now ask it first in every teardown:

If I stopped paying tomorrow, what would I lose besides access?

For a tool lease the honest answer is nothing. The workout library, the meal plans, the guided sessions, the score on the home screen — they were never mine, and none of them were doing anything while I wasn't looking. For a service the answer is a list: the record of what I've done, the plan that's mid-flight, the position I've accumulated, the thing it knows about me that took months to learn. That list is the whole difference between churn and renewal, and it's also the only switching cost these products can build, because it is the one asset a competitor can't ship.

Renewal asks a different question of each

Renewal isn't a payment. It's a re-purchase decision, and the question the customer asks depends entirely on which of the two they bought.

Tool lease

“Did I use it enough to justify the fee?”

Answered from the customer's own memory, and it gets harder to answer yes to every month the novelty wears off. Nothing the product holds helps them.

Service

“Is it still working on my behalf?”

Answered with evidence the product generated. It can show the target it set, what changed, and what's next — and the answer improves with tenure instead of decaying.

Most of the health and wellness apps I've torn down are being renewed against the left-hand question, and none of them had to be.

02The loop

Four nodes, four joins — but only the nodes get the attention

The loop is what converts a feature set into a service. Diagnosis tells me something true I couldn't have known. Assignment turns that into a specific instruction with a number on it, which I accept. Verification checks whether I did it. Progress accumulates what I did into something visible that extends.

Roadmaps are written in nodes. Nodes are what you can demo, price and put on a feature list. But a node is a capability, and capability is not a service — what makes a product feel like a coach rather than a library is whether the nodes are wired to each other. That's the join.

To be fair to these teams, some of the joins do get built. What they don't get is design attention. They arrive late, sit one tab off the main path, or connect to the wrong object — the shape of something added after the feature it connects, rather than the thing the feature was built to serve.

And a join is precisely where the product does work the customer doesn't have to. That's why it's the unit that matters commercially: every broken join hands a job back to the user, and a job the user does is a job they can do somewhere else for free.

So there are two ways to fail, and much of health and wellness is doing both. The nodes are only partially fulfilled, and the joins between them are afterthoughts — or, in the case of the last one, missing entirely.

Diagnosis a real instrument Assignment a real prescription Verification counts attendance Progress renders attendance 01 is this about my finding? 02 will I actually do it? 03 did anything change? 04 why get measured again?
Fill levels are my judgment, not a measurement. Diagnosis and assignment are genuinely built. Verification and progress exist but only ever grade attendance. The three joins that exist are real but unattended. And the one that completes the loop — back to a new diagnosis — is the one I rarely find built at all.
03The joins

Three of them usually get built. The fourth usually doesn't.

The patterns below come from my teardowns in health and wellness — a wearable and a set of mobility apps, each used over dated days of real use. I wrote my predictions before reviewing any tape, so the products could correct me. They did, repeatedly, and mostly in their favor. That matters, because the argument isn't “these apps are bad.” Teams in this space have built more than they get credit for, and the loop still doesn't complete.

01  Diagnosis → Assignment Built, and orphaned

“Does this plan have anything to do with what you just found in me?”

The instruments in wellness have gotten good: camera-based movement screens, sleep staging, blood panels, recovery scores. The better products carry the finding into a plan with the reason attached. The failure usually isn't the join — it's routing. The most credible thing the product produces often sits off the path a new member actually walks.

Job handed back → find the thing that makes this a service

02  Assignment → Verification Built, wrong object

“Am I actually going to do this?”

There's usually a real commitment object — a goal you pick, a plan you accept, sometimes a forgiveness layer for missed days. The mechanic is right. What you're committing to is time or volume: minutes, sessions, days in a row.

Job handed back → decide what counts as success

03  Verification → Progress Misallocated

“Did anything actually change?”

Here it starts to go. A product can hold a real measure of the member — a composite score, named problem areas, a baseline from a lab — and still show a meter after every session that is really a count of days completed. Compliance gets rendered as if it were capability.

Job handed back → work out whether it's working

04  Progress → Diagnosis Rarely built

“Why would I come back and get measured again?”

This is the one I rarely find. Products tell members to retest on a schedule and then nothing schedules it, so an assessment from many months ago keeps being presented as current state. For an assessment-led product a stale assessment is worse than none: it prescribes confidently against a body that has changed.

Job handed back → remember to re-measure, and know when

Read the right-hand column on its own and you have the lease. Four jobs the customer performs, in a product they are paying monthly for precisely so they don't have to.

04The cause

The loop can't complete because there's nothing to complete against

Most goal objects in health and wellness are made of participation.

Streaks. Rings closed. Minutes meditated. Sessions completed out of seven. Days logged. Meanwhile the same products compute real measures of the member — a recovery score, a sleep score, a mobility score, a fitness age — and rarely let a member set a goal on one. A target state for the body is the thing the category is least likely to offer.

That single fact propagates through everything above. A product can only verify against a declared target, so attendance becomes the only thing verification can grade. The progress meter therefore renders attendance. And once the payoff is a streak, the streak is what you come back for — the reassessment becomes optional, nothing schedules it, and the loop circles back on participation instead of returning to diagnosis.

The nodes being partial and the joins being broken turn out to be the same problem seen from two angles. You can't fill the verification node while the only thing it's allowed to measure is whether someone showed up.

Why I expect to keep finding this

The tell is consistent: an assessment, a content library, and a subscription — in a category where the content has a free substitute. Fitness, mobility, sleep, nutrition, meditation and skincare all fit it, and so do adjacent categories like language learning, personal finance and dog training. Wherever the library is the product, the loop is the only thing left to charge for, and it's rarely finished.

Duolingo is the counterexample worth studying, and it's instructive that language had an external capability ladder — CEFR — sitting there before the app existed. It could tell a user what a level means. Most wellness categories have no ladder that clean, which is why their products fall back on counting. The ones that already have a physiological scale to borrow — VO₂ max, resting heart rate, sleep efficiency — have a head start they mostly aren't using.

05Why this matters

A counter wins attention. A complete loop wins attention and results.

The obvious objection is that participation loops work. They do — streaks and rings are some of the most effective engagement mechanics in consumer software, and I'd be wrong to write them off. In the mobility apps I tore down, the one with no diagnosis at all had by far the best engagement trend.

The reconciliation

Participation mechanics win attention. Verification mechanics win effectiveness. A product that proves you showed up can get you to show up more. It struggles to charge much, because what it proves isn't what you bought. In that same set, the apps that verify something about the member's body can begin to charge more per member than the one that doesn't.

A complete loop doesn't make you choose between the two, and it pays off twice.

First, it justifies a premium. The value proposition moves from access to outcome. The product is selling a result it can show rather than a library the member has to work through alone, and outcomes support a higher price than access does.

Second, it lifts retention and renewal, because it wins on both axes at once. Participation keeps the member opening the app; verification gives them a reason to believe it's working. A product with only attention loses the member when the novelty fades. A product with only effectiveness loses them in the quiet weeks between assessments. A complete loop holds them through both.

The fix is smaller than it sounds. It isn't more content, better filters or a more accurate instrument — those are all more tool. It's a target on a real number and a date the claim gets settled — sleep consistency 64 to 75, settled November 30 — and then the sentence few products in the category are built to write:

Sleep consistency went 64 to 78. Next up: training load.

That sentence is the loop completing. It is also goal extension, a new chapter opening, and the answer to the renewal question — evidence the product generated that it is still working on the member's behalf.

Complete the loop and the thing you're selling changes category. The features stay the same. What changes is that the member has a reason to keep showing up, a reason to believe it's working, and something to lose by stopping. That is the basis on which a premium subscription gets renewed.

MWG Advisory · mwgadvisory.com Related: the Whoop teardown · the Loop Audit

← Back to all research