Building the company
What a moat is
A structural advantage that protects returns. Features are not moats — they can be copied.
A company that grows fast but has no defense is a temporary cash machine: rivals copy the product, prices collapse, and growth becomes a race to the bottom. A moat is whatever makes it hard for a competent competitor to take your customers away at a similar cost. Investors care because venture returns come from durable value capture, not from a single good year of revenue.
Peter Thiel's framing is useful even if you never want a "monopoly" in the legal sense: in perfect competition, margins go to zero. The businesses that create lasting wealth look more like unique products with pricing power than restaurants fighting for the same block.
Concept
A moat (Warren Buffett's metaphor) is a structural advantage that protects economic returns from competition. Features are not moats: features can be copied. Scale, networks, switching costs, brands, exclusive resources and hard-to-copy processes can be.
Competition versus durable advantage
Competition is not the enemy of customers. It is often the enemy of your margins. Two restaurants on the same street compete on price, taste and location until neither makes economic profit. Two SaaS tools that solve the same workflow with similar onboarding will compete on discounting and feature checklists until gross margins and sales efficiency erode.
The engineering question is the same as the strategy question: what compounds in our favor as we get bigger?
Thiel's advice for startups is to start narrow: dominate a small market where you can be the default, then expand. Facebook began with Harvard students, not "social networking for everyone." Stripe started with developers who wanted payments in seven lines of code, not every merchant on earth. Narrow focus is how you earn a position that later becomes a moat. You do not get network effects or switching costs on day one.
Trade-off
Compete head-on vs flank. Head-on attacks against a well-funded incumbent (feature parity + cheaper price) usually lose: they have more distribution, more integrations and more cash. Flanking — a different customer, job, or channel — is slower to explain to investors but more likely to produce a real position. Default to flank unless you have a 10× advantage on a dimension customers already pay for.
Walking through a flank
You build an AI writing assistant for enterprise security teams. Competing with a horizontal chatbot on "better prose" is hopeless. Competing on connectors into the ticket system and SIEM, evals against past incidents, and SSO and audit logs from day one creates switching costs and a cornered resource (incident-labeled data). The horizontal tool remains better at generic writing. You become the default inside that workflow.
Common mistakes
- Calling features a moat. A rival can ship the checklist in a quarter.
- Attacking an incumbent head-on on price. They have more cash and more distribution.
- Waiting for a moat on day one. You earn it by dominating a narrow market first.
Check yourself
Why are features not a moat?
They can be copied. A moat is a structural barrier — scale, network, switching cost, brand, scarce resource or process.
When would you compete head-on with an incumbent?
When you have a 10× advantage on a dimension customers already pay for. Otherwise flank.
Key takeaways
- Moats protect long-term returns. Features and funding do not.
- Start narrow. Dominate a small market, then expand.
- Default to flanking incumbents unless you have a true 10× edge.
- Ask what compounds as you get bigger. That is the seed of a Power.
Further learning
Next, Helmer's taxonomy: 7 Powers.