Question 1

How Can Small Game Teams Scale Production With Outsourcing Partners?

Accepted Answer

Start with the disciplines that have clear deliverables: art, animation, audio, localization and QA. Each can be briefed, counted and accepted without a designer in the loop every day. Keep design and core engineering in house, because work that changes weekly costs more to brief than to do. Brief with reference images, a style guide and the technical budgets. Then grow one vendor from a paid pilot into a standing relationship, rather than spreading the same money across four studios that each have to learn your game.

Studios listed here that take this work include Fox3D Consulting, Somatone Interactive, The Audio Guys and Leartes Studios.

Question 2

What should a small game team outsource first?

Accepted Answer

Start with art. It is the most specifiable work, the hardest to staff part time, and it can be accepted against a reference image without a designer in the loop every day. Animation, audio, localization and QA follow for the same reasons: each is finite, each needs a specialist you could not keep busy full time, and none of them blocks daily development while you wait. Keep design, the core loop and anything still being prototyped in house. The test is whether you could write down what done means today. If you could not, the work is not ready to leave the building.

Question 3

How do you write a brief an outsourcing studio can quote from?

Accepted Answer

A quotable brief has five parts: a counted deliverable list, reference images or clips showing the target quality, the technical constraints such as engine, polygon and texture budgets, naming conventions and file formats, the dates, and the acceptance criteria. Say what the work is for, because a studio that understands the context catches problems you did not specify. Include one finished asset from your own project if you have one, since it is worth more than a page of adjectives. Send the same brief to every candidate so the quotes compare line by line. The brief generator walks through the same structure.

Question 4

How many outsourcing vendors should a small team run at once?

Accepted Answer

One at a time, until the first is routine. Every active vendor costs a standing share of a producer's week in briefing, review and integration, and a small team has one producer at most. Two vendors on unrelated disciplines is manageable once the first relationship needs no explaining. Four vendors on the same budget means four onboardings, four style calibrations and four sets of files arriving in different conventions. Grow the vendor that works instead: a studio on its third package with you needs a shorter brief and lands closer to the target on the first pass.

Question 5

When should a small team move from outsourcing to co-development?

Accepted Answer

Move to co-development when the work stops being specifiable, which is when the tasks you want to send change weekly, touch the core loop, or cannot be separated from your codebase. Co-development buys capacity inside your project, but it needs someone on your side to plan the external team's week, review daily and unblock them across a time-zone gap. Small teams rarely have that person spare, so the honest sequence is to outsource specified packages first and open the repository only once a producer exists to run it. A technical gap in your own build is the common exception.

Question 6

How does an outsourcing budget scale as a small team grows?

Accepted Answer

Budget from an asset list and a schedule rather than a monthly figure, because outsourcing cost is a discipline rate multiplied by staffed weeks. Add the three things small budgets miss: revision rounds beyond the contracted number, your own briefing and integration time, and the ramp-up weeks where a new team is slower than it will be later. Scale by extending the vendor you already trust rather than adding another, since the second package with the same studio costs less to brief. Budget the paid pilot explicitly, because you will pay for it either way.

How Can Small Game Teams Scale Production With Outsourcing Partners?

What should a small game team outsource first?

How do you write a brief an outsourcing studio can quote from?

How many outsourcing vendors should a small team run at once?

When should a small team move from outsourcing to co-development?

How does an outsourcing budget scale as a small team grows?

Small studios that take art, animation, audio or QA packages

Where to go next

Other questions buyers ask

Ready to shortlist studios?