The Estimator
Enter your average revenue per user (ARPU) and your monthly churn rate. The estimator applies the standard SaaS CLTV formula and returns your result immediately — no email address, no account required.
CLTV = ARPU ÷ Monthly Churn Rate
Example: $85 ARPU ÷ 2.5% churn = $3,400 lifetime value per customer
The Formula Behind the Number
The standard SaaS CLTV formula is deliberately simple: divide your average monthly revenue per customer by your monthly churn rate expressed as a decimal. That quotient is the expected total revenue a single customer will generate before they cancel — assuming both figures stay constant over time.
CLTV = ARPU ÷ Churn Rate
Where churn rate is expressed as a decimal (e.g. 2.5% = 0.025).
Equivalently: Average Customer Lifespan = 1 ÷ Churn Rate
So CLTV = ARPU × Average Customer Lifespan in months.
A few things this formula assumes — and where it breaks down. It treats churn as constant, which is rarely true across cohorts. It uses ARPU rather than revenue per account, which can mask the difference between a $29/month plan and a $299/month plan sitting inside the same average. And it does not account for expansion revenue: if customers upgrade over time, your real CLTV is higher than this formula states.
For most bootstrapped SaaS teams, this formula is accurate enough to make the decisions that matter — whether you can afford to spend $X to acquire a customer, and whether this month's churn rate shift has meaningfully changed that answer. For a deeper look at what churn rates are typical at your stage, the B2B SaaS Churn Benchmarks 2026 guide gives you numbers to compare against.
If you want to include expansion revenue in your CLTV model, the calculation moves to a gross revenue retention (GRR) base. The GRR Guide explains how that metric feeds into a more complete picture of revenue durability.
See the Stripe signals that move your CLTV every day.
Dnoise watches your churn events, failed payments, and ARPU shifts in real time — so you know when your lifetime value calculation has changed before you open a spreadsheet.
No credit card. Read-only access. Setup in 2 minutes.
What Actually Moves Your CLTV
CLTV is sensitive to two inputs and two inputs only: ARPU and churn. But both of those inputs are themselves downstream of specific events inside your Stripe account — events that happen every day and that most founders only catch in hindsight.
Churn rate is the dominant lever. Because churn sits in the denominator, small changes compound fast. Going from 3% monthly churn to 2% monthly churn on $100 ARPU takes your CLTV from $3,333 to $5,000 — a 50% increase in lifetime value from a single percentage point of improvement. According to B2B SaaS benchmarks, median monthly churn for early-stage B2B SaaS sits around 2–3%. If you are above that, churn reduction is almost certainly worth more per dollar of effort than any acquisition channel.
Failed payments are the silent churn driver. Industry data puts involuntary churn — customers lost not because they chose to leave but because a payment failed and was never retried successfully — at roughly 20–40% of total churn for subscription businesses. These are customers with intact intent to stay, whose CLTV you are forfeiting to a declined card. Spotting which failed payments are still recoverable is covered in detail in the Stripe Failed Payments Recovery Guide.
ARPU moves with plan mix. If lower-tier plans grow faster than higher-tier plans, your blended ARPU falls — and your CLTV falls with it even if churn holds steady. This is the plan-mix problem that often hides inside an otherwise healthy MRR growth number. Seeing the split clearly requires tracing your MRR by plan, not just in aggregate.
Expansion revenue makes the formula optimistic in your favour. If customers upgrade, your real average revenue per customer per month is higher than the ARPU at acquisition. This is why net revenue retention (NRR) above 100% is so valuable — it means each cohort becomes worth more over time, compounding the CLTV figure upward rather than degrading it.
CLTV in Context: The CAC Ratio
CLTV in isolation is not a decision-making metric. It only becomes useful when measured against what you spend to acquire each customer — your customer acquisition cost (CAC). The CLTV:CAC ratio tells you whether your business model works at the unit level before you pour more money into growth.
The commonly cited benchmark is a CLTV:CAC ratio of 3:1 or higher. At 3:1, you generate three dollars of lifetime revenue for every dollar spent acquiring a customer — enough margin to cover infrastructure, support, and still produce profit. Below 2:1, most SaaS businesses are acquiring customers they cannot afford. Above 5:1, some argue you are underinvesting in acquisition and leaving growth on the table.
The second question is how long it takes to earn back your CAC from a customer's revenue. That is the CAC payback period — typically expressed in months. If your CAC payback is 18 months but your average customer stays 14 months, the unit economics do not work regardless of what the CLTV:CAC ratio says. The CAC Payback Guide walks through how to calculate and interpret this alongside your CLTV figure.
Both ratios depend on CLTV being accurate. If your churn rate is pulled from a dashboard that counts cancellations but misses failed-payment churn, your CLTV is overstated — and every downstream decision built on it is off.
Know when your churn rate moves — before it changes your CAC math.
Dnoise surfaces churn events, failed payments, and ARPU shifts the day they happen in Stripe. Click any number to see the exact subscription event behind it.
No credit card. Read-only access. Setup in 2 minutes.
What Dnoise Shows You
This estimator tells you your CLTV given the inputs you provide. Dnoise watches your Stripe account every day and shows you when those inputs are shifting — so your CLTV figure reflects reality, not last quarter's assumptions.
Specifically, Dnoise surfaces the following signals that directly affect your CLTV calculation. First, it shows you your active churn events — every cancellation that happened in Stripe, with the plan, amount, and customer visible in one click. Second, it surfaces failed payment events that have not been retried — customers whose subscriptions are about to lapse not by choice but by billing failure. Third, it tracks your ARPU trend over time, broken down by plan, so you can see plan-mix shifts before they move your blended average. And fourth, it shows MRR movement by category — new, expansion, contraction, and churn — so you know which component is driving your revenue line each day.
Every number Dnoise displays is traceable. Click any figure and you see the raw Stripe events behind it — no normalization layer, no proprietary weighting, no black box between your data and the number on screen. The formulas are documented. The source events are visible. If the number looks wrong, you can verify it yourself in under a minute.
Setup is read-only and takes under two minutes. Dnoise cannot move money or modify anything in your Stripe account. You can remove access from Stripe's dashboard at any time. See the Live Dashboard Demo to watch it calculate against a real account before connecting your own.
Frequently Asked Questions
Is this CLTV formula accurate enough to use for real decisions?
For the decisions most founders need to make — whether to raise or lower acquisition spend, how to set a target CAC, whether a churn improvement is meaningful — yes. The ARPU ÷ churn formula is the standard SaaS CLTV model used by investors and operators alike. Its limitations are real: it assumes constant churn, ignores cohort differences, and does not account for expansion revenue. But for a bootstrapped team without a data team, starting with this formula and tracking how it moves month over month is far more useful than having no figure at all. Refine the model as your data matures.
Should I use monthly churn or annual churn in this formula?
Use monthly churn if your ARPU is monthly revenue. The formula is ARPU ÷ churn rate, and the time units must match. If you bill annually and think in annual figures, convert: your monthly churn rate is approximately your annual churn rate divided by 12 (though the relationship is not perfectly linear — monthly compounding means annual churn is slightly higher than 12× monthly churn). For most SaaS businesses with monthly billing, monthly figures are the natural unit and simplest to keep consistent.
Why does a small change in churn rate change CLTV so dramatically?
Because churn is in the denominator. When a denominator shrinks, the quotient grows non-linearly. At 5% monthly churn, CLTV is 20× ARPU. At 2% monthly churn, CLTV is 50× ARPU — a 2.5× improvement in lifetime value from a 3-percentage-point drop in churn. This is why churn reduction has such a strong ROI relative to almost any other growth lever, particularly at the early stage where each percentage point represents a meaningful fraction of your total churn. The B2B SaaS Churn Benchmarks 2026 guide gives you the context to know whether your current rate has room to move.
Does this formula account for failed payments and involuntary churn?
Not explicitly — it uses whatever churn rate you enter. If your churn rate is pulled from a tool or dashboard that only counts voluntary cancellations, your input will understate true churn, and your CLTV estimate will be too high. Involuntary churn from failed payments can represent 20–40% of total subscription losses. To get an accurate churn rate to use in this formula, you need to count every subscription that lapses — whether the customer clicked cancel or a payment silently failed. The Stripe Failed Payments Recovery Guide covers how to identify and separate these two components in your Stripe data.
How is this different from what Dnoise calculates?
This estimator is a static calculator: you enter numbers, it returns a result. Dnoise is a live system connected to your Stripe account. It calculates your actual ARPU and churn from raw Stripe events every day — reflecting what happened overnight, not what you remember from last week. The difference is that Dnoise shows you when your CLTV inputs are moving in real time, so you are not making decisions with a number that is weeks out of date. You can see the Live Dashboard Demo before connecting anything.
Connect once. Know what your CLTV inputs are doing every morning.
Dnoise reads your Stripe account — churn events, failed payments, ARPU by plan — and shows you what changed overnight. Every number traced to the exact Stripe event behind it.
No credit card. Read-only access. Setup in 2 minutes.
See also
- LTV Calculator — get a quick CLTV estimate from ARPU, gross margin, and churn rate without the full worked model.
- Dnoise vs ChartMogul — compare how each platform tracks the retention data that feeds your CLTV.
- Live Dashboard Demo — see Dnoise calculate against a real Stripe account before you connect your own.
- Connect Stripe Free — read-only access, setup in under 2 minutes, remove anytime.
- B2B SaaS Churn Benchmarks 2026 — know whether your churn rate is typical or an outlier at your stage.
- Stripe Failed Payments Recovery Guide — find the involuntary churn that is silently dragging your CLTV down.
- GRR Guide — understand how gross revenue retention feeds into a more durable CLTV model.
- CAC Payback Guide — put your CLTV number in context against what you spend to acquire each customer.