Create

Game Development Agreement: Work-for-Hire or Publishing Deal?

The central decision point of the game development agreement explained: Work-for-hire with full transfer of rights or a publishing deal with license and recoupment.

Updated 4 October 2026

The game development agreement covers the two central constellations in the games industry. The most important decision in the wizard is the contract model selection – it determines almost all subsequent clauses.

Work-for-Hire

A client commissions a developer studio on the basis of a contract for work and services (§ 631 BGB (German Civil Code)). The studio receives a fixed price or milestone-based compensation and, in return, transfers the full rights to the game – including source code, assets, graphics, and sound design. Important: The statutory fairness adjustment according to § 32a UrhG (German Copyright Act) remains mandatory despite the full transfer of rights. In the event of a striking disproportion between the compensation and the later success of the game, additional remuneration can be demanded – regardless of what was contractually agreed.

Publishing Agreement

Here, the relationship is reversed: The developer studio remains the rights holder and grants the publisher only a temporally and territorially limited, usually exclusive license. The publisher pays an advance for this, which is recouped via the recoupment mechanism from net proceeds – i.e., the proceeds after deduction of the platform fee (e.g., approx. 30% on Steam) as well as after refunds and chargebacks. Only once the advance has been fully recouped does the studio receive the agreed revenue share from further proceeds. The rights revert to the studio if the contract ends or if agreed milestones are not reached.

Milestones that are truly justiciable

Both models share a curated milestone template (Vertical Slice, Alpha, Beta, Gold Master, optional post-launch patch) with clear acceptance rules: After the inspection period has expired, a milestone is automatically deemed accepted if there is no response (§ 640 para. 2 BGB). The contract text explicitly clarifies that only objective-technical criteria such as functionality or freedom from crashes are justiciable – subjective artistic discretion such as "fun factor" is not a suitable standard for acceptance.

Further components

Engine/middleware license compliance (e.g., revenue thresholds for Unity or Unreal Engine) and disclosure of used open-source components – both as a mandatory confirmation in the wizard.
Kill-fee option for early termination after milestones have already been accepted.
Limitation of liability to intent/gross negligence and foreseeable damage.
For online/multiplayer functions with user accounts or telemetry, the contract refers to our data processing agreement (DPA) template – see also Privacy Policy and DPA: two building blocks, one goal.

Important

Transfer of rights, recoupment, and international jurisdictions are high-liability areas, especially with six-figure advance payments. In such cases, we recommend legal review before signing the contract (Finding a lawyer).

Was this article helpful?