Step 1
One directory
Stripe, your own table, a CSV or the SDK. Whatever you connect merges into one list.
Product analytics
Who stayed,and what they were worth.
What each one paid, and whether the next cohort will do the same.
How it works
Step 2
LTV and ARPU, kept apart
Revenue per payer and revenue per user are different numbers, and a product with a free plan needs both.
Step 3
D1 to D30 retention
Measured on cohorts old enough to answer. A window that has not elapsed reads as unknown, not as zero.
Step 4
Churn risk
Who has gone quiet, and how much revenue sits with them.
Questions
- Where does the customer list come from?
- Stripe, your own Supabase table, a CSV, or the SDK, whichever you connect. They merge into one directory.
- Why do LTV and ARPU differ?
- LTV spreads revenue over the people who paid. ARPU spreads the same revenue over everyone still using the product. They match only when nobody is on a free plan.
- What does an empty D30 mean?
- That no cohort is thirty days old yet. Bloow shows a dash rather than zero, because the two mean opposite things.
- Can I exclude my own accounts?
- Yes. Internal emails are left out of revenue and retention so your own testing does not flatter the numbers.
Scan your market
Free to start. No card, no plan to choose.