---
title: "Why Is My Customer Lifetime Value Calculation Wrong? 7 Causes"
description: "A customer lifetime value calculation breaks in seven places: gross profit, churn basis, blended segments, horizon, discount. The bridge that reconciles it."
topic: "Metrics"
author: "Jay Bheda, Co-founder, GainTrace"
audience: "CS Operations, Head of Customer Success"
published: 2026-09-18
modified: 2026-09-18
source: https://gaintrace.com/explore/metrics/customer-lifetime-value-calculation-wrong
---

# Why Is My Customer Lifetime Value Calculation Wrong?

*When customer success says one number and finance says another*

**Short answer:** A customer lifetime value calculation goes wrong in seven places, and four of them move the number by more than half. The usual causes: revenue used in place of gross profit, logo churn used in place of revenue churn, one blended rate across every segment, and no horizon cap or discount rate. Build the bridge from your number to the finance number before anyone argues about either.

**Key takeaways**

- Finance discounts capped gross profit; customer success divides revenue by a churn rate. Those are two different quantities, so the two numbers were never going to match.
- Applying gross margin is the single largest correction most calculations need, and it costs nothing but one figure from the income statement.
- Logo churn understates revenue churn whenever the accounts that leave are smaller or larger than average, and it ignores contraction entirely.
- Dividing by net churn when net expansion is above 100% returns an infinite or negative lifetime, which is why some teams quietly stop publishing the number.
- One blended churn rate across self-serve and enterprise produces an LTV that describes no customer you have; segment first, then compute.

Your customer lifetime value calculation says one thing, the finance model says roughly a third of it, and the meeting where that surfaced did not go well. Both numbers were produced in good faith. They disagree because they are different quantities wearing the same three letters: customer success divides average revenue by a churn rate, finance discounts capped gross profit over a fixed horizon. Nobody in the room usually knows which adjustment did the damage.
This page is for the CS Ops lead or Head of CS who has to defend an LTV figure in front of a CFO. It names the seven places the number breaks, shows the four that move it most, and gives you a four-adjustment reconciliation you can build in an afternoon so the gap becomes a set of named adjustments instead of an argument.

## Why does my customer lifetime value calculation disagree with finance?

> **The LTV bridge:** The LTV bridge is a four-adjustment table that walks from the customer success lifetime value number to the finance one, naming each adjustment (gross margin, churn basis, horizon cap, discount rate) and the money it moves. Teams argue about whose LTV is right for months. The bridge ends the argument, because each row is a decision somebody can defend or overturn on its own.

A customer lifetime value calculation in a customer success tool is almost always average revenue per account divided by a churn rate. The finance version discounts gross profit, caps the horizon at 36 or 60 months, and uses revenue churn including contraction. Run both on the same accounts and the second is routinely 50% to 70% lower. Neither side is lying; they are answering different questions, and only one of them is being used to set acquisition spend.

> "Customer Lifetime Value (CLTV): The total revenue expected from a customer over their relationship with the company."
>
> — r/CustomerSuccess, 2025

That definition, written by a CSM preparing for a leadership interview, is the one most customer success teams use, and the word doing the damage is revenue. A CFO will not spend against revenue, because serving that revenue costs money. The same thread pattern shows up in the modelling advice founders give each other.

> "Calculating LTV without Gross Margin: If your gross margin is 75%, your true LTV is (ARPU * 0.75) / Churn."
>
> — r/SaaS, 2026

Lifetime value is also, unlike churn or health, not a metric your tooling computes for you. In 4,978 public G2 reviews of five customer success platforms, only 6 reviews (0.1%) mention LTV, CLTV or lifetime value at all, against 686 (13.8%) for churn. The number is built by hand, in a spreadsheet, from inputs nobody audits.

## Which seven mistakes break a customer lifetime value calculation?

Seven errors account for nearly every gap we have seen between a customer success LTV and a finance LTV. Find your rows first: most calculations carry four or five of them at once, and the first three below usually explain the bulk of the difference.

