A mobile game soft launch is a process, not a KPI dashboard. Most studios obsess over the metrics — D1, D7, ARPDAU, ROAS — and miss the harder question: what decision are you trying to make, and what evidence will let you make it? Having managed 50+ launches at Gameloft, SFR and Blacknut across mobile and cloud gaming, I have watched well-instrumented teams burn $200K of UA on a soft launch and still ship a doomed game, because they never agreed on the go / extend / kill thresholds before opening the test. This guide is the playbook that fixes that — market selection, iteration cycles, weekly decision rituals, and the explicit criteria for extending, scaling, pivoting or killing. (For the underlying KPI targets — D1/D7/D30, ARPDAU, conversion — see our companion guide on mobile game KPIs and benchmarks.)
The Soft Launch Decision Framework
A soft launch exists to answer four binary questions, in this order:
- Does the core loop retain? Is D1 above the genre threshold without paid acquisition driving artificial early retention?
- Does retention compound? Does D7/D30 hold the curve, or does the game leak players faster than competitors?
- Does it monetize? Once retention is proven, do payer conversion and ARPDAU clear the breakeven LTV needed for your CPI?
- Does it scale? When you push 3-5x the daily UA spend, do unit economics survive?
Treating each phase as a separate decision — not a continuous “are we ready?” — is the single biggest discipline gap I see in the field. Each question gets a phase, a budget, and an explicit go / extend / kill threshold agreed before data is collected.
What a Soft Launch is For (and What it is Not)
A soft launch is a limited, controlled release in select markets, and its only job is to convert the four questions above into a defensible go-global decision. It is not a marketing campaign, not a slow ramp to global, and not a place to validate creative strategy at scale (that is a UA discovery phase, run separately).
The mobile gaming market ships ~500K titles a year on the App Store and Google Play. The reason most fail is rarely the build quality — it is that the team never agreed on the kill criteria before launch, so every weak signal got rationalized away.
Choosing Your Soft Launch Markets
Market selection is critical. You want markets that:
- Low CPI — Affordable user acquisition
- English-speaking — Easier localization
- Representative behavior — Players similar to your target market
- Decent infrastructure — Low latency, stable connections
Recommended Markets
| Market | CPI Range | Pros | Cons |
|---|---|---|---|
| Canada | $1-3 | Similar to US, English | Smaller scale |
| Australia | $2-4 | High quality users | Small population |
| Philippines | $0.30-1 | Very low CPI, English | Lower LTV |
| New Zealand | $2-4 | Quality users | Very small |
Avoid initially: US, Japan, South Korea, China. These markets have high competition and expensive CPIs that can burn your budget quickly. For a detailed breakdown of CPI by region and genre, check our 2026 UA cost benchmarks.
Diagnostic Thresholds (the kill / continue signals)
The full target benchmarks live in our mobile game KPI guide — what matters in soft launch is the diagnostic threshold below which you stop and fix, not the target you aspire to.
| Phase | Diagnostic floor | If you hit it… |
|---|---|---|
| Phase 1 — core loop | D1 below 30% (any genre) | Stop. Onboarding or first-session loop is broken. Do not pay to acquire more users. |
| Phase 2 — retention curve | D7 below 12% or D30 below 4% | Stop scaling. Deepen meta layer / progression. Reassess after 2-4 weeks of iteration. |
| Phase 3 — monetization | Payer conversion below 1.5% by D14 | Diagnose offer placement and pricing before adding monetization layers. |
| Phase 4 — scale test | CPI rises >40% when daily spend triples | Channel saturated. Validate next channel before global commit. |
These are floors, not targets. The genre-specific targets (D1 40%+ casual, ARPDAU $0.15-0.50 hybrid, etc.) belong in the KPI dashboard, not in the kill-criteria document. For tuning levers once you are below the floor, see our retention strategies guide; for hybrid casual specifics, the hybrid casual playbook covers meta-layer design that moves D7 and D30. Monetization tuning sits in the F2P monetization models comparison.
Iteration Cycles: How a Soft Launch Actually Runs
A soft launch is a sequence of weekly iteration cycles, each tied to one of the four decision questions. Each cycle has a build, a test, a review, and a decision — and the decision is binary: continue, extend (one more cycle to confirm), or kill.
Cycle 1-2: Technical Validation (decision: ship to UA, yes/no)
- Deploy to test markets, monitor crash rate (<1%), loading times, device coverage
- Fix critical bugs before spending UA dollars on broken builds
- Decision gate: stability is non-negotiable. No paid traffic until crash rate clears.
Cycle 3-4: Core Loop Validation (decision: D1 floor met?)
- Analyze D1 retention by cohort, channel, and ad creative
- Diagnose onboarding friction at session 1, 2, 3
- Begin A/B testing onboarding variants
- Decision gate: D1 below 30% triggers a stop-and-fix cycle, not a “let’s see if it improves with more data”
Cycle 5-8: Retention & Monetization Layering (decision: LTV economics defensible?)
- Iterate on D7/D30 retention; add or rebalance meta layers if D7 leaks
- Layer monetization events only once retention is stable
- Optimize UA targeting and creative; validate cohort LTV against blended CPI
- Decision gate: payer conversion above 1.5% by D14, ARPDAU clearing breakeven LTV at expected CPI
Cycle 9-12: Scale Test & Pre-Global (decision: green-light global?)
- Triple daily UA spend in one market; verify CPI does not blow up by more than 40%
- Lock the global launch strategy and the first 90 days of LiveOps calendar
- Final polish, localization, and store-listing optimization
- Decision gate: all four questions answered yes; global commit signed off by leadership
Common Soft Launch Mistakes
1. Launching in the Wrong Markets
Starting in the US or Japan burns budget fast. CPI can be 3-5x higher than Canada or Philippines.
2. Ignoring Early Retention Data
If D1 retention is 25%, don’t hope it will improve. Stop, analyze, and fix the fundamental issues.
3. Rushing to Monetization
Focus on retention first. A game with 50% D1 and weak monetization can be fixed. A game with 20% D1 and great monetization will fail.
4. Not Iterating Fast Enough
Soft launch is about rapid iteration. Ship updates weekly, not monthly. Every week of stagnation is wasted learning.
The Go / Extend / Kill Decision Matrix
Not every game should go global. The hardest discipline in soft launch is making the kill call early enough to preserve runway for the next bet. Use this matrix in the weekly decision review:
| Signal | Go | Extend (one more cycle) | Kill / Pivot |
|---|---|---|---|
| D1 retention | At or above target by Cycle 4 | Within 5 points of target, trending up | Stuck below 25% after 6+ cycles |
| D7 retention | Above genre threshold | Below threshold but improving with build iterations | Flat or declining despite 2+ build iterations |
| Payer conversion (D14) | Above 1.5% with healthy ARPPU | Below floor but unmonetized — has not been tested yet | Tested but conversion below 0.8% with no clear lever |
| CPI scale test | Stable when spend triples | Rises 30-40% — suspect channel mix | Rises >50% — channel saturation, no clear next channel |
| Technical | Crash rate <1%, all devices | Isolated device class issues | Architectural blockers requiring rebuild |
Pivot signals (kill the current configuration but keep the IP):
- Specific features showing promise while others fail — strip back, ship leaner
- Unexpected player behavior worth exploring — re-pitch the core loop
- Market feedback suggesting different positioning or genre framing — restart Cycle 3 with new ad creative angle
The discipline that separates studios that ship hits from studios that ship runners-up is not analytic depth — it is the willingness to walk into the Cycle 6 review with the kill option on the table, and not blink when the data calls for it.
The Soft Launch Readiness Checklist
Use this checklist to evaluate your game’s readiness at each phase of the soft launch process.
Pre-Launch Readiness
- Analytics SDK integrated and validated (events firing correctly)
- Test markets selected (2-3 low-CPI, English-speaking markets)
- UA budget allocated ($10K-$30K/month across test markets)
- KPI thresholds defined and agreed with stakeholders
- A/B testing framework configured
- Crash reporting and performance monitoring active
During Soft Launch (Weekly Review)
- Crash rate below 1%
- D1 retention trending above 30% (minimum viable threshold)
- Session length and frequency within genre benchmarks
- UA campaigns running across at least 2 channels
- Weekly builds shipping with data-driven improvements
- Cohort-level analysis tracking (not just aggregate metrics)
Go / No-Go for Global Launch
- D1 retention at target: 40%+ (casual) or 35%+ (mid-core)
- D7 retention above 15% (casual) or 12% (mid-core)
- ARPDAU and conversion rate validated against genre benchmarks
- CPI sustainable at scale in target Tier 1 markets
- Technical stability confirmed across target devices and OS versions
- Global launch plan and budget approved
Conclusion
A well-executed soft launch is the difference between a successful global launch and an expensive failure. Take the time to:
- Choose the right markets (Canada, Australia, Philippines)
- Focus on retention before monetization
- Iterate rapidly based on data
- Know when to kill or pivot
The investment in soft launch pays for itself many times over when you hit global launch with confidence.
Need help with your soft launch strategy? With 20+ years of mobile gaming experience, I help studios optimize their soft launch approach and hit their KPI targets. Book a free consultation to discuss your game.