2/5+150 XP

LTV models that survive board scrutiny

# LTV models that survive board scrutiny

A board member once killed a Series C term sheet with one slide: the CFO's LTV/CAC ratio of 5:1 fell to 1.8:1 once she applied a discount rate and a realistic gross margin. The company had been dividing average revenue per user by churn rate, a shortcut that flatters almost every SaaS (Software as a Service) business and collapses under scrutiny in usage-based pricing models. This lesson builds the version that survives.

Why the naive formula is popular, and wrong

The textbook shortcut is:

LTV = ARPU / Churn Rate

ARPU (average revenue per user, usually monthly) divided by monthly churn gives you "average customer lifetime in months" multiplied by monthly revenue. If ARPU is $100/month and monthly churn is 2%, naive LTV = $100 / 0.02 = $5,000.

Three problems:

1. It uses revenue, not profit. A customer generating $100/month at 40% gross margin contributes $40, not $100, to the business.

2. It ignores the time value of money. A dollar collected in month 36 is worth less today than a dollar collected in month 1, because capital has a cost and risk compounds over time.

3. It assumes flat, predictable revenue per customer. Usage-based pricing (customers pay by API call, seat, or consumption, as with Snowflake or Twilio) makes revenue expand or shrink unpredictably, so a static ARPU figure misrepresents the real cash flow curve.

The defensible formula

A board-grade LTV calculation looks like this:

LTV = Σ [ (ARPU_t × Gross Margin) / (1 + d)^t ] summed over each period t, for as long as the cohort survives.

Where:

ARPU_t: average revenue per user in period t (can vary by period for usage-based products)
Gross Margin: revenue minus cost of goods sold (hosting, support, payment processing), expressed as a percentage. SaaS companies typically report 70 to 85% gross margins as of 2024 estimates (source: KeyBanc SaaS Survey, figures vary by year); usage-heavy infrastructure products often run lower, 60 to 75%, because compute costs scale with consumption.
d: discount rate per period, reflecting cost of capital and risk. A common SaaS convention is 10 to 15% annualized, converted to a monthly rate.
t: time period, month by month, until the survival probability becomes negligible.

Worked example: subscription vs. usage-based

Case A: Flat subscription SaaS.

ARPU: $100/month, flat
Gross margin: 80%
Monthly churn: 2% (so average lifetime approx. 50 months, though we won't just multiply)
Discount rate: 12% annualized, roughly 1% monthly

Naive LTV = $100 / 0.02 = $5,000

Defensible LTV: discount each month's margin-adjusted cash flow ($100 × 0.80 = $80 per surviving customer) by both the survival probability (98% retained each month) and the discount factor (1.01^t). Doing this month by month for 60 months converges to roughly $2,800 to $3,100, an estimate depending on rounding, versus $5,000 naive. That's a 40%+ overstatement from the shortcut alone.

Case B: Usage-based pricing (e.g., a data platform billed by consumption).

ARPU starts at $100/month but grows as customers ramp usage: $100, $130, $160, plateauing near $200 by month 12, a common "expansion" pattern
Gross margin: 65% (compute costs eat more of each incremental dollar)
Logo churn: 2%/month, but net revenue can still grow due to expansion

Here the naive formula is worse than wrong, it's directionally confused. Dividing a snapshot ARPU by churn ignores that usage-based revenue is volatile: some months spike (a customer runs a big batch job), others dip. Applying flat ARPU to a churn-based annuity formula assumes a steady-state that usage-based products never reach in year one. The correct approach forecasts a *revenue curve* per cohort, applies the lower margin, and discounts it. In practice this often lands 20 to 35% below what naive ARPU/churn suggests, even though gross usage grows, because the margin haircut and discounting outweigh the expansion.

Why gross margin matters more than people think

Two companies with identical ARPU and churn can have wildly different LTV if their margins differ. A vertical SaaS company reselling embedded payments or financing (common in fintech-adjacent SaaS) might report blended gross margins in the 50 to 65% range, dragged down by transaction costs, while a pure software product sits at 80%+. If your board deck uses revenue instead of gross margin times revenue, you're implicitly assuming 100% margin, which no real SaaS business has.

Discounting: the piece almost everyone skips

Cost of capital isn't just a finance department concern, it's a marketing accountability question. If your CAC (customer acquisition cost) payback period is 24 months, and you're not discounting future cash flows, you're overstating the return on every dollar of marketing and sales spend. A discount rate converts future dollars into today's dollars, which is exactly what a board or investor cares about when judging whether acquisition spend was rational.

A rough monthly discount factor: if annual discount rate is 12%, monthly rate ≈ 12%/12 = 1% (a simplification; the precise compounding rate is (1.12)^(1/12) − 1 ≈ 0.95%, close enough for this exercise). Multiply each period's cash flow by 1/(1+monthly rate)^t.

Simple spreadsheet logic

Month | Survival % | ARPU  | Margin$  | Discount factor | PV contribution
1     | 100%       | $100  | $80      | 0.990            | $79.20
2     | 98%        | $100  | $78.4    | 0.980            | $76.83
3     | 96.04%     | $100  | $76.8    | 0.971            | $74.58
...
Sum across all months = Defensible LTV

This is a five-minute build in any spreadsheet: one column for survival probability (compounds the churn rate), one for margin dollars, one for discount factor, then sum the products.

Vérification des acquis

1. Why does the naive LTV = ARPU / Churn Rate formula overstate customer value?

2. A board member recalculates a startup's LTV/CAC ratio and it drops sharply after applying a discount rate and realistic gross margin. What does this most likely reveal?

3. For which type of business is a static, single-period ARPU figure LEAST appropriate for calculating LTV?

CHOIX MULTIPLES

4. Select ALL correct answers describing components required to move from the naive LTV formula to a board-defensible LTV formula.

Sélectionnez toutes les réponses correctes.

CHOIX MULTIPLES

5. Select ALL correct answers about why gross margin matters in LTV calculations.

Sélectionnez toutes les réponses correctes.

Benchmarks to sanity-check your number

As of 2024 to 2025 estimates, sector-reported ranges (treat as directional, not precise):

LTV/CAC ratio: a commonly cited healthy target is 3:1 or higher, based on the *defensible* LTV calculation, not the naive one (Bessemer's State of the Cloud, published estimates). If your naive LTV/CAC is 5:1, your true ratio using margin and discounting is often closer to 2 to 3:1.
CAC payback period: US public SaaS medians hover around 12 to 18 months as of recent surveys; European SaaS companies often report slightly longer payback (15 to 24 months), partly reflecting smaller average deal sizes and longer sales cycles in fragmented markets.
Gross revenue retention (GRR): keeping churn out of your LTV assumptions requires knowing GRR, typically 85 to 95% annually for healthy B2B SaaS.
Net revenue retention (NRR): expansion-heavy usage-based businesses can post NRR above 120%, but this doesn't override the need to discount and margin-adjust the LTV calculation, it just means the survival curve looks different.

🎬 [VIDEO: "SaaS Metrics That Matter" - youtube.com/@SaaStr - a practitioner walkthrough of LTV, CAC, and retention metrics used in real board decks, search SaaStr's channel for the latest metrics session]

The board-ready checklist

Before presenting an LTV number, confirm you've applied:

1. Gross margin, not revenue

2. A discount rate reflecting real cost of capital (ask finance for the company's actual rate, don't assume 10%)

3. A survival curve based on actual cohort churn, not a single blended churn rate

4. For usage-based products, a revenue curve per cohort rather than static ARPU

Key Takeaways

Naive LTV (ARPU / churn) ignores gross margin and time value of money, routinely overstating true customer value by 30 to 50%.
The defensible formula discounts margin-adjusted cash flows period by period: LTV = Σ (ARPU_t × ) / (1 + discount rate)^t.

The CAC formula marketers keep getting wrong

Funnel conversion benchmarks by pricing motion

LTV models that survive board scrutiny

# LTV models that survive board scrutiny

Why the naive formula is popular, and wrong

The textbook shortcut is:

LTV = ARPU / Churn Rate

Three problems:

1. It uses revenue, not profit. A customer generating $100/month at 40% gross margin contributes $40, not $100, to the business.

2. It ignores the time value of money. A dollar collected in month 36 is worth less today than a dollar collected in month 1, because capital has a cost and risk compounds over time.

The defensible formula

A board-grade LTV calculation looks like this:

LTV = Σ [ (ARPU_t × Gross Margin) / (1 + d)^t ] summed over each period t, for as long as the cohort survives.

Where:

ARPU_t: average revenue per user in period t (can vary by period for usage-based products)
Gross Margin: revenue minus cost of goods sold (hosting, support, payment processing), expressed as a percentage. SaaS companies typically report 70 to 85% gross margins as of 2024 estimates (source: KeyBanc SaaS Survey, figures vary by year); usage-heavy infrastructure products often run lower, 60 to 75%, because compute costs scale with consumption.
d: discount rate per period, reflecting cost of capital and risk. A common SaaS convention is 10 to 15% annualized, converted to a monthly rate.
t: time period, month by month, until the survival probability becomes negligible.

Worked example: subscription vs. usage-based

Case A: Flat subscription SaaS.

ARPU: $100/month, flat
Gross margin: 80%
Monthly churn: 2% (so average lifetime approx. 50 months, though we won't just multiply)
Discount rate: 12% annualized, roughly 1% monthly

Naive LTV = $100 / 0.02 = $5,000

Case B: Usage-based pricing (e.g., a data platform billed by consumption).

ARPU starts at $100/month but grows as customers ramp usage: $100, $130, $160, plateauing near $200 by month 12, a common "expansion" pattern
Gross margin: 65% (compute costs eat more of each incremental dollar)
Logo churn: 2%/month, but net revenue can still grow due to expansion

Why gross margin matters more than people think

Discounting: the piece almost everyone skips

Simple spreadsheet logic

Month | Survival % | ARPU  | Margin$  | Discount factor | PV contribution
1     | 100%       | $100  | $80      | 0.990            | $79.20
2     | 98%        | $100  | $78.4    | 0.980            | $76.83
3     | 96.04%     | $100  | $76.8    | 0.971            | $74.58
...
Sum across all months = Defensible LTV

This is a five-minute build in any spreadsheet: one column for survival probability (compounds the churn rate), one for margin dollars, one for discount factor, then sum the products.

Vérification des acquis

1. Why does the naive LTV = ARPU / Churn Rate formula overstate customer value?

2. A board member recalculates a startup's LTV/CAC ratio and it drops sharply after applying a discount rate and realistic gross margin. What does this most likely reveal?

3. For which type of business is a static, single-period ARPU figure LEAST appropriate for calculating LTV?

CHOIX MULTIPLES

4. Select ALL correct answers describing components required to move from the naive LTV formula to a board-defensible LTV formula.

Sélectionnez toutes les réponses correctes.

CHOIX MULTIPLES

5. Select ALL correct answers about why gross margin matters in LTV calculations.

Sélectionnez toutes les réponses correctes.

Benchmarks to sanity-check your number

As of 2024 to 2025 estimates, sector-reported ranges (treat as directional, not precise):

LTV/CAC ratio: a commonly cited healthy target is 3:1 or higher, based on the *defensible* LTV calculation, not the naive one (Bessemer's State of the Cloud, published estimates). If your naive LTV/CAC is 5:1, your true ratio using margin and discounting is often closer to 2 to 3:1.
CAC payback period: US public SaaS medians hover around 12 to 18 months as of recent surveys; European SaaS companies often report slightly longer payback (15 to 24 months), partly reflecting smaller average deal sizes and longer sales cycles in fragmented markets.
Gross revenue retention (GRR): keeping churn out of your LTV assumptions requires knowing GRR, typically 85 to 95% annually for healthy B2B SaaS.
Net revenue retention (NRR): expansion-heavy usage-based businesses can post NRR above 120%, but this doesn't override the need to discount and margin-adjust the LTV calculation, it just means the survival curve looks different.

The board-ready checklist

Before presenting an LTV number, confirm you've applied:

1. Gross margin, not revenue

2. A discount rate reflecting real cost of capital (ask finance for the company's actual rate, don't assume 10%)

3. A survival curve based on actual cohort churn, not a single blended churn rate

4. For usage-based products, a revenue curve per cohort rather than static ARPU

Key Takeaways

Naive LTV (ARPU / churn) ignores gross margin and time value of money, routinely overstating true customer value by 30 to 50%.
The defensible formula discounts margin-adjusted cash flows period by period: LTV = Σ (ARPU_t × ) / (1 + discount rate)^t.

The CAC formula marketers keep getting wrong

Funnel conversion benchmarks by pricing motion

LTV models that survive board scrutiny

Why the naive formula is popular, and wrong

The defensible formula

Worked example: subscription vs. usage-based

Why gross margingross marginGross margin is the share of revenue left after subtracting the direct cost of producing goods or services, expressed as a percentage of revenue.Voir la définition complète → matters more than people think

Discounting: the piece almost everyone skips

Simple spreadsheet logic

Benchmarks to sanity-check your number

The board-ready checklist

Key Takeaways

LTV models that survive board scrutiny

Why the naive formula is popular, and wrong

The defensible formula

Worked example: subscription vs. usage-based

Why gross margingross marginGross margin is the share of revenue left after subtracting the direct cost of producing goods or services, expressed as a percentage of revenue.Voir la définition complète → matters more than people think

Discounting: the piece almost everyone skips

Simple spreadsheet logic

Benchmarks to sanity-check your number

The board-ready checklist

Key Takeaways

Why gross margin matters more than people think

Why gross margin matters more than people think