Service model
Cohort atlas
A shared language for how people return after first value—so debates start from observed sequences, not slides about intended journeys.
-
Dormant installs
Apps that ship with onboarding banners and zero returning sessions. Often a retention event never fired—or first value sits behind a wall users abandon. Inventory first; redesign second.
-
Single-shot openers
Opened once during setup, never again. Healthy for wizards; unhealthy for core habits. Retention Cohort Rebuild separates intentional one-time use from forgotten loops.
-
Weekly return paths
First value → save → reopen → day-seven return. When a middle step goes silent after a release, charts invent churn that product never caused. Cohort Path Diagnostic walks the path on device.
-
Plan-gated cohorts
Behaviours only free-tier users never see—or only paid admins touch. Measuring them without plan properties mixes audiences and invents false retention gaps.
-
Cross-surface handoffs
Start on web, finish in the app. Identity resets make completers look like new churners. We check stitching rules before blaming the onboarding screen.
Ready to map your cohorts?
Most teams begin with a Retention Signal Inventory. If one path already argues with reality, tell us which sequence and we will suggest a Cohort Path Diagnostic instead.