Stephen Brenish
A revenue share offer is an investment request. The studio is asking you to defer some or all of your fee in exchange for a percentage of income from a game that does not exist yet. Treat it like an investment: understand what you are putting in, what has to happen for you to get it back, and what protects you if it does not.
If a predictable paycheck matters more to you than upside, compare any offer against what a salaried producer role actually pays, and use the revenue share calculator to model splits.
What you are actually being asked to give up
With a flat fee, you work, invoice and get paid. The studio carries all the commercial risk.
Revenue share flips that. You carry the risk that the game ships late, sells poorly or never ships at all, and you carry it without control over most of the decisions that determine the outcome. The first question is simple: what would this work earn at your normal rate? That number, the deferred value, is what the revenue share has to beat.
Run the numbers before you say yes
Here is how to test an offer, using an illustration with made-up but plausible inputs.
Illustration: a composer on a small indie game. The composer delivers 45 minutes of finished music at a normal rate of $300 per finished minute, so the deferred value is $13,500. The game sells 1,200 copies at $12.99, for $15,588 gross. After Steam’s standard 30% share, about $10,912 is left. An 8% share of that is about $873, roughly $12,600 short of the composer’s normal fee.
Nothing about that game is a disaster. It is simply a modest launch, and modest launches are common. Before accepting any offer, run this calculation with realistic sales numbers for the genre and team, not the numbers in the pitch.
The side-by-side
| Factor | Flat fee | Revenue share |
|---|---|---|
| Payment certainty | High, if the studio is solvent | Depends entirely on sales |
| When you get paid | On your invoice terms | After sales, platform fees and any recoupment the contract allows |
| Who carries the risk | The studio | You |
| Upside | Capped at the agreed fee | Uncapped in theory |
| If the game is cancelled | You keep what you were paid | You get nothing unless the contract says otherwise |
| Portfolio rights | Usually negotiable | Often unclear unless written down |
| Sensible default for | Most work | Only teams that have shipped, with protections in place |
When revenue share can make sense
Three conditions make an offer worth considering.
The team has shipped before. Finishing a game is a different skill from starting one, and many projects never reach release. A team with a shipped game has already cleared the hardest filter.
There is a deferred fee, not just a percentage. The strongest structure pays a deferred fee from first revenues before any percentage split kicks in, ideally with milestone payments or escrow. It is a signal that the studio is putting something on the line too.
The scope and timeline are fixed. Defined deliverables, a fixed end date and a completion milestone in the contract. Open-ended revenue share invites “just a few more tweaks” forever.
Illustration: a hybrid deal. A small team with one shipped game offers a programmer 7% of net revenue on a four-month contract. The programmer negotiates a $2,000 per month deferred fee, $8,000 in total, paid from first revenues. The game sells 9,800 copies at $14.99, about $146,900 gross and $102,800 after Steam’s 30%. The $8,000 deferred fee is paid first, then 7% of the remaining $94,800 is about $6,640, for a total of roughly $14,640. If the programmer’s normal fee for the work would have been around $18,000, that is below market but in a reasonable range, with a shipped credit, and far better than the percentage alone would have paid.
The contract terms that decide your payout
Even a fair deal can pay nothing if the contract is loose. Read these clauses closely.
The definition of net revenue. “Net” can mean revenue after platform fees, or it can mean revenue after platform fees, marketing, publisher recoupment and the studio’s own development costs, in which case your share may never start. Get the definition in writing, explicitly, with any deductions listed.
Payment triggers and schedule. The contract should say when payments are due: monthly, quarterly or at a sales threshold. “We’ll pay you when we can” is not a schedule.
Audit rights. A clause letting you request a sales report each quarter costs the studio nothing and protects you from missed payments.
Portfolio rights. You should be able to show your work and list the game regardless of commercial outcome.
Cancellation, sale and transfer. What happens to your share if the game is cancelled, sold to another company, or the studio closes?
Illustration: what a loose contract costs. An animator accepts a share with no audit clause, no payment trigger and no definition of net revenue. The game earns $88,000 gross, and the studio then counts $91,000 of development costs against it, so “net” is zero and the animator’s share is zero after eight months of work. Every one of those gaps is fixable in the contract before work starts.
Negotiating a better deal
- Ask for a deferred fee repaid from first revenues before the split.
- Ask for a reduced rate during development plus a smaller percentage afterwards, rather than all-or-nothing.
- Cap the scope with defined deliverables and an end date.
- Tie payments to milestones so you are paid as the project progresses, not only at the end.
- Have a lawyer review it. An hour of review is cheap next to months of deferred work, and the definition of net revenue alone justifies it.
If you are on the studio side, structuring deals this way is also how you keep good contractors willing to work with you twice. The Game Producer’s Handbook by Dan Irish covers managing contractor relationships from the producer’s chair.
Related reading
Photo: cottonbro studio via Pexels
