How we work
A clear question. The right people. Something you can play.
Turn a promising premise into a focused set of player actions, then build the smallest playable version that can answer the important questions.
Design pillars and player journey / Core-loop and mechanic specification
A new idea, an uncertain mechanic, or a project that needs a clearer playable direction.
Discuss this focusConnect story, place, character, and visual language so every part of the game feels as though it belongs to the same world.
World premise and narrative framework / Visual development and mood direction
A new intellectual property, an early vertical slice, or a world that needs a coherent identity.
Discuss this focusTranslate design into responsive mechanics, practical tools, and a technical plan that fits the project's constraints.
Technical discovery and risk map / Gameplay systems implementation
A mechanic that needs engineering, a prototype ready for structure, or a defined gameplay feature.
Discuss this focusShape a defined contribution around your project and team. Agree on ownership, interfaces, and review points, then work through a shared production rhythm.
Scoped work package and responsibility map / Milestone and review plan
A studio that needs a focused partner for a system, level, prototype, or production workstream.
Discuss this focusGet clear on the player, the creative promise, the constraints, and the question this project needs to answer first.
A focused brief, shared priorities, and a practical first scope.
Build a small version early enough that the team can still change its mind. Put the important interaction in someone's hands.
A testable prototype with explicit questions and a decision on what comes next.
Develop the systems, places, and assets around a clear direction. Keep work visible and connect each milestone to a useful review.
Integrated work, documented decisions, and a build that reflects the agreed scope.
Watch how people play, investigate the friction, and check the changes. Testing runs through the process rather than waiting for the end.
Prioritized findings, revisions, and an evidence-led next step.
Yes. The proposed starting point is a focused discovery or prototype brief. Describe the feeling, player action, or uncertainty you want to explore; a complete design document is not required.
The co-development model is designed around a defined contribution. The first conversation should establish the current project, team interfaces, technical context, and the work that needs ownership.
Tell us about your engine, platform goals, existing tools, and the systems you need support with. The first conversation establishes the technical fit and the scope of a useful contribution.
We begin with the goals, constraints, and expected deliverables, then shape a scope that can be discussed clearly. Share any milestones or budget boundaries that should guide the conversation.