Will Your Indie Game Pay the Bills?
A good launch can still leave you choosing between paying yourself and paying for the next build. Sales are coming in, players are finding the game, and the project looks successful from the outside. Inside the studio, the money may have several jobs to do before any of it reaches you.
A public account from Northend Games co-founder Omer makes that tension concrete: he reports $560,000 in gross Steam sales and $73,000 in personal income across five years. We would use that case to ask whether a project can support the people making it, and which decisions could improve the next one.
Start with the income the project has to support
Before setting a sales target, write down what the game needs to pay for. Include your living costs, each collaborator’s compensation, outside work, ongoing support, and the money you want available for the next project.
For illustration, two founders each needing $2,000 a month over an 18-month project require $72,000 between them. Add $20,000 in external costs and the total reaches $92,000 before allowing for taxes, a reserve, or the next game. These are hypothetical inputs; the useful exercise is to put your own numbers in their place.
Then work backwards through the deductions that apply to your business. This gives you a sales requirement you can compare with your forecast. If the two are far apart, you have a reason to change the scope, timeline, funding, or income expectations before spending another year on development.
Separate money earned from money available
Steam’s reporting and payments FAQ explains that gross sales are adjusted for returns, chargebacks, and applicable taxes before the revenue share is calculated. The studio’s payout still has to cover whatever obligations remain in its own business.
We would keep four amounts visible in the budget:
- Sales: what customers bought, with the report’s definition of gross revenue recorded alongside it.
- Studio receipts: what reaches the company after the deductions and splits that apply.
- Available project cash: what remains after costs already paid and money reserved for outstanding obligations and support.
- Founder income: what each person can receive under the ownership and payment arrangements, allowing for their tax obligations.
Reconcile those amounts with reports, invoices, and bank deposits. A founder split divides the amount available between owners. Calling it a loss hides the more useful question: can that amount support everyone involved?
Investigate refunds before chasing more sales
Omer reports a 22% refund rate. We would investigate that before spending more to attract players, because extra sales may carry the same unresolved problems. The percentage alone cannot tell us whether the problem is stability, expectations, or something else. Steamworks provides refund categories and written player notes, which give you a place to start.
Look for repeated complaints, then test a specific explanation. If players mention crashes, try reproducing them on the affected setups. If they expected a different kind of game, compare the store page and trailer with the opening session. If they cannot understand the controls, watch someone unfamiliar with the game play without coaching.
Keep those explanations provisional until you have evidence. Compare similar reporting periods after a change, and record discounts or campaigns that could affect the comparison. Steam notes that weekly refund rates can be volatile around launches and sales. A 2025 GameDiscoverCo survey also found a wide range between games. Use benchmarks as context, and track both returned copies and returned revenue when estimating the financial effect.
Make the publisher earn its place in the plan
It is tempting to look at a publisher’s share and imagine keeping all of it. Omer’s publisher handled China, Korea, and Japan. For that kind of arrangement, we would evaluate those territories separately: what revenue remained for the studio, what work the publisher did, and what reaching those players independently would require.
Here is a deliberately simplified example. If a publisher keeps 40% of the amount available for that split, you retain 60%. The deal would need about 67% more revenue at that stage to leave you the same amount as keeping 100% yourself, assuming everything else stayed equal. That is a comparison tool, not a description of Omer’s contract. Advances, recoupment terms, additional costs, and work the publisher saves you can change the result.
Ask for a concrete plan: which territories, what localization and marketing work, which reporting, and what commitments? Build a credible alternative alongside it. Self-publishing means assigning that work to someone too. We would favor the option with the stronger expected result for the studio and a workload the team can actually handle.
Put development time in the budget
Omer’s reported $73,000 averages $14,600 a year over five years. That average says little about when the money arrived or what future sales will bring. A game that eventually pays its developers may still leave them short during production. Extra months add living costs, support work, and whatever other expenses continue while the project grows.
Set a scope you can finish within the resources you have. Before adding a feature, estimate the extra development and testing it creates. Ask what evidence suggests it will help players enough to justify that work. A smaller release may be a better choice when the alternative requires sales your forecast cannot support.
Plan payments by month as well. Steam says it pays by the 30th of the month following sales, with possible additional bank processing time. Put expected receipts beside bills and contractor payments. Check the withholding shown in your Steamworks account; its tax FAQ explains why rates vary. Use advice appropriate to your own business when setting aside money for tax.
What we would change before the next launch
For a team facing this situation, we would start with these decisions:
- Define the income floor. Write down what each founder needs and how long existing cash can cover the gap.
- Model a slower result. Build conservative, expected, and optimistic sales cases, each showing costs, retained income, and payment timing.
- Choose a problem to investigate. Use refund notes and playtests to decide which fix or expectation mismatch deserves attention first.
- Compare publishing options. Include the services, costs, contract terms, and workload behind each revenue split.
- Set limits on expansion. Decide which features or delays the budget can absorb before the next development milestone.
Our view at NGL is that a promising game needs a plan for paying its makers. If that plan only works under the most optimistic sales forecast, adjust it while there is still time. The next useful step could be a smaller scope, a better tested opening, a different publishing arrangement, or more time earning elsewhere before committing to full-time development. Choose the change that addresses the constraint you can actually identify.