Building a Team of 26. Then Cutting It Back to 3.

When I started the team, there were 3 of us. Over four years we grew to 26. By the time we hit 26, we were spending more time managing the team than serving customers. That is the inflection point nobody warns you about: the moment when internal complexity starts costing more than external growth generates.

The symptoms were clear in hindsight. Meeting time doubled. Decision speed halved. The best performers were spending 40% of their week managing up, across, and down instead of doing the actual work. We had built a coordination machine that consumed its own output.

The cut to 3 was brutal but clarifying. We kept the people with the broadest skill range, not the deepest specialization. Generalists who could own outcomes end-to-end. The 3 remaining people produced roughly 70% of what the 26 had produced — because they had no coordination overhead and complete ownership of their domains.

The lesson: headcount is not leverage. Systems, processes, and ownership are leverage. Adding people without changing the underlying system just adds weight. The right question when you are growing is not 'who else do we need?' but 'what is slowing down the people we already have?'

I would not change the decision to cut back. I would change when I made it. I waited until the pain was undeniable. By then, 6 months of organizational momentum had already been lost. The better discipline is to set a headcount ceiling before you start hiring — and treat every addition as a decision that requires explicit justification, not a default response to growth.