a16zFrom the Dot-Com Crash to the AI Era: How Builders Survive Waves of Disruption
At a glance
WHAT IT’S REALLY ABOUT
How incumbents and startups ride disruption waves from cloud to AI
- VMware’s history illustrates the arc from being a disruptor (virtualization) to being disrupted (cloud and Kubernetes), with disruption often driven by new abstractions, new user classes, or new business models.
- Cisco’s cloud miss is framed as a “loss of soul” common in scaled companies, prompting a deliberate reset toward founder/owner mentality, faster innovation cycles, and clearer bets.
- Large-company innovation requires explicit structure—ring-fenced teams with top-level air cover, defined insertion points in brownfield markets, and a staged ICP expansion rather than broad selling on day one.
- Go-to-market realities can make or break innovation: successful products align with existing routes-to-market when adjacent, but require new motions or overlays when targeting new practitioners or buyers.
- AI is presented as a first-principles shift that rebuilds the stack (power-to-tokens), expands infrastructure demand dramatically, and forces new strategies around vertical integration paired with ecosystem openness and partner/competitor interoperability.
IDEAS WORTH REMEMBERING
5 ideasDisruption usually comes from new abstractions, users, or business models—not incumbents’ best customers.
Raghuram frames “weapons of mass disruption” as shifts that re-aggregate the industry around a new layer or unlock a new user base (e.g., AWS giving developers infrastructure without IT), which incumbents often miss because incentives keep them focused on top accounts.
If you only talk to your best customers, you’re probably looking in the wrong place for the next wave.
Casado and Raghuram note that disruption tends to originate outside the 20% of customers driving 80% of revenue, so incumbents need separate mechanisms to learn from front-line practitioners and emerging segments.
Ring-fencing works: small teams with agency and executive air cover beat part-time innovation and “do old + new” mandates.
Patel argues for starting with a two-pizza incubation team protected from organizational antibodies, then later leveraging the full enterprise machine once product/ICP fit is proven.
Define insertion points to win in brownfield markets: coexist before you displace.
Patel stresses that most real markets are brownfield, so entrants must integrate into existing environments, pick a wedge where they can land, and only then extract incumbents over time—requiring an ecosystem-minded posture.
Adjacency determines whether organic innovation can use the existing sales force—or needs a new motion.
Raghuram’s vSAN example shows early failure when selling to the “storage buyer,” then success by expanding the compute buyer’s scope; by contrast, Nicira/networking required different approaches because it changed who operated the product and how.
WORDS WORTH SAVING
5 quotesIf you look at VMware's roughly twenty-year history, the first decade was us disrupting and growing, and the second decade was others coming after us to disrupt us, right?
— Raghu Raghuram
But, but you've kind of lost the soul of the business, which is, are you innovating at, at, at, at a very impatient velocity-
— Jeetu Patel
Don't delegate the storytelling to anyone in the company. You go do it yourself-... because you need one voice.
— Jeetu Patel
In fact, I'll go one step further and say the story is the strategy.
— Raghu Raghuram
The reality is the market's not greenfield, it's brownfield. So you have to identify an insertion point where your competitor might be there, and then over time you have to make sure that you extract the competitor... it's like, no, you actually have to coexist first before you can displace.
— Jeetu Patel
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome