I Will build a playable Unity or Godot prototype of your game idea

What a prototype is for

Not to prove you can make a game — to find out whether this one is worth making. So the prototype targets a single question, usually the core loop, and everything that does not serve that question is deliberately absent: menus, save systems, settings, art polish.

What you get

• A playable build for desktop or web, plus the full project in Unity or Godot.
• The core mechanic implemented properly enough to judge: input, feedback, difficulty curve, and a win or lose condition.
• Placeholder art that reads clearly — coloured geometry with distinct silhouettes — rather than grey cubes.
• A short written read on how it plays: what works, what fights the player, and what I would change next.

How I work

We agree the single question first, in one sentence. Then I build the smallest thing that can answer it, usually within days, and you play it. Feedback goes into the next build rather than into a backlog. Godot suits 2D and fast iteration; Unity suits 3D and console paths — I will recommend one based on your idea rather than my preference.

What is deliberately not included

Final art, audio, monetisation, multiplayer, store submission and long-term progression. Those belong to production, and building them before the loop is proven is how prototypes become expensive dead ends.

What I need

A paragraph on the idea, references to two or three games whose feel is close, and the platform you care about most. If you have existing art or a design document, send it — but a paragraph is enough to start.

Turnaround and communication

First playable build inside a week, deliberately rough, because the point is to answer the question while changing course is still cheap. You play it, we talk about what felt wrong, and the next build responds to that. If the loop turns out not to be fun, you will hear that from me plainly rather than being sold more scope to fix it.