What Should Indie Devs Outsource?

Outsource bounded, specialist, one-off work where quality gaps show: capsule/key art, music and sound, trailer editing, localization, porting. Keep the unbounded and identity-defining work: game design, the core loop's feel, and anything you'll iterate on weekly. The rule: buy products (defined deliverables), don't rent hands for work you can't yet specify. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

The high-leverage buys

The best outsourcing targets share a profile — specialist craft, bounded scope, visible quality gap: the Steam capsule (a specialist's version measurably outconverts yours), music (composers are cheap relative to their impact), trailers (editors who cut game trailers weekly beat your first attempt), localization (translation is a profession), and console porting (certification knowledge you'd pay dearly to learn once).

Each is a defined deliverable you can evaluate on receipt — which is exactly what makes them buyable. A few thousand dollars across these five often lifts a game's commercial ceiling more than six months of additional dev time.

What stays in-house, almost regardless

Keep whatever you iterate on continuously: the core mechanic's feel (tuning is daily and forever), game design (outsourced design is someone else's game), and systems so woven into everything that handoff costs exceed the work (your save system, your engine glue). Iteration speed is the indie advantage; outsourcing the iterated thing surrenders it.

Also keep — at least at first — the things that build your taste: writing your store page, cutting your first trailer draft, even rough art direction. You can buy execution later, but only after doing it badly once do you know how to brief and judge it.

Buying work well is its own skill

Good outcomes are specified: a brief with references, exact deliverables and formats, revision rounds, rights, and deadlines. Start every new contractor with a small paid test, pay promptly (the good ones choose clients too), and budget your own time for the management — review rounds and integration are real hours the quote doesn't include.

Timing matters: outsource against a stable target ('the game's style is locked; here's the guide') rather than mid-churn, or you'll pay revision rates for your own indecision. The cheapest contractor engagement is the one whose inputs stopped moving before it started.

Decide how you'll know it's working

Every project needs a definition of done that isn't a feeling. Pick the few signals you'll trust — playtesters finishing the demo, crash-free sessions, wishlists per week — and check them on a schedule. Otherwise you'll steer by whichever anxiety is loudest that day.

This is also the honest defence against endless polishing. When the signals say players get through it, enjoy it, and nothing breaks, the feature is done. Move on.

Scope is the boss fight

Almost no indie game dies from bad code or bad art. They die from being half of a too-big idea. The skill that separates shipped games from abandoned ones is ruthlessly matching the design to the time and energy you actually have — not the time you wish you had.

Write down your honest weekly hours, halve them for life's interruptions, and scope to that. A small game that exists beats a big game that doesn't, every single time.

Close the loop with real players

Advice gets you to a sensible starting point; only real player behavior tells you if it worked. Ship the change, then watch what actually happens — the reports that come in, the errors that spike or vanish, the place sessions end.

Make that loop short. When a player can report a bug in ten seconds and you see it with logs attached, you stop guessing what to fix next. Tight feedback loops are the closest thing indie development has to a cheat code.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Scope to the hours you really have, then ship the small game that fits them.