Four Great Engineers Beat Twelve Good Ones

A founder showed me his post-raise hiring plan a few months ago. Twelve engineers in twelve months: two squads, a platform team, an engineering manager layer. It was a good plan. I'd have approved it myself in 2021. I told him to hire four people and keep the difference.

Not because the roadmap shrank. Because the math under every headcount plan quietly changed, and most hiring plans are still running the old constants.

The math that changed

Team size was always a trade between production and coordination. Every engineer adds output; every engineer also adds communication paths, and those grow faster than headcount. The old equilibrium landed where it did because one person could only produce so much, so you ate the coordination tax to get the production.

AI tools moved one side of that trade and left the other alone. A strong engineer directing agents now carries the throughput that used to justify a pod of three or four. But the coordination cost of a twelve-person org didn't drop a cent. Standups, handoffs, interface negotiations, the pull-request queue, the roadmap meeting about the roadmap meeting: all still priced in human hours. When production per person triples and coordination per person doesn't move, the optimal team gets smaller. That's not a philosophy. It's arithmetic.

And a smaller team of stronger people compounds in ways the spreadsheet undersells. Fewer handoffs means fewer places for context to die. Whole-system ownership means the person debugging the API also wrote the schema and remembers why. The velocity difference between a tight four and a coordinated twelve isn't twenty percent. On the teams I've run, it's routinely two to three times, in the small team's favor.

What the twelve-person plan actually buys you

I want to be fair to the big plan, because it isn't stupid, it's nostalgic. Headcount used to be the honest measure of seriousness. Investors read team size as traction. Managers read span of control as career progress. And redundancy was real risk management when every engineer held irreplaceable context in their head.

But look at what the extra eight hires cost in the AI era, beyond salary. You now need a management layer, so you hire managers, so you need alignment rituals, so your best builders spend mornings in meetings. Onboarding twelve people through a codebase moving at AI speed is its own project. And averaged-down talent doesn't average: on a modern team, output that has to be rewritten is negative work, and the engineer who ships confident, unreviewed, agent-generated code is a cost center with a good attitude.

The failure mode I keep getting called into is exactly this: a company that hired to its 2021 org chart, is paying 2026 salaries for it, and can't understand why a team of fourteen ships less than the founding three did. The answer is almost never effort. It's structure built for a constraint that no longer exists.

Role design changes too

Smaller teams don't just mean fewer of the same roles. The roles themselves reshape.

• The narrow specialist gets rarer. When agents cover breadth, a person who only does one slice of the stack creates handoffs a four-person team can't afford. You hire product-minded generalists with a deep spike, and rent true specialization when you hit it.
• Every senior hire is a force multiplier or a mistake. There's no crowd to hide in. One low-judgment engineer on a four-person team is a quarter of your company's output.
• The first leadership hire comes later, and matters more. Four strong owners barely need a manager. What they eventually need is a leader who shapes problems and sets appetite, which is a different job description than meeting-runner.
• Junior hiring becomes deliberate instead of volumetric. You still hire juniors, but as an investment you actively develop, with real mentorship, not as cheap capacity, because capacity is no longer what's scarce.

What this means for how you recruit

Here's the consequence nobody puts in the pitch deck: hiring four instead of twelve makes recruiting harder, not easier. Every single pick carries triple the weight. A tolerable-miss process, where one mediocre hire in ten washes out in the noise, becomes intolerable when the miss is 25% of the team. The bar goes up exactly as the volume goes down.

That's why I tell founders to spend on vetting depth what they used to spend on pipeline width. Fewer searches, run properly: org design first, so you know which four roles actually compose into a team; a real technical screen run by someone who has built these teams; a work sample that shows judgment with AI tools on real work. The savings from the eight hires you didn't make will fund the most rigorous search you've ever run, several times over.

This is the work I do: I design the small, sharp team and then I go find it, vetting every candidate personally. Here's how the team build works, or let's talk about your hiring plan →