What is game co-development?
In full outsourcing you hand the whole game to a studio. In co-development you keep part of the work and share the rest. Your team may own the game design and the art direction, and the external team builds the code, the tools or a whole feature.
In team extension the outside developers join your process. They take tasks from your backlog, attend your meetings and follow your rules for code. Both models fit new games well. You keep control of the product and you can move faster.
When does an external team make sense for a new game?
- A fixed deadline. A launch date, a publisher milestone or a festival demo is close, and your team cannot finish all the work in time.
- Missing skills. You need people who know a given engine, web builds, shaders, multiplayer or performance on weak phones.
- A new platform. You want the game on the web, on mobile or on desktop, and nobody in your team has released a game there yet.
- A prototype. You want to test an idea quickly and keep your core team on the current project.
- A peak in production. Content, levels or ports need more people for a few months, and you do not want to hire full time.
If you have no team and nobody to lead the project on your side, it is usually better to ask a studio for full development.
Which cooperation model should you choose?
- Full development. The studio builds the whole game from your brief. You approve the milestones and own the result. This works when you have a clear idea and no production team.
- Co-development. You and the studio split the game into areas. Each side owns its part, and both teams work to one shared plan.
- Team extension. Developers from the studio work as members of your team, in your tools and your process. You lead the work.
- Prototype first. The studio builds a short playable prototype. After it you decide whether to continue, change the idea or stop. This is the safest start for a new idea.
You can also change the model during the project. Many teams start with a prototype, move to co-development during production and use team extension for later updates.
How to split responsibilities
Most problems in co-development come from unclear ownership. Before the work starts, write down who decides and who builds each part of the game.
- Product decisions. Game design, scope and priorities. Your side usually keeps them.
- Technical decisions. Engine version, architecture, libraries and the build pipeline. Agree on one person who has the last word.
- Features. For each feature, name one team that builds it and one person who accepts it.
- Art and audio. Who creates the assets, who adds them to the game and in which format.
- Testing. Who tests each build, on which devices, and who decides that a bug blocks a release.
A simple table with the areas, the owners and the person who approves the work is enough. Keep it in a shared document and update it when the scope changes.
IP and contracts at a general level
We are not lawyers, so treat this list as topics for a talk with your own legal advisor.
- Who owns the code, the assets and the game design created during the project, and when the rights pass to you.
- What each side brings from before the project, such as engines, tools or code libraries, and on what terms you can use it.
- Confidentiality rules, especially when you have not announced the game yet.
- How you accept a milestone and what happens when it needs fixes.
- How either side can end the cooperation and what the studio hands over at that moment.
In our guide on outsourcing we write more about milestones and collaboration with a studio, source code and store accounts.
The first weeks: onboarding the external team
Plan the first weeks with care, because the pace of the whole project depends on them. Treat them as a small project of their own.
- Access. Before the first day, prepare accounts for the repository, the task tracker, the chat, the build server and the test devices.
- Repository and large files. Agree on the branch model. For art and audio in Git, look at Git LFS. With it you keep only text pointers to large files in the repository, and the files themselves sit on a remote server.
- Code standards. Share the style guide, the folder structure and the rules for code review. If you have none, write short ones together in the first week.
- A first small task. Give the new team a real feature that is small. You will see how they work with your code and your review process.
- Communication cadence. Agree on a short daily update in writing or a short call, a weekly planning meeting and a demo at the end of each sprint. Pick one main chat channel and one place for decisions.
Name one contact person on each side. These two people answer questions, unblock work and keep the plan up to date.
Milestones and builds
Split the project into milestones that you can play. Each milestone should end with a build that your team can install or open and test.
- Prototype. The core loop works and you can judge whether the game is fun.
- Vertical slice. One level or one mode at the final quality.
- Content complete. All features and content are in the game.
- Release candidate. Only bug fixes, tests on target devices and the requirements of stores or web portals are left.
Set up automatic builds early. If you build the game automatically after each merge, both teams test the same version and find problems sooner.
How to keep quality high
- Review code from both teams with the same rules. With shared reviews, both teams also get to know the whole codebase.
- Agree on a definition of done. For example, the feature works on target devices, has no known blocking bugs and has passed review.
- Track performance from the start. In every milestone, measure frame rate, memory and loading time on the weakest target device.
- Play each build together. In a short shared playtest every week you catch design problems early.
- Keep the technical documentation short and current, so a new person can start without long calls.
Red flags when choosing a co-development partner
- The studio promises a full plan and a fixed date before it has seen your code, your design or your tools.
- Nobody can show you playable builds or code from earlier projects, even in a short call.
- You can talk only with sales and never with the developers who will work on your game.
- The studio wants to work only in its own repository and tools and does not give you access.
- There is no clear answer about who owns the code and the assets.
- People in the team change often, and nobody can explain how new members learn the project.
Our guide on choosing a game development studio lists more questions to ask before you sign.
How to finish the cooperation or hand over the work
Plan the end of the cooperation at the start. Then the change goes smoothly, whether you release the game, your team takes over or you stop the project.
- All code, assets and build scripts are in your repository, with the full history.
- Your team can build the game on your own machines or build server without help from the studio.
- You have documentation of the architecture, the build process, known issues and the next planned tasks.
- The external team runs a few handover sessions and walks your developers through the code.
- You agree on a short support period after the handover for questions and urgent fixes.
Working with Codeward
Codeward is a game studio from Kraków with many client projects behind it. We join new game projects as a full development team, as co-developers or as an extension of an existing team. We work in Defold for web, mobile and desktop. Our team also includes experienced Unity and C# developers, so we are at home in projects built with different engines. If you plan a new game, send us a short description and tell us which model you have in mind.