K Khan GC

Independent Game Studio

We build games thathold up under a thumb.

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.

Discipline
Design · Engineering · Live Ops
Model
Independent, self-funded
Team
Small, senior, distributed
Contact
[email protected]
01

The studio

Est. as an independent practice

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.

Focus
Interactive products, end to end
Ownership
Independent, no outside control
Structure
Small cross-functional teams
Working model
Remote-first, written by default
Engagements
In-house production and partnerships
Contact
[email protected]
02

Capabilities

What we actually do in-house
C·01

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
C·02

Engineering & platform work

Client, backend and tooling are built by the same team, which keeps performance and iteration speed honest.

  • Cross-platform client development
  • Backend services and data pipelines
  • Internal tooling and build systems
C·03

Art, audio & feel

Visual and audio direction are treated as functional systems, not decoration applied at the end.

  • Interface and interaction design
  • 2D/3D asset production
  • Audio design and feedback tuning
C·04

Live operations

Once something ships, we run it — monitoring, tuning and updating against real usage rather than assumptions.

  • Telemetry and performance monitoring
  • Release management and rollouts
  • Ongoing balance and content updates
C·05

Quality & release engineering

We test continuously rather than at the end, and treat a release process as part of the product surface.

  • Automated and manual QA
  • Device and platform coverage
  • Store submission and compliance
C·06

Partnership & co-development

We work with publishers and partners on defined scopes, with clear ownership boundaries and fixed decision points.

  • Scoped co-development
  • Technical and design consulting
  • Production support
03

How we work

01

Define the target

We write down the outcome first — what a user should be able to do, and what would make it fail.

02

Build the smallest version

Everything starts as a working prototype. If it cannot be played or used, it is not ready to be discussed.

03

Tune against real use

Timing, feedback and balance get adjusted from observed behaviour, not from internal opinion.

04

Ship and operate

Release is a starting point. We monitor, patch and iterate until the thing holds steady in the wild.

04

Operating principles

The rules we do not trade away
P·01

Scope is a feature

A tighter scope means a finished product. We cut aggressively up front so we can afford to polish what remains.

P·02

Performance is design

Frame time, input latency and load speed shape how something feels. They are treated as product requirements, not engineering cleanup.

P·03

Decisions get written

If a decision matters, it exists in text with an owner and a date. Verbal agreement does not survive a schedule change.

P·04

Ownership over approval

Each discipline owns its output. We prefer people who can make a call and defend it to layers of sign-off.

P·05

Sustainable by default

Crunch is a planning failure, not a badge. We protect the pace because it produces better work over time.

P·06

No unexplained complexity

If a system cannot be described in a paragraph, we either simplify it or stop and reconsider it.

05

Working with us

Two ways in
Partnerships

Co-development & production

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]
Careers

Joining the studio

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]
Contact

Have a scope worth discussing?

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]