Shape vs Moat
How to Know If Your Company Survives the Day It Gets Copied
The Three Engines framework, eight case studies, one forty-year-old counterexample, and the four tests I run before I believe any defensibility story.
Over my career, I have sat in rooms where companies decided what made them safe, and I helped win over $2 billion in strategic deals by watching what actually protected the winners. In almost every one of those rooms, someone pointed at the product and called it the moat. In almost every case, they were pointing at the wrong thing. This piece is the correction, written so you can run it on your own company this week.
Read it as a working session, not an essay. There is a framework, a set of case studies to steal from, and a worksheet at the end. By the last section, you will be able to answer one question with evidence instead of hope: if a competitor with more money ships a copy of your product tomorrow, what do your customers do on Thursday?
The framework is called The Three Engines. Here is the claim it rests on, stated once, plainly.
Product shape is everything about your product a rival can observe: the interface, the workflow, the output format, the pricing page, the demo. A moat is whatever makes customers stay when a rival offers the same thing cheaper. Shape is visible. Moats are not. And anything a rival can see, a rival can copy. So shape is never the moat. It is the paint on top of three engines: segment knowledge, workflow entrenchment, and a data loop. Companies with the engines survive being copied. Companies with only the paint do not.
Subscribe to continue reading
Become a paid subscriber to get access to the rest of this post and other exclusive content.
