How to Structure a Publisher-Studio Deal: Contracts, Milestones and IP Ownership
Quick answer: A publisher-studio deal is defined by four decisions made before a line of code is written: the contract type (fixed price, T&M, revenue share, or work-for-hire), the milestone structure that ties funding to deliverables, the IP ownership model that determines who controls the game's commercial future, and the revenue share mechanics that determine how returns flow back to the studio. Each decision has long-term consequences that compound through the full game lifecycle. This guide covers what each decision involves, what the current market looks like, and what to watch for in each.
Note: This article provides educational information about game development contract structures. It does not constitute legal advice. Always consult with a qualified attorney before signing any contract.
Quick navigation:
Why the Deal Structure Matters More Than the Deal Size
A studio that signs a large publishing deal with a poorly structured IP clause can end up owning nothing if the game performs. A studio that signs a smaller deal with a well-structured milestone plan and retained IP can build a long-term commercial asset that generates revenue for years beyond the initial publishing relationship.
The deal size is the number that gets discussed in founder communities. The deal structure is the number that determines the actual commercial outcome.
The four structural decisions below — contract type, milestone structure, IP ownership, and revenue share mechanics — each have consequences that compound over the full game lifecycle. A milestone acceptance clause that gives the publisher subjective approval power is not a minor detail. A cross-collateralization clause that pools multiple game revenues before triggering developer payouts is not standard boilerplate. The definition of "breach" in a transfer-on-breach clause that can cost the studio its IP over a missed milestone is not a negotiating nicety.
This guide is built to make those decisions legible before the term sheet arrives.
Contract Types: Fixed Price, T&M, Revenue Share, and Work-for-Hire
The contract type determines how financial risk is distributed between the publisher and the studio. Choosing the right model for the right phase of the project is one of the most consequential early decisions in any publisher-studio relationship.
Fixed Price
In a fixed price contract, the studio delivers a defined scope for a defined total cost. The price does not change if the project takes longer than estimated. Financial risk sits primarily with the studio.
When it works: When the scope is fully defined before the contract is signed — specific features, specific platforms, specific quality standards, specific deliverables. A well-written fixed price contract with a detailed scope document is the most protective structure for a publisher, because cost overruns are the studio's problem, not the publisher's.
When it fails: When the scope is vague. A studio interpreting a vague brief will make assumptions that minimize its own cost exposure — producing something technically compliant that doesn't match the publisher's intent. Fixed price only works when both parties agree on what "done" looks like before production begins.
The scope change problem: Fixed price contracts require a formal change order process for any modification to the agreed scope. Publishers and studios that do not establish this process before production begins consistently encounter disputes when the inevitable mid-production design evolution triggers scope changes that the studio treats as additional cost and the publisher treats as included.
Time and Materials (T&M)
In a T&M contract, the publisher pays for hours worked at an agreed rate. Scope can evolve during the engagement. Financial risk sits primarily with the publisher.
When it works: For projects where the scope is genuinely uncertain — early-stage exploration, MVP development where the design is expected to evolve based on playtesting, or ongoing LiveOps work where content requirements change week to week.
When it fails: Without clear scope boundaries, weekly hour limits, or milestone checkpoints, a T&M engagement can significantly exceed the publisher's budget before the problem becomes apparent. T&M without budget governance is an open-ended financial commitment.
The budget control solution: T&M engagements should include weekly hour caps, budget alert thresholds, and milestone checkpoints where the publisher reviews progress and approves continued spend. These controls preserve the flexibility benefits of T&M while managing the cost exposure.
Revenue Share
In a revenue share arrangement, the publisher provides development funding — either as a non-recoupable investment or as a recoupable advance against future revenue — in exchange for a percentage of the game's net revenue after defined recoupment thresholds.
When it works: When both parties are genuinely invested in the commercial outcome of the game — the publisher wants a hit, the studio wants a long-term commercial asset — and the revenue share terms are structured to align those incentives rather than create adversarial dynamics.
When it fails: Cross-collateralization — where the publisher pools the revenues from multiple games before triggering studio payouts — can prevent a studio from receiving meaningful revenue even from a commercially successful game if another game in the publisher's portfolio is underperforming. Recoupment terms that define "net revenue" in ways that maximize publisher deductions before studio payouts begin are a common source of commercial disappointment for studios that signed revenue share deals without understanding the recoupment calculation.
The 2026 market reality: Stepped revenue shares appear in 80.3% of agreements with an advance, according to Voyer's 2026 publishing deal data. The opening stage averages 24% to the developer, with the step-up stage averaging 60.3%. The real negotiation in most revenue share deals is not whether a step-up exists — it almost always does — but where the step-up triggers and what specifically causes the transition.
Work-for-Hire
In a work-for-hire arrangement, the studio is paid a flat fee or hourly rate to produce deliverables that the publisher owns outright. The studio receives no ongoing revenue from the game's commercial performance.
When it works: For specific, scoped production disciplines — art outsourcing, porting, QA, LiveOps content production — where the studio is providing production capacity rather than creative ownership.
When it fails: When applied to full-game development where the studio contributes significant creative and strategic value. A work-for-hire structure for a full-game development engagement transfers all of the commercial upside to the publisher while leaving the studio with only its production fee — regardless of how successful the game becomes.
IP implications: In a work-for-hire arrangement, IP ownership automatically transfers to the publisher upon payment. This is the intended structure for production service work and the wrong structure for a studio that intends to build long-term value through its creative output.
Milestone Structures: How Funding Connects to Deliverables
Milestone-based funding is the standard structure for publisher-studio development deals. It ties funding tranches to specific, defined deliverables — aligning the publisher's financial exposure with verifiable production progress.
Standard Milestone Sequence
Common milestones in a game development publishing deal include:
|
Milestone |
Typical Payment % |
Deliverable |
|
Contract signing |
15–25% |
Project kickoff; NDA and IP documentation signed |
|
Prototype / Vertical slice |
15–20% |
Playable demonstration of core mechanic |
|
Alpha build |
15–20% |
Core loop complete; major systems functional |
|
Beta build |
15–20% |
Content complete; QA testing phase |
|
Content complete |
10–15% |
All content locked; final QA pass |
|
Release candidate |
10–15% |
Platform compliance passed; submission ready |
|
Post-delivery holdback |
5–10% |
Released 30 to 60 days after launch; covers critical bug fixes |
The milestone schedule serves as both a funding mechanism and a project management framework. The risk lies in the acceptance criteria.
Acceptance Criteria: The Most Negotiated Clause
If the publisher's acceptance criteria are vague or subjective — "the publisher, in its reasonable discretion, determines the milestone is complete" — the publisher can effectively delay or withhold milestone payments on grounds that are difficult to dispute. Vague acceptance criteria benefit the publisher and create cash flow risk for the studio.
The protective structure for studios: acceptance criteria should be objective and specific — defined pass/fail tests, specific feature lists, measurable quality thresholds — that either are met or are not, without requiring a subjective judgment from the publisher.
The missed milestone consequence: The stakes of milestone acceptance are not only financial. A missed milestone — under a poorly structured deal — can trigger escalating remedies including IP transfer to the publisher. Transfer-on-breach clauses that allow the publisher to claim IP rights if the developer misses a milestone are present in approximately 7% of published agreements, according to Voyer's 2026 data. The definition of breach and the definition of milestone acceptance are directly connected. A missed milestone that counts as breach under a vague acceptance criterion can cost the studio its IP.
Termination Rights and Kill Fees
Publisher agreements typically include termination rights — the publisher's right to cancel the project if the studio misses milestones, if the game fails to meet quality standards, or at the publisher's discretion after a defined notice period.
The studio-protective terms to negotiate: a kill fee that compensates the studio for work completed if the publisher terminates for convenience (at no fault of the studio), IP reversion rights that return the game's IP to the studio if the publisher terminates, and a cure period — typically 30 to 60 days — during which the studio can address the grounds for termination before the publisher can exercise termination rights.
IP Ownership: The Decision That Defines the Studio's Future
IP ownership is the most commercially consequential decision in a publisher-studio deal — and the one most frequently treated as non-negotiable boilerplate rather than as a strategic negotiation.
The Three IP Models
Studio owns IP (licensing model). The studio retains ownership of the game's intellectual property — the characters, the world, the story, the underlying game systems — and licenses the publisher the right to distribute, market, and sell the game for a defined territory and term. The publisher has commercial rights; the studio has the asset.
This is the developer-protective model, and according to 2026 industry data, most reputable indie publishers have shifted toward developer-owned IP models because they recognize that creators who own their work are more motivated to produce high-quality hits. Developer-owned IP also means the studio can develop sequels independently, license the IP to other parties, and build long-term franchise value without publisher approval.
Publisher owns IP (work-for-hire / assignment model). All IP created during the project — characters, story, game systems, source code — transfers to the publisher upon payment or upon project completion. The studio has no ongoing commercial interest in the game's success beyond its contracted fee.
This is the publisher-protective model. It is appropriate for production service work where the publisher is providing the creative direction and the studio is providing execution capacity. It is inappropriate for development engagements where the studio is providing significant creative and design contribution.
Co-owned IP. Both parties share ownership of the game's intellectual property. Commercially simple in theory; operationally complex in practice. Co-ownership requires agreement on every subsequent decision involving the IP — sequel development, licensing, platform expansion, character merchandise — which creates decision-making friction that most publisher-studio relationships are not structured to manage efficiently.
Sequel Rights and Right of First Refusal
Even where the studio retains IP ownership, publishers frequently negotiate sequel rights or right of first refusal clauses that constrain the studio's freedom to work with other publishers on subsequent games in the same IP.
Right of first refusal: The publisher has the legal right to match any third-party offer the studio receives for its next project. While it provides a sense of security, it can also act as a "golden handcuff" that limits the studio's ability to leverage competing bids to increase equity or funding.
Sequel publishing rights: A clause giving the publisher the right to publish sequels to the game — on terms to be negotiated at the time — is a common and significant limitation on the studio's commercial freedom. A studio that retains its IP but grants the publisher sequel rights has a commercial asset whose full value it cannot independently realize.
Source Code Escrow
A source code escrow arrangement deposits the game's source code with a neutral third party, with defined release conditions — typically the publisher's financial insolvency or material breach — that return the source code to the studio if the publisher is unable to fulfill its obligations.
For studios licensing their IP to publishers, source code escrow is a protection against scenarios where the publisher controls distribution but cannot continue operating. Without it, a publisher that goes insolvent can leave the studio without access to its own game's code.
Revenue Share Mechanics: What the Numbers Actually Mean
A revenue share percentage without understanding the recoupment structure and the definition of "net revenue" is meaningless. The mechanics of how the percentage is calculated determine whether the studio receives meaningful commercial returns.
Recoupment
Publishers typically recoup their advance investment from the studio's share of revenue before any revenue flows to the studio. This means the studio receives no revenue share payments until the game has generated enough revenue to return the publisher's investment — plus any defined overhead charges — from the studio's portion of earnings.
The recoupment calculation is where most publisher-studio financial disputes originate. Studios should ensure the contract specifies: what exactly counts as recoupable (development advance, marketing spend, QA costs, porting costs); what the revenue base is that recoupment is calculated against; and whether the publisher is also recouping from the publisher's own revenue share or only from the studio's portion.
Net Revenue Definition
"Net revenue" — the revenue base on which the studio's percentage is calculated — is almost always less than gross revenue. Typical deductions before net revenue is calculated include platform fees (15 to 30%), payment processing fees, refunds, chargebacks, and in some cases publisher overhead charges.
The studio should negotiate a clear, specific definition of net revenue — ideally mirroring the platform's own reporting — and audit rights to verify that the publisher's net revenue calculations match the agreed definition. Include audit rights in all royalty agreements allowing you to hire accountants to examine publisher records, typically once per year.
Stepped Revenue Shares
Escalating developer percentages at revenue milestones reward success. An example structure: 60/40 in favor of the publisher up to $1M in net revenue, shifting to 70/30 from $1M to $5M, and to 80/20 above $5M. This gives the publisher a fair return on its investment while ensuring the studio benefits proportionally from a commercial hit.
Cross-Collateralization
Cross-collateralization clauses allow publishers to pool the revenues from multiple games in their portfolio before triggering studio payouts. A studio with one successful game and one underperforming game in the same publisher's portfolio may receive no revenue share from the successful game until the underperforming one's losses are recovered.
This is one of the most developer-unfavorable clauses in a publishing agreement and should be rejected or limited to games within a clearly defined franchise or series relationship. A studio signing a multi-game deal with cross-collateralization is effectively guaranteeing the publisher's portfolio risk with its own commercial success.
Red Flags Before You Sign
The following terms signal a publisher deal that is materially unfavorable to the studio — either through structural design or through ambiguity that will resolve in the publisher's favor in any dispute.
Vague milestone acceptance criteria. "Publisher's reasonable discretion" is not an acceptance criterion. Every milestone should have objective, pass/fail definitions that do not require a subjective publisher judgment.
Transfer-on-breach clauses with vague breach definitions. A contract that can transfer the studio's IP to the publisher for "breach" — where breach is defined broadly enough to include a missed milestone — is a contract that can cost the studio its most valuable asset over a production dispute.
Cross-collateralization across unrelated games. Accepting portfolio-level cross-collateralization in a single-game deal effectively makes the studio responsible for the publisher's entire portfolio risk.
No kill fee or IP reversion on publisher termination for convenience. A publisher that can terminate a project at will, without paying for work completed or returning the IP, has no financial stake in the relationship's continuity.
"Net revenue" defined by the publisher at its discretion. Revenue share calculations should be based on a specific, auditable definition agreed before signing — not on a definition the publisher can adjust through its accounting methodology.
No audit rights. Without the right to examine the publisher's financial records, a studio has no mechanism to verify that revenue share calculations are accurate.
Right of first refusal on all future projects. A right of first refusal on all future projects — not just sequels to the specific game — is a significant constraint on the studio's commercial freedom that the publisher should be required to pay for specifically.
How Galaxy4Games Approaches Publisher-Studio Relationships
Galaxy4Games approaches publisher and co-development relationships as partnerships where both parties' commercial interests are aligned through the deal structure — not as vendor relationships where the studio delivers scope and the publisher captures all commercial upside.
The studio's co-development model — including revenue share arrangements — reflects this approach. Galaxy4Games has experience on both sides of the publisher-studio dynamic: as a development partner building games for publishers, and as the developer-publisher of its own live titles. This dual experience informs how the studio approaches deal structuring: with an understanding of what publishers need to justify their investment and what studios need to protect their long-term commercial interests.
For studios and founders entering publisher conversations, Galaxy4Games can support the pre-deal preparation that publishers evaluate before opening serious conversations: product readiness, KPI validation, LiveOps infrastructure, and the pitch documentation that demonstrates commercial viability. A well-structured deal negotiation begins with a strong product foundation — not with the term sheet.
For publishers evaluating development partners, Galaxy4Games' experience operating its own live games means the studio understands the post-launch obligations that publishing agreements create — event production, economy management, content pipeline operations — and builds the infrastructure to fulfill them from day one of the development engagement.
Learn more about game co-development services and full-cycle game development.
Further Reading
-
How to Hire Game Developers for Indie Projects: A Founder's Checklist — Galaxy4Games
-
Game Launch Strategy in 2026: From ASO and Ad Creatives to Publishers, UA Scaling — Galaxy4Games
-
Game MVP Best Practices: KPIs, Budgets and Studios That Can Help — Galaxy4Games
Sources
-
Game Publisher Agreement Guide for Indie Studios — Promise Legal
-
Video Game Royalties: What Developers and Publishers Need to Know 2026 — Legal Moves Law Firm
-
Understanding Video Game Publishing Deals: A Founder's Guide for 2026 — Studio Showdown
-
Game Development Contracts: Complete Legal Guide 2025 — Generalist Programmer
-
How to Hire Game Developers for Indie Projects: A Founder's Checklist — Galaxy4Games
