Game prototypes that answer a playable question.

Choose what to learn

We clarify the intended player, device, core action, feedback, and the uncertainty the prototype should expose. A puzzle rule, movement system, or short learning activity can provide a useful focus. We keep unrelated future features in a separate backlog.

Build enough to test

Temporary visuals and a short sequence may be appropriate. The scope states what is playable, what is simulated, and what is absent. A prototype is not presented as a nearly finished commercial game or proof of market demand.

Observe actual play

We agree a practical test method and record useful behavior: where players hesitate, what they understand, and what needs another iteration. Small samples can reveal concrete problems while leaving broader audience questions open.

Decide the next milestone

The handover can include the build, source as agreed, findings, and a prioritized next-step list. Production art, a vertical slice, additional platforms, and a full release are distinct projects with their own requirements.

Bring the concept and the question you cannot answer from a document alone. We can help define a small first test with a clear ending.