Go to any industry event and listen to how owners size each other up. The first question is always the same: "How many people do you have?" The number comes back, and everyone silently converts it into a status ranking. Two hundred beats eighty. Eighty beats twenty. Bigger team, bigger company, bigger deal — it's the oldest scoreboard in business.
I want to say the heretical thing out loud: that scoreboard is now backwards. Headcount is the last acceptable vanity metric — the one number owners still brag about that measures input, not output. And I've earned the right to say it, because I've stood on both sides of it: my company went from 320 people to 38, does over $10 million in revenue, and I will tell you plainly — downsizing might be the biggest upsize we ever executed. It made us the most powerful force in our industry, and it wasn't close.
Pride and ego versus efficiency and delivery
Let's be honest about what a big team gives an owner, because it's real: it feels like success. It photographs well. It sounds impressive from a stage. "We're three hundred strong" is an identity — and I understand the pull of it, because it was once mine.
But feel is not function. The market doesn't pay you for the size of your team. It pays you for efficiency, controls, consistency, and delivery — and on every one of those dimensions, the honest question is not "how many people do we have?" but "how much of what we do actually requires them?" Pride measures the org chart. Customers measure the outcome. When those two scoreboards conflict, ego picks the wrong one every time — and ego is exactly why most owners will read this essay, nod, and change nothing. It's frightening to shrink the thing you built your identity on. Both things can be true: the fear is real, and the math is unforgiving.
What downsizing actually eliminated
Here's the part nobody tells you: when we rebuilt around high-functioning technology, the things we eliminated were mostly not jobs. They were the frictions between jobs:
- The coordination tax. Handoffs, status meetings, meetings about meetings, the telephone game where every relay loses fidelity. Systems don't need to be synced up; they're never out of the loop.
- The management stack. Layers whose entire function was moving information up and decisions down. When the intelligence layer carries the information, the layers above it stop earning their drag.
- The diffusion of responsibility. In a 320-person company, every miss has a dozen plausible owners. In a 38-person company, there is nowhere to hide — and the remarkable thing is how much people rise when hiding stops being an option.
- Waiting. The invisible killer. Waiting for approvals, for the other department, for the meeting on Thursday. Small teams on strong systems make decisions in hours. We run fast because there is nothing structural left to run slow.
- Inconsistency. Human delivery varies with mood, tenure, and Tuesday. Encoded delivery — the systems our stewards run — produces the same standard every single time. That's the "controls" nobody associates with small teams, and it's the opposite of what people assume: we became more consistent as we became smaller.
The power of tiny teams with high-functioning technology
What's left after all that elimination is something the old model can't compete with: a small group of people, every one of them essential, every one of them a steward of systems that carry the volume. Talent density instead of headcount mass. Speed instead of process. A cost structure priced in tokens instead of layers — the economics I keep writing about, lived.
A tiny team with high-functioning technology isn't a smaller version of a big company. It's a different machine entirely — and it's faster, more consistent, and more profitable than the machine it replaced.
The proof is the operating data: more output than the 320-person version of ourselves, delivered faster, with fewer errors and a revenue-per-person ratio the traditional model cannot approach. Powerful force is not a slogan; it's what it feels like to compete against companies still paying the coordination tax we deleted.
Before you quote this at your leadership meeting
One honest warning, because I've lived the human side of this: downsizing as a panic move is not what I'm describing. Cutting people without building the systems first just gives you a smaller company that does less — the worst of both worlds. The sequence matters: infrastructure first, intelligence layer second, and the org finds its true size on the other side — with the truth told early and the people treated honestly. The goal was never small. The goal is right-sized on top of systems — small is simply what right-sized turns out to be.
So here's the question to sit with, the one ego hates: if you rebuilt your company today, on today's technology, with today's tools — how many people would it actually take? If the honest answer is far fewer than you employ, that gap is your coordination tax. Your competitors are already deleting theirs. The biggest companies of the next decade will be some of the smallest — and the owners who get there first will be the ones who traded the scoreboard that flatters them for the one that pays them.