LTV is a profit number, not a revenue number. When teams skip the margin step or mix monthly and annual rates, the figure stops meaning anything, and every decision made from it quietly drifts off the real economics.
LTV, or customer lifetime value, is the total gross profit a customer is expected to generate over the full length of the relationship with your company. The simple formula is average revenue per user multiplied by gross margin, divided by the churn rate. Teams use LTV to size acquisition budgets, set pricing, and judge which segments and channels actually produce profitable customers rather than just loud ones.
The six things to know about LTV before you quote the number in a board deck, pricing meeting, or acquisition plan.
LTV is the gross profit a customer generates across their entire relationship with the company, not the top-line revenue. Revenue minus the cost to serve, averaged over how long the customer stays, is the honest version. Teams that quote revenue LTV are over-counting by whatever the gross margin leaves out.
The textbook formula is average revenue per user, multiplied by gross margin, divided by the customer churn rate for the same period. If ARPU is monthly, churn must be monthly. If ARPU is annual, churn must be annual. Mixing the two periods is the single most common error on this metric.
LTV is the number acquisition cost (CAC) is measured against. Healthy consumer and B2B software businesses target an LTV-to-CAC ratio of around three to one. Below that, growth burns cash. Above that, you may be under-investing in acquisition. Without LTV, CAC is a number with no gravity.
Four levers move LTV: raising price, improving gross margin, lowering churn, and growing accounts over time through upsell and expansion. Of the four, retention and expansion compound the fastest, which is why mature revenue teams spend more energy on the install base than on the top of funnel.
A single company-wide LTV number averages the best segment with the worst segment and the result describes neither. The month a team segments LTV by plan, by acquisition channel, and by vertical is usually the month the leadership team learns that half the growth is unprofitable.
LTV is calculated from three systems: billing data (what customers pay), product data (how much they use and cost to serve), and CRM data (who they are, how they came in, and how long they stay). A CRM like Strkr joins the three so the number is sourced instead of guessed.
There is no single LTV calculation. There are three methods, each honest for a different stage of company maturity. Teams usually start with the simple formula, graduate to cohort-based LTV once they have twelve to twenty-four months of billing data, and move to predictive LTV once they have enough customers for a model to generalize. Picking the wrong method for your stage is where most LTV mistakes begin.
ARPU times gross margin, divided by churn rate. One line of math. Good for early-stage teams with limited data and for quick sanity checks. The weakness is that it assumes churn and ARPU are flat forever, which they are not. Treat the number as a floor, not a forecast.
Group customers by the month they signed up. Track the gross profit each cohort produces every month after that, until the cohort is small enough to be unreliable. Add the actuals, project the tail, and you have an LTV grounded in the real revenue curve rather than a theoretical steady state.
A statistical model (regression, survival analysis, or a probabilistic model like BG/NBD and Gamma-Gamma) estimates each customer's remaining value based on their behavior, plan, segment, and tenure. Powerful when it works. Over-engineered and misleading when applied to a dataset too small to train on.
Fewer than a hundred customers or less than a year of history: simple formula only. One to three years and a few hundred customers: cohort-based. Enough data to split by segment, channel, and plan with statistical significance: predictive. Using method three on a method one dataset produces confident, meaningless numbers.
Never quote LTV without naming the method, the margin assumption, and the time horizon. "LTV is this value" means nothing. "Cohort LTV at the twenty-four-month mark, assuming the published gross margin and a decaying churn curve, is this value" is a number you can defend.
Even the predictive version is a model, and models drift when the market, pricing, or product changes. Rerun the number quarterly, flag the inputs that moved, and expect to be surprised at least once a year. Treating LTV as a settled fact is how teams miss retention cliffs before they become retention problems.
LTV is a famously easy metric to compute wrong. The math looks simple, the inputs are everywhere, and the error only shows up two quarters later when the acquisition budget is set against a number that was never real. Below are the six mistakes that show up on nearly every first-pass LTV calculation, and what to do about each one before quoting the result to leadership.
Multiplying ARPU by lifetime without applying gross margin produces revenue LTV, which is always larger than reality. If gross margin is somewhere around seventy to eighty percent, the error on this one step alone can be twenty to thirty percent. Always apply margin. Always.
If ARPU is monthly and churn is annual, the division produces a number that is off by a factor of twelve. Pick a period, use it everywhere, and label the result with the period. Monthly-ARPU divided by monthly-churn is a monthly LTV. Multiply by twelve if you want the annual equivalent.
The company-wide LTV is almost never the number that drives a decision. The LTV of enterprise customers acquired through outbound is different from the LTV of self-serve customers acquired through paid search. Segment first, then roll up. The blended number is almost always lying.
Early-tenure customers churn at a different rate from year-two customers. Using a single blended churn number treats a healthy install base and a wobbly new cohort as the same, which flatters LTV. Cohort analysis exposes this. Simple formulas hide it.
In B2B SaaS, mature customers often expand through seat growth, add-ons, or usage overage. If the LTV calculation uses the signup ARPU and never updates it, the number undercounts healthy accounts by a wide margin. Net revenue retention above a hundred percent means ARPU grows with tenure, and LTV should reflect that.
LTV is a quarterly conversation, not a once-a-year calculation. Pricing changes, churn trends, margin shifts, and segment mix all move the number. Teams that quote the same LTV for three quarters in a row are usually quoting a number that stopped being true two quarters ago.
LTV sits at the intersection of three systems: billing, product, and CRM. Billing says what customers pay. Product says how they use the service and what it costs to serve them. CRM says who they are, how they came in, and the relationship context around every subscription event. A revenue operations team that cannot join those three cannot calculate LTV at the segment level, which is where the number actually matters. The paragraphs below describe what each system contributes and how a modern CRM like Strkr pulls them together without a data engineering project.
Every invoice, every plan change, every refund, every cancellation. Billing data is the source of truth for ARPU, expansion revenue, and the exact month a customer churned. Pulled into the CRM through a Stripe, Chargebee, or Zuora integration, it hangs off the company record and feeds the LTV calculation directly.
How much the customer uses, how much that usage costs to serve, which features they adopt, and the leading indicators that predict renewal versus churn. Product data turns a flat revenue number into a profit number by exposing cost to serve, and it turns a lagging LTV into a predictive one by exposing engagement.
The acquisition channel, the owner, the deal source, the sales motion, the segment, and the activity history. Without this context, LTV is a flat average. With it, LTV becomes a per-channel, per-segment, per-plan number that actually tells acquisition, pricing, and retention teams what to do differently.
The point of a modern CRM is that the company record is the join key. Billing events, product events, and sales history all hang off the same account. The LTV calculation reads from one place instead of a quarterly spreadsheet reconciliation, which is where most LTV reports go to die.
Customer support is part of the cost to serve, which means it belongs in the LTV calculation. Ticket volume, time to resolve, and premium support utilization vary wildly by segment. A segment with twice the support load has a lower LTV than its revenue suggests, and segment-level LTV is the only way to catch that.
Once the three systems are joined, LTV becomes a dashboard metric with the same refresh cadence as pipeline and ARR. Rolled up by plan, by channel, by vertical, and by cohort. The quarterly spreadsheet reconciliation is replaced by a report the leadership team can actually trust between reviews.
Strkr pulls billing events, product usage, and relationship history onto one customer record, so LTV becomes a dashboard metric instead of a quarterly spreadsheet project. Marketing, pipeline, and documents live in the same tool, which is why the number stays honest.
LTV stands for lifetime value, more precisely customer lifetime value, sometimes abbreviated as CLV or CLTV. All three acronyms refer to the same concept: the total gross profit a customer is expected to generate across the full relationship with the company. In day-to-day business conversation, LTV is the most common shorthand.
The simple formula is average revenue per user (ARPU) multiplied by gross margin, divided by the customer churn rate for the same time period. If ARPU is a monthly number, use the monthly churn rate. If ARPU is annual, use annual churn. The gross-margin step is what turns revenue LTV into profit LTV, which is the only version worth comparing to acquisition cost.
The common benchmark is around three to one: three units of lifetime value for every unit of customer acquisition cost. Below one to one, acquisition is unprofitable. Below three to one, growth is likely burning cash. Significantly above three to one can mean the business is healthy, or it can mean the acquisition team is under-investing. The ratio is a frame, not a target to game.
ARR, or annual recurring revenue, is the current annualized run rate of subscription revenue right now. LTV is the total profit a customer is expected to generate over the full length of the relationship. ARR looks at the present. LTV looks at the lifetime. The two numbers are related but not interchangeable, and acquisition decisions should be made against LTV, not ARR.
Quarterly for most companies, monthly if pricing, churn, or segment mix is moving quickly. LTV is a function of several moving inputs (ARPU, margin, churn, expansion), and treating it as a once-a-year number means every decision in between is made against a stale figure. The teams that trust LTV the most are the teams that recalculate it the most often.
SaaS LTV is usually calculated against monthly or annual recurring revenue, with gross margin typically higher than consumer or services businesses. Expansion revenue (seat growth, add-ons, usage upgrades) is often a bigger contributor to SaaS LTV than price increases, which is why net revenue retention is such a load-bearing metric in the category. Churn is the dominant variable at every stage.
Because segments really are different, and the blended number was hiding that. Self-serve customers acquired through paid search often churn faster and expand less than enterprise customers acquired through outbound sales. The LTV gap can easily be five or ten times between the best and worst segments. The gap is a feature of the data, not a bug in the math.
A modern CRM like Strkr pulls billing events (through a Stripe or similar integration), product usage, and CRM relationship data into one record per customer, which is the join needed to calculate segment-level LTV. The calculation itself is a report, not a feature. The hard part is the data join, and that is what the CRM provides.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
