How Indie Game Publisher Deals Work

A typical deal: the publisher fronts an advance and marketing in exchange for a revenue share (often 20-50%), which they keep entirely until the advance 'recoups' — only then do royalties flow to you. The split headline matters less than what recoups, what rights you grant, and for how long. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

Follow the money through recoup

An advance is a loan repaid from your share of revenue. Read precisely what gets recouped: just the advance, or also marketing spend, porting costs, platform fees? 'Recoupable marketing' means the publisher spends, you repay — a deal can sell well and pay you nothing for years if the recoup bucket is bottomless.

Model concrete scenarios before signing: at 50k units and your price, when do royalties start? Publishers respect developers who do this math; the ones who discourage it are answering a different question.

Rights are the long game

The split lasts years; the rights can last forever. Watch the IP clause (you should keep ownership; license, don't assign), the term (time-limited beats perpetual), sequel and platform-exclusivity options, and what reverts to you if the publisher shelves the game or folds.

Termination terms are the deal's true shape: who keeps what when it ends badly defines your downside far more than the royalty rate defines your upside.

What good publishers actually contribute

The strong ones bring funding, QA, localization, porting, platform relationships, and a marketing team with real reach in your genre — capabilities that cost more to build than their share takes. The weak ones bring a logo and a newsletter.

Diligence them like they diligence you: talk to three of their previous developers, especially from games that underperformed. How a publisher behaves when a game misses is the part of the deal no contract shows you.

Protect the downside first

Indie game revenue is lumpy and unpredictable, and most advice quietly assumes a hit. Plan for the median outcome instead: a launch that earns modestly and grows slowly. Keep fixed costs low, keep some runway, and make deals you could live with if the game sells a tenth of your hopes.

None of this is pessimism — it's what lets you take real creative risks. A developer who can afford to miss is a developer who can afford to be interesting.

Get unglamorous things in writing

Splits, deadlines, deliverables, who owns what if the project dies — the awkward conversations are dramatically cheaper before money shows up. A one-page agreement between friends feels like overkill right up until it's the only thing that saves the friendship.

You rarely need a lawyer for a first project, but you do need clarity. Write down what was agreed, date it, and make sure everyone has a copy. Future-you will be grateful.

The quiet work that protects all of this

Everything in this post gets undone by an unstable build. A great store page, a clever marketing beat, a perfect jam entry — none of it survives 'crashed twice, refunded'. Stability isn't a feature players praise, but it's the floor everything else stands on.

Give yourself visibility before you need it: crash reports with stack traces, a simple way for players to flag issues from inside the game, and a habit of fixing the top recurring error before adding anything new.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Make the guesses cheap, the agreements written, and the runway longer than the plan.