Gavel Gavel
Experts Skills
Cited from real sources 7 min read Updated June 2026

A distribution thesis by Evan Spiegel

Evan Spiegel's Distribution Moat: How to Win When Software Is Not a Moat

Evan Spiegel, Snapchat's CEO, argues that software is not a moat. Features get cloned, and with AI anyone can rebuild them in a weekend, so a great product is necessary but never sufficient. The durable advantage is distribution: getting into people's hands and staying there, plus the ecosystem of creators, hardware, and habits that rivals cannot copy. Snap learned this fifteen years ago. Every founder is learning it now. It is the thesis underneath the AI Distribution Cheat Sheet.

The lesson Snap learned 15 years before AI

"Software is not a moat."

Features get cloned. With AI, faster than ever. What lasts is distribution, and the ecosystem of creators, hardware, and habits competitors cannot copy.

Evan Spiegel on Lenny's Podcast How to win when software is not a moat Watch at 00:38

The framework

The product gets you in the game. Distribution keeps you in it.

The core claim is uncomfortable for anyone who fell in love with their product: a software feature is not defensible. If you can build it, a competitor can copy it, and in the AI era they can copy it faster than ever. So shipping a great product is table stakes, the price of entry, not the thing that protects you once you are in.

That inverts the instinct most founders run on. The instinct says build something better and the users will come and stay. Spiegel's experience at Snap says the opposite: building a great product is not enough, because the platforms that win solve the harder problem of distribution. Getting into people's hands, and the ecosystem of creators, hardware, and habits around it, is what a rival cannot clone overnight.

15 years ago, we essentially learned that software is not a moat, which is something that everyone is discovering today with AI.
Evan Spiegel on what Snap learned early Watch at 10:24

So the moat is not the code. The moat is everything that surrounds the code and takes years to assemble: distribution, the creator and developer ecosystem, hardware, and the habit of opening your app instead of someone else's.

How to apply it

How do you build a moat when the software won't be one?

Five moves, drawn from how Spiegel has run Snap through 15 years of being cloned.

  1. 1

    Assume your features get cloned.

    Plan for parity to evaporate. Anything you can ship, a funded competitor can ship too, faster now that AI writes the boilerplate. Design for the world where they already have your feature list.

  2. 2

    Treat distribution as the hard problem, not the launch step.

    Spiegel calls distribution the new moat and the new biggest challenge, and the part AI will not solve for you. Put your best thinking there, not just into the product surface.

  3. 3

    Build defensibility software cannot carry.

    Snap builds durability through ecosystems, creators, and hardware integration. Pick the layer you can own: a creator network, a developer platform, a community habit, a device. Those compound and resist cloning.

  4. 4

    Ride the next platform while distribution is still cheap.

    The biggest consumer companies were born on a new platform; mobile gave us Uber and Snapchat. Watch for the next surface, like AR glasses, where the distribution land grab has not happened yet.

  5. 5

    Compete on humanity, not only technology.

    Spiegel argues humanity dictates how technology is adopted. The flat, critique-driven team structure that lets Snap ship fast is itself part of the moat. Culture and speed are hard to copy too.

Boundary conditions

When it works, when it fails

Works best when

  • Your features are genuinely easy to replicate, as in consumer apps or thin AI wrappers
  • A new platform is emerging and distribution is still up for grabs
  • You can build ecosystem, hardware, or community defensibility over time
  • You have the patience and capital a durable-moat strategy demands

Fails when

  • You mistake a temporary feature lead for a lasting moat
  • You postpone distribution until the product has supposedly won
  • You are in deep-switching-cost B2B where software genuinely can be sticky
  • You chase ecosystem and hardware before the core product earns any pull

The honest counter is that not all software is undefendable. On Lenny's Podcast, Spiegel traces the strategy back to the moment Snap accepted it had to build something more durable than features:

So easily cloned by our competitors, we started to think about how to build a more durable business, how to build a business that had bigger and more effective moats.
Evan Spiegel on why Snap changed strategy Watch at 10:36

This is where the experts disagree, and the disagreement is the useful part. Spiegel says software is not a moat. Hamilton Helmer's 7 Powers says software businesses absolutely can hold durable power through counter-positioning, switching costs, and scale economies. Both are right at different layers: a single feature is not a moat, but a system of features wrapped in switching costs can be. Read them together before you bet the company on either.

The sources

Where Spiegel discusses this

06:21
Timestamp

Lenny's Podcast · How to win when software is not a moat

Innovation and 'software is not a moat'

Spiegel reflects on the reality that software features are easily cloned and discusses how Snap builds defensibility through ecosystems, creators, and hardware integration.
04:36
Timestamp

Lenny's Podcast · How to win when software is not a moat

The role of distribution in success

Spiegel explains that building a great product is not enough; successful platforms like TikTok and Instagram-based products succeeded because they effectively solved the problem of distribution.
00:00
Timestamp

Lenny's Podcast · How to win when software is not a moat

Why consumer social is difficult

Evan Spiegel discusses the extreme challenges of building a durable, lasting consumer social product and why most startups fail in this space.
13:51
Timestamp

Lenny's Podcast · How to win when software is not a moat

Organizational structure and innovation

Spiegel shares the internal structure that allows Snap to innovate at speed, emphasizing a flat design team structure and the importance of critique-based workflows.

Useful? Pass it to a founder who thinks a better product is the whole plan.

Want the full playbook?

Get 108 product & growth frameworks.

35 frameworks 20 rules 45 heuristics & principles 51 operators

From Hamilton Helmer, Bill Carr, Rahul Vohra, and 48 more. Drop one .md into Claude, Cursor, or ChatGPT. Your AI cites practitioners, not guesses.

See the pack

Instant .md download · One-time purchase · No subscription

Related frameworks

Distribution

Controversy Marketing

Roy Lee

The algorithm rewards authentic provocation, and almost no founder will press the button. Manufacture reach with controversy, but never punch down.

Distribution

Distribution as Moat

Greg Isenberg

Building is commoditized. The durable moat is owned distribution: audience, community, channels you control.

Distribution

Core Four Customer Acquisition

Alex Hormozi

Warm, cold, content, ads. Pick one. Four hours a day for a quarter.

Sales

Hook-Meat-CTA Ad Framework

Alex Hormozi

Failed ads die at the hook. Name the pain in three words, deliver the meat, then make one clear ask.