Product & systems design
We define the core loop, the progression, the economy and the failure states before anything gets built.
- Interaction and flow design
- Systems, balance and tuning
- Rapid prototyping and playtesting
Independent Game Studio
Khan GC is a game studio focused on tight, well-engineered interactive experiences. We handle design, development and live operations in-house, and we ship what we can stand behind.
Khan GC is an independent studio built around one idea: that small, well-made interactive products outperform large, unfocused ones.
We work across the full production chain — concept, prototyping, engineering, art, audio and post-launch operations. Rather than scaling headcount, we keep teams tight and give each discipline real ownership over what it ships.
Our output is deliberately narrow in scope. We would rather understand one system completely than half-build five. That constraint shapes how we plan, how we hire and how we decide when something is finished.
We operate remotely, document decisions in writing, and treat clear specs as part of the product rather than overhead.
We define the core loop, the progression, the economy and the failure states before anything gets built.
Client, backend and tooling are built by the same team, which keeps performance and iteration speed honest.
Visual and audio direction are treated as functional systems, not decoration applied at the end.
Once something ships, we run it — monitoring, tuning and updating against real usage rather than assumptions.
We test continuously rather than at the end, and treat a release process as part of the product surface.
We work with publishers and partners on defined scopes, with clear ownership boundaries and fixed decision points.
We write down the outcome first — what a user should be able to do, and what would make it fail.
Everything starts as a working prototype. If it cannot be played or used, it is not ready to be discussed.
Timing, feedback and balance get adjusted from observed behaviour, not from internal opinion.
Release is a starting point. We monitor, patch and iterate until the thing holds steady in the wild.
A tighter scope means a finished product. We cut aggressively up front so we can afford to polish what remains.
Frame time, input latency and load speed shape how something feels. They are treated as product requirements, not engineering cleanup.
If a decision matters, it exists in text with an owner and a date. Verbal agreement does not survive a schedule change.
Each discipline owns its output. We prefer people who can make a call and defend it to layers of sign-off.
Crunch is a planning failure, not a badge. We protect the pace because it produces better work over time.
If a system cannot be described in a paragraph, we either simplify it or stop and reconsider it.
We take on scoped engagements where our design and engineering teams can contribute from the start rather than being handed a finished spec. Typical arrangements run from a defined prototype phase through to live operation.
We prefer clear boundaries: who owns what, what counts as done, and where the decision points sit. Everything else is negotiable.
[email protected]We hire slowly and for specific gaps. If you work in design, engineering, art or production and prefer small teams with real ownership, we would like to hear from you.
Send a short note about what you build and how you work — a portfolio or a shipped project carries more weight than a résumé.
[email protected]Tell us what you are trying to build and what stage you are at. We reply to every serious enquiry, whether or not there is a fit.
[email protected]