First deliverable
A game or interaction brief that identifies the player loop and the smallest playable proof.
Who this is for
Teams exploring an original game concept, interactive experience, or technical art and gameplay prototype.
What the work can include
- A focused game or interaction brief that identifies the player loop and the smallest playable proof.
- The agreed prototype work: gameplay systems, scenes, assets, save behavior, or a browser/native build.
- A playtest or review handoff with the known limits of the current slice.
How we work together
Clarify the player, core loop, reference constraints, target platform, and what the prototype needs to prove.
Build and review the smallest playable version before expanding content or systems.
Test the agreed experience, record the remaining production work, and hand over the sources and evidence in scope.
What to prepare
- A concise concept, target player, gameplay references, and any original-world or art direction constraints.
- The target platform, input devices, distribution plan, and whether persistence or multiplayer is in scope.
- Confirmation that supplied assets, names, and reference material can be used for the intended purpose.
Boundaries
- A prototype or vertical slice does not establish commercial readiness, audience demand, performance across all devices, or a release schedule.
- Third-party intellectual property, likenesses, trademarks, and licensed assets require appropriate rights and review from their owners.
- Online services, store approvals, ratings, moderation, and long-term live operations require separate planning when relevant.
Questions about this service
Does a prototype mean the game is ready to sell?
No. A prototype or vertical slice does not establish commercial readiness, audience demand, performance across all devices, or a release schedule.
Can we use existing characters or licensed assets?
Third-party intellectual property, likenesses, trademarks, and licensed assets require appropriate rights and review from their owners.