Contract Killers: What Developers Should Eliminate From Their Publishing Agreement.
summary
Look for the actual deal terms not the buzzwords: avoid handing over IP via one percent assignment or perpetual grants, insist on carving out proprietary tools, prefer an exclusive license with a return mechanism after a fixed term (typically five to ten years), ask for deemed approval (14 days) on milestone builds so payments don’t stall, require clear deliverables for each platform and who pays for ports, and limit publisher deductions to verifiable third‑party costs rather than vague internal expenses.
AI-written summary · about
chapters (9)
- 0:00Publishing contract pitfalls
- 5:46IP assignment risks
- 13:07Exclusive license dangers
- 20:10Territory and marketing
- 26:49Platform rights and porting
- 33:24Franchise rights
- 37:37Payment terms
- 43:17Revenue sharing
- 45:26Summary
related talks
40mHow to fail a software project fast and efficiently?
13mBuild license management into your pipelines
26mTen (Hard-Won) Lessons of the DevOps Transition
41mHow To Ship A Top-Tier Game Without A Top-Tier Budget: Practical Tips For Cost-Effective.....
43mLibrary Developer Confidential
05mKill the Project. Build a Team.
38mWhen Software Delivery Goes Wrong
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling