LTV:CAC Ratio Calculator for SaaS: Unit Economics & 3:1 Benchmark

If your LTV is not at least 3x your CAC, you are subsidizing users who will never be profitable.

  • Instant result
  • No sign-up
  • Visible assumptions
  • Deterministic calculation

In 30 seconds: Simulate the balance between CAC and LTV under different retention rates, ARPU, and acquisition costs per channel. Deterministic calculation with auditable formulas. The result is indicative — adjust the assumptions to reflect your real operation.

Mobile apps have low CAC in absolute value but also low ARPU, which compresses the margin for error. This calculator gives CAC, payback and Magic Number — if your payback exceeds 6 months with high churn, you're likely burning capital without building a base.

Methodology

CAC = S&M spend in period ÷ New customers acquired

Contribution per customer/month = ARPU × Gross margin

Payback (months) = CAC ÷ Monthly contribution

Magic Number = (Quarterly ΔMRR × 4) ÷ Quarterly S&M spend

Variables

S&M Spend
Total sales and marketing investment in the period (ads, team, tools, agencies).
New Customers
Paying customers acquired in the same period.
ARPU
Average monthly revenue per customer.
Gross Margin
% of ARPU available after direct service costs.
Current / Prior MRR (optional)
Current and prior quarter MRR for the SaaS Magic Number.

Practical example

Freemium productivity app for LatAm: $80,000 monthly marketing spend (Meta + TikTok + Apple Search Ads), 800 new paid subscribers per month, ARPU $12/month (premium subscription), 70% gross margin (server, Apple/Google fee 30%, support).

CAC = $80,000 ÷ 800 = $100 per paid customer. Monthly contribution = $12 × 0.70 = $8.40.

CAC payback = $100 ÷ $8.40 = 11.9 months. In consumer apps this payback sits at the upper edge — only healthy if churn < 5% monthly.

If churn is 8% (typical for mid-market consumer apps): month 12 retention = 0.92^12 = 37%. Only 37% of the cohort is still paying at the theoretical payback point. Real LTV = $8.40 ÷ 0.08 = $105 → LTV:CAC ratio = 1.05x, barely profitable model.

Optimized scenario: if you cut CAC to $60 (better creative testing, better lookalike targeting) and lift ARPU to $15 (annual prepay with net-positive 20% discount): payback drops to $60 ÷ ($15 × 0.70) = 5.7 months. LTV:CAC with 8% churn rises to 2.2x.

Operating recommendation: in consumer apps, the primary dial is CAC, not ARPU. Every $20 USD shaved off CAC equals 2-3 extra margin points without touching product. Before scaling spend, audit your Meta/TikTok funnel: install → activation → first purchase. The biggest drop is almost always between install and activation (60-75% drop), and is closed by onboarding with no opt-out until the first 'aha moment'.

Interpretation

CAC payback under 12 months is excellent for B2B SaaS; 12-18 months is acceptable; above 24 months is usually unsustainable unless there is significant expansion revenue.

Magic Number above 1.0 indicates high efficiency: each dollar of S&M generates more than a dollar of new ARR over 12 months. 0.5-1.0 is healthy; below 0.5 suggests inefficiency or channel saturation.

Short payback with low magic number can indicate high ARPU but stalled growth.

Long payback with high magic number suggests valuable customers but rising acquisition costs — watch for channel saturation.

Assumptions and limitations

  • Assumes the cohort acquired in the period reflects average behavior (no bias from atypical campaigns).
  • Does not discount the flow to present value: payback is nominal, not NPV.
  • Magic Number assumes the quarter's ΔMRR is attributable to that quarter's S&M spend (no multi-month lag).
  • Does not distinguish between new customers and expansion: if the mix shifts, CAC can look better than it is.

When to use this calculator

  • Every month-end to catch early deterioration in acquisition efficiency.

  • Before raising ad budget: if payback already exceeds 18 months, scaling will worsen cash flow.

  • When comparing channels: blended CAC hides large differences between Google Ads, paid social, outbound and referrals.

  • For board or investor reports: payback and Magic Number are standard SaaS metrics.

  • When the growth team requests a budget increase: Magic Number quantifies how much ARR each marginal dollar generates.

