Indie Game Budget: Plan Cash, Time, and Scope

An indie game budget should track three different costs: unavoidable release fees, optional production spending, and founder-time burn. Keep them separate, attach each line to a scope decision, and revise the forecast using actual production speed. A single cash total hides the most common way a solo project becomes unaffordable: unpaid time keeps expanding after the bank balance looks stable.

This guide includes a spreadsheet structure and a fictional worked scenario. The numbers in the scenario are examples, not market averages or a promise about what a game “should” cost.

Use it beside the indie game development roadmap, because a budget without milestone evidence is only a wish expressed in currency.

Ledger 1: Unavoidable Release Costs

These are costs required by the chosen release path or legal operation. “Unavoidable” depends on the project. A PC game released only on itch.io has different obligations from a console game with online services.

Possible lines include:

• platform submission or app fee;
• business registration and required accounting;
• tax or legal advice for the actual jurisdictions involved;
• age-rating or certification costs where applicable;
• required signing certificates or development hardware;
• domain, support email, and policy hosting;
• required third-party service minimums;
• bank, payment, or currency-conversion costs.

As of this article's August 2026 source check, Steam's official Direct Fee documentation states a $100 USD or equivalent fee for each new app distributed on Steam. It also states that the fee is not refundable but can be recouped in a later payment after the product reaches at least $1,000 in Adjusted Gross Revenue, subject to its documented conditions.

Record the fee as cash required before release. Do not erase it from the budget because it might be recouped later. A future conditional repayment does not pay today's invoice.

Platform terms, taxes, and fees can change. Add a “source checked” date and link beside every changeable line.

Ledger 2: Optional Production Spend

These purchases can reduce time, increase quality, satisfy a requirement, or create risk. Optional does not mean frivolous. It means the game could change scope, method, or quality target instead of paying that exact cost.

Categories include:

• commissioned art, animation, music, sound, writing, or localization;
• asset packs and plugins;
• contractor programming or quality assurance;
• accessibility review;
• trailers, store art, and capture tools;
• hardware for target-device testing;
• hosting, backend, analytics, or crash reporting;
• event submissions and travel;
• advertising or creator outreach services;
• contingency for replacement and rework.

For every line, record the decision it buys:

Do not buy an asset because it is discounted and then reshape the game around the purchase. Start with the production constraint, compare options, confirm license terms, and keep the receipt and license text with the project.

Ledger 3: Founder-Time Burn

Time is a budget even when no salary leaves the account. Give it a rate for planning.

Choose one of these approaches:

• Replacement rate: what comparable work would cost to hire.
• Opportunity rate: what the developer could reasonably earn doing other available work.
• Survival rate: the minimum personal runway the project consumes per month.

None is perfect. Pick one, name it, and use it consistently. Do not call the result an accounting expense unless your accountant treats it that way. It is a planning value that reveals scope.

Use:

Founder-time burn = forecast development hours × planning hourly rate

Also calculate runway:

Available project hours = weekly sustainable hours × funded weeks
Scope gap = forecast remaining hours - available project hours

If the scope gap is positive, the options are to cut, extend, fund, reduce required polish, or improve the production method with evidence. The spreadsheet should not solve the gap by setting the founder's hourly value to zero.

Free Tools Still Have a Cost Shape

Godot is free and open source under the MIT license. The official Godot license page says it can be used for any purpose and that games made with it remain owned and licensed by their creators. Distribution must still include the required Godot copyright notice and license statement for the engine binary.

That removes an engine license purchase from many budgets. It does not remove:

• learning time;
• custom tooling;
• porting and platform work;
• third-party asset licenses;
• test hardware;
• production labor;
• support after release.

“Engine cost: $0” can be true while “game cost: $0” is false.

Create the Budget Sheet

Use these columns:

Add a separate time sheet:

Keep low, expected, and high values. A single estimate disguises uncertainty. The high case should reflect identifiable risk, not an arbitrary percentage pasted onto every row.

Examples:

• Low music cost assumes the existing licensed library fits.
• Expected assumes two commissioned tracks.
• High assumes stems, revisions, and an extra trailer cut.

Write the assumption in the sheet. Otherwise the ranges become decorative numbers no one can update rationally.

A Fictional Solo-Game Scenario

Suppose a developer plans a small downloadable PC puzzle game. The following amounts are invented to demonstrate the model:

Cash Ledger

The Steam fee is sourced above; every other figure is a fictional assumption, not a price quote.

Time Ledger

At a fictional planning rate of $25 per hour, founder-time burn is $14,000. The combined planning cost is therefore $14,880, even though only $880 is expected to leave the bank.

That does not mean the developer must pay themselves $14,000 before launch. It means a four-month delay or forty extra content units has a visible cost instead of being labeled free enthusiasm.

Tie Every Feature to All Three Ledgers

Consider adding online co-op.

Cash effects may include hosting, security review, test devices, support tooling, and platform services. Production spending may include networking expertise and wider QA. Founder time includes architecture, synchronization, failure handling, matchmaking, moderation, deployment, and support.

The feature is not “a few network calls.” It changes the roadmap and the operating model.

Use a feature cost card:

Feature:
Player promise improved:
Unavoidable cash added:
Optional spend added:
Founder hours added, low/expected/high:
Testing surface added:
Ongoing monthly cost:
Cut alternative:
Evidence required to approve:

Do this before the feature enters production. A feature that cannot justify its cost against the game's one-sentence promise stays in the cut list.

Update the Forecast With Throughput

After the representative slice, record how long one content unit actually took. After the next unit, record it again.

Forecast remaining time as a range:

Remaining content hours = remaining units × observed hours per unit

Then add known non-content work separately: save systems, menus, platform integration, regression testing, store review, release setup, and support preparation.

Do not multiply the fastest unit by the remaining count. Include rework and integration, which often grow as systems interact.

Set three review points:

• after prototype;
• after representative slice;
• at content freeze.

At each point, compare forecast cash and time with actual runway. Cut before the gap becomes an emergency.

Protect a Real Contingency

Contingency covers unknown required work, not new ideas. Define what can use it:

• replacing an asset with unusable license terms;
• repairing a release-blocking device issue;
• extra platform review work;
• emergency contractor help for a reproducible blocker;
• extending a required service during a delayed review.

It does not cover a new biome because the project is “ahead.” If contingency remains near content freeze, keep it for launch and support.

Budget Completion Rule

The budget is usable when:

• every chosen platform has current sourced fees;
• cash, optional spend, and founder time are separate;
• low, expected, and high cases have written assumptions;
• every major feature has a cost card;
• actual production speed updates remaining hours;
• a cut order exists before runway is exceeded;
• post-launch support has time and cash reserved.

The companion guide to publishing a game on Steam covers the release path. Bring its current requirements back into this ledger before paying or promising anything.

An indie game budget is not a prediction that survives contact with production unchanged. It is the mechanism that notices the change early enough to preserve the game.