| Mistake | Symptom | Fix |
| --- | --- | --- |
| Revenue in place of gross profit | Your LTV is 25% to 40% higher than finance's and the difference is close to your cost of revenue. | Multiply by gross margin taken from the income statement, not from a guess. Hosting, support and professional services all sit inside it. |
| Logo churn in place of revenue churn | The LTV holds steady while ARR falls, because downgrades never enter the number. | Compute churn on revenue, including contraction. A 40% seat reduction is 40% of that account churned. |
| Net churn used as the divisor | Expansion pushes net churn to zero or below, and the formula returns an infinite or negative lifetime. | Never divide by net churn. Use gross revenue churn in the denominator and model expansion as a separate uplift. |
| One blended rate for every segment | The LTV describes no customer you have: too low for enterprise, far too high for self-serve. | Segment by contract value band or motion, compute an LTV inside each, and report the set. A weighted average is a reporting choice, not the answer. |
| The flat-hazard assumption | Early cohorts churn hard and survivors stay for years, but one rate treats month 2 and month 30 as equally risky. | Plot monthly churn by tenure. If the rate falls with age, compute LTV from the survival curve or from mature cohorts only. |
| No horizon cap and no discount rate | The formula pays you revenue in year nine at full value, which no CFO will accept. | Cap at 36 or 60 months to match how long your product and pricing stay recognisable, and discount at the rate finance already uses. |
| Contract data that disagrees with billing | Two systems hold ARR and they differ, so the average revenue input is wrong before any formula runs. | Reconcile the account list to billing once a quarter. Fix the ARR field before touching the formula. |

> "[the platform] doesn't seem to manage this well, resulting in erroneous data around ARR, renewal dates, customer stage, and health."
>
> — Mid-Market reviewer, public G2 review

The last row is the one people skip and the one that invalidates everything above it. Reviewers describe the same failure from the reporting side, where the financial fields are the ones that need hand-holding.

> "For example, some of the out-of-the-box reporting features, particularly around financial metrics like ARR and NRR, have required more manual effort than expected."
>
> — Senior Director of Customer Success, small-business SaaS, public G2 review

## What is the right lifetime value formula for B2B SaaS?

Use gross profit in the numerator, gross revenue churn in the denominator, a capped horizon and your company's discount rate. The naive formula below is the one in most customer success decks, and it is worth writing out only so you can see what it assumes.

**The formula to stop using**

```
LTV = ARPA ÷ Monthly churn rate
```

Where:
- ARPA: average recurring revenue per account per month, before any cost of serving it
- Monthly churn rate: usually logo churn, which ignores downgrades and treats a 10-seat account as equal to a 400-seat one
- What it assumes: that risk never changes with tenure, that money in year eight is worth what money is worth today, and that serving the customer is free

**The formula finance will accept**

```
LTV = (ARPA × Gross margin) ÷ (Monthly gross revenue churn + Monthly discount rate)
```

Where:
- Gross margin: gross profit divided by revenue, from the income statement; B2B SaaS typically sits in the 70s or low 80s once support and hosting are loaded in
- Monthly gross revenue churn: lost and contracted recurring revenue divided by starting recurring revenue, expansion excluded
- Monthly discount rate: the annual rate finance already uses, divided by twelve; 10% a year is about 0.8% a month
- What good looks like: a number you can rebuild from four cells that each point at a named source system

**Capped lifetime, in months**

```
Capped lifetime = (1 − (1 − c) ^ n) ÷ c
```

Where:
- c: monthly gross revenue churn as a decimal, so 2.6% is 0.026
- n: months in the cap, normally 36 or 60
- Why it matters: at 2.6% monthly churn the uncapped formula pays you 38.5 months of revenue; a 60-month cap pays 30.5, and the difference is money you would have banked in 2032

> "Customer lifetime value and churn for that specific channel, not blended across your whole customer base"
>
> — r/startups, 2026

## How do I reconcile my customer lifetime value calculation with finance?

Build the bridge in one sitting: start from the number your team publishes, apply the four adjustments in order, and show the money each one moves. The output is a table a CFO can mark up line by line, which is a different conversation from two people defending two totals.

1. **Write down the number you publish today and how it was built.** Name the ARPA figure, the churn rate, the period both were measured over and the system each came from. If two people cannot rebuild the same figure from that description, stop here and fix the inputs.
2. **Apply gross margin.** Take gross profit divided by revenue from the last reported quarter. Ask finance which costs sit above the line, because support and customer success salaries sometimes do and that changes the answer.
3. **Switch the churn basis.** Recompute churn on recurring revenue rather than logos, including contraction. Report both rates side by side; the gap between them tells you whether your churn is concentrated in small accounts or large ones.
4. **Cap the horizon.** Pick 36 or 60 months, apply the capped-lifetime formula, and say why you picked it. Contract length, product roadmap and pricing stability are all reasonable justifications.
5. **Discount at the company rate.** Use the rate finance already applies in its own models. Borrowing their rate removes the last place where the two numbers can differ for a reason nobody wrote down.
6. **Publish the bridge, not the number.** Show all six rows every time the figure appears. A single total invites the question; the bridge answers it before it is asked.

> **Worked example:** A B2B SaaS company carries ARPA of $1,000 a month and 2.0% monthly logo churn, so the published LTV is $50,000. Gross margin is 76%, which takes it to $38,000. Churn recomputed on recurring revenue including contraction is 2.6%, not 2.0%, because the accounts that left were larger than average: $29,231. A 60-month cap gives a capped lifetime of 30.5 months, not 38.5: $23,214. Discounting at 10% a year lands at $19,514. The gap is $30,486, or 61% of the number the team had been publishing, and every pound of it is now attributable to a named decision. These figures are illustrative; run the bridge on your own accounts.

| Row | Adjustment | Value | Change |
| --- | --- | --- | --- |
| 1 | Published customer success LTV (ARPA ÷ logo churn) | $50,000 |  |
| 2 | Apply gross margin of 76% | $38,000 | −$12,000 |
| 3 | Churn basis: revenue churn 2.6%, not logo churn 2.0% | $29,231 | −$8,769 |
| 4 | Cap the horizon at 60 months (30.5 months of lifetime) | $23,214 | −$6,017 |
| 5 | Discount at 10% a year | $19,514 | −$3,700 |

**Before you publish an LTV figure**
- [ ] Gross margin is applied and the source quarter is named.
- [ ] The denominator is gross revenue churn, never net churn and never logo churn alone.
- [ ] Contraction is inside the churn figure, and seat reductions above 20% are counted.
- [ ] The horizon cap is stated in months, with the reason.
- [ ] The discount rate matches the one finance uses elsewhere.
- [ ] The number is computed inside segments, and any blend is labelled as a blend.
- [ ] The ARR feeding ARPA reconciles to billing within 2%.
- [ ] The bridge appears wherever the number appears.

## Why does one blended customer lifetime value describe none of my customers?

A blended LTV averages populations that behave nothing alike, so the result sits in a gap where no customer lives. Self-serve accounts churn at several percent a month and enterprise accounts at a fraction of that; one rate across both produces a figure too low to justify enterprise acquisition spend and too high to justify self-serve spend, at the same time.

