People sometimes ask when we plan to grow. The honest answer is that we have thought about it, and we keep choosing not to. The way we work depends on being a certain size, and we like the way we work.
The size of a conversation
There is a limit to how many people can sit around one table and still have one conversation. Past that limit the table splits. Two conversations start, then three, and someone has to carry news from one end to the other.
Studios hit the same limit. Once a project has more people than one conversation can hold, it needs someone whose job is to pass messages between the client and the people doing the work. That role is useful in a big agency. It also means the person who will actually design your site has never spoken to you.
We stay at the size where that role is not needed. Every person who works on a project is someone the client can talk to directly.
Everyone at the table
In practice, that means the designer who presents a concept is the one who drew it. The developer who joins the review is the one who will build it. When a client has a question about why a column is a certain width, the person who chose that width answers.
It sounds simple, and it changes a lot. Feedback arrives with its reasons intact. Nobody has to translate "make it pop" through two layers of people before it reaches a file. And the client hears the trade-offs from the people who have to live with them.
The shortest path between a question and an answer is a person who knows.
It also changes how we work with each other. There is no hand-off from strategy to design to build, because the same small group sees the project from the first workshop to the day it goes live.
What we say no to
Staying small means saying no more often than we would like. We take on a limited number of projects at a time, and when the calendar is full, it is full. We would rather start a project a month later than start it with half our attention.
It also means we do not take on every kind of work. If a project needs a team much larger than ours for a long stretch, we say so early and, where we can, point to someone better suited. That conversation is easier to have in the first week than in the third month.
What small costs
There are real downsides, and we try to be open about them. We cannot staff a project overnight. We cannot run a dozen workstreams in parallel. If someone on the team is away, the project schedule accounts for it, because there is no bench of people waiting to step in.
We plan around these limits instead of hiding them. Timelines are agreed at the start and shared week by week. If something slips, the client hears it from the person it slipped for, along with what we are doing about it.
Why it stays this way
The work we are proudest of came from close conversations: a founder and a designer looking at the same screen, a developer suggesting a simpler way to do something in the middle of a review. Those moments do not show up in a process diagram, and they get rarer as teams get bigger.
So we keep the table small. It limits how much we can take on, and it is the reason the work turns out the way it does.