Game Prototyping Services
Test, Debug, Build & Repeat

A prototype tests whether a mechanic or concept works, usually with placeholder art and minimal polish. A vertical slice is a fully polished, representative section of the finished game, built to show what the final product will actually look and feel like. Prototypes answer "is this fun." Vertical slices answer "is this real."

A focused core mechanic prototype typically starts at $5,000 to $15,000 depending on platform and scope. A full vertical slice for publisher or investor pitching runs $25,000 to $75,000 depending on length and fidelity. Itemized quotes within 48 hours of a brief.

Yes. We review the GDD, identify the highest-risk assumptions worth testing first, and scope a prototype around answering those specifically rather than trying to build the entire document at once.

Yes. Networked prototypes tested against real latency conditions, not a same-room LAN test that hides the actual problems multiplayer games run into.

Yes. Full IP ownership of the prototype, its code, and its assets transfers to you on final payment. We retain no rights to reuse or reference the work.

Yes. Prototype code is often production-adjacent by design, and many of our prototyping engagements convert directly into full development contracts with the same team that built the original.

Unity for most fast-iteration prototypes given its rapid build cycle. Unreal when visual fidelity is part of what the prototype needs to prove. Godot for lightweight 2D concepts. We recommend the engine that answers your question fastest.

As few as possible. A prototype testing one mechanic in isolation produces a clean, trustworthy answer. A prototype testing five mechanics at once produces a muddy result where you cannot tell which mechanic caused the reaction.

Yes. Publisher and investor-facing prototypes are scoped differently from internal validation prototypes, with the polish and pacing calibrated to hold an external audience's attention in a pitch meeting.

Yes, always, before any concept details are shared. Signed before the first substantive conversation, not after we have already heard the pitch.

The playable build, source files, a playtesting findings report, and an honest recommendation on next steps. What is included beyond that is scoped to the specific brief.

Two structured iteration rounds based on playtesting findings are standard. Additional iteration rounds are scoped and priced if the findings suggest the concept needs more testing before a decision can be made responsibly.

Yes. Structured internal playtesting with documented findings is a standard part of every prototype engagement, not an optional add-on.

A prototype tests whether an idea works, often disposably. An MVP is a minimum but real, shippable version of the product, built to be shown to actual players or investors and potentially to become the foundation of the live product. Prototypes are disposable by design. MVPs are not.