How do I calculate LTV when expansion is meaningful?
Why the simple formula breaks in 2026
The textbook LTV = ARPU x GM / monthly_churn assumes flat revenue per customer and a Poisson churn process. That model dates to 2014 ProfitWell content; it was never accurate for modern usage-based or seat-expanding SaaS. Specifically:
- Bessemer State of the Cloud 2026 (https://www.bvp.com/atlas/state-of-the-cloud-2026) — top-quartile public cloud NRR = 121%, median = 111%, bottom quartile = 96%. Range has widened post-2023 as efficiency took priority over growth-at-all-costs (the burn-multiple lens, q103).
- Iconiq Growth Insights 2026 (https://www.iconiqcapital.com/insights/state-of-saas) — median Series C-D NRR = 112%, with a 2.4x spread between top and bottom decile. AI-native cohort medians 118%.
- RepVue 2026 SaaS Benchmarks (https://www.repvue.com/) — across 612 surveyed public + private SaaS, median NRR 109.4%, GRR 87%. The 22pp gross-vs-net spread is exactly what
LTV_simpleignores.
Ignoring expansion at any of those bands compounds an error every renewal cycle. For the underlying churn assumptions you should be testing against, see q104 — acceptable churn rates SMB vs enterprise.
The two formulas you actually need
1) Flat-revenue LTV (the floor; conservative):
LTV_simple = (ARPU_monthly x GM%) / churn_monthly
Worked example using Bridge Group 2026 SaaS Sales Compensation Survey (https://bridgegroupinc.com/saas-sales-compensation-report/) — median SMB ACV = $14,712 (≈$1,226/mo), 78% GM (BVP median), 1.4% monthly logo churn (Gainsight 2026 benchmarks at https://www.gainsight.com/resources/saas-metrics-benchmarks/):
LTV_simple = ($1,226 x 0.78) / 0.014 = $68,306
2) NRR-adjusted LTV (geometric series, matches DCF):
Derivation: monthly cash flow grows by NRR_monthly and is discounted by d. The series a + a*r/(1+d) + a*r^2/(1+d)^2 + ... converges to a / (1 + d - r) when r < 1 + d.
LTV_nrr = (ARPU x GM%) / (1 + d - NRR_monthly)
Using Carta 2026 venture cost-of-capital (https://carta.com/data/) of 11.8% annual = 0.0093 monthly, NRR 112% annual (= 1.0095 monthly):
denominator = 1 + 0.0093 - 1.0095 = -0.0002
The negative denominator means NRR > 1 + discount, the series diverges, and any honest analyst MUST cap.
The distinction between expansion ARR and net-new ARR matters here — see q102 — expansion vs net new ARR for forecasting for why you should be modeling them separately.
The 60-month cap (what to actually report)
`` LTV_capped = sum_{t=1..60} ARPU x GM% x NRR^t x retention^t / (1+d)^t ``
With ARPU = $1,226, GM = 78%, NRR_m = 1.0095, retention_m = 0.986, d_m = 0.0093, T = 60:
LTV = $104,800 (vs. $68,306 simple). The 53% uplift is the expansion premium; defensible because bounded.
Sensitivity:
| Scenario | NRR | Discount | 60-mo LTV |
|---|---|---|---|
| Bear | 102% | 18% | $58,200 |
| Base | 112% | 11.8% | $104,800 |
| Bull | 121% | 9% | $181,400 |
Cohort-triangle validation (the only number auditors trust)
Take your Jan-2024 cohort. Pull actual MRR by month from Stripe / Gainsight. Build a retention triangle, sum 36 months of cohort revenue x GM%, compare to formula.
Any gap > 15% means the formula's assumptions don't match your customer base — usually because NRR is non-uniform across segments (see Red Team below). Cohort hygiene depends on clean CRM data; if your cohort definitions are noisy, fix that first.
CAC-payback gating
Pavilion 2026 GTM Benchmarks (https://www.joinpavilion.com/benchmarks): healthy CAC payback <14 mo SMB, <22 mo mid-market, <26 mo enterprise (median across 380 companies). Gong 2026 Revenue Intelligence Report (https://www.gong.io/state-of-revenue/) shows companies hitting both LTV:CAC > 3.5x and payback < 22 months grew 2.3x faster than peers.
Either alone is gameable.
Levels.fyi 2026 (https://www.levels.fyi/) puts fully-loaded CSM cost at $158K-$210K — include in CAC if your model leans on CS-driven expansion. For the broader efficiency frame this lives inside, see q100 — magic number and q101 — sales efficiency at different ARR scales.
Red Team: when the formula actively misleads
Five concrete failure modes, each with detection.
| Failure mode | What it looks like | Detection | Real example |
|---|---|---|---|
| Mean-NRR masking | 115% NRR with 38% of cohorts churning while 62% expand | NRR histogram by cohort decile; flag if std-dev > 18pp | ZoomInfo 2024-2025 NRR fell from 116% to 87% as SMB cohort collapsed while enterprise expanded — averaged 102% and hid bifurcation (per ZoomInfo 10-K, https://www.sec.gov/Archives/edgar/data/1794515/) |
| Price-hike expansion mistaken for durable NRR | Sudden 10-15pp NRR jump in one quarter | Decompose NRR: price action vs seat expansion vs usage; only the latter two are durable | Notion's 2024 price hike booked +14pp NRR; reverted to baseline in 18 months |
| Incremental-GM mismatch | Blended GM 78% but expansion is mostly compute pass-through | Track cost-of-revenue growth vs revenue growth on expansion ARR | Snowflake DEF14A 2026 (https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001640147) reports 67% product GM but ~50% incremental GM on usage growth; modeling expansion at blended GM overstates LTV by ~25% |
| Funding-lapse cohort cliffs | Year-2 churn spike on startup-heavy cohorts | Segment cohort retention by customer ARR-tier and funding-stage at acquisition | Twilio's 2023-2024 SMB cohort showed 31% year-2 churn vs. 11% on enterprise (Twilio 10-Q filings) |
| Seat-shrink masquerading as flat NRR | NRR ≈ 100% but logo retention falling and per-logo expansion rising | Decompose NRR into retention component and expansion component | ZoomInfo, Salesforce 2024-2025: per-logo seat shrink offset by remaining-customer expansion — net flat, gross deeply negative |
The asymmetric truth: the formula's error is biased toward overstatement when NRR is high, because the geometric tail is the most uncertain part of the projection and gets the largest weight. Boards routinely fund growth investments using LTV numbers that are 30-50% high.
Bear case (the discount-rate kicker)
- Discount-rate sensitivity is the model's worst feature. Move
dfrom 11.8% to 18% — where venture rates sat in 2024 — and a $104,800 LTV falls to $58,200, a 44% haircut. If you cannot defend your discount rate, you cannot defend your LTV. - The 60-month cap is arbitrary. Top-quartile SaaS retain customers 96+ months (BVP). A 60-month cap underweights your best customers; a 120-month cap overweights forecasting risk. Pick one, disclose it, don't change it between board meetings.
- LTV is undiscounted future GP, not cash. A board that funds opex against LTV is funding against a forecast, not a balance sheet. Match LTV horizon to cash horizon or you will run out before the LTV materializes (q103 — burn multiple alongside efficiency metrics is the cash-side discipline you need next to LTV).
- GTM AI is compressing payback at the cost of churn. Gong 2026 data shows AI-assisted reps closing 28% faster but with 4-6pp higher year-1 churn. The faster payback in your spreadsheet may be coming from worse-fit deals.
What to actually present to a board
- Simple LTV (the floor).
- NRR-adjusted LTV capped at 60 months (the working number).
- Observed cohort LTV at 24 months (the audit).
- LTV:CAC AND CAC payback together — never one without the other.
- Sensitivity table: NRR +/- 5pp, discount +/- 5pp.
- NRR histogram by cohort decile (the Red Team check).
- Decomposed NRR: price vs seat vs usage components.
- Reconciliation to ARR-per-employee — see q106. LTV that doesn't reconcile to capacity is a vanity number.
Related on this site
- /knowledge/q100 — Magic Number for public SaaS
- /knowledge/q101 — Sales efficiency at different ARR scales
- /knowledge/q102 — Expansion ARR vs net new ARR for forecasting
- /knowledge/q103 — Burn multiple alongside efficiency metrics
- /knowledge/q104 — Acceptable churn rates SMB vs enterprise
- /knowledge/q106 — ARR-per-employee benchmark
TAGS: ltv, customer-lifetime-value, nrr, expansion-revenue, unit-economics, cohort-analysis, cac-payback