LTV > CPI in Plain Language: A developer’s guide to payback math

You’ve shipped your app. Downloads are trickling in. Someone mentions “paid UA” and suddenly you’re drowning in acronyms: CPI, LTV, ROAS, ARPU, cohorts, payback windows. The jargon creates paralysis—you can’t decide if spending $500 or $5,000 on ads makes sense, so you spend nothing and growth stalls.

This guide strips away the noise. We’ll define the four metrics that matter, show you back-of-the-napkin LTV math you can do in five minutes, and give you safety rails so you don’t burn money on users who’ll never pay back their acquisition cost.

The four numbers you actually need

CPI (Cost Per Install): What you pay to acquire one user. If you spend $220 on a Facebook campaign and get 100 installs, your CPI is $2.20.

ARPU (Average Revenue Per User): Total revenue divided by total users in a cohort. If 100 Day-0 users generate $150 by Day 30, your D30 ARPU is $1.50.

LTV (Lifetime Value): The total revenue you expect from a user over their entire lifespan. In practice, you’ll estimate this by multiplying early ARPU by a retention tail factor (more on that below).

Payback window: How many days until the revenue from a cohort covers its acquisition cost. Industry benchmark: aim for payback within 180 days. Subscription apps often hit it by Day 60–90; ad-monetized apps may take longer but should show clear trajectory by Day 30.

Back-of-the-napkin LTV: the tail factor shortcut

Waiting 365 days to calculate true LTV kills momentum. Instead, use this rough formula:

LTV ≈ D30 ARPU × Tail Factor

The tail factor estimates how much additional revenue trickles in after Day 30 based on retention. Here’s a quick lookup:

• D7 retention 20–30%: Tail factor ~1.3–1.5 (weak retention, revenue drops fast)
• D7 retention 30–45%: Tail factor ~1.5–1.8 (decent retention)
• D7 retention 45%+: Tail factor ~1.8–2.2 (strong retention, long tail)

Example: Your app has D30 ARPU of $1.50 and D7 retention of 35%. Use tail factor 1.6. Estimated LTV = $1.50 × 1.6 = $2.40.

The golden rule: LTV / CPI ≥ 1.5–2.0 for early tests

Once you have estimated LTV, divide it by CPI. This ratio tells you if paid acquisition makes economic sense:

• LTV / CPI < 1.0: You’re losing money on every user. Stop immediately.
• LTV / CPI = 1.0–1.5: Breakeven to thin margin. Risky—any drop in retention or monetization puts you underwater.
• LTV / CPI = 1.5–2.0: Healthy buffer. Room for optimization experiments.
• LTV / CPI > 2.0: Strong unit economics. Scale aggressively and reinvest.

Why the 1.5–2.0 cushion? Three reasons:

1. Estimation error: Your tail factor is a guess. Retention might degrade as you scale to broader audiences.
2. Platform fees: App stores take 15–30%. Payment processing adds another 2–3%. Your net revenue is lower than gross.
3. Operational costs: Server hosting, support, product iteration. These eat into margin.

Worked example: when the math is borderline

You’re testing Instagram ads for a productivity app. After one week:

• Spend: $440
• Installs: 200
• CPI: $2.20
• D7 retention: 32%
• D30 ARPU: $1.50 (mostly trial starts + a few conversions)

Step 1 – Estimate LTV:
D7 retention 32% → tail factor ~1.6
LTV = $1.50 × 1.6 = $2.40

Step 2 – Calculate ratio:
LTV / CPI = $2.40 / $2.20 = 1.09

Verdict: Borderline. You’re barely above breakeven. Before scaling, ask:

• Can you improve retention? A 2pp boost in D7 (32% → 34%) lifts tail factor to ~1.65, pushing LTV to $2.48 and ratio to 1.13. Still tight, but trending better.
• Can you lower CPI? Better creatives or targeting might drop CPI to $2.00. Ratio jumps to 1.20.
• Can you increase ARPU? Adjust paywall placement or trial length. Lifting D30 ARPU to $1.70 gives LTV $2.72, ratio 1.24.

What to adjust first: Retention has the biggest leverage because it affects both ARPU (more days = more monetization chances) and the tail factor. Fix onboarding, clarify value in the first session, and reduce friction before the Day 7 drop-off.

Sensitivity check: what if retention drops?

The scariest part of scaling paid UA is that retention often degrades as you move from early adopters to mass market. Run this quick test:

If D7 retention drops 2 percentage points (e.g., 32% → 30%), your tail factor might fall from 1.6 to 1.5. New LTV: $1.50 × 1.5 = $2.25. New ratio: $2.25 / $2.20 = 1.02. You’re now breakeven.

Safety protocol: Before scaling beyond $1,000/day, cohort your users by acquisition week. If you see retention slipping, pause and diagnose. Cheaper users who churn fast destroy unit economics.

