Retained cohort revenue value
What is a cohort retention value calculator?
A cohort retention value calculator estimates how much revenue remains from a starting group of customers after a retention checkpoint, such as 90 days or 365 days. SaaS teams, subscription businesses, product-led growth teams, CFOs, RevOps teams, and lifecycle marketers use it to connect retention curves with retained customers, annual ARPU, customer value, CAC payback, and growth quality.
Cohort retention value formula
The calculator multiplies the starting cohort size by the percentage retained at 365 days, then multiplies that retained customer count by annual ARPU. The 90-day retention checkpoint helps diagnose early activation, while the 365-day checkpoint drives the year-one retained revenue estimate.
Year-1 retained revenue value = Starting customers x Retained after 365 days % x Annual ARPU- Use paying customers in the starting cohort if the output is meant to represent retained revenue.
- Use annual ARPU when the output should represent year-one retained revenue value.
- Model expansion, contraction, downgrades, and net revenue retention separately when ARPU changes materially over time.
Inputs explained
Cohort retention value is strongest when retention percentages come from a consistent cohort definition and ARPU matches the same customer base.
- Starting customers in cohort
- The number of customers, accounts, subscribers, workspaces, or users at the start of the cohort window. Use the same cohort entry rule your analytics or finance team uses for retention reporting.
- Retained after 90 days
- The percentage of the starting cohort still active after 90 days. This checkpoint is useful for diagnosing onboarding quality, activation, product fit, early churn, dunning issues, and low-intent acquisition.
- Retained after 365 days
- The percentage of the starting cohort still active after one year. This drives the headline retained customer count and retained revenue value in the calculator.
- Annual ARPU
- The average annual revenue per retained customer. Use recognized subscription revenue or a finance-approved annualized ARPU definition.
- Year-1 retained revenue value
- The estimated revenue value of the customers who remain in the cohort after one year, before separate adjustments for expansion, contraction, discounts, or margin.
Example cohort retention value calculation
If a cohort starts with 5,000 customers, 48% are retained after 365 days, and annual ARPU is $420, then 2,400 customers remain at one year. The year-one retained revenue value is $1,008,000 before expansion, contraction, discounts, refunds, or gross margin adjustments.
Retained cohort revenue value
Starting customers x retained% x ARPU
Want a similar calculator on your website?
Describe your fields and formula in plain English, match your brand, and embed the widget anywhere—WordPress, Webflow, Shopify, or custom HTML. Capture leads when you're ready.
How to estimate retained cohort revenue value with this wizard
- Define “starting customers in cohort” as the paying accounts entering the analysis window—exclude trials unless finance recognizes them as paid conversions.
- Set day-ninety and day-three-sixty-five retention from survival curves exported from your warehouse—align churn definitions across voluntary cancel, failed renewal, and involuntary dunning policies.
- Input annual ARPU as recognized subscription revenue per retained account year—use blended averages when SKUs differ materially only if leadership accepts the smoothing error.
- Compare year-one retained revenue value against “customers retained at three hundred sixty-five days” to sanity-check scale—flag unrealistic ARPU when retained counts imply enterprise whales hidden inside SMB labels.
Common cohort retention value mistakes
- Using trial signups as starting customers when the revenue model should use paying customers.
- Mixing customer retention and revenue retention without labeling the difference.
- Applying monthly ARPU to an annual retained revenue formula.
- Ignoring expansion, contraction, and downgrades when ARPU changes materially after signup.
- Comparing cohorts from different acquisition channels without accounting for lead quality and intent.
- Treating 90-day retention as interchangeable with 365-day retention in year-one revenue estimates.
- Using blended retention when monthly, annual, SMB, enterprise, and self-serve cohorts behave differently.
Interpreting checkpoint retention against retained revenue
- Checkpoint curves by category
- Consumer subscription apps often exhibit steep early decay while sticky B2B contracts plateau—benchmark rolling cohort curves against your own historical vintages before citing category medians from vendor reports
- ARPU stability assumption
- Annual ARPU inputs work when expansion and contraction roughly net out—material NRR drift belongs in separate expansion models rather than a flat ARPU lever
- Day ninety versus day three hundred sixty-five roles
- Early checkpoints diagnose activation quality while headline retained revenue here keys off the later checkpoint paired with annual ARPU—do not substitute ninety-day retention into the primary multiplier unless you deliberately redefine the formula
Best use cases
- Growth and performance planning
- Budget and forecast scenario modeling
- Client-facing pre-qualification and education
FAQs
Why does the headline revenue multiply day-three-sixty-five retention but day-ninety appears earlier in the wizard?
Day ninety exposes onboarding health while the published formula pairs annual ARPU with accounts projected to survive a full year—keep both checkpoints for narrative context even though only the later percentage feeds the primary multiplier.
Should ARPU include expansion revenue from upsells?
If net-dollar retention routinely exceeds one hundred percent, either lift ARPU to reflect expansion or treat this output as a conservative baseline and model uplift separately.
Can I use monthly ARPU instead of annual ARPU?
Only if you reinterpret the output as monthly retained revenue—misaligned periods double-count or undercount annual run-rate; convert monthly ARPU times twelve before plugging in.
Does this replace net revenue retention reporting?
No—this snapshot multiplies surviving cohort mass by static ARPU—NRR still captures expansion and contraction within surviving accounts at finance-grade precision.
How do I use cohort retention value to judge acquisition quality?
Compare retained revenue value by acquisition channel, campaign, plan, region, and signup month. A channel with cheap CAC can still be poor quality if its 90-day retention, 365-day retention, or retained revenue value falls below higher-cost channels.
What should I do if 90-day retention is strong but 365-day retention drops sharply?
Investigate renewal friction, product depth, usage decay, annual billing shock, poor expansion fit, support issues, and customer success coverage. Strong early activation with weak one-year retention often means the product solves an initial problem but does not become a durable habit or budget priority.
How should I model expansion and downgrades in cohort value?
Use this calculator for retained customer value at a static ARPU, then run a separate net revenue retention or expansion model for upsells, seat growth, downgrades, and contraction. Mixing everything into one ARPU can hide whether value comes from retention or expansion.
How does cohort retention value affect CAC payback?
Higher retained revenue value improves the chance of recovering CAC, but payback also depends on gross margin, billing timing, sales costs, and support costs. Compare retained revenue by cohort against acquisition cost to see which customer groups actually pay back.
Should I calculate retention by users, accounts, or revenue?
Choose the unit that matches the decision. User retention is useful for product engagement, account retention is useful for customer survival, and revenue retention is useful for financial planning. Do not mix the units in one benchmark without explaining the definition.
Why does a blended retention curve hide retention problems?
A blended curve can mask weak cohorts when stronger enterprise, annual-plan, or high-intent segments offset poor self-serve or low-intent acquisition. Segmenting retention reveals where onboarding, lifecycle, pricing, or acquisition quality needs attention.
Glossary
Scenario modeling
Comparing multiple assumption sets to estimate potential outcomes before execution.
Conversion intent
User behavior that indicates readiness to take a commercial action such as signup or purchase.
Related calculators
Related guides
Step-by-step articles on building, embedding, and ranking calculator pages like this one.
Category: Cohort analytics & subscription retention economicsTopics: Cohort retention value, Annual ARPU, Day-365 retention
Last reviewed: 2026-05-07
Reviewed by: Calclet Growth Team