# When an LTV model hides a constant-churn assumption > A precise lifetime value is presented despite changing retention and customer economics. Diagnose the cause, choose a bounded correction and verify ltv estimates accompanied by sensitivity and model limits. Source: https://saas-marketing.net/guides/ltv-model-assumes-churn-is-constant/ Topic: SaaS Metrics and Analytics Type: guide Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/ltv-model-assumes-churn-is-constant/ ## Short answer A precise lifetime value is presented despite changing retention and customer economics. Start with this check: Inspect the model's churn, margin, expansion and time-horizon assumptions. The corrective action is to show scenarios or cohort-based alternatives when the simplifying assumptions are not credible. ## Key takeaways - Inspect the model's churn, margin, expansion and time-horizon assumptions. - Show scenarios or cohort-based alternatives when the simplifying assumptions are not credible. - Do not present a planning estimate as a guaranteed customer value. - Review ltv estimates accompanied by sensitivity and model limits. --- A precise lifetime value is presented despite changing retention and customer economics. The useful response is a diagnosis that changes a decision, not another report describing the symptom. Use this play with the metric owner and the source-system owner. The working evidence should include metric dictionary, source records and cohort definition, with private or sensitive details removed from any shared example. ## Confirm the problem in the actual workflow Inspect the model's churn, margin, expansion and time-horizon assumptions. Start with one representative case and follow it from the original action to the reported outcome. Identify where the observed behavior first differs from the intended process. A screenshot of a final dashboard can be useful, but it may hide the source record, a delayed update or a decision made elsewhere. Keep the unit of analysis explicit: a consistent account, user, event or revenue cohort. The same label can conceal different populations or stages. Before comparing two results, check that they describe the same kind of work and have had a comparable chance to complete it. ## Separate the visible symptom from the cause Write the numerator, denominator, unit, period, source and exclusions before interpreting the number. Separate observed data from assumptions and forecasts. A metric can be calculated correctly while still answering the wrong business question. The symptom in this case is specific: a precise lifetime value is presented despite changing retention and customer economics. Ask which piece of evidence would distinguish an operating failure from a measurement failure or a mismatch in the original plan. If the evidence is unavailable, record the missing source and its owner instead of treating the preferred explanation as established fact. ## A situation to work through A young product with changing cohorts may not support a stable lifetime estimate from one recent monthly churn rate. This is an illustrative situation, not a reported client case. Record the equivalent evidence and assumptions for your own workflow. ## Choose the smallest useful correction Show scenarios or cohort-based alternatives when the simplifying assumptions are not credible. Keep the change narrow enough that the responsible people can implement and inspect it. If a correction changes several things at once, describe it as a combined operating change; do not later claim that one small element caused the whole result. Assign the correction to the metric owner and the source-system owner. Agree which artifact will show that the work is complete. An owner without an observable acceptance condition can close a task while leaving the original problem unresolved. A detailed checklist without an owner creates the opposite problem: the evidence requirement exists, but nobody is accountable for producing it. ## Preserve the important limitation Do not present a planning estimate as a guaranteed customer value. This condition belongs beside the recommendation because it can change the decision. It should not disappear when the plan becomes a short presentation or a status update. Twenty activated accounts divided by eighty eligible accounts is 25%. Dividing the same twenty accounts by two hundred individual signups produces 10%, but it mixes units. Both inputs can be real while the second ratio is unsuitable for an account-activation claim. ## Verification worksheet | Review item | What to record for this issue | Owner | Evidence | | --- | --- | --- | --- | | Observed symptom | A precise lifetime value is presented despite changing retention and customer economics. | | | | Diagnostic test | Inspect the model's churn, margin, expansion and time-horizon assumptions. | | | | Proposed correction | Show scenarios or cohort-based alternatives when the simplifying assumptions are not credible. | | | | Guardrail | Do not present a planning estimate as a guaranteed customer value. | | | | Review measure | LTV estimates accompanied by sensitivity and model limits | | | Download a working copy and follow the [worksheet instructions](/resources/#using-worksheets). Keep unknown facts visible rather than filling gaps with guesses. ## Decide whether to keep, revise or stop the change Review ltv estimates accompanied by sensitivity and model limits after the agreed observation period. Keep the correction when the intended behavior is verified and the guardrail remains acceptable. Revise it when the diagnosis was useful but the intervention did not resolve the cause. Stop and reassess when new evidence shows that the original problem was framed incorrectly. Record what changed in metric dictionary, source records and cohort definition. This gives the next review a stable starting point and prevents a definition change from being mistaken for a performance improvement. ## Related methods and next steps - [NRR and churn benchmarks: align the revenue cohort](/research/nrr-and-churn-benchmarks/) - [Attribution model comparison calculator](/calculators/attribution-model/) - [One customer journey, different attribution answers](/examples/attribution-models-one-dataset/) - [SaaS Cohort Analysis: A Practical Guide for Marketers](/guides/cohort-analysis-for-saas-marketers/) Return to the [saas metrics topic guide](/saas-metrics/), browse its [complete resource collection](/topics/saas-metrics/), or use the [working resource library](/resources/). The [primary reference](https://amplitude.com/docs/analytics/charts/funnel-analysis/funnel-analysis-interpret) provides relevant platform or methodological context; the diagnosis and example here are original editorial guidance. ## Frequently asked questions ### What is the first diagnostic check? Inspect the model's churn, margin, expansion and time-horizon assumptions. Inspect the actual working record or customer path rather than relying only on a summary report. ### What should change after the diagnosis? Show scenarios or cohort-based alternatives when the simplifying assumptions are not credible. Record the owner and the evidence needed to verify the correction. ### What limit should the team keep visible? Do not present a planning estimate as a guaranteed customer value. A local improvement does not establish a universal benchmark or guarantee a commercial result. ### How should the correction be evaluated? Review ltv estimates accompanied by sensitivity and model limits using a consistent unit and observation window. Keep the original evidence and record any measurement changes.