Cited from real sources 7 min read Updated September 2026

A distribution thesis by Evan Spiegel

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

Evan Spiegel runs Snapchat, and he argues that software is not a moat. Rivals clone features. With AI anyone can rebuild them in a weekend. A great product is the price of entry. The durable advantage is distribution: getting into people's hands and staying there. Add 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."

Rivals clone features. 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. In the AI era they can copy it faster than ever. So shipping a great product is table stakes, the price of entry. It does not protect 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. 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 15 years of Spiegel running Snap while rivals cloned it.

  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 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 won
  • You are in deep-switching-cost B2B where software 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 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

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, Anuj Rathi, 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

New experts every week

Know when the next expert lands.

Gavel adds new operators to the database every week, each one with cited frameworks you can check and a note on where they disagree with the others. You found this page by searching. Get the next one by email instead.

53 experts 66 cited frameworks

Latest: Amjad Masad on Levels of AI Autonomy

One email a week, only when new experts shipped. Unsubscribe with one click. We never sell or share email.

Related frameworks