What it really takes to ship a game people finish — how budgets are set, why you prototype first, which engine fits, and where the money is made after launch.
Most people ask us what a game costs before they ask what it should do — which is understandable, but backwards. A game's price is downstream of a hundred design decisions, and the honest answer to 'how much' is always 'it depends on the loop, the platform and the polish'. This guide walks through the decisions that actually move the number, so the quote you eventually get makes sense rather than arriving as a mystery.
Prototype before you commit real budget
The single most expensive mistake in games is building a full production of something that isn't fun yet. You can't design your way to certainty on paper — the core loop either feels good in your hands or it doesn't, and you only find out by playing it. So we start with a short prototype phase: a rough, ugly, playable version of the one thing the whole game rests on. If the loop lands, you scale up with confidence. If it doesn't, you've spent a few weeks finding out instead of your entire budget. It's the cheapest risk you'll ever buy down.
What actually drives a game's budget
Four things, mostly. Scope — how many levels, systems and hours of content. Fidelity — a stylised 2D mobile title is a fraction of the art and engineering of a high-detail 3D world. Platforms — shipping to iOS, Android, Steam and web each carries its own build, testing and submission work. And backend — leaderboards, matchmaking, cloud saves and anti-cheat are real infrastructure, not a checkbox. In our experience prototypes start around $5k, polished casual titles typically land in the $15k–$50k range, and anything larger is planned and quoted milestone by milestone. Every milestone gets a fixed price before it starts.
Choosing an engine: Unity, Unreal, or web
There's no universally right engine, only the right fit for your title. We use Unity for most mobile and cross-platform work — its tooling and asset pipeline suit fast iteration and the platforms most first games target. Unreal earns its place on high-fidelity 3D, where its rendering does heavy lifting you'd otherwise pay engineers to reproduce. For instant-play experiences that live inside a browser or a messaging app, web tech like PixiJS or Three.js is the honest answer. The choice follows the game; we won't push you onto an engine because it's the one we felt like using this quarter.
Monetisation, without ruining the game
The fastest way to kill retention is to bolt aggressive monetisation onto a game that hasn't earned it. Our order of operations is fun first, revenue second: design a loop players genuinely enjoy, then build a balanced economy across ads, in-app purchases and battle passes that respects their time. The players who enjoy a game are the ones who spend on it — so a well-tuned economy and good retention aren't in tension, they're the same project. If a monetisation idea makes the game worse to play, it makes the game worse to earn from too.
The work doesn't stop at launch
For live games, launch is the starting line. Retention and revenue live in what comes after — events, seasons, balance passes and fresh content that give players a reason to come back next week. This is live-ops, and it's where a healthy game separates from one that spikes on release day and flatlines by Friday. Every build we ship includes 30 days of post-launch support for fixes; beyond that, a live-ops cadence is what keeps daily active users climbing rather than draining. Plan for it in the budget from the start, not as an afterthought when the numbers dip.
You own the game outright
This matters more than it sounds. On every project you own the code, the art and the IP in full, assigned to you in writing, living in your own repositories and store accounts. That means the finished game is genuinely yours to publish, update and build a sequel on — with us or with anyone. Ownership is one of the twelve questions we'd tell you to ask any studio before signing, and the only acceptable answer is an unqualified yes.
A good game starts as a small, honest question — is this loop fun? — and everything else is scoped from the answer. If you've got an idea and want a straight read on what it would take, our game development service begins with exactly that prototype-first conversation, and you can tell us about the game to get a dated plan and a fixed first milestone. No mystery, no meter running.
Code Craft Engineering
Games Team at Code Craft — the team behind our published work and products and the 39-plugin product suite.
