Ratio = CLTV ÷ CAC
Both inputs are assumption-heavy, so the ratio inherits every weakness of CLTV and adds one of its own.
The blind spot is time
The ratio has no time dimension. A customer worth $30,000 over five years and one worth $30,000 over eighteen months produce identical ratios at the same CAC, and they are completely different businesses to finance.
That is why the ratio must be read with payback period. Ratio says whether the economics work eventually. Payback says whether you survive until then.
A business at 4:1 with a 30-month payback is more fragile than one at 2.5:1 with a 9-month payback, and the ratio alone ranks them the wrong way round.
Where 3:1 came from
It is a convention that hardened into a rule. The reasoning behind it: below 3:1 there is little room for the assumptions in CLTV to be wrong, and above 5:1 you are probably underinvesting in growth.
Both halves are judgement rather than arithmetic. Treat 3:1 as a prompt to ask questions, not a threshold to pass.
Make CAC comparable
CAC has the same definitional trap as CLTV:
- Fully loaded or programme-only. Salaries, commission, and tooling
included or not. The gap is large.
- New customers only. Expansion spend does not belong in acquisition cost,
and neither do win-backs unless you count them as new. See win-back rate.
- Blended or by channel. Blended CAC hides that one channel is subsidising
another.
State the construction beside the number, exactly as with sales efficiency.
A worked example
Capped five-year CLTV of $29,900 against a fully loaded CAC of $11,400.
Ratio = 29,900 ÷ 11,400 = 2.6:1
Using the uncapped CLTV from the same inputs gives 81,067 ÷ 11,400 = 7.1:1. Same business, same quarter, two numbers that would drive opposite decisions. The horizon cap is the difference, and it is usually invisible on the slide.
The traps
- Comparing a capped CLTV to someone else's uncapped one.
- Programme-only CAC against fully loaded CLTV, or the reverse.
- Blended across segments with very different churn.
- Reading it without payback.
- Using it to justify spend increases, since the ratio typically falls as
volume rises.
Where this sits
This ratio is Measurement in the Tenbound Pipeline Architecture Standard. It is a portfolio diagnostic rather than an operating metric: nobody changes what they do on Monday because of it, which is why it belongs in a board pack and not on a team dashboard.