Forgiven 
A useful indie game budget is a decision tool, not a single optimistic total. It shows when money is needed, what assumptions support the plan and which parts of the project can change if the schedule or funding changes.
Start with scope and milestones
Describe the smallest version of the game that can deliver its central promise. Break production into milestones such as prototype, vertical slice, production, content complete, testing, launch and post-launch support. Give each milestone clear acceptance criteria so that payment and progress are tied to completed work.
Estimate tasks with the people responsible for them. Include integration, revisions, meetings, build engineering and bug fixing; these are real production costs even when they do not create a visible asset.
Build the budget by cost category
- People: salaries, employer costs, contractor fees, recruitment and specialist support.
- Technology: computers, test devices, engine or middleware licences, cloud services, source control and backups.
- Content: art, animation, audio, music, writing, voice recording and licences.
- Quality: testing, accessibility, compatibility, localisation and ratings.
- Business: legal advice, accounting, insurance, company administration and tax compliance.
- Publishing: store fees, trailers, capsule art, events, public relations, advertising, community support and creator outreach.
- Operations: servers, customer support, moderation, patches and other post-launch obligations.
Separate fixed, variable and contingent costs
Fixed costs continue regardless of sales. Variable costs change with usage, transactions or the number of territories. Contingent costs arise only if a condition is met, such as a royalty, revenue share or milestone bonus. Marking each line this way makes it easier to understand what happens when the project grows or slips.
Use the current licence and commercial terms from each supplier’s official documentation. Do not rely on an old blog post for engine royalties, platform deductions or payment thresholds.
Create a monthly cash-flow forecast
Place every expected payment in the month when cash will leave the account, not merely when the work occurs. Do the same for funding receipts. Late milestone payments, tax timing and annual software renewals can create a cash shortage even when the overall project appears funded.
Track three values for every budget line: approved budget, committed cost and actual cost. Add an estimate to complete. This shows overspend early enough to make a deliberate trade-off.
Include contingency and runway
Contingency should cover identifiable uncertainty, not hide an under-scoped plan. Record the risk it protects against: extra compatibility work, contractor availability, localisation changes or a delayed release. Keep a separate operating runway for the studio and for essential post-launch support.
When contingency is used, note the cause and revise the forecast. Repeated use for the same category is evidence that the underlying estimate needs correction.
Budget marketing as production work
Store art, trailers, demos, festival builds, localisation and community management require time as well as invoices. Schedule them alongside development. For Steam, allow time for the Coming Soon page, store review, build review and release controls described in Valve’s release documentation.
Model revenue conservatively
Create scenarios rather than treating a sales forecast as guaranteed income. State the list price, expected discounting, regional prices, taxes, refunds and contractual deductions. Keep gross receipts, net receipts and profit separate.
Use your own store-page, demo, wishlist and campaign data as it becomes available. Public estimates and market-size reports can be useful background, but they are not reliable evidence for a particular game’s sales.
Control changes
Every substantial feature request should show its cost, schedule effect and the item it displaces. If the budget cannot absorb it, reduce scope, secure more funding or move the release. Quietly adding work while holding the same deadline turns a budget into fiction.
Review the budget at least at each milestone and more often when cash is tight. The aim is not perfect prediction. It is early visibility, clear ownership and enough room to finish and support the game without depending on unsupported success statistics.
