Skip to main content
Industries · Consumer Subscription

Find the step where subscribers quietly give up

DecisionBox follows onboarding, trials, renewals and engagement in your app data, and shows which step and which group of subscribers is costing you, even when overall retention looks fine.

CriticalOnboarding cliff

Onboarding step 4 (set goal + pick reminder) completion fell 28% after the March UX update. Aggregate D7 retention held flat — iOS promo surge masked it.

~118,000 affected signups. Users who skip step 4 retain at D30 at 4% vs 22% for those who complete it. The step is the habit-loop anchor.

RecommendationRoll back the UX change for non-iOS-promo cohorts; A/B test the next iteration at 10% exposure.

Built for Heads of Growth, Heads of Retention, VPs of Monetization, and Heads of Analytics at fitness, learning, productivity, dating, and wellness subscription apps.

The cost of late signals

The subscriber count looks fine. The cohort underneath is where the growth actually moved.

Three benchmarks every consumer subscription leader recognizes. Each points to the same gap: your data already holds the signals — habit-formation drop-off, channel-level LTV, paywall conversion drift — but they only surface when somebody asks the right question. Most weeks, nobody does.

D30 app retention
5%

Median Day-30 retention across consumer subscription apps. Habit-formation drop-off in week one drives most of the gap — and your data already holds the signals.

Source: Adjust, Mobile App Trends Report
App-store fee
15-30%

Of subscription revenue paid to Apple and Google. The dashboard reports gross subscription; the underlying data reports net contribution after fees and cancel-friction differentials.

Source: Apple App Store / Google Play developer terms
Free-trial conversion
~25%

Typical free-trial to paid conversion rate for subscription apps. Source-level conversion varies by 30+ points; the blended number conceals which acquisition channels convert and which buy installs that never pay.

Source: RevenueCat, State of Subscription Apps
From real runs

From a finding to a plan

Three shapes the team sees every quarter: a single-system onboarding-completion cliff the aggregate concealed, a cross-system habit-loop vs. price-elasticity pattern the dashboard couldn't see, and an app-store-vs-web LTV mirage the gross-revenue dashboard averaged into the wrong winner.

CriticalOnboarding cliff

Onboarding step 4 (set goal + pick reminder) completion fell from 71% to 51% after the March UX update. Aggregate D7 retention held flat because iOS in-app promo surged at the same time.

period
6-week rolling, post-March 14 build
step 4 completion
71% → 51% (-20 pts)
affected signups
~118,000
D30 retention (skip step 4)
4% / (complete step 4): 22%
P1Roll back UX + A/B retest at 10%

Roll back the March 14 UX update for non-iOS-promo cohorts; A/B test the next iteration at 10% exposure with the reminder-time field optional.

target
restore step-4 completion + D30 retention
effort
small (UX revert + experiment setup)
modeled D30 lift if reverted
+4.5 pts on next cohort
CriticalHabit-loop signal

The January price increase showed flat aggregate churn. Habit-formed users (3+ sessions/week) absorbed it; users still in habit formation churned at 2.4× the rate.

price increase
$9.99 → $12.99 (Jan 8)
aggregate churn (post-change)
6.1% (vs 6.0% baseline)
habit-formed cohort churn
4.2%
in-formation cohort churn
10.1% (2.4× baseline)
P1Habit-stage price gating + comms timing

Hold price for users still in habit formation (under 3 sessions/wk); reweight price-change comms toward habit-formed users; gate the next change on cohort habit state.

target
stop training future change against in-formation users
effort
medium (billing config + comms segmentation)
recoverable churn (modeled)
~38,000 subs over 6 mo
HighChannel LTV mirage

App-store subscriptions convert at 12% higher D1. Web subscriptions deliver 31% higher 12-month LTV after fees and renewal-cancel friction net out — the dashboard reports the wrong winner.

D1 conversion
app-store 24%, web 21%
12-mo LTV (net of fees)
app-store $48, web $63 (+31%)
app-store fee drag
-30% gross
unintended-renewal share (app-store)
18% of revenue
P1Reweight paywall + audit cancel friction

Reweight the paywall flow toward web checkout where eligible; audit app-store cancel-friction signals for compliance review; instrument net-contribution KPIs alongside gross.

target
shift the conversion mix toward net-LTV-positive channel
effort
medium (paywall flow update + compliance review)
modeled annual lift
~$3.40 × ~580,000 subs ≈ $2.0M
Use cases

Five surfaces the team already owns, one continuous discovery.

Same engine, same data, five categories of work your team is already doing — or wants to do, if the queue ever clears. Pick the surface that matters this quarter.

The cohort that signed up and never built the habit.

Onboarding step-level drop-off, habit-formation milestones (first session, third session, first-week cadence), and the patterns that separate users who build the habit from users who stall. DecisionBox reads onboarding events, session cadence, and downstream subscription state together — and surfaces the cohorts whose habit-formation shape changed before the weekly growth deck shows it. The deep dive lives in how DecisionBox decides what to investigate.

Sample analysis areas
  • Onboarding-step drop-off and its downstream retention impact
  • Habit-formation milestones (first session → third session → week-one cadence)
  • Build-version regression catches per release
  • Cohort-level signup → activation → first-week-habit funnel
  • Push notification and reminder cadence impact on session frequency
Why DecisionBox

Built for subscription apps who want a cohort analyst running overnight, not three dashboards to reconcile.

Three things every finding from DecisionBox carries. None of them changes how your team works in your subscription platform, your product analytics SDK, your paywall tooling, or whatever data tools and BI you already standardized on.

01

Sees what nobody had time to look into

DecisionBox picks which cohorts, acquisition sources, onboarding steps, and channel segments to investigate from your acquisition, onboarding, billing, and engagement data. Findings ship into a queue your team triages in the morning. The cohort-level question stops sitting in the data waiting for the next QBR.

02

Every number you'd defend at the subscription review

Your team re-runs anything, extends anything, overrides anything. No black boxes, no billing-system-reported or SDK-reported numbers the data can't validate, no "trust the AI."

03

Reads all your data, not just RevenueCat and the analytics SDK

Subscription state plus onboarding, paywall, billing, sessions, and engagement — read together. The patterns subscription-management tools can't see (because they only see subscription state) and the patterns product-analytics tools can't see (because they only see events) surface when your data is read end-to-end. Open source, AGPL v3. DecisionBox meets you on the stack you already run.

For your security and compliance review

What Consumer Subscription security teams ask first

How Enterprise handles it

Does our data move?

No. DecisionBox only reads it where it is, and can run inside your own environment, on-prem or air-gapped.

What can the AI see?

Only what you allow. Personal and sensitive data is hidden before the AI sees anything.

Which AI does it use?

The one your company approved, in your cloud account or on your own servers.

Can we audit it?

Every action is recorded: who, what, when and under which rule.

Videos

See DecisionBox at work

All videos
Product tourThe AI analyst that finds what nobody askedA two-minute tour: discovery, validation, Ask and reports on a real marketplace dataset.
DecisionBox for business · Episode 1How to read a finding, and how much to trust itThe numbers, the validation verdict and the evidence behind a finding, before you share it.
DecisionBox for business · Episode 4From finding to decision: read a recommendationThe expected impact, the steps, the findings behind it and its validation.

The next subscription review, with the cohort shifts already mapped.

Let's run it on your data.