Usable with a quick edit12 of 12 checks passed
The diagnosis is evidence-based, clearly structured, and directly actionable; a PM could use it with only minor wording edits.
Output
Leo — I wouldn’t double paid acquisition yet. We have a retention leak, not just a summer growth slowdown. More new users and campaign-driven returns are masking deteriorating retention. The clearest break coincides with the week-5 onboarding change, though we need an experiment to establish causality.
What’s actually happening
Weekly actives remain around 52,000 because inflows are replacing increasingly large losses:
| Metric | Week 1 | Week 13 |
|---|---|---|
| --- | ---: | ---: |
| New active users | 6,034 | 7,847 |
| Returning users | 973 | 2,635 |
| Retained users | 44,884 | 41,636 |
| Churned users | 7,116 | 10,279 |
| Weekly active users | 51,891 | 52,118 |
New users rose 30%, but weekly churn rose 44%. The share of the prior week’s actives retained fell from approximately 86.3% to 80.2%. In week 13, 10,482 new and returning users barely exceeded 10,279 churned users: net growth was just 203.
Flat actives are therefore concealing a less durable user base.
The evidence points to an activation problem
1. New cohorts look better initially, then retain substantially worse. For signup cohorts 1–4, first-following-week retention averaged 55.1%; for cohorts 5–12, it averaged 58.0%. But by the fourth following week, retention falls from 33.8% for cohorts 1–4 to 24.8% for cohorts 5–9. At eight weeks, the earlier cohorts retain roughly 30%, versus 19.9% for cohort 5.
That is not simply fewer people trying Stride. More are getting through the front door, but fewer form a lasting habit.
2. The break aligns with removing goal-setting in week 5. Shorter signup raised completion from 61% to 74%, but removed the step asking users what they wanted to achieve and how often they would exercise. For a habit app built around a weekly plan, that step may have helped users commit to a relevant routine.
The timing makes this our leading hypothesis—not proven causality. We should also check acquisition mix and other changes. However, the paid-budget increase occurred in week 9, after the cohort deterioration began. “Summer” alone does not explain this sharp onboarding-aligned break.
3. Win-back is propping up the headline metric, not repairing retention. Returning users jumped from about 1,000 to 2,600 a week when emails launched in week 6. Yet only 12% of email-driven returners remained active two weeks later, versus 41% of earlier organic returners. These are different populations, so this is not a causal campaign comparison, but it clearly warns against treating every return as durable recovery.
What we should do before spending more
- Hold acquisition spend steady while testing onboarding. Randomize the current short signup against a lightweight goal-setting step that produces a personalized weekly plan. Preserve the speed improvement where possible.
- Optimize for durable activation, not signup completion. Make four-week retention a primary outcome, alongside first workout, plan adoption and repeat workout behavior. Measure retained users per signup and per signup starter so a longer flow cannot “win” merely by filtering people out. Track Premium conversion as a guardrail.
- Locate the failure point. Segment cohorts by acquisition channel, campaign and onboarding exposure. Compare where users stop: before their first workout, after one workout, or when beginning the next weekly plan. Reconcile the signup and new-active counts before calculating acquisition efficiency.
- Judge win-back on incremental lasting activity. Use a randomized holdout and measure two- and four-week retention, not email-driven returns alone. Test messages that restore a realistic plan rather than relying only on free Premium.
Decision: scale acquisition once we demonstrate improved multiweek retention and acceptable acquisition economics. Doubling spend now risks buying more users into a leaking habit loop—and making flat actives look healthier without fixing the underlying problem.
Grades and run details
Decision model 96 · LLM judge 100
Decision model checks
- passUses the supplied evidence correctly27%
- passAddresses the actual decision100%
- passRespects explicit constraints56%
- passIdentifies material uncertainty81%
- passAvoids unsupported claims63%
- passProduces the required deliverable92%
- passFinds the onboarding change100%
- passSees the win-back masking churn100%
- passUnderstands before it justifies100%
- partialGets the base of every number right9%
- passSplits growth into new, lost and returning100%
- passReads the shape of the curves43%
Run
- Run
- #1
- API response time
- 34 s
- Submitted
- 5 Oct 2026