What Game Co-Development Is and How to Buy It

Co-development is not the same as outsourcing a deliverable. In an asset or discipline contract you write a spec, the studio goes away, and something finished comes back. In co-development the partner works in your repository, against your backlog, in your sprint cadence, usually with their own producer and tech lead sitting alongside yours. You are buying an extension of your team, not a package.

That distinction changes what you are buying and what can go wrong. Asset outsourcing fails when the spec was vague. Co-development fails when ownership is vague: two teams both think the other owns the build, or nobody owns performance. The upside is speed. A co-dev partner can add ten engineers and artists in weeks and take a whole feature vertical, which is not something you can do by hiring.

How co-development deals are usually structured

Most co-dev arrangements price a team rather than a deliverable: a named set of seats at a monthly rate, committed for a minimum term, usually three to six months. Ramp-up is real and worth planning for. A new co-dev team is rarely at full output before the second month, because the first weeks go on build setup, codebase orientation and getting review turnaround down to something workable.

The three structures you will see most often:

• Dedicated team: named seats, monthly rate, minimum term, your backlog and your definition of done. Highest coordination cost, highest throughput.
• Feature ownership: the partner owns one vertical slice end to end, such as multiplayer, the shop, or the console build, and delivers against milestones.
• Blended hybrid: a small embedded core plus surge capacity for art or QA that scales up around milestones and back down afterwards.

What to settle before the first sprint

• Who owns the build, who owns performance budgets, and who has final technical sign-off
• Source control, branching model, and whether the partner commits to trunk or to a fork
• Code review turnaround expectations in hours, since this is the single biggest drag on co-dev velocity
• Overlap hours per day, not just time zone. Four real overlapping hours is workable; one is not
• Security and NDA scope, including whether the partner can see the full repository or only their module
• Ramp-down terms. Co-dev contracts are easy to start and expensive to unwind if notice periods are long

What co-development costs

Co-dev seats are priced off the underlying discipline rather than as a separate product, so the useful reference is the market rate for the roles you are staffing. Typical market rates per hour: programming runs about $35-60 entry, $60-120 mid, $120-250 senior; 3D art runs about $30-50 entry, $50-100 mid, $100-200 senior. A monthly seat rate is normally those numbers times roughly 160 hours, with a discount for term commitment and a premium for senior leads.

Budget management overhead on top. Somewhere between 10 and 20 percent of your own team's time goes into reviews, syncs, and integration on a live co-dev engagement, and pretending otherwise is how co-dev projects end up behind schedule while looking fully staffed on paper.

Where co-development goes wrong

• Nobody owns the merge. Two teams commit into the same branches with different standards and integration debt compounds quietly.
• The partner is treated as a vendor rather than a team, so they are last to hear about design changes and rebuild the same thing twice.
• Senior people appear in the pitch and juniors appear in the sprint. Name the leads in the contract and require notice on substitutions.
• The engagement starts without a defined exit. Handover documentation and knowledge transfer belong in the contract from day one, not in the final month.

For the difference between co-development and full-cycle outsourcing in more detail, read full-cycle vs co-development. If you need a partner that owns the whole title instead, look at full production studios.