CLTR = ARPA per period ÷ churn rate
The same construction as CLTV with the gross margin term removed.
What it is legitimately for
- Capacity and revenue planning. How much top-line a cohort will produce.
- Segment comparison where cost of service is roughly equal across
segments.
- A quick sanity check, because it needs one fewer assumption.
The one place it does damage
Substituting CLTR for CLTV in a ratio against acquisition cost. At 76% gross margin, that overstates the ratio by roughly a third, and it does so silently, because both numbers are called "lifetime value" in conversation.
A business that looks like 3.4:1 on lifetime revenue is 2.6:1 on lifetime value. One clears the conventional bar and the other does not, from the same data.
If the number is going into an economics decision, apply margin. See CLTV to CAC.
It inherits the same assumptions
Everything that makes CLTV fragile applies here too: which churn, whether the horizon is capped, and whether the segments are blended. Using gross revenue churn and capping the horizon is as necessary here as there.
A worked example
ARPA $9,600 a year, gross annual revenue churn 9%, 76% gross margin.
CLTR uncapped = 9,600 ÷ 0.09 = $106,667
CLTV uncapped = (9,600 x 0.76) ÷ 0.09 = $81,067
CLTR capped at 5 years ≈ $39,360
Three numbers, one customer. The label has to say which.
The traps
- Calling it lifetime value.
- Feeding it into a CAC ratio.
- No horizon cap, exactly as with CLTV.
- Blending segments with different cost to serve, which is precisely what the
margin term would have exposed.
Where this sits
CLTR is Measurement in the Tenbound Pipeline Architecture Standard. Its practical value is as a check: if CLTR and CLTV are far apart, the cost of serving that segment is high, which is itself a finding.