BRAND NEW COLORS
Small scopes at fixed fees, on a ladder where each rung credits toward the next. Start with the amount of certainty you actually have.
Each rung is useful on its own. Move forward within 60 days and the earlier fee comes off the next build.
A 90-minute working session where we pressure-test the idea together, followed by a written verdict.
A focused playable build that proves the core mechanic, tone, and world before anyone commits to more.
The prototype grown into a finished browser game built to be completed by a player and handed off cleanly.
Multiple chapters or scenarios, expanded original art, and optional light backend systems.
HOW THE CREDITS WORK: book a Concept Session and its $750 comes off your prototype. Book a prototype and its $4,500 comes off your finished game. Reaching a Standard game rung by rung costs the same $16,500 as walking in the front door.
Prices are published before we ever talk. Each rung credits fully toward the next within 60 days. Either side can stop after the prototype with nothing further owed.
One loop, one scenario, up to three screens. It is evidence, not a miniature promise of every feature someone can imagine.
A 50% prototype deposit reserves the slot. The balance is due at delivery, and deposits become non-refundable once scheduled.
Standard payments split 40 / 40 / 20. Content freezes at build week five so the game actually ships.
The client receives the finished game and a practical source handoff. Continued access is not conditional on a Care Plan or on keeping us as the developer.
These are separate offers with separate jobs: one adds a contained piece of game; the other keeps the existing build healthy.
Two to three weeks. One new scenario, chapter, or seasonal event built on the game’s existing systems.
Or $3,000 prepaid for a year. Hosting management, updates, and a couple hours of small changes each month.
Scope changes from project to project. The point of this section is to make the studio’s position clear before the agreement supplies the legal detail.
The client does. The commissioned game is handed over as a whole: the playable release, its project-specific content and custom assets, and a practical source handoff. The agreement names the exact legal form—an assignment, an exclusive license, or another arrangement suited to the project—because third-party tools and licensed components can affect the paperwork. That detail does not turn the game into a rental or make continued access depend on us.
The working browser release; project-specific writing, art, audio, data, and configuration; the current source; and the notes reasonably needed to run, host, or continue developing it. We also identify any open-source packages, stock material, fonts, models, or other third-party components whose original licenses still apply. The handoff should be usable, not ceremonial.
What the studio brought in and what a practice must be able to carry forward: pre-existing tools, general libraries, production workflows, internal prompts, methods, and accumulated game-design and coding knowledge. We also keep the ordinary learning that comes from doing the work better. We do not keep the client’s confidential material, characters, stories, community data, custom art, or distinct expression of that world.
Usually, yes at the level of general technique. Deeper game and coding dynamics are rarely born from one commission alone; they draw on patterns learned across games, software, and the wider field. If a project helps us improve a reputation system, save architecture, dialogue tool, or way of pacing choices, that learning can enter the practice. We do not resell your game, reskin your world, or reuse its protected and confidential material. If exclusivity around a genuinely novel system matters, name it before scoping so the agreement and price can reflect it.
Yes. The source and operating handoff are intended to make that possible. Another developer may still need time to understand the build, and third-party services may require their own accounts or fees, but you are not contractually locked to Brand New Colors for ordinary access, hosting, or future changes.
The game can live at a private link, on your domain, or at a public address. Publicity is separate from ownership: we show a commissioned game, name the client, publish screenshots, or discuss the process only with permission stated in the agreement or given later.
We use it to make the game and limit access to the people and tools needed for production. Private interviews, member information, internal documents, and unpublished history do not become reusable studio content. The project agreement can add stricter handling, deletion, or confidentiality requirements when the material calls for them.
AI assists with code drafts, art roughs, research organization, iteration, and deployment chores. Brand New Colors remains responsible for direction, review, integration, and the finished build. Machine assistance is not used as a reason to withhold the game from the client. Any material third-party restrictions that affect handoff or use should be disclosed rather than hidden inside the phrase “AI-generated.”
Then it did its cheapest possible job. For $4,500, you learned the idea’s real shape before committing five figures. You keep the prototype under its stated terms, and either side can stop with nothing further owed.
Plan for a kickoff hour, a short weekly check-in, and real consolidated feedback while the build can still change. Standard projects need one person empowered to settle conflicting notes. Expanded projects may also need scheduled access to subject-matter experts or a small playtest group.
Possibly none beyond a domain and basic hosting. Accounts, databases, analytics, paid APIs, licensed fonts, original music, or higher traffic can add third-party costs; those are identified during scope. The Care Plan is optional. It buys upkeep and small changes, not continued ownership or access.
Yes, when the game needs them. They change scope because they add systems, testing, content production, legal review, or ongoing services. We price those requirements before they quietly become obligations inside a fixed-fee build.
We decide whether it is a fix, a swap inside the agreed scope, or a new feature. Fixes are fixed. Equal-sized swaps can usually fit before the content freeze. New systems, new scenes, and new review rounds are quoted or moved into a Season Drop so the release date remains real.
The Niche Game Brief is a free nine-page worksheet for turning a community, story, or inside idea into a game concept worth building.