Getting a publisher interested in a game can feel like winning the hardest part of development. In reality, the next challenge may be even more important: deciding how much financial risk each side will carry once the contract is signed.
Understanding how studios negotiate publishing deals means looking beyond the headline revenue split.
Development advances, milestone payments, recoupment, marketing expenses, launch responsibilities, and termination rules can dramatically change the economics of the same deal.
A strong agreement gives the studio enough funding to finish while giving the publisher reasonable protection for the capital and services it provides.
Start With the Real Amount of Funding the Studio Needs
Negotiation should begin with the game’s actual financing gap.
A studio that needs $2 million to finish development is in a different position from a team with a nearly complete game that only needs distribution and marketing support. The publisher is taking more financial risk in the first situation, so it will usually expect stronger economics.
That can include a larger revenue share, recoupment rights, more milestone oversight, or greater commercial authority.
Odin Law notes that development advances are commonly recouped from game proceeds, while publishers entering later in development may take a lower royalty percentage because they are assuming less overall risk.
Studios therefore need a realistic budget before discussing percentages.
Accepting extra funding that the project does not need can make the eventual deal more expensive.
Treat the Advance as Risk Capital, Not Free Money
A publishing advance usually finances development before the game starts generating sales.
The important word is advance.
In many agreements, the publisher expects to recover that investment from future revenue. A historical analysis of 30 indie publishing agreements found that 81% of deals containing advances made those advances recoupable, while milestone payments were also common.
The commercial question is therefore not simply, “How much will the publisher give us?”
It is also, “How does that money come back?”
A $1 million advance followed by aggressive recoupement may create less attractive post-launch cash flow than a smaller advance with a more developer-friendly waterfall.
Studios should model several sales scenarios before agreeing.
Negotiate the Revenue Waterfall, Not Just the Percentage
A developer might celebrate a 60% royalty and still receive less money than expected.
The reason is the revenue waterfall.
Before either side gets paid, the agreement may deduct platform fees, taxes, refunds, localization, porting, marketing expenses, development advances, and other approved costs.
Odin Law explains that publishers commonly recoup investment before normal royalty sharing begins, though some agreements use tiered structures that provide developers with revenue from the first dollar and increase their share after recoupment.
That makes the definition of net revenue extremely important.
If “publisher expenses” is written broadly, the denominator can keep expanding.
Studios should negotiate what is recoupable, which expenses require approval, and whether those costs have caps.
Marketing Spend Needs Its Own Risk Rules
A publisher offering major marketing support sounds positive.
But who pays for it economically?
If the publisher spends $500,000 on advertising and all of it becomes recoupable against the developer’s royalties, that campaign effectively increases the project’s financial break-even point.
Odin Law recommends defining whether marketing expenditure is recoupable and considering caps where the publisher can spend additional amounts only with developer approval or by making those extra costs non-recoupable.
Studios should also ask what the publisher is actually committing to provide.
“Commercially reasonable marketing” is much less concrete than a defined campaign, minimum budget, platform outreach plan, trailer support, PR schedule, or event strategy.
Good negotiations convert promises into measurable responsibilites.
Milestone Payments Transfer Production Risk
Publishers rarely want to fund an entire project on signing.
Instead, development financing is often broken across production milestones.
Devolver Digital says its third-party projects are typically fully or partially funded through developer advances tied to milestone plans, with revenue shared after costs are recouped. It also states that it generally does not require developers to surrender their IP or sequel rights.
Milestone funding protects publishers because capital is released gradually.
For developers, the danger is vague acceptance language.
A payment should not depend on a publisher deciding that a build “feels insufficient” without previously agreed standards.
Studios should define deliverables, review periods, rejection reasons, correction windows, and what happens if publisher feedback itself causes a delay.
A good milstone clause protects cash flow as much as production quality.
Price Publisher Control Against Publisher Risk
Control is partly an economic negotiation.
A publisher investing heavily before launch may reasonably want authority over release timing, pricing, platform strategy, marketing, or commercial positioning.
A publisher providing relatively little funding has a weaker argument for controlling the same areas.
Odin Law notes that publishers often hold significant authority over marketing strategy, release timing, pricing, sales, and distribution even when developers maintain creative control.
Studios should therefore compare control rights with capital at risk.
If a publisher wants broad authority but contributes little funding, little marketing, and limited operational support, the trade may be unattractive.
Every right the studio gives away should ideally correspond to something valuable the publisher is bringing to the relationship.
Negotiate Different Economics Before and After Recoupment
One useful compromise is changing the revenue split over time.
During recoupment, the publisher may receive a larger percentage because it is recovering its investment. Once that amount has been recovered, the developer’s share can increase.
This reflects changing risk.
The publisher has much more capital exposed before recoupment than afterward.
Historical publishing-deal data discussed by Game Developer found several arrangements where both parties received revenue during recoupment rather than developers receiving nothing until the publisher had fully recovered its advance.
That structure can be valuable for studio survival.
A successful launch still produces developer cash flow instead of forcing the team to operate for months while waiting for the publisher to cross the recoupment threshold.
Publisher Reputation Is Part of the Economic Deal
Two publishers can offer identical financial terms and provide completely different value.
One may have strong platform relationships, experienced producers, localization capabilities, trusted marketing teams, and a history of helping projects through difficult launches.
Another may mainly provide capital.
Playstack’s leadership has argued that publishers and developers should use contract discussions to clarify responsibilities, milestones, marketing, and release support rather than treating the royalty percentage as the entire deal.
That is why studios should perform due diligence.
Talk to developers whose games succeeded with the publisher—and preferably developers whose projects struggled too.
A favorable revenue share means little if the publisher cannot deliver the support used to justify its percentage.
Model the Bad Outcome Before Signing
Negotiations naturally focus on success.
The contract becomes most important when success does not happen.
What if development takes another nine months? What if a milestone is rejected? What if the publisher reduces marketing? What happens if the publisher cancels the project?
Termination terms deserve special attention because losing funding midway through development can threaten the entire studio.
Odin Law warns that termination-for-convenience provisions may allow publishers to exit without developer breach and can create serious financial and IP consequences if protections are weak.
The agreement should define outstanding payments, rights reversion, repayment obligations, work-in-progress ownership, and whether the developer can take the game elsewhere.
A contract should make a bad scenario survivable, not just describe a perfect partnership.
Learning how studios negotiate publishing deals shows that financial risk is spread across much more than the royalty percentage.
Advances, recoupment, milestones, marketing costs, control rights, and termination rules all affect the real value of an agreement.
Before signing, studios should model both strong and weak sales outcomes and ensure the contract keeps development financially workable under either scenario.