Common mistakes

  • Calculating CAC only with ad spend, omitting go-to-market team salaries and tooling. Fully-loaded CAC is usually 1.5-2× the ads-only blended CAC.

  • Mixing new customers with expansion: if your 180 'new' customers include upgrades, your real CAC is worse.

  • Not adjusting for seasonality: Q4 tends to have artificially good payback due to annual purchases.

  • Comparing Magic Number between companies with different models (B2C vs B2B enterprise) — healthy ranges differ.

Industry use cases

Freemium consumer app

CAC $0.50-3 per install, payer conversion 1-3%. Effective CAC $20-150. Reasonable payback 3-9 months if ARPU is $5-15/month.

Premium subscription app

CAC $30-80, ARPU $10-25/month. Payback 4-8 months with 5-10% churn. Magic Number > 0.7 means room to scale UA.

Fintech / wallet app

High CAC ($100-300) due to compliance and onboarding, but multi-year LTV once activated. Payback of 12-18 months is acceptable.

Gaming app

Highly variable CAC ($1-10) by genre. IAP model requires measuring LTV on payer cohorts, not total users.

Methodology and assumptions

How results are calculated, what we assume when modeling, and where the method loses precision.

Formula

CAC = S&M spend ÷ New customers · Payback = CAC ÷ (ARPU × Gross margin)

Assumptions

  • All customers in the period are attributable to that period's spend.
  • Stable monthly contribution throughout the payback window.
  • ΔMRR for Magic Number is net MRR (includes expansion and churn).

Applicability limits

  • Multi-touch attribution is not solved here — use MMM or lift testing for reallocation decisions.
  • Payback for long-cycle channels (B2B enterprise) requires keeping cohorts visible 12+ months.
  • Magic Number compares quarters: with fewer than 4 quarters of history the reading is noisy.

Sources

You know your CAC and payback. Now find the price that improves your LTV:CAC without losing volume. Pricing Simulator

Want to go beyond the quick calculation?

Sign up to access advanced simulators with multiple scenarios, data export, and detailed projections.

No spam. Just early access to the ltv/cac ratio for saas simulator.

Complete guide

What the LTV:CAC ratio measures in a mobile app

LTV:CAC for mobile apps compares the discounted value a user contributes across the app relationship against the total cost of acquiring them. The reading is not the same as in B2B SaaS: in mobile, the retention curve drops very fast in D1-D7, monthly ARPU is usually low, and CAC varies 3x-5x across channels by bid and vertical. That is why the ratio loses meaning if it is not computed with the real retention curve and with CAC segmented by source.

Formulas that work in mobile

The simple version — LTV = ARPU × gross margin / monthly churn — underestimates value when the app has cohorts with long retention (subscription apps, fitness, finance). The actionable version decomposes LTV as:

  • Net LTV = ARPPU × (cumulative 12-month payers) × gross margin − platform costs (Apple/Google 15%-30%).
  • CAC by channel = spend on that channel ÷ attributed installs that were still active at D30.
  • Payback period = CAC ÷ (monthly ARPU × gross margin). Under 12 months is healthy; under 6 months is excellent.

Why flat monthly churn misleads

Typical mobile apps lose 75%+ of users by D7 and 95%+ by D30 (AppsFlyer 2024). If you apply a flat 20% monthly churn you are assuming linearity where there is exponential decay. Real retention is modeled with the D1/D7/D30 curve and extrapolated with a power function — not with constant churn — to approximate mature cohort behavior.

CAC broken down by channel

Apple Search Ads, Meta UAC, Google App Campaigns and TikTok Ads have very different profiles. ASA wins on intent (CR 67% in 2024, SplitMetrics) but caps volume; Meta and Google UAC scale better but with more volatile CAC after iOS 14.5 and the SKAdNetwork era. A blended CAC hides that one channel subsidizes another: that is why the simulator lets you input CAC by channel and see which source has the best real ratio and payback.

When your unit economics do not work

Ratio 2:1 with payback >18 months and runway <12 months is a red flag: every dollar spent on UA drains cash with no return before you run out of runway. The answer is almost never to cut CAC proportionally — the best channels are already optimized — but to raise ARPU via a more aggressive paywall, annual bundles or hybrid monetization (IAP + ads).

