Why we stayed small on purpose.
Four people can move faster than forty — if the four agree on what "done" means.
Every studio we’ve worked inside eventually hit the same inflection point: the moment headcount became the product. More people meant more coordination, more coordination meant more process, and more process meant the actual work — the code, the interfaces, the decisions — got thinner and thinner at the center.
So when we started code9, we made one structural decision before anything else: the team does not grow to meet demand. Demand shrinks to meet the team. We take fewer projects, scope them honestly, and say no early and often.
Headcount is the easiest thing to add and the hardest thing to subtract.
What small buys us
Speed, mostly — but not the sprint-board kind. When four people share one definition of done, review cycles collapse from days to minutes. There is no handoff tax. The person who scoped the work is the person building it, and the person building it is the person you talk to.
It also buys honesty. A small team cannot hide a bad estimate behind a resourcing spreadsheet. If something is going to slip, you hear it from the engineer, that day, with a reason attached.
What it costs
Scale, obviously. We will never run twelve projects in parallel, and we have stopped apologizing for that. The projects we do run get the whole collective — every discipline, every time zone, every opinion.