How much does it cost to make a game? There is no useful single figure without knowing what the game needs to do, where it will run, and how much content it needs. A small browser experience and a multi-platform online game may both be called games, but their production needs are very different.
A better way to build a budget is to divide development into stages: concept and feasibility, prototype, vertical slice, production, polish, launch, and live support. Each stage should answer a specific question before you commit to the next. This makes the budget easier to understand and gives you a chance to change direction before a costly assumption becomes part of the finished game.
Build the budget around decisions, not guesses
A game budget is the cost of reducing uncertainty and then making the approved experience real. Early work tests whether the idea is understandable and feasible. Later work creates the full set of features, content, and technical systems. The total depends on how much work those decisions require, not just on the length of the game or the number of screens.
Before requesting estimates, describe the intended player or audience, the experience you want them to have, and the outcome the game should support. For a brand experience, that outcome might be product discovery, event participation, or a memorable interaction. A clear goal helps a development team recommend a fitting scope instead of pricing an undefined wish list.
Ask for stage-based estimates with assumptions and deliverables spelled out. For example, clarify whether a prototype includes placeholder art, whether a vertical slice includes sound, and which devices will be tested. An estimate is useful when you can see what it covers—and what it does not.
Concept and prototype: prove the idea is worth building
The concept and feasibility phase turns an idea into a testable plan. It can define the core interaction, audience, platform, visual direction, and technical risks. It should also identify what the project will deliberately leave out. The goal is not to produce a polished pitch deck; it is to decide what is worth testing and what evidence would support moving forward.
A paper prototype uses sketches, cards, or a simple facilitator-led exercise to explore rules and flow. A grey-box prototype uses rough shapes and minimal visuals to test movement, interaction, pacing, or navigation. Either can reveal that a mechanic is confusing or that an experience needs too many steps before anyone has spent time on finished art.
Set a clear question for each prototype. Can a new player understand the main action? Does the interaction work on a phone? Can the intended experience run in a browser? Review the result against that question, then decide whether to revise, test again, or stop. Prototype work is valuable precisely because it can expose a weak idea while changes are still manageable.
For a facilitated path through concept, testing, and development planning, see ASAYA's Develop an Interactive Experience program. It can help a team decide what to validate before committing to a larger build.
Vertical slice: prove the production approach
A vertical slice is a small but representative piece of the intended final experience. It may include one level, one interaction loop, or one short journey, with a closer-to-final mix of art, sound, interface, and technology. Unlike a rough prototype, it tests not only whether the idea works, but also how the team can produce it to the required standard.
This stage helps answer questions such as: Does the visual style hold up in the chosen engine? Does the interaction feel right on the target device? Are assets taking longer to create than expected? Can the game communicate the brand without interrupting play? A slice also gives stakeholders something concrete to review before they approve a larger production plan.
Keep the slice intentionally limited. It should represent the difficult or important parts of production, not quietly grow into a substantial first release. Agree on what will count as a successful test, who will review it, and what decision follows. If the slice changes the scope, revise the plan before moving on.
Production, polish, launch, and live support
Production is where the approved experience is built out. The team creates the remaining levels, interactions, assets, interfaces, and supporting systems. A content plan makes this stage easier to estimate: list what must be made, how many variations are needed, and which pieces can be reused. Reuse can reduce repeated work, but it still takes time to integrate and test each use.
Polish improves clarity, feel, and reliability. This may include tuning controls, improving feedback, refining animations, correcting visual inconsistencies, and testing across agreed devices. It is not an unlimited pass to keep adding features. Define a polish window and separate required fixes from optional enhancements so that finishing work does not become unbounded.
Launch includes preparing the build for its intended destination, checking the experience in that environment, and confirming that key flows work. A browser game, an app-store release, and an event installation have different practical requirements. Agree on who provides accounts, copy, art approvals, device access, and release coordination. Delays in those inputs can affect the schedule even when the development work is ready.
Live support is a separate decision, not an automatic extension of launch. You may need help fixing issues, updating content, or adapting the experience after release. Decide whether the game is a finite campaign or an ongoing product, and specify what support is expected, how requests will be handled, and what counts as new development.
The scope drivers that change the estimate
Platform affects both implementation and testing. A browser-first experience may need responsive layouts and checks in the browsers and devices you care about. A game intended for desktop, mobile, and consoles has more environments to account for. A kiosk or event installation may need to work with particular hardware and recover cleanly when something interrupts a session.
Art style and content volume are connected. A simple, graphic look may require fewer bespoke assets than a detailed world with many characters, environments, and animations, though any style still needs thoughtful execution. Count the content: levels, scenes, characters, items, dialogue, and variations. A short game with many unique assets can take more work than a longer experience built from a small set of reusable elements.
Multiplayer adds systems beyond the visible gameplay. Depending on the design, it can involve connecting players, keeping game states in sync, handling interruptions, and testing different network conditions. First decide whether players truly need to interact online, or whether a shared-screen, turn-based, or single-player design can meet the goal. Choose the simplest form that supports the experience.
The engine should fit the experience and the team's needs. Godot and Unity are options for game development, with the right choice depending on requirements such as target platforms, interaction, available tools, and team familiarity. Three.js is a JavaScript library for 3D graphics in the browser and may suit a web-based experience. The best option is not the most fashionable one; it is the one that supports the intended scope and can be maintained appropriately.
Reusable assets can help with some visual needs, but they do not remove integration work or guarantee a match with the project's style. ASAYA Games publishes game-ready 3D asset kits in Blender, FBX, and GLB formats on ASAYA Games. Treat asset selection as a production choice: confirm usage rights, technical fit, and whether adaptation is needed.
A practical checklist before approving the next stage
Use this checklist at each funding decision. The questions help keep a project focused on evidence and deliverables instead of assumptions.
- What specific question is this stage meant to answer?
- What will be delivered, and what is explicitly out of scope?
- Which platform, devices, and browsers are included in testing?
- How much original content is required, and what can be reused?
- What does success look like, and who has authority to approve it?
- What inputs must the business provide, and by when?
- What decision will we make when the stage is complete: proceed, revise, or stop?
Funding one stage at a time is not the same as refusing to plan ahead. You can map the whole journey and understand likely dependencies, while approving spend in increments. After each stage, review what was learned, update the scope, and authorize the next phase only if the evidence still supports it.
Where to start
Start with a short brief: the audience, the experience, the intended platform, the most important interaction, and the main unknowns. Then ask a development partner to recommend a first stage with defined outputs and a decision point. ASAYA's Browser Game Development work and other game work are scoped per project, starting with a concept and feasibility phase.
That first phase should give you a grounded view of what to test, what the next stage would involve, and which requirements are driving the plan. You do not need to settle every production detail before beginning. You do need a clear first question and agreement on what evidence will justify moving forward.
Frequently asked questions
Usually not as a meaningful project estimate. First clarify the core experience, target platform, and major unknowns; then scope an initial concept and feasibility phase.
No. A small, straightforward project may be validated with a prototype and a clear production plan. A vertical slice is useful when the art, technology, or production approach needs a realistic test.
Choose based on the experience, target platform, and team's ability to build and maintain it. Define those requirements first, then compare engines against them.

Written by
Daniel Lamberth
Founder & Creative Director at ASAYA Media. 15+ years across visual effects, motion, illustration, and software; author of Mastering FLUX.



