Game Pre-Launch Checklist: Timelines by Game Type
A game’s launch outcome is largely set months before release day. What has to be ready, and when, depends on the business model. Indie PC titles live or die on wishlist momentum, mobile games on retention and unit economics, and live service games on infrastructure and content cadence. The timelines below reflect what industry data and practitioner benchmarks suggest, but they work best as starting points. Genre, budget, and platform rules will likely move the dates, so each checklist is worth adapting to the game in question.
Indie PC (Steam-first)
Timeline
- 12 to 6 months out: Publish the Coming Soon page. A common recommendation is to open the page 6 to 12 months before launch, and Valve states that no minimum threshold is required for Steam to show a game. Early publication gives every trailer, post, and creator video somewhere to point.
- 6 to 4 months out: Build the demand loop. Effective programs lead the trailer with gameplay in the first five seconds and end every clip and devlog with a wishlist prompt. Community participation should be genuine, not driven by promotion.
- 3 months out: Lock the demo and festival plan. At this point the demo should be polished and a Next Fest slot planned. Analysis of 3,000+ games across four Next Fests found that total wishlists and recent wishlist growth were the strongest predictors of success, which makes the festival a multiplier on existing momentum, not a replacement for it. Next Fest runs three times a year and every game is eligible.
- Final month: Creator and press outreach, launch-date lock, and launch-week content.
Benchmarks to plan against
- Roughly 7,000 wishlists is the commonly cited point where a game becomes likely, though not guaranteed, to appear on Steam’s Popular Upcoming list. One analysis suggests treating 5,000 as the floor for a commercially serious release.
- A typical game converts around 15% of wishlists to sales.
- Next Fest readiness thresholds vary by source. One guide recommends entering with at least 2,000 wishlists, while another suggests at least 1,000 wishlists, 10+ organic wishlists per day, a stable demo, and a launch date within 12 months.
- Festival results are uneven. In February 2026, the median demo gained roughly 200 wishlists, while the top 5% gained around 7,000. Per Zukowski’s research, 68 to 88% of Next Fest wishlists come from people who never downloaded the demo.
Readiness checklist
- Store page: Capsule art, sub-genre tags, short description, gameplay-first trailer
- Wishlist tracking and a weekly reporting cadence
- Demo stable and tested
- Creator target list matched to genre
- Press kit and platform disclosures (including AI content, where applicable) finalized
- Launch date and Next Fest timing aligned
Mobile
Timeline
- Alpha (tech and core loop): Soft launch works best in two stages: alpha for tech and core gameplay, then beta for progression, acquisition, and monetization. Teams should document their retention, monetization, and cost targets before testing begins. Setting targets after the results arrive is a common way soft launches go wrong, since the goalposts tend to move to fit the data.
- Soft launch (beta): One to three markets should be chosen by fit to the question being tested, and at least 60 days should be budgeted for statistically meaningful D30 cohorts. One guide puts soft launch spend at $10K to $30K per month in low-CPI markets such as Canada, Australia, and New Zealand.
- Decision gate: Proceed, iterate, or stop.
- Global launch: The first 72 hours are critical for App Store and Google Play algorithmic ranking.
Retention targets for global launch are far less settled than most guides suggest. One guide recommends that a mid-core title reach D1 retention (players returning the day after install) above 35%, or above 40% for casual, with D7 retention above 15% and an LTV model validated by 30 days of monetization data.
A large dataset paints a different picture: median D1 sits near 22%, and top-quartile D7 lands at just 7% to 8%. Genre-level retention data has also not been broadly republished since 2022, so many current tables rely on older figures. The practical answer is to set genre-specific targets before the test starts and treat cross-industry numbers as reference points, not verdicts.
Readiness checklist
- Documented success thresholds for retention (D1, D7, D30), ARPDAU, and LTV versus CPI, agreed before soft launch begins.
- Analytics and attribution verified end to end
- Real-device testing, since it exposes performance drops, crashes, and battery drain that emulators cannot simulate
- Store listing (ASO) and creative variants prepared
- Pre-registration campaign, where the platform supports it
- Tier-1 market budget contingent on soft launch results
Live service
Timeline
- Alpha to beta: Alpha asks whether the game works, while beta asks whether it is ready, run with external testers and live telemetry.
- Infrastructure lead time (6+ months out): Backend and hosting work needs early scheduling. Amazon GameLift’s guidance asks developers to submit a launch questionnaire at least three months before the first load test. Heroic Labs recommends more than one round of load testing before launch, and notes that provisioning add-ons and assigning engineers takes lead time. These are vendor-specific examples, but they illustrate the scheduling reality.
- Closed beta: Performance and load testing peaks here, with real server traffic. Console certification and security also belong in the pre-launch phase.
- Content roadmap: Practitioners advise planning the first three months of events, economy checkpoints, and A/B tests before launch, and flag launching with only a general roadmap as a common mistake.
Good marketing brings a large crowd of players at once, and the servers have to handle them. XDefiant passed one million players within about two and a half hours of launch. Its servers struggled with the rush, and it took roughly eight to ten hours to fix the problems. The lesson for live service teams is to estimate the launch-day crowd in advance and test the servers against it before release.
Readiness checklist
- Multiple load-test rounds completed against projected peak concurrency
- Certification and security reviews scheduled
- 90-day content and event calendar approved
- Economy monitoring and A/B testing framework in place
- Community moderation and incident-communication plan ready
- Support and status-page process defined
Shared checklist for every game type
- Analytics and reporting set up before the first campaign
- Brand assets, press kit, and platform disclosures finalized
- Community channels (Discord, Reddit, social) staffed and briefed
- Crisis and issue-response plan with a single approving owner
- Localization scope decided
- Launch-window review to avoid clashes with competing releases
Takeaway
Each model has a different bottleneck. Indie teams need demand signals early, mobile teams need proof of retention before spending at scale, and live service teams need infrastructure and content that survive contact with real players. Setting the gates in advance, in writing, is what keeps a launch from being decided by a deadline instead of by data.
Is your title on track against these benchmarks? Game Marketing Genie helps studios and publishers map pre-launch timelines, wishlist and retention targets, and go/no-go criteria for each release. Book a launch-readiness review to find out.
