Why A Focused Few Beats A Crowd Every Time You're Tempted To Scale Headcount
Before you hire, check whether the gap is raw volume, because an AI stack can often absorb that without adding a voice to every decision. A focused few decides in minutes; a crowd adds meetings, approvals and competing priorities, so hire only when you need new judgment, not just more hands.
Revenue is up, the work is piling up, and the obvious answer is to hire. Then hire again. That's how most companies grow, and most founders never question it.
I do. The model I teach is deliberately never a crowd. It's a focused few, or one, moving with total clarity. That sounds like semantics until you watch what happens to decision speed once a team crosses from focused few into crowd.
Before you ask for money, know you're ready.
Your number, your terms, your system to find investors and your answers. One checklist, built by a founder who has been on both sides of the table.
SEND ME THE CHECKLIST →What changes when a team becomes a crowd?
A focused few, whether that's a solo founder with an AI stack or two or three aligned people, can make a real decision in minutes. There's no coordination layer between the idea and the action.
Past a certain headcount, that layer shows up whether anyone designs it or not:
- Meetings to align.
- Approvals to gather.
- Competing priorities to reconcile.
Decision speed drops even when every person is talented and well-intentioned. Larger teams can work, and plenty do. The point is that coordination cost is real, structural and easy to underestimate when you picture what more headcount will do for you.
The math is unforgiving. Three people have three working relationships between them. Fifteen people have 105. Coordination grows much faster than headcount does.
Should you hire or use AI?
Start by naming the gap. Much of the reason founders historically added people was raw capacity: more hands for more volume. An AI stack can absorb a large share of volume-driven work without adding a single voice to the coordination layer.
| The gap you're feeling | Better first move |
|---|---|
| More volume of repeatable work like research, drafts and reports | Extend the AI stack |
| A skill nobody on the team has | A contractor, scoped to one outcome |
| A function that needs a daily owner with real judgment | A hire, once the system is written down |
Before you hand anything off, to a person or a tool, learn when a task is ready to hand to an agent.
Find out what an investor will ask before they ask it.
The Raise Readiness Checklist walks you through everything you need before you ask for money.
GET THE FREE CHECKLIST →And write the system down before you add anyone; I explain why systems come before people, every time.
Two hypothetical businesses at the same revenue
Picture Business A at $5M in revenue with fifteen employees. That's about $333,000 in revenue per person. A routine pricing change that should take a day takes three weeks of cross-department alignment.
Business B does the same $5M with a focused team of three and a deep AI stack. That's about $1.67M in revenue per person. The same kind of pricing decision gets raised, made and shipped in one afternoon. Same revenue. Very different speed.
The objection: "Doesn't real growth require real headcount?"
At a large enough scale, yes. Headcount is sometimes the right call. The point is that the threshold for needing it is much higher than founders instinctively assume, and a lot of hiring happens well before that threshold, out of habit or a feeling that growth is supposed to look like more people.
Hiring is also hard to reverse. A tool you can cancel next month. A person you brought on to fix a volume problem becomes a relationship, a salary and a seat at every decision.
What to do this week
Before your next hire, write down the exact capacity gap you're trying to close. Then ask whether extending your AI stack could close it without adding a voice to the room. A crowd isn't automatically stronger than a focused few. It's usually just slower, and the slowness compounds quietly until someone measures it.
Key takeaways
- Every new person adds coordination cost that rarely shows up in the hiring plan.
- If the gap is volume, extend your AI stack before you add headcount.
- Hire when you need new judgment, not just more hands.
Frequently asked questions
Should I hire an employee or use AI?
Name the gap first. If it's repeatable volume like research, drafts or reports, extend your AI stack. If you need a skill nobody has, scope a contractor. Hire when a function needs a daily owner with real judgment and the system is documented.
Why do bigger teams make decisions more slowly?
More people create a coordination layer of meetings, approvals and competing priorities, even when everyone is talented. A focused few can move from idea to action in minutes because nobody needs to be aligned first.
When does a small business need to add headcount?
When it needs new judgment, not just more capacity. That threshold usually comes later than founders assume, because AI can absorb much of the volume that once required hires. Add people once the system is written down and the role is clear.
Mike Nathan
Founder & CEO, Impero Ventures · Founding Partner, Exit 156 Capital
20+ companies. $170M revenue. $55M raised. 3 exits. 2 VC funds. 1M+ YouTube subscribers.
He doesn't just pitch investors. He founded two venture capital funds.
More about Mike →Got a real business and never raised?
The Raise Academy takes founders from frustrated and floundering to fundable and raising. Four weeks with Mike Nathan. Investor-ready, GUARANTEED.
The guarantee covers getting you investor-ready. No one can guarantee a raise.