Your LTV/CPI calculator template

Here’s a simple spreadsheet structure to track your math. Make a copy and plug in your numbers weekly:

Add sliders for:

• D1 retention (to model first-day drop-off)
• D7 retention (to auto-update tail factor)
• D30 ARPU (to test pricing/paywall changes)
• CPI (to evaluate creative/targeting experiments)

This lets you answer “what if” questions in seconds: What if I cut CPI by $0.30? What if retention improves 3pp? What if I raise subscription price 20%?

Decision tree: when to spend, when to wait

If LTV / CPI ≥ 2.0: Scale. Increase daily budget 20–30% per week while monitoring retention cohorts. Reinvest profit into creative testing and new channels.

If LTV / CPI = 1.5–2.0: Cautious scale. Run small tests ($50–100/day) across 2–3 creatives and audiences. Track payback weekly. Optimize onboarding and monetization in parallel.

If LTV / CPI = 1.2–1.5: Hold. Don’t scale yet. Focus on product improvements: better onboarding (lift D1/D7), clearer value props (lift conversion), reduced friction (lift ARPU). Retest ads in 2–4 weeks.

If LTV / CPI < 1.2: Stop paid UA. You’re subsidizing users who won’t pay back. Either fix core retention/monetization or consider whether the market fit exists. Organic growth and word-of-mouth are your only safe paths until unit economics improve.

Alternatives when the math works but you lack capital or ops bandwidth

Your LTV/CPI ratio is 1.8. The math checks out. But you’re a solo developer or small team, and you face two blockers:

1. Capital: Scaling to $500–1,000/day means fronting $15K–30K per month before revenue comes back. You don’t have that runway.
2. Operations: Managing campaigns, creative iteration, cohort analysis, ASO, and localization is a full-time job. You need to keep shipping product updates.

Option A – DIY on a shoestring: Start with $10–20/day. Use that to validate one creative and one audience. Scale only when you see consistent 7-day payback. Slow, but capital-efficient.

Option B – Hire a contractor/agency: Pay a freelancer or growth agency $2K–5K/month to run campaigns. You still front the ad spend. Works if you have capital but not time. Watch for misaligned incentives—they get paid regardless of ROAS.

Option C – Partner with a publisher: A publisher fronts UA budget, handles ASO/creative/analytics, and splits revenue with you. You keep building; they run growth. Best fit when you have strong product but zero growth capital. Trade-off: you share upside, but you also share risk and get immediate scale.

How publisher partnerships typically work: You retain IP and code ownership. The publisher gets publishing rights (App Store/Play listings, paid UA, monetization optimization). Revenue splits range from 50/50 to 70/30 depending on who covers what (e.g., if you handle all updates vs. if the publisher has a product team). Contracts are short (1–2 pages), with clear SLAs on communication, release cadence, and data access. You get weekly reports on spend, CPI, retention, and LTV. If the app doesn’t hit target payback windows within 60–90 days, both sides can walk away cleanly.

Checklist: before you spend your first dollar on UA

• ☐ Track installs by source (UTM parameters, MMP like Adjust/AppsFlyer, or at minimum iOS/Android campaign IDs)
• ☐ Instrument revenue events (subscriptions, IAP, ad impressions) tied to cohort date
• ☐ Calculate D1, D7, D30 retention for at least 100 organic users as baseline
• ☐ Estimate D30 ARPU and tail factor using the lookup table above
• ☐ Set target CPI based on LTV / CPI ≥ 1.5 safety threshold
• ☐ Prepare 3–5 ad creatives (video + static) and 2–3 audience segments
• ☐ Define kill switch: if LTV / CPI drops below 1.2 for two consecutive weeks, pause and diagnose
• ☐ Schedule weekly cohort reviews: compare new paid cohorts to organic baseline on retention and ARPU

When to revisit your LTV model

Recalculate every time you:

• Change pricing or paywall (affects ARPU)
• Launch a major feature (can lift or hurt retention)
• Expand to a new audience or geography (different behavior, different LTV)
• See retention drift (2pp+ change up or down over two weeks)
• Scale budget significantly (e.g., $100/day → $500/day; broader targeting often means lower intent users)

Set a calendar reminder every 30 days to re-run the numbers. LTV is not static.

Key takeaway: margin of safety beats precision

You don’t need perfect LTV calculations. You need a rough, reliable model that keeps you out of trouble. The 1.5–2.0 ratio rule gives you buffer against estimation error, retention decay, and hidden costs. If your numbers are close to that threshold, invest in product improvements before scaling ads. If you’re well above it, you have a growth engine—now the question is capital and operational capacity.

The math is simple. The discipline is hard. Run the numbers weekly, cohort your users, and never scale into negative unit economics hoping it’ll fix itself later. It won’t.

Questions about partnership structures, revenue share models, or how TorApps evaluates apps for publishing? Check our Open Call page or reach out directly.