How a growth manager uses this calculator

Enter ARPU, margin, D1/D7/D30 curve and CAC by channel. Get projected 12- and 24-month LTV, LTV:CAC ratio by source, payback period and a per-channel break-even line. The output tells you which channel to cut, which to double and where to raise paywall before committing runway.

Cohort analysis: the only honest LTV

Aggregate LTV is a lagging illusion; the real shape lives in the cohort. Extract installs by acquisition week, track revenue and retention at D7/D30/D60/D90/D180 and plot cumulative ARPU by cohort. You will see three things a blended number hides: whether new cohorts monetize better or worse than previous ones (product-market fit direction), which channels deliver cohorts with durable tail vs fast decay, and when a seasonal spike inflated an average that is no longer representative. If your dashboard still only shows blended LTV and blended CAC, your UA team is optimizing on an average that contains two or three regimes glued together.

Benchmarks by vertical

Segwise's gaming-vertical breakdown works as a sanity check: simulation games LTV $0.50-$1.20, puzzle $1.00-$2.50, action $2.00-$5.00, hypercasual $0.10-$0.35. Subscription apps live on a different curve: Adapty 2024 reports iOS subscription apps averaging ~$8.39 D90 ARPU vs $1.54 on Android — a 5.4x spread driven by willingness-to-pay and the share of organic installs. For a subscription app, blended LTV of $15-25 with CAC of $4-8 is typical in healthy categories (meditation, fitness, finance).

Common mistakes that break the math

  1. Using gross revenue instead of net: Apple and Google take 15%-30%. Skipping it inflates LTV and makes a 2:1 ratio look like 2.5:1.
  2. Mixing paid and organic in CAC: organic installs have cost (brand, content, ASO) but should not load onto paid CAC. Report paid and blended CAC separately.
  3. Forgetting gross margin: ARPU × lifetime is not LTV; ARPU × lifetime × gross margin is. In subscription apps with platform fees the typical margin is 60%-75%, not 80%-90% as in pure SaaS.
  4. Projecting LTV on incomplete cohorts: a 30-day cohort cannot tell you 12-month LTV without a curve-fitting model. Always label your LTV with the observation window (D90 LTV, D180 LTV, pLTV-projected 12m).
  5. Confusing payback with LTV:CAC ratio: a 4:1 ratio with 24-month payback can still be lethal if your runway is 14 months — you run out of cash before the math closes. Always read both numbers together and pair them with cash-on-hand.

Privacy-first attribution: the post-iOS 14.5 reality

Apple's App Tracking Transparency (ATT) framework (released iOS 14.5, April 2021) and the deprecation of IDFA for user-level tracking fundamentally changed mobile attribution. In 2026, the UA manager operates in a world where:

  • SKAdNetwork (SKAN 4) provides deterministic but delayed conversion reporting with limited dimensionality — you know a campaign drove installs, but you cannot always attribute to which specific creative, audience, or targeting.
  • Modeled attribution (Meta Advantage+ SKAN, Google Privacy Sandbox) fills the IDFA gap with statistical inference, not user-level data.
  • Apple Search Ads retains user-level data within Apple's own ecosystem (no IDFA required for ASA targeting), which is why ASA conversion rates (67% in 2024 per SplitMetrics) remain exceptionally high — it targets based on App Store signals, not cross-app tracking.

Implication for LTV:CAC analysis: pre-ATT CAC data from 2020–2021 is not comparable to post-ATT data from 2023–2026. If you are modeling a cohort that spans this period, the apparent improvement in CAC may reflect attribution loss (fewer installs being credited to paid, inflating organic attribution) rather than genuine channel efficiency.

Retention benchmarks by vertical (2026)

D30 retention is the most cited cohort metric in mobile because it filters out the long tail of bounced installs and represents a user who has had time to experience the core product loop. AppsFlyer State of App Monetization 2024 benchmarks:

  • Gaming (casual/puzzle): D1 35–45%, D7 15–22%, D30 6–10%.
  • Gaming (mid-core/strategy): D1 30–40%, D7 12–18%, D30 5–8%.
  • Health and fitness: D1 25–35%, D7 12–18%, D30 8–14%.
  • Fintech / personal finance: D1 40–55%, D7 25–35%, D30 15–25%.
  • Social and messaging: D1 60–75%, D7 40–55%, D30 25–40%.

