WTF is a Software Moat in 2026?
Summary
Reis argues that traditional software moats like feature velocity and large engineering teams are being destroyed by AI coding agents, forcing a fundamental rethink of what makes a company defensible. He identifies three surviving moat categories: deeply embedded systems of record, proprietary data with custom workflows, and deep expertise paired with brand and distribution. The shift is also killing per-seat SaaS pricing in favor of per-action and token-based models.
Key Insight
In the AI era, defensible moats have shifted from engineering speed and feature output to high-friction assets like embedded infrastructure, proprietary data, and irreplaceable human expertise and brand.
Spicy Quotes (click to share)
- 5
When coding agents can ship features around the clock for pennies on the token, that entire model gets inverted.
- 6
If your entire product is a harness around a public model, I wouldn't call that a moat or an interesting product with any sense of longevity in the marketplace.
- 7
Moats exist wherever there is high friction. If an LLM can do it easily, it's not defensible.
- 5
AI can aggregate existing knowledge, but it can't create net-new frameworks from lived experience. Building something fundamentally new and tying it to a trusted personal reputation is something an LLM can't replicate.
- 4
This is exactly why improving your data architecture and models is now a business survival tactic, as AI amplifies the effects of poor architecture and data models.
Tone
analytical
