Why "small" just became an unfair advantage
For a hundred years, being small meant being outgunned — no marketing team, no analyst, no support desk. AI agents quietly inverted that math. Here's what changed, and what to do about it this week.
The 1937 figure and the website example are Salim Ismail's framing on EP #258; the reading of what they add up to is this article's.
The disadvantage you were born with
You know the moment. A bigger competitor shows up with a polished campaign, a dedicated analyst, a support desk that answers in seconds — and you, running the whole operation from a laptop, wonder how you are supposed to compete with a company that can simply afford more people.
For as long as there have been businesses, size has been treated as a stand-in for capability. The more you could hire, the more you could do. Marketing, analysis, support, bookkeeping — those were departments, and departments meant payroll, and payroll meant you needed to be big enough to carry it. If you were a team of one to ten, you were told, gently or otherwise, that you were structurally outmatched.
So it is worth sitting with a claim made on Peter Diamandis's Moonshots podcast by his guest, Salim Ismail — co-author of Exponential Organizations — that the change now underway is useful whether you run a Fortune 500 or a one-person shop.2:42 That second half is the part nobody says out loud to small operators. The reframe is not for enterprises only. It may matter most to you.
Name the handicap precisely, because we are about to overturn it: you could never afford the departments. That was the disadvantage, the whole of it. Hold that thought — it is about to stop being true.
The 1937 rule that made big win
Bigness was never vanity. It was math. In 1937 an economist named Ronald Coase asked a question that sounds obvious until you try to answer it: if markets are so efficient, why do companies exist at all? Why not hire a freelancer for every task and skip the overhead?
His answer — in a paper called The Nature of the Firm, work that helped earn him a Nobel Prize, as Ismail notes4:02 — is that using the open market carries hidden costs. Finding the right supplier, negotiating, writing the contract, checking the work: economists call this coordination cost — the friction of getting separate parties to work together. For most of the last century, that friction was lower inside a company than outside it. Put people on payroll, under one roof, and you can simply direct them — no contract per task, no renegotiation every morning.4:02
That single fact is why firms grew. Every department you ever envied existed because it was cheaper to coordinate that work internally than to buy it on the open market each time you needed it. Scale wasn't a flex; it was the cheapest way to get reliable work.
There was always a crack in the logic. Clayton Christensen's innovator's dilemma observed that as a company grows, smaller rivals can deliver cheaper, simpler products the incumbent can't be bothered to defend.4:43 Small always had a latent edge. It just never had the tools to make that edge decisive — because the moment you tried to add a capability, you ran straight back into Coase: to do more, you had to hire more. Until now.
The rule just broke
Here is the pivot, in Ismail's words: "the whole thing breaks in the face of agentic AI."5:33 (An agentic workflow is just an AI system that carries out a multi-step task for you — not only answering a question, but doing the job end to end.) His example is mundane on purpose. To get a website built inside a company, you go through layers: a brief, meetings, a branding review, privacy and legal sign-off, an IT queue. Step outside that company, describe what you want to a free AI website tool, and you can have it live in roughly five minutes.5:33
When that becomes true, every approval layer that used to feel like prudence starts to look like a tax. A line Ismail quoted from a post he'd seen online puts it with uncomfortable precision:
"Building the feature is cheaper than having the meeting about the feature." A line Salim Ismail quoted · EP #258 · 6:06
That is the whole shift in one sentence. Coordination — the meetings, the alignment, the sign-offs — is now more expensive than execution itself, especially as AI keeps driving the cost of execution down.6:23 Plot the two costs against time and, at some point, they cross.
Be careful how big a claim this is. Ismail frames it hard — a Nobel-winning law that "no longer applies."5:33 Treat that as the provocation it is. Coase's logic still holds wherever trust, regulation, and relationships dominate; you cannot agentic-workflow your way past a medical license or a decade-long client bond. What has genuinely changed is the cost of making things — and for a small operator, that is precisely the cost that always hurt most.
Rent the department you used to hire
So what does the new math actually buy a one- or two-person business? It buys the departments you could never staff — not as hires, but as workflows you rent by the task. Take the most ordinary job there is: shipping a landing page. The old way and the new way are not a little different. They are different in kind.
| Stage | Inside a company | Outside, with an AI tool |
|---|---|---|
| Kick off | Write a brief, book a kickoff meeting, find a slot on five calendars. | Describe the page in a sentence or two. |
| Design | Wait on a designer; circulate a branding review. | Generate a first layout in minutes; nudge it. |
| Copy | Route to marketing; loop in revisions. | Draft and edit the copy in the same place. |
| Sign-off | Legal and privacy review; stakeholder approvals. | You read it once and approve it. |
| Ship | File an IT ticket to deploy. | Publish it yourself. |
| Elapsed | Days to weeks. | An afternoon. |
Illustrative comparison of the same task, grounded in the "build a website in ~5 minutes" example.5:33
The pattern generalizes past landing pages. Ismail's reframe is to stop organizing your business around a chain of command and start architecting it "around intelligence" — his phrase for building the operation on AI-native agentic workflows rather than headcount.0:35 For a micro-business that never had a chain of command to begin with, this isn't a wrenching reorganization. It's just permission to wire up capability without hiring for it.
| Function | If you hired it | If you rent it as a workflow |
|---|---|---|
| Marketing | A marketing hire or an agency retainer. | A content and ads agent that drafts posts, pages, and campaigns from a brief. |
| Analysis | A data analyst on staff. | A research agent that pulls, cleans, and summarizes the numbers on demand. |
| Support | A support desk. | AI front-line support that answers and triages, escalating only the hard cases to you. |
| Bookkeeping | A part-time bookkeeper. | Automated reconciliation that flags only the exceptions. |
| The catch | Salaries, management, fixed cost. | You still own judgment, taste, and the final review. |
Illustrative applications, not endorsements — each "agent" is a generic, off-the-shelf workflow you configure, never a specific product.
None of this means the legal entity disappears. Ismail is explicit that you still need an organization — but mainly as a container for purpose and liability, not as a coordination machine; the costs that made being a "real" company expensive fall away.6:35 Translated for you: a one-person LLC is enough of a container. You don't need the headcount that used to come bundled with the nameplate.
Now you're the unfair advantage
Put the pieces together and the conclusion is almost rude. If coordination is the expensive part, then the organizations carrying the most coordination — the layers, the approvals, the standing meetings — are now carrying the most dead weight. You are not. The absence of hierarchy you used to apologize for is the very thing that lets you move.
Ismail aims a deliberately provocative question at incumbents: is there a high-margin line in your business that a pair of people with off-the-shelf AI agents could replicate in 60 to 90 days?10:13 It's a provocation, not a forecast, and an honest reader should hold it at arm's length. Plenty of lines don't fall that fast — regulated work, trust-heavy relationships, anything where the moat is reputation rather than execution. And the same blade cuts both ways: if two people can come for an incumbent's line, two people can come for yours.
But turn the barrel around. The question the source pointed at big companies is the one you get to ask first. That high-margin line you could never attack because you "didn't have the team"? You may now have exactly enough team.
"Instead of organizing the company around hierarchy, you organize it around intelligence." Salim Ismail · EP #258 · 10:48
That is the reframe in a single line.10:48 Your smallness stops being a ceiling and starts being a clock speed.
What your job becomes
There's a fear hiding under all this optimism: if agents do the work, what is left for you? The answer here isn't "nothing." It's "a level up." When execution and coordination are handled by agents, Ismail argues, human beings "rise up a level" — dashboard oversight, monitoring, exception handling, problem solving.14:02 You stop being the person who does every task and become the person who directs and checks the systems that do them.
His analogy is worth keeping. In Germany, he notes, you can walk a modern factory floor and find almost no one on it — and yet unemployment didn't collapse.14:02 The work moved up, not away. For you, that means the bottleneck stops being your hands and starts being your judgment: what to build, what "good" looks like, and when to overrule the machine.
Three moves you can make this week
None of this requires an IT department or a funding round. It requires picking one thing and starting. Three moves, in order of how fast they pay off:
-
Hire one workflow, not one person
Pick the single repeatable task you'd most like to "hire" for — writing first-draft listings, triaging support email, reconciling receipts — and stand up one agentic workflow to do it. One task, one agent, this week. (Standing it up well, and keeping it reliable, is its own discipline — a topic for another day.)
-
Replace one meeting with an artifact
Find a recurring meeting whose real output is a decision or a document, and have an agent produce the draft first. You're testing the article's core claim on your own calendar: is building the thing cheaper than meeting about it?6:06
-
Keep a human in the loop — you
Agents are fast and occasionally confidently wrong. Put one review step you own on anything customer-facing or money-touching. This is the oversight role from the last section, turned into a habit.14:02
For a hundred years the math rewarded the company that could hire the most people. That math has inverted. The job now is not to grow large enough to afford a department — it's to architect a small operation around intelligence, and to start before the competitor who read the same memo does.0:28 Being small was the handicap. Now it's the head start.
Questions, answered
What is Coase's theory of the firm, in plain English?
Companies grew large because coordinating work inside one organization — everyone on payroll, directable on command — was cheaper than buying each task on the open market, where you'd have to search, negotiate, contract, and verify every time.4:02 That lower internal coordination cost is the reason firms exist at all.
Do I still need to hire employees if I use AI agents?
What does "AI-native" actually mean for a one- or two-person business?
It means organizing the business around intelligence — agentic workflows that carry out multi-step tasks — instead of around a chain of command.10:48 For a micro-team with no hierarchy to begin with, that's permission, not reorganization.
Can two people really replicate a bigger company's product?
Sometimes — but it's a provocation, not a forecast.10:13 Pure-execution lines can fall fast, but regulated, trust-heavy, and relationship-driven lines don't. And the same threat cuts both ways, so a small operator can be disrupted just as easily. Treat it as a prompt to act, not a guarantee.
Where do I start this week without an IT team or a big budget?
Pick one repeatable task you'd otherwise hire for and stand up a single agent workflow for it; replace one recurring meeting with a built artifact; and keep one human review step you own on anything customer-facing or money-touching.
Sources & citations
This essay translates one idea from a longer conversation — the collapse of coordination cost — into moves a 1–10 person business can make. The economic argument is the guest's; the small-business application is the article's own reasoning.
- Diamandis: the shift is useful for everyone — explicitly including entrepreneurs and small companies, not just the Fortune 500. 2:42
- Ismail: retool your organization or be disrupted — "someone doing it is going to just eat your lunch." 0:28
- Ismail: old structures were organized around hierarchy; they need to be AI-native agentic workflows — "architected around intelligence, not hierarchy." 0:35
- Ismail on Coase (1937), The Nature of the Firm: coordination is cheaper inside a company than out — work that he notes won a Nobel Prize. 4:02
- Ismail on Christensen's innovator's dilemma: as a company grows, smaller rivals can deliver cheaper products. 4:43
- Ismail: "the whole thing breaks in the face of agentic AI" — building a website inside means layers of approvals; outside, a free AI tool does it in ~5 minutes. 5:33
- A line Ismail quoted: "building the feature is cheaper than having the meeting about the feature." 6:06
- Ismail: coordination is now more expensive than execution, especially as AI drives the cost of execution down. 6:23
- Ismail: you still need an organization, but mainly as a purpose and liability container; coordination and execution costs fall away. 6:35
- Ismail's provocation: is there a high-margin line two people with off-the-shelf AI agents could replicate in 60–90 days? (Presented as a provocation, with counterweight.) 10:13
- Ismail: the "organizational singularity" — organize the company around intelligence, not hierarchy. 10:48
- Ismail: when agents handle execution and coordination, humans rise a level — oversight, monitoring, exception handling; the Germany factory-floor analogy. 14:02