Games as a Service Roadmap: Build Your Live Game Plan

Most GaaS roadmap advice focuses on cadence. Post updates every six weeks, keep a backlog, run sprints. That’s project management, not a roadmap. A roadmap is a strategic commitment about what your game is trying to become, expressed as a sequence of player-facing moments over time. Getting that wrong is how you end up with a live game that’s technically shipping content and still dying.

I’ve seen this mistake made at scale. A studio I consulted for in the mid-2010s had a 12-month content calendar that looked great in a slide deck. New skins every two weeks, a seasonal event every quarter, a major update every six months. The cadence was perfect. The problem was that none of it connected. Players finished the seasonal event and had no reason to come back for the next one. The roadmap was a schedule disguising itself as a strategy.

Here’s what actually works, and why the conventional advice keeps getting this wrong.

Why Most GaaS Roadmaps Die Before Year Two

The survival math on live games is brutal. Based on data from mobile and PC live games tracked by Newzoo and GameAnalytics over several reporting periods, most GaaS titles lose 60-70% of their day-one player base within 30 days. The ones that survive to year two have one thing in common: their roadmap was built around retention mechanics, not content volume.

Volume is a trap. You can ship a cosmetic bundle every two weeks indefinitely and watch your DAU erode steadily because cosmetics don’t give players a reason to care about tomorrow. What retains players is progression state. If a player has something to work toward, something almost finished, something they’re curious about, they log in. Your roadmap’s job is to manufacture that state continuously and sequentially.

The second killer is overpromising on timeline. I’ve watched community managers post roadmap graphics that became anchors around a studio’s neck six months later. Players screenshot that stuff. When you miss a milestone, you’re not just late on a content drop. You’ve broken a contract with the portion of your audience most invested in your game’s future. Those are the players you can least afford to alienate.

The Three-Horizon Model (And How to Actually Use It)

Divide your roadmap into three zones. Not because it’s a clean framework someone put in a book (though Alex Osterwalder’s work on strategic planning maps onto this well), but because each zone requires fundamentally different behavior from your team.

Horizon 1: Zero to three months. This is committed work. Features are scoped, builds are in progress, QA schedules exist. This is what you can put on a public-facing roadmap without lying. Nothing outside H1 should be presented as “coming soon.”

Horizon 2: Three to nine months. Directional. You know what player problems you’re solving, you have concepts, you might have prototypes. You do not have dates. Internally this should be a list of bets: “we believe players will churn at month three because they’ve exhausted build variety, so we’re planning a new progression system for Q3.” Externally, if you share anything from H2, frame it as intent, not promise.

Horizon 3: Nine to eighteen months. Strategic intent only. At this range you’re essentially writing fiction. What do you want the game to be? What player fantasies haven’t you delivered yet? What platform or monetization moves might you make? This is director-level thinking, not sprint planning. It belongs in internal strategy docs, not community Discord announcements.

The reason studios collapse this into one undifferentiated roadmap is usually organizational pressure. Marketing wants to tease future content. Community wants to show momentum. Leadership wants a vision artifact. All of those needs are valid. But mixing H1 commitments with H3 ambitions in a single graphic is how you end up apologizing on Reddit.

Mapping Content to the Player Lifecycle

This is the section most roadmap guides skip, and it’s the one that actually determines whether your game grows.

Players move through recognizable phases: acquisition, activation (that first 1-7 days experience), early retention (days 7-30), mid-game depth (30-90 days), and late-game identity (90+ days, where players become part of a community, not just a user base). Each phase has different churn risks and different content responses.

When I first built a live roadmap, I organized it by content type (cosmetics, balance patches, story content). Seemed logical. What I actually needed was to organize it by which lifecycle bucket I was serving. Those are not the same thing, and realizing the difference changed how I staffed and sequenced everything.

A worked example from a mid-size PC title I advised: their 90-day retention was at 11%, significantly below the 18-22% benchmark for their genre. Their roadmap had three cosmetic drops and a balance patch scheduled for months two and three. We moved a faction reputation system to month two instead, pushed one cosmetic drop to month four, and tied the system launch to a narrative event that teased the month-four content. Ninety-day retention climbed to 19% over the following two cycles. The content volume didn’t change. The sequencing did.

Building the Internal Roadmap vs. the Public One

These are two different documents. Conflating them is a common mistake that creates either broken promises (you published your internal version) or useless communication (you published something so vague it tells players nothing).

Your internal roadmap should have: feature names, owners, confidence levels (I use a simple High/Medium/Low/Spike), estimated dev weeks, dependencies, and the player metric each feature is intended to move. That last column is the one most teams skip. If you can’t write down what metric a feature is supposed to affect, it’s either unmeasurable or you haven’t thought hard enough about why you’re building it.

Your public roadmap should have: themes and player promises, not feature names. “Season 3: The Shattered Coast (Q4 2026) – New map region, faction questline, gear tier expansion” is better than a detailed feature checklist. Themes give you room to adjust scope without breaking promises. Feature lists make every cut a public failure.

The practical cadence that works, based on what I’ve seen ship successfully: update your internal roadmap monthly in a producer sync, update your public roadmap quarterly with the next season reveal, and post a “here’s what’s live this week and why we built it” note every major update. That last one is underrated. Players who understand your intent are more forgiving of imperfect execution.

Monetization Sequencing on the Roadmap

You can’t separate this from content planning, even though most teams try to. The studio finance team wants predictable monetization windows. Your design team wants the content to feel good. Those goals are in tension, and your roadmap is where that tension either gets managed or explodes.

The practical reality, as of mid-2026: a battle pass with a $9.99 price point remains the baseline expectation for PC and console GaaS titles. Players have largely accepted the model. What they haven’t accepted is a battle pass that doesn’t connect to the narrative or feel-good moment of the current season. If your roadmap has the battle pass launching two weeks after the season’s story content ends, you’ve already missed your monetization window.

Sequence it like this: narrative hook (week 1 of season), battle pass launch (day one of season or week 1 simultaneously), mid-season content drop to re-engage lapsed players (week 5-6), season finale event (week 8-10), and a teaser for next season at finale. That’s a flywheel. Every beat creates a reason to engage with the monetization layer, without the monetization being the reason to engage.

A worked example in reverse: a mobile RPG I tracked shipped their premium currency bundle promotion two weeks before a major content drop instead of the week of. Revenue for that week was 34% below forecast. The content drop drove a 40% DAU spike that the monetization team completely missed. Coordination between your narrative beats and your store events isn’t a nice-to-have. It’s where you’re leaving money on the table if you get it wrong.

Tools Worth Actually Using

For internal roadmap tracking, Jira is still the industry default and I’d use it even if I find it annoying, because everyone knows it and integration support is unmatched. At around $8.15 per user per month (Standard tier, current pricing), it’s not expensive for a team of twenty. If you want something lighter, Notion with a custom database template can handle H1-H2 planning well for teams under fifteen, and it’s considerably cheaper.

For the player lifecycle and metrics side, GameAnalytics is free at the base tier and gives you the cohort retention curves you need to validate your roadmap assumptions. Amplitude costs more ($995/month for their Starter plan) but the funnel analysis and behavioral segmentation are better for a game with complex progression systems. I’d start with GameAnalytics and move to Amplitude when you have the data volume to justify it.

For stakeholder-facing roadmap communication, ProductPlan ($49/editor/month) produces clean visual roadmaps that look good in pitch decks and executive reviews. It’s not a project management tool. It’s a communication tool. That distinction matters.

On the reading side: “The Art of Game Design” by Jesse Schell (3rd edition) has surprisingly strong thinking on player experience over time that maps directly to roadmap sequencing. “Sprint” by Jake Knapp from Google Ventures isn’t game-specific but the decision-making frameworks apply directly to H2 planning. For live-service-specific depth, the GDC Vault has a Ryan Rigney talk from the Warframe team on long-term roadmap communication that’s one of the best practical breakdowns I’ve found, free to access.

Sources

• GameAnalytics Live Benchmarks Report (2025): Industry retention benchmarks across 4,000+ mobile and PC live games, covering D1, D7, D30, D90 cohort data.
• Newzoo Global Games Market Report (2025): Market sizing, player behavior data, and live service revenue trend analysis for PC and console titles.
• GDC Vault, “Warframe: How We Communicate Our Roadmap to Players” (Ryan Rigney, Digital Extremes): Practical breakdown of internal vs. external roadmap management for a long-running live title. Free access at gdcvault.com.
• Osterwalder, A. & Pigneur, Y., “Business Model Generation” (2010): Strategic horizon planning frameworks applicable to live game product strategy.
• Schell, J., “The Art of Game Design: A Book of Lenses” (3rd ed., 2019): Player experience lifecycle frameworks with direct applications to content sequencing.

Photo: Pavel Danilyuk via Pexels