Fintech apps retain meaningfully better because financial utility is daily and the switching cost (re-entering bank accounts, learning a new interface) is real. A fintech app at D30 20% vs a casual game at D30 7% will produce 3–4× the LTV on the same install, which justifies 2–3× higher CAC tolerance.

The viral coefficient and organic flywheel

Many LTV:CAC models ignore the viral coefficient (K-factor): the number of new users each existing user generates through referrals, social sharing, and word of mouth. If K = 0.3, each paid install generates 0.3 organic installs on top; effective CAC = paid CAC ÷ (1 + K) = CAC ÷ 1.3 — a 23% reduction in effective acquisition cost.

Apps with strong referral programs (Robinhood's free stock referral, Cash App's $5 send referral, Duolingo's streak-share mechanic) achieve K-factors of 0.4–0.8, effectively cutting blended CAC in half while organic channels scale. The implication for LTV:CAC is material: a 3:1 ratio on paid-only basis can become 5:1 or 6:1 when organic flywheel effects are included. Apps that grow from word-of-mouth and content (TikTok virality, Reddit communities, influencer review) can sustain unit economics that appear impossible on a purely paid basis.

Worked example: fintech app, $48 CAC vs $145 LTV (3.0:1)

Nómada Capital (fictitious name, representative data) is a personal finance app targeting freelancers and self-employed workers in Mexico and Colombia. Monthly subscription: MXN 99 / COP 12,000 (approximately USD 5.80/month blended). Apple/Google fee: 15% (small business rate). Gross margin on subscription revenue: 72%.

Retention curve (D-day → retention): D1 58%, D7 38%, D30 22%, D90 14%, D180 10%, D365 7%.

LTV calculation (12-month cohort):

  • Average active months per user: integral of retention curve ≈ 5.8 months.
  • Net ARPU: USD 5.80 × 85% (after platform fee) × 72% (gross margin) = USD 3.54/month.
  • LTV (12m): 5.8 × USD 3.54 = USD 20.50 (12-month observable window).
  • Projected LTV (24m with power-law extrapolation): USD 32.80.
  • Blended CAC (ASA 40% budget + Meta 40% + organic 20%): USD 48.
  • Effective LTV:CAC ratio (24m pLTV): USD 32.80 ÷ USD 48 = 0.68:1 — loss on every install.

Diagnosis: the subscription price (USD 5.80) is too low for the CAC the channels require. Action: annual plan at USD 49.99/year (USD 4.17/month) with 14-day free trial, reducing churn friction and improving LTV to USD 145 projected (paid upfront at 72% margin = USD 36 net, with 85% year-1 retention on annual plan). Blended CAC stays USD 48. Ratio: 3.0:1 with 16-month payback on annual cohort.

How to read the result alongside cash runway

Healthy unit economics on paper are not enough if the business does not survive long enough to harvest them. A practical heuristic: payback period must be shorter than (current runway − 6 safety months). With 12 months of runway, only channels paying back in under 6 months should receive incremental UA budget; the rest go on hold until you raise, hit cash-flow positive, or reduce burn. The simulator surfaces this constraint by combining the LTV:CAC view with a runway view, so growth, finance and product can decide together rather than each defending their own dashboard.

Illustrative case

Composite case for instructional purposes: combines sector dynamics with realistic figures. Names are fictional and do not represent a specific company.

Nómada Fit (fictional name, realistic data) launched its workout app in Q2 2025 with $1.8M USD seed investment and $95k monthly burn. At 6 months they had 42,000 installs but the CFO did not know whether the unit economics worked. Blended CAC showed $6.40 and monthly ARPU $3.20, with 70% gross margin after Apple and Google fees. The simple model gave them an LTV of $11.20 and an LTV:CAC ratio of 1.75x — red zone.

Breaking it down by channel they saw ASA generated users with 8.2% D30 retention and $4.10 CAC, while Meta UAC got D30 2.9% at $5.80 CAC and TikTok Ads dropped to D30 1.4% with $9.70 CAC. The blended was lying: TikTok was being subsidized by ASA.

They cut TikTok Ads, redirected 40% of budget to ASA and launched an annual paywall ($49.99 with 7-day free trial) that lifted ARPPU from $8 to $14.50. Three months later the weighted CAC dropped to $5.10, net LTV reached $18.40 and the ratio rose to 3.6:1. Payback dropped from 28 months to 11 months, right before closing Series A. The lead investor asked to see the D1/D7/D30 curve by cohort — the model already had it ready. Series A closed at $26M valuation (vs $18M from a competing term sheet) citing explicitly per-channel unit economics discipline as the decision rationale. The CMO who had pushed TikTok was reassigned to creative strategy; the growth lead who had run the numbers ended up as VP of Growth post-round.

From theory to calculation

The calculator on this page runs with your numbers — no forms, no login. Scroll up and try it.

Try the calculator

Sector reference ranges

Indicative ranges based on public sector literature and operational observation. Your business may differ — use the numbers as a starting point, not as a target.

MetricValueSource
D30 retention — iOS (global average)4.1%AppsFlyer State of App Monetization 2024
D30 retention — Android (global average)2.6%AppsFlyer State of App Monetization 2024
ARPU at D90 — subscription apps iOS vs Android$8.39 vs $1.54 (5.4x)AppsFlyer State of App Monetization 2024
Apple Search Ads average CPA 2024$2.90 (vs $2.58 in 2023)SplitMetrics Apple Ads Benchmarks Report 2024
Apple Search Ads — Sports category CPA$14.10 (vs $3.73 in 2023)SplitMetrics 2024
Apple Search Ads conversion rate 202467.2%SplitMetrics 2024
Healthy LTV:CAC ratio — industry standard≥ 3:1 (>5:1 may indicate under-investment)Wall Street Prep / a16z / Bessemer consensus
Hypercasual ARPU at D90 — hybrid vs IAA-only$0.60 vs $0.47 (+28%)AppsFlyer 2024

Frequently asked questions

1What is a good LTV:CAC ratio for a mobile app?
3:1 is the industry standard; below 1:1 the app burns cash on every install and above 5:1 you are usually under-investing in acquisition. For freemium subscription apps the real target is 3:1 with payback under 12 months.
2How is LTV calculated in a mobile app?
LTV = ARPU × gross margin × lifetime, where lifetime is approximated by the real retention curve (D1/D7/D30/D90) and not by flat monthly churn. For subscription apps: ARPPU × cumulative payers × margin − 15%-30% platform fee.
3What is payback period and how is it calculated?
It is the number of months to recover CAC from monthly gross margin per user. Formula: CAC ÷ (ARPU × gross margin). Under 12 months is healthy, under 6 months is excellent for mobile.
4How do I calculate CAC by acquisition channel?
Divide each channel's spend (ASA, Meta UAC, Google App Campaigns, TikTok) by attributed users still active at D30. Using blended CAC hides that a good channel subsidizes a bad one.
5What is the difference between LTV and ARPU?
ARPU is average revenue per user over a period (usually monthly). LTV integrates ARPU × margin × expected lifetime, so it captures retention. ARPU is a snapshot; LTV is the full movie.
6How does retention affect LTV?
Retention is the most sensitive LTV multiplier. Raising D30 from 3% to 5% can double net LTV because it lengthens the entire curve, not just shifts one point.
7Should I use gross or net revenue to calculate LTV?
Net. For subscription or IAP apps you must subtract the 15%-30% Apple and Google fee before multiplying by gross margin. Using gross revenue inflates LTV artificially and leads to wrong UA decisions.
8What is predictive LTV (pLTV) and when to use it?
pLTV estimates the LTV of a new user with models that project cohort behavior from early signals (D1, D3, D7). It is useful after iOS 14.5 and SKAdNetwork, when you cannot wait 90 days to optimize UA campaigns.

Tools from the same topical cluster. Use them together to close the loop on your analysis.

Last updated: April 30, 2026 · Reviewed by the Simúlalo editorial team. Figures and benchmarks are indicative; verify with your own data before deciding.

View methodology