DEV Community

Cover image for The LTV:CAC Ratio: The One Number That Decides Your Startup's Fate
Hammad Ali
Hammad Ali

Posted on

The LTV:CAC Ratio: The One Number That Decides Your Startup's Fate

The LTV:CAC Ratio: The One Number That Decides Your Startup's Fate

Ask a founder their CAC and you'll get a number. Ask for their LTV:CAC ratio and you'll get a blank stare — which is strange, because that ratio is the number investors, acquirers, and good operators actually use to judge whether a business works. CAC alone is trivia. The ratio is the verdict.

What the ratio means

LTV:CAC = Customer Lifetime Value ÷ Customer Acquisition Cost

It answers: for every dollar I spend acquiring a customer, how many dollars do I get back over their lifetime?

  • Below 1:1 — you're lighting money on fire. Each customer costs more than they return.
  • 1:1 to 3:1 — surviving, but fragile. There's no margin for churn spikes or rising ad costs.
  • 3:1 — the widely cited healthy benchmark for SaaS. Room to grow, absorb shocks, and reinvest.
  • Above 5:1 — you might be under-spending. Growth is being left on the table; competitors will take it.

The ratio forces honesty because it combines both sides of the business: how efficiently you acquire (CAC) and how well you retain and monetize (LTV).

Computing LTV without fooling yourself

Most bad ratios come from inflated LTV. The clean formula:

LTV = (Average revenue per account per month × Gross margin %) ÷ Monthly churn rate

Example — a B2B SaaS:

  • ARPA: $120/month
  • Gross margin: 80%
  • Monthly churn: 4%
  • LTV = (120 × 0.80) ÷ 0.04 = $2,400

Now CAC. The honest version includes everything that touches acquisition:

CAC = (Sales + marketing salaries + ad spend + tools + overhead) ÷ New customers acquired

Say that totals $45,000 in a quarter for 75 new customers: CAC = $600.

LTV:CAC = 2400 ÷ 600 = 4:1. Healthy — with room to spend more aggressively on growth.

The three ways founders inflate the ratio

  1. Ignoring churn in LTV. Using "average customer lifespan: 3 years (assumed)" instead of measured churn. If your monthly churn is 6%, your real average lifespan is ~16 months, not 36. Measure, don't assume.
  2. Excluding salaries from CAC. Ad spend alone isn't CAC. If two salespeople cost $16k/month fully loaded, that belongs in the numerator. Fully-loaded CAC is often 2–3× the ad-only number.
  3. Mixing cohorts. Blending enterprise deals (high LTV, high CAC) with self-serve signups (low LTV, low CAC) produces a meaningless average. Compute the ratio per segment — you'll often find one segment subsidizing a broken one.

The payback period: the ratio's impatient sibling

The ratio tells you if the math works. The payback period tells you when you see the money:

CAC payback = CAC ÷ (ARPA × Gross margin %)

With our numbers: 600 ÷ (120 × 0.80) = 6.25 months. Under 12 months is generally fine for SaaS; over 18 months means you're financing your customers' growth with your own cash — dangerous without deep funding.

A 4:1 ratio with a 20-month payback is a business that works on paper and dies in practice. Watch both.

What to do with your number

  • Ratio < 3:1: fix retention and pricing before spending another dollar on acquisition. Raising prices 10% with no churn change lifts LTV — and the ratio — immediately.
  • Ratio 3–5:1: you have a growth engine. Scale the channels that produce it, and monitor the ratio monthly — it degrades as you exhaust the best channels.
  • Ratio > 5:1: spend more. Hire the salesperson, double the ad budget, test the expensive channel. Under-investment at this ratio is the most common scaling mistake I see.

Run your own numbers with an LTV and CAC calculator — plug in ARPA, margin, churn, and acquisition spend, and see your ratio and payback period with the full working shown. WebChatKit has 520+ free calculators for business and finance math, each showing its formula step by step.

Hammad Ali builds WebChatKit Calculators — 520+ free calculators for business, finance, and logistics math, every one showing its formula and step-by-step working.

Top comments (0)