The disruption shift
A startup's edge over an enterprise used to be simple: no brand to protect, no release process to follow, no stakeholders to align. A small team could ship what an enterprise needed a quarter to plan. That edge is still there. It just belongs to someone else now.
The old logic
Startups became the unit of disruption because they could move. Enterprises had the moats and the distribution, but they also had the overhead. Every change had to pass through approvals and roadmaps before anything shipped. The startup's advantage was the absence of that apparatus. No governance meetings, because there was no governance. No release train, because there was no release train. No negotiating with legal, because there was no legal yet.
Investors, writers, and talent markets organised themselves around the premise that startups disrupt and enterprises defend.
The shift
The same logic applies one level down. What used to be a startup's edge over an enterprise is now an individual's edge over a startup.
If shipping something requires a spec, a scoping meeting, and a release process before anything lands, you are running the startup's version of enterprise overhead. An indie developer can do the whole thing in a single sitting, because deciding and building happen in the same moment when there is only one person.
Startups are still faster than most enterprises. That comparison hasn't gone away. But when the competitive unit is an individual with good taste and a laptop, "faster than an enterprise" is measuring against the wrong thing.
Speed and no baggage used to be the startup's edge over the enterprise. It's now the individual's edge over the startup.
Where the old playbook still holds
Some frontiers still need groups. Hardware runs into physical constraints that don't fold under a single person's attention. Regulation requires institutional relationships and compliance infrastructure. Supply chains span geographies nobody assembles solo.
Most software has no such anchors. Naval's take: pure software is rapidly becoming un-investable. No moats, no durable returns, no reason for capital to pool around a single team. The value moves to the operator - the builder who doesn't need the money, only the taste and the execution.
What this means for how you work
This is not advice to work alone. Some work needs a team, and that won't change. What has changed is what coordination costs you.
For a long time, coordination was cheap relative to building. You wrote the spec, you had the meeting, you agreed the plan, and then the real work began. The meeting was an investment in getting the build right. Now the build is the cheap part. Coordination burns whatever momentum you have.
The cheapest advantage right now is no longer building faster. It is deciding faster. Not isolation - feedback loops still matter, and taste sharpens by other people. But when a decision has to pass through two calendars and three opinions, its real cost is the velocity you burn to get everyone aligned.
The biggest advantage left is not a technology, a market, or a playbook. It's the ability to close the gap between deciding and doing.