Why we stay a four-person team
The obvious next step we didn't take
The pitch from every consultant we've ever spoken to is the same. "You're leaving money on the table. Hire ten more engineers. Add project managers. Build the leverage." And for a while, looking at our pipeline, we believed it.
Then we did the math on what it would cost — not in salary, in attention — and we didn't.
What we'd be selling
Every additional engineer we'd hire would have to be as senior as the four of us, or we'd stop being able to promise the bar we promise now. Senior engineers who want to work at an agency are rare. Senior engineers who want to work at an agency and are good enough to ship unsupervised from day one are rarer still.
We know this because we are those people and we know how few others are. If we hired fast, we'd be selling "four Weblier engineers and six people learning how to be Weblier engineers." That's a different product, at a different price, with different outcomes.
The overhead nobody factors in
An agency of four has no process. We know what everyone is working on by walking over to their desk (or pinging them on Slack, since nobody has a desk in the same city). Decisions happen in a sentence. Nothing is blocked on a meeting.
At twelve, all of that breaks. You need a PM. You need a handoff doc. You need an internal escalation policy. The work hasn't changed; the overhead has. And the overhead gets charged to the client, one way or another.
We priced it out. At twelve engineers we'd need to raise rates by roughly 30% just to absorb the coordination tax. Our clients would notice. Some wouldn't come back.
The quality ratchet
The quiet thing about small teams is that the bar is the bar because everyone sees everyone's code. There's no back channel where someone's PRs quietly drop in quality because nobody's reviewing them. If Alex ships something sloppy, Nina sees it, Nina says something, it gets fixed. The ratchet only goes up.
Scale breaks the ratchet. Not all at once — gradually. First you stop code-reviewing every PR. Then you stop knowing the architecture of every project. Eventually a client calls and you have to ask a PM what's going on. That's the moment the agency stops being what it used to be.
What we do instead
We turn down work. We say no to things that aren't a great fit, and we say no to things that would need people we don't have. We refer out the overflow to friends we trust.
The number of projects we can take in a year is capped. The bar on each one isn't.
Four people, one sustainable rate
Our rule is simple: the four of us ship what the four of us can ship well. Some quarters that means six engagements, some it means three. We don't chase a headcount number or a revenue target that would force us into running more work than we can do properly.
Growth, for us, doesn't mean more engineers. It means better engineers, harder work, clients who care about the same things we do. That's the ceiling we're aiming at. We're nowhere near it yet.
