App Adoption & Usage Model
A cohort calculator for subscription-app growth. Model who signs up, who bails on the trial, who sticks around month after month, and how a heavy-using few drive most of the usage. Tuned with real fitness-app benchmarks — configure any scenario.
Model Inputs drag to explore — everything recalculates live
Acquisition
Trial Funnel
Retention
Engagement Mix
Unit Economics
Usage Concentration the Pareto reality — a few heavy users drive most of the activity
Unit Economics flat subscription revenue vs usage-driven cost to serve
Industry Benchmarks the evidence base behind the defaults
How The Model Works
Each month a fresh cohort of sign-ups enters and is routed through a trial funnel. Whatever fraction survives to activate then decays along a retention curve, and every active user is classed as a heavy, medium, or light user with its own session rate. Totals are the sum over all cohorts.
1 · Trial funnel — for a cohort of S sign-ups:
2 · Retention — activated users persist with a decaying rate plus a loyal floor:
R(t) = coreFloor + (1 − coreFloor) · monthlyRetentiont Active(T) = Σm ≤ T activatedm · R(T − m) // superpose cohorts3 · Usage — the active base splits into heavy/medium/light; total sessions weight each segment by its per-week rate. Because heavy users log many multiples of a light user's sessions, they dominate total usage even though they're the smallest group — the Pareto effect.
4 · Unit economics — every active user pays the same subscription, but the cost to serve them scales with usage:
revenue/day = active · (price / 30.44) // flat per subscriber cost/day = Σ activeSeg · costPerDayseg profit = revenue − costBecause a heavy user logs many multiples of a light user's sessions, their cost to serve can exceed the flat subscription price — so the heaviest segment may run at a loss while light users are near-pure margin. Acquisition cost (CAC) and trial-period serving costs are not modeled, so real margins are tighter.
Modeling caveat: subscription-renewal retention (RevenueCat/Adapty) and app-open retention (AppsFlyer/Localytics) are measured differently. Here "activated" ≈ a committed/subscribed user, so its retention is gentler than raw first-week app-open curves. Treat outputs as directional planning estimates, not forecasts.