The second cohort problem is age. Monthly churn usually falls with tenure, because the accounts that were a bad fit leave early. Dividing by a blended rate applies the churn of a three-month-old cohort to a four-year-old customer. Plot monthly churn by tenure band before you trust any single divisor. If the curve flattens after month nine, compute lifetime from mature cohorts and treat the first nine months as an onboarding survival rate, which is the same logic behind [why customers churn after onboarding when time to value is long](https://gaintrace.com/explore/onboarding/time-to-value-onboarding-complete-but-churned).

> "LTV is similarly difficult because we do not have enough history yet to know what mature customer lifetime and churn will look like."
>
> — r/startups, 2026

That founder is right, and the honest response for a company under two years old is a horizon-capped LTV with the cap set to the history you have. A 24-month capped lifetime value computed from 24 months of data is a real measurement. An extrapolated lifetime of nine years from 14 months of data is a guess with a currency symbol in front of it.

## What is a good customer lifetime value, and is there a benchmark?

No trustworthy public benchmark for B2B SaaS customer lifetime value exists, and any figure quoted as one should be treated as marketing. LTV depends on price point, gross margin, segment mix, horizon and discount rate, and no published survey holds those constant, so a cross-company comparison compares five things at once. Numbers circulate anyway, with no publisher and no sample.

> "I've been diving into EU SaaS benchmarks from the 2024 and here's what we often see"
>
> — r/CustomerSuccess, 2024

The list under that sentence gave a customer lifetime value band of 20,000 to 50,000 euros, a CAC to CLV ratio and an NPS range, with no publisher, no sample size and no method. Benchmark the inputs instead, where real survey data exists. SaaS Capital's September 2025 retention brief, a self-selected survey of more than 1,000 private B2B SaaS companies, puts median gross revenue retention at 91%, rising to 95% above $250,000 average contract value. High Alpha's 2025 benchmarks, 800 or more self-selected private SaaS respondents, put median CAC payback at 8 months between $1M and $5M ARR and 14 months between $5M and $20M, with the warning that early-stage figures understate cost because onboarding and customer success are often left out of CAC.

| Function | What they mean by LTV | Inputs | Use when |
| --- | --- | --- | --- |
| Customer success | Expected revenue over the relationship | ARPA, logo churn, no cap | Prioritising accounts against each other, where relative size matters more than absolute accuracy |
| Finance and FP&A | Discounted gross profit over a capped horizon | Gross margin, revenue churn, cap, discount rate | Unit economics, board reporting and any decision that commits cash |
| Growth and marketing | Realised revenue per acquired customer by channel at 12 months | Cohort billings by acquisition source | Judging paid channels, where a short realised window beats a long forecast |
| Investors and diligence | LTV to CAC on gross profit, plus payback months | Gross profit LTV, fully loaded CAC | Fundraising, where the ratio is compared against payback and both must agree |

If the point of the exercise is to argue for customer success headcount, LTV is a weak instrument and retention is a strong one. [How to calculate net revenue retention for B2B SaaS](https://gaintrace.com/explore/revenue/how-to-calculate-net-revenue-retention-b2b-saas) and the [cost of churn calculator](https://gaintrace.com/tools/cost-of-churn-calculator) both produce numbers a CFO can check in an afternoon, which LTV cannot.

## When is a customer lifetime value calculation the wrong argument to have?

Drop the LTV argument whenever the decision in front of you turns on a period, not a lifetime. Renewal forecasting, customer success capacity planning and this year's retention target are all period questions, and LTV answers none of them: it is a forecast about money arriving in 2030 being used to settle a dispute about next quarter.

Three situations where a different number is the right one. For headcount and coverage, use ARR per CSM and the accounts-per-CSM model. For the value of preventing a churn, use the account's remaining contract value plus the expansion you would have booked, which is a figure with a date on it. For whether customer success is working at all, use gross and net revenue retention by cohort, which [measuring customer success team impact for a CEO and CFO](https://gaintrace.com/explore/customer-success/measure-customer-success-team-impact-on-revenue) covers in the form finance accepts. LTV earns its place in one decision only: how much you are willing to spend to acquire a customer, and that decision belongs to whoever owns the acquisition budget. If your team is being asked to pick a single number to be judged on, [the north star metric for customer success](https://gaintrace.com/explore/metrics/north-star-metric-for-customer-success) is the argument to have instead.

## How does GainTrace keep lifetime value inputs honest?

GainTrace connects billing, CRM, product usage and support, so the recurring revenue behind ARPA comes from the system that invoices the customer, not a CRM field somebody last edited in March. Contraction is recorded as it happens, which is the input most customer success LTV figures miss. [Renewal forecasting](https://gaintrace.com/solutions/renewal-forecasting) shows revenue at risk by period with the movements that produced it, and [customer health](https://gaintrace.com/platform/customer-health) shows the usage and champion changes behind each account. You still build the bridge; the inputs stop being the argument.

## Frequently asked questions

### Why is my LTV so different from what finance calculated?

Because finance discounts capped gross profit and customer success divides revenue by a churn rate. Four adjustments explain nearly all of the gap: gross margin, revenue churn in place of logo churn, a 36 or 60 month horizon cap, and a discount rate. Apply them in that order and write down what each one moves. The residual is an input problem, usually ARR that does not reconcile to billing.

### Should I use gross margin in the customer lifetime value formula?

Yes. Revenue is what the customer pays; gross profit is what you keep after serving them. A CFO will not commit acquisition spend against revenue, so an LTV without margin cannot be used for the one decision LTV exists to inform. Take gross profit divided by revenue from the last reported quarter and ask finance which costs sit above the line, because the treatment of support and customer success salaries varies.

### Why does our LTV go infinite when NRR is over 100%?

Because someone put net churn in the denominator. When expansion exceeds churn, net churn is zero or negative and dividing by it returns infinity or a negative number. Use gross revenue churn as the divisor. Model expansion separately as an uplift on the gross figure, or report expansion through NRR and leave it out of the lifetime calculation entirely.

### How do I calculate LTV when we only have 14 months of history?

Cap the horizon at the history you have. A 12 or 24 month capped lifetime value computed from real cohorts is a measurement; a nine-year lifetime extrapolated from 14 months is a guess. Report it as capped, state the cap, and revise it as cohorts age. Pair it with CAC payback in months, which needs no forecast at all and answers most of the same questions.

### What is a good LTV to CAC ratio for SaaS?

The commonly quoted 3:1 has no primary research behind it that we could trace, so treat it as a convention rather than a benchmark. The measurable partner is CAC payback. High Alpha's 2025 benchmarks, from 800 or more self-selected private SaaS respondents, put median payback at 8 months between $1M and $5M ARR and 14 months between $5M and $20M, noting that early-stage figures understate cost.

### Should customer success own the LTV number at all?

Customer success should own the inputs and finance should own the calculation. Your team knows which accounts contracted, which champion left and which ARR field is stale; finance knows the margin, the discount rate and the horizon policy. Splitting it that way removes the incentive to pick a churn basis that flatters the story, which is what produces two numbers in the first place.

## How this was researched

We searched 29,027 sentences from 4,978 public G2 reviews of five customer success platforms and 33,600 posts from r/CustomerSuccess, r/SaaS, r/sales and r/startups, published May 2024 to September 2026, for every mention of LTV, CLTV, CLV and lifetime value. Only 6 of the 4,978 reviews (0.1%) mention it in any form, against 686 (13.8%) for churn, which is why the practitioner evidence on this page comes from Reddit and the benchmark evidence from named publishers. Retention and CAC payback figures are from SaaS Capital's September 2025 retention brief and High Alpha's 2025 SaaS benchmarks, both self-selected surveys. The seven-mistake taxonomy, the bridge and the priority order are our own analysis; the worked example uses illustrative figures.

## Sources

- [SaaS Capital, 2025 B2B SaaS Retention Benchmarks (Research Brief 32, September 2025)](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)
- [High Alpha, 2025 SaaS Benchmarks Report](https://www.highalpha.com/saas-benchmarks)
- [r/SaaS: I spent 3 weeks building the SaaS financial model VCs expect to see](https://reddit.com/r/SaaS/comments/1w6u8mr/)
- [r/startups: How should an early startup calculate CAC and LTV?](https://reddit.com/r/startups/comments/1vnuog2/)
- [r/startups: Revenue-driven growth channels lie to you if you only look at the top number](https://reddit.com/r/startups/comments/1ulgvc2/)
- [r/CustomerSuccess: How do these metrics apply to hybrid SaaS models?](https://reddit.com/r/CustomerSuccess/comments/1h5m1za/)

## Next steps

Build the bridge this week, then keep the inputs behind it connected to billing, not to a CRM field. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).