The disruption shift
The startup's edge over an enterprise is now the individual's edge over a startup. The unit of disruption keeps shrinking, and the reasons are structural.
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.
The playbook of the last few decades grew up around that premise: startups disrupt, enterprises defend.
The shift
The same logic now applies one level down, and the reason is cost. For most of software's history, building was the expensive part. It took people, and people needed coordinating. AI tools have made the build itself cheap enough for one person to carry. Once that happens, the coordination a team needs stops being the price of building and becomes the main cost of it.
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 individual 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.
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. Without them there's little to protect a team's position, and little reason for capital to pool around one. The value moves to the operator - the builder who doesn't need the money, only the taste and the execution.
Speed and no baggage used to be the startup's edge over the enterprise. It's now the individual's edge over the startup.
The price of coordination
This isn't advice to work alone. Some work needs a team, and that won't change. What has changed is what coordination costs.
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, and coordination is where the momentum goes.
Feedback loops still matter, and taste sharpens against other people's. But when a decision has to pass through two calendars and three opinions, the price is paid in velocity.
The biggest advantage left isn't a technology, a market, or a playbook. It's the ability to close the gap between deciding and doing.