What to Budget for After Your Game Goes Live

A live mobile game costs money every month it exists. Server hosting, store fees, customer support, updates, and user acquisition all continue after launch, and together they typically run 15% to 30% of the original development cost per year. Founders who budget only for development arrive at launch with a finished game and no runway to operate it.

Why this matters

The most common financial mistake in a first game project is treating launch as the final expense. Development is the largest single cost, but it is not the last one.

A game that launches successfully and then runs out of operating budget within three months is a worse outcome than a game that never launched, because it accumulated players, expectations, and obligations that cannot be met.

Planning the post-launch budget before development starts changes how the overall budget is allocated, and that change is almost always an improvement.

The cost categories

Seven ongoing costs, in rough order of how quickly they start.

1. Server and hosting. If the game has any online component, leaderboard, save sync, analytics, or multiplayer, there is a server cost. This scales with player count, which means it grows as the game succeeds.

For a small casual game, expect $20 to $200 per month depending on the backend complexity and player volume. Games with real-time multiplayer can cost significantly more.

2. Store fees. Both major stores take 15% to 30% of revenue depending on your annual earnings. This is not a post-launch cost you pay separately, but it affects your net revenue and therefore your budget.

Factor it into every revenue projection. A game earning $10,000 per month in gross revenue delivers $7,000 to $8,500 after store fees.

3. Updates and maintenance. Operating system updates, device changes, and store policy changes require periodic updates to keep the game functional. Budget for at least one maintenance update per quarter.

Each update costs development time. For a small studio, estimate two to five days per quarterly update, plus emergency fixes for critical issues.

4. Customer support. Players contact you about bugs, lost progress, billing issues, and feature requests. The volume scales with the player base, but even a small game generates support requests.

For the first year, most solo developers handle this personally. Budget the time cost even if you are not paying someone else, because it takes hours every week.

5. User acquisition. Unless the game grows purely through organic discovery, you will spend money to acquire players. This is usually the largest ongoing cost and the one with the most variable range.

Small campaigns start at $500 to $2,000 per month. Scaling a game that works can cost tens of thousands. Budget at least a modest test budget for the first three months.

6. Content updates. Players who stay expect new content: levels, events, challenges, seasonal themes. The frequency depends on the genre, but even a casual game benefits from monthly additions.

Content updates cost development time and sometimes art. Budget three to seven days per month for a small team.

7. Analytics and tools. Crash reporting, analytics dashboards, A/B testing tools, and attribution services. Many have free tiers, but games that grow usually cross into paid plans.

Budget $50 to $300 per month for the tool stack once you pass the free tier thresholds.

The post-launch budget is not a single number. It is a monthly operating cost that continues as long as the game is live.

A first-year budget template

For a casual mobile game with a small team.

The largest variable is user acquisition. A game with strong organic growth can spend less. A game competing in a crowded genre will spend more.

What most founders miss

Three costs that are frequently absent from first-time budgets.

The time cost of being live. Even without paid help, a live game consumes founder time: support, monitoring, update planning, and community management. This is time not spent on the next project.

The cost of success. Server costs, support volume, and tool costs all scale with player count. A game that performs well costs more to operate, and the revenue does not always scale at the same rate during the early months.

The cost of shutting down. If the game does not perform, shutting it down properly takes time and communication. Existing players need notice, refund policies need following, and store listings need updating. This is a cost of the decision to launch, not a cost of failure, as covered in When to Kill a Game and What to Salvage.

How to plan the budget before launch

Four steps, done before development starts.

1. Estimate the monthly operating cost using the ranges above and your specific game's requirements.
2. Set a runway. Decide how many months you will operate the game before it must be self-sustaining. Six months is a reasonable minimum.
3. Include the operating runway in the total project budget. If development costs $40,000 and six months of operation costs $12,000, the project budget is $52,000, not $40,000.
4. Set a review point. At month three, evaluate whether the game's revenue trajectory supports continued operation. If not, make the decision then rather than when the money runs out.

The review point is the most important step. It turns an open-ended commitment into a structured test with a defined decision moment.

What we would do

Add six months of operating costs to the development budget from the start. Present this to investors or board members as the total project cost, not as a surprise after launch.

Set monthly budget reviews from launch day. Track actual costs against the estimates and adjust the user acquisition spend based on what the retention and monetisation data shows.

Then make the month-three decision deliberately. If the numbers support continued operation, allocate the next quarter. If they do not, wind down with the remaining runway rather than scrambling, following the same logic as Changing Scope Mid-Project.

The short version

• A live game costs 15% to 30% of its development cost per year to operate.
• Seven cost categories: servers, store fees, updates, support, user acquisition, content, and tools.
• User acquisition is usually the largest ongoing cost and the most variable.
• Include six months of operating costs in the total project budget before starting.
• Set a month-three review point to decide whether to continue, adjust, or wind down.
• Budget for the cost of success: servers, support, and tools all scale with player count.

Add your post-launch operating costs to your project budget this week. If you want help planning a budget that covers development through the first six months of live operation, start a conversation.

Related reading: When to Kill a Game and What to Salvage, How Game Development Billing Works, and Changing Scope Mid-Project.