the minimum viable firm

what changes when serious work stops needing a big team to hold it

11-Jun-26

The cost of producing a serious deliverable fell hard, and the org chart has not caught up.

You have seen the old shape. A dozen people on a piece of work that a handful now carry. The analyst whose real job is reconciling versions. The standing call whose only output is confirming everyone read the same file.

That shape existed for a reason. Coordination was expensive, so you needed an institution to absorb the cost: payroll, offices, management layers, the overhead of keeping twelve people pointed the same way.

The cost moved. The shape has not.

the glass wall

That cost was a glass wall, and for most of a career, hitting it is simply what work feels like.

Walls like that come down quietly. Nothing announces the change. You keep routing around a constraint that stopped existing, and it feels like good judgment.

This cuts both ways. A firm that reorganizes around small pods gets the same arithmetic as the person who leaves to start one. The difference is who does the designing. Firms that move first keep the people who would otherwise go build it themselves.

where the value moves

Execution is becoming abundant. Judgment is becoming scarce. Every competitor has the same tools now, which crowds the market and pushes the edge somewhere the tools cannot reach.

Code production gives way to deciding what to build. Content generation gives way to knowing what matters. Financial modeling gives way to choosing the assumptions. Research synthesis gives way to holding a worldview steady under noise.

AI fluency is a depreciating asset. The gap between power users and everyone else narrows every few months. What compounds is domain expertise, relational trust, and the judgment of a team that has learned to work together under pressure. Those appreciate while tool skill expires.

the infrastructure gap

The “go build your own thing” genre diagnoses the shift well and ends at the diagnosis. There are essays, courses, and frameworks about deciding to go. There is very little on the mechanics of four people becoming a functioning unit.

The market is flooded with recipes. The kitchen is still missing.

A kitchen holds the parts a working team needs before it has revenue:

• Matching on role complementarity and aligned income floors. Networking events and personality quizzes test for neither.
• Governance written while everyone is still friendly. Operating agreement, vesting, exit protocol, decision rights, on paper before the first real fight.
• A shared operating stack installed early. CRM, decision log, financial dashboard, the AI workflows everyone actually agrees to use.
• A trust test with real money at stake. Watching people work under mild financial pressure tells you what self-report cannot.
• Distribution into one specific audience that shares a view of the problem.
• A dissolution protocol that lets people leave cleanly while exit is still cheap.

Every one of those is a solved problem inside a large firm. HR does the matching, legal does the governance, IT does the stack, and twenty years of shared reputation does the trust test. Strip the institution away and all six become the founder’s problem at once, in the same quarter, with no revenue.

what would settle it

The survival rate of small professional firms is poorly measured, and the number changes the recommendation entirely. A high base rate makes this a real alternative to a job. A low one makes it a bet that should be sized accordingly.

The productivity multiplier is unsettled too. Anecdote runs far ahead of measurement, and the gap between them decides whether four people is the right number or wishful thinking.

Nobody wanting this would look identical to nobody having built it yet, and the two have very different implications.

One real cohort would answer more than another year of reading, and it would produce the first honest failure data in a field that currently reports only its survivors.

what to do with this

If you run a practice, the question is what your team looks like at a third of its current size, and whether you would rather design that or have it happen to you.

If you are thinking about building something small, the hard part arrives before the first client does.

The arithmetic has already moved. Org charts are the lagging indicator.