Quote template for game developers
Game scope grows by default. A level becomes three, a mechanic gets reworked after playtesting, a platform gets added because a publisher asked for it. Your quote should define each milestone as a build with a list of features that must be playable, and it should say that new features or reworked mechanics after approval are priced as change requests.
Say which engine and version you are building on, which platforms are in scope, and who handles certification. Engine upgrades mid-project and console submissions both cost real time, and neither belongs inside a fee that was calculated for a single PC build.
From
Prepared for
Details
Items
Notes and terms
Free, no account. Everything stays in this browser: we don't receive or store what you type.
The example lines and prices are illustrations. Replace them with your own.
What a game developer's quote should spell out
- Milestone builds, each with the features it must contain and a target date.
- Engine and version, target platforms and minimum hardware.
- Who supplies art, audio and design documents, and when.
- Whether platform certification and submission are included.
- Fee per milestone and any royalty or revenue share, with how it is reported.
- How change requests are estimated and approved.
Questions game developers ask
Fee or revenue share: which should a game developer ask for?
A revenue share only pays if the game sells, and many do not. If you take one, take it on top of a reduced fee rather than instead of one, and make sure the contract says how sales are reported and how often you are paid.
How do I quote a game when the design keeps changing?
Quote the first milestone, usually a prototype or vertical slice, as a fixed job and estimate the rest as ranges. Re-quote after the slice is approved, when the design has settled enough to price.
Should porting be in the original quote?
Only if it is definitely happening. Otherwise list it as an option with a rough estimate. Ports carry their own performance work and certification rounds, and they are easier to price once the main build exists.
Quote it, then invoice it, without retyping
In OIO a proposal belongs to its client and project. When it's accepted it becomes an invoice draft with the same lines, and the money view shows what is outstanding and what is paid. Free plan, no card.
Start freeAlso for game developers: invoice template and contract template. Quote templates for related trades: 3D artists, software developers, animators, music producers. Or browse all quote templates.