15 Jun, 2026 | 7 min read

Managing cash runway between game launches

Zara Chechi
Zara Chechi

Most cashflow advice assumes revenue arrives in a reasonably steady stream. For a game studio it does not. Your income is shaped by launches: a big spike in the launch month, a tail that declines for weeks or months afterwards, and then a dry spell until the next title ships. Standard burn-rate thinking, which divides a cash pile by a flat monthly spend, badly misreads this. The question is not just how many months of runway you have, but whether your cash survives the gap between a decaying revenue stream and the next launch that has not happened yet.

This is the defining financial challenge of running a studio, and it gets harder the moment you start a new project, because you are spending hard on a game with zero revenue while leaning on the fading tail of the last one. Get the shape wrong and a studio with a successful title can still run out of money before its follow-up ships. This guide is about that specific cycle, the launch lump, the declining tail, the dry spell and the overlap, and how to plan cash around it rather than around a flat average.

A business account built for game studios

Open your account
A business account built for game studios

Your revenue is launch-shaped, not a flat line

A game's revenue curve has a recognisable shape. Sales and in-app spend peak in the launch window, driven by wishlists, press, the storefront's new-and-trending placement and your own marketing push. Then they decline, sometimes steeply, as the initial audience is served and attention moves on, settling into a long, lower tail that content updates, sales events and seasonal spikes can lift but rarely restore to launch levels.

The mistake is to annualise the launch month. A title that earns strongly in its first weeks can produce a flattering monthly average that bears no relation to month eight, when the tail has thinned to a fraction of the peak. Treating that average as your steady income invites overspending in the good months and a scramble in the lean ones. The healthier mental model is to map the expected curve, peak, decline rate, settled tail, and plan spending against the shape, holding back a large slice of the launch lump precisely because you know the line is coming down.

Storefront payout lags push the spike past launch day

The launch spike in your bank account is not the launch spike in your sales dashboard. Storefronts report sales monthly and pay out on a delayed cycle, so the cash from a strong launch week often lands weeks later, net of the storefront's cut, taxes and any refunds. For a studio that has spent heavily on marketing right up to launch, that gap between spending the money and receiving the proceeds is a genuine cash-timing risk.

It also means your leanest cash moment can be the weeks immediately around launch, before the first big payout clears, even though that is exactly when the game is performing best. Refund windows and chargeback clawbacks then trim that first payout further, so the cash version of your spike is both later and smaller than the sales version. Plan the launch period assuming you fund it from reserves and only later get reimbursed by the payout, rather than expecting the money to arrive in step with the sales.

Surviving the dry spell between titles

After the tail thins comes the hardest part of the cycle: the dry spell, where the last game earns little and the next has not launched. Costs do not pause for it. Payroll, tools, engine and middleware fees, and the cost of building the next title all run continuously while incoming revenue is at its lowest. A studio can be creatively healthy and still hit a cash wall here purely because of timing.

The way through is to treat a portion of every launch as fuel for the dry spell, not as profit to spend. When the launch lump and early tail are strong, the discipline is to ring-fence reserves sized to carry fixed costs through the expected gap to the next release, including a margin because games slip. That reserve is not idle cash, it is what converts a lumpy revenue stream into a survivable one. The studios that endure are usually the ones that decided, at peak, how much of the peak they were not allowed to touch.

Funding the next project from a decaying stream

The cycle's real pressure point is the overlap: you are deep into building the next game, spending at full tilt, while the only revenue coming in is the declining tail of the last one. You are effectively funding a zero-revenue project from a shrinking income, and the two lines cross at the worst possible angle, costs rising as revenue falls.

Planning this means looking at the tail honestly. Project the declining revenue forward, set it against the next project's burn, and find the point where the gap must be covered by reserves or external funding, whether milestone-based publisher money or other sources. Knowing that crossover date in advance turns a slow-motion crisis into a deadline you can plan around: either the new title ships before reserves run out, you raise or secure funding to bridge it, or you adjust the next project's scope and spend. The danger is discovering the crossover only when the balance is already low; by then your options have narrowed to the painful ones.

How Altery fits

Managing a launch-shaped cash cycle is mostly about visibility and discipline, and an Altery account supports both. Real-time balances across currencies show what has actually landed from platform payouts, so you can tell the cash spike from the sales spike and see how fast the tail is decaying, while categorised spend and balance alerts flag when the dry-spell burn is drawing down faster than planned.

The core move is ring-fencing reserves in dedicated pots: carve the dry-spell buffer and the next-project fund out of the launch lump at peak, separate from operating cash, so the money meant to bridge the gap is not quietly spent in a good month. Multi-currency accounts holding USD, EUR and GBP let you keep platform proceeds in their native currency and convert when rates suit rather than when cash is tight, which matters most precisely during a dry spell. If you build several titles, multi-entity management keeps each project's runway visible on its own. Altery is not a bank and provides general information, not advice.

Frequently asked questions

Standard burn-rate maths divides a cash pile by a flat monthly spend, but studio revenue is not flat. It spikes at launch, declines along a tail, then dries up until the next title. Annualising the launch month produces a flattering average that overstates lean-period income, so the right approach is to plan against the expected revenue curve and the gap to the next release, not a single average.

Two moments. The weeks right around launch, before the first platform payout clears, because you have spent on marketing but the proceeds arrive weeks later net of fees and refunds. And the dry spell between titles, when the last game's tail has thinned, the next has not shipped, and fixed costs keep running. Reserves ring-fenced at peak are what carry you through both.

There is no fixed percentage; it depends on your fixed monthly costs, how long until your next release and how quickly your titles' tails decay. The practical method is to project fixed costs across the expected gap to the next launch, add a margin because games slip, and ring-fence at least that amount from the launch lump before treating anything as profit.

Project the declining tail of the current title forward and set it against the next project's burn to find the crossover point where the gap must be covered by reserves or external funding. Knowing that date early lets you plan around it, ship before reserves run out, secure milestone or other funding to bridge it, or adjust scope, rather than discovering it when the balance is already low.

This guide is general information to help game studios and is not financial, tax or legal advice. Altery is not a bank. Check your own circumstances before acting.

Run your studio's finances from one account

Open your account
Run your studio's finances from one account

Keep reading

05 Jun, 2026 | 7 min read

Surviving milestone-based publisher funding

Most publishing deals pay your advance in tranches tied to milestones, so a late or rejected milestone can leave you cash-starved mid-development. Here is how to plan around it.

Zara Chechi Zara Chechi
16 Jun, 2026 | 7 min read

Ring-fencing user-acquisition ad spend from operating cash

User-acquisition budgets scale up fast and bill across several ad networks at once. Here is how to ring-fence UA spend from your operating cash and keep per-platform control.

Zara Chechi Zara Chechi
31 May, 2026 | 6 min read

How app store and storefront payouts actually work

Every storefront pays on its own schedule, in its own currency, above its own minimum. Here is how mobile app store and PC storefront payouts actually reach your studio.

Zara Chechi Zara Chechi
Open account