I run an over-ten-million-dollar company with 38 people. I used to run it with 320. I am not telling you headcount is virtue. I am telling you tiny teams with the right architecture beat large organizations still billing hours — and the trades are about to feel that gap in every market.
Why do tiny teams win now?
Because the cost of coordination collapsed. Work that required departments — reporting, production, fulfillment, glue tasks — now runs through systems and agents when data is connected and intelligence is applied end to end.
Large orgs add people to fix handoff problems they created. Tiny teams fix the handoff. That is the difference between a revenue engine and an agency pyramid — see The Agency Model Is Broken.
When does this matter to you?
It matters when you are competing against a national player or a well-funded startup while running a traditional back office. It matters when your margin shrinks every time you win a big account because fulfillment eats the profit.
It does not matter if you have not nailed the basics — answer the phone, show up on time, do what you said. Systems amplify excellence or amplify chaos. Soul first, then stack — Systems and Soul.
What large orgs get wrong
- Meetings as work. Coordination theater replaces customer outcomes.
- Heroics as strategy. Firefighters promoted instead of system builders — systems, not heroes.
- AI as department. Chat licenses instead of architecture — AI is not ChatGPT.
- Knowledge in heads. Bus factor everywhere; entity files empty while agents search competitors who documented truth.
What tiny teams get right
They hire A players who steward systems — the SME Inversion at team scale. They measure revenue per person without apology. They connect customer touchpoints so follow-up is never heroic.
My 38 are not doing smaller versions of 320 jobs. They build, improve, and govern an intelligence layer. Chris engineered it. Leaders operate it. That is Three Hands in production — builder, operator, steward.
Why large orgs hate this truth
Large organizations have careers built inside coordination overhead. Cutting overhead threatens identities — not only budgets. That is why incumbents dismiss tiny teams until a competitor ships faster at lower cost. By then the architecture gap is years wide.
Trades are especially vulnerable to this surprise: the contractor across town with a robot and a clean entity file is not a gimmick — it is a different cost structure. Pride in the trades means adopting leverage, not mocking it.
Large orgs confuse motion with progress. Tiny teams confuse leverage with laziness — then they win.
Proof, not theory
The full case study is From 320 to 38. I wrote it because conference stages are full of people who have never lived a restructure. Trades owners deserve the operator version — including the human cost.
When I speak for Women in HVACR or at contractor events, this is the slide that lands: your competitor's headcount is not your destiny. Your architecture is.
What tiny teams refuse
They refuse meetings that could be a shared scoreboard. They refuse custom everything when a repeatable offer serves the customer better. They refuse to hire before a loop is named. That refusal looks arrogant until you compare output — 320 to 38 was refusal at company scale.
Action
- Calculate revenue per employee today — and what it would be if glue work halved.
- List three handoffs that exist only because teams do not share data.
- Pick one workflow to systemize this quarter — not buy, systemize.
Tiny teams are not a aesthetic. They are an outcome of serious architecture. If you want help designing yours, work with me. If your association or peer group needs the wake-up call, book a keynote.