Analysis & Opinion

The Next Tech Moat Is Not the Model, It Is the Workflow

As frontier models converge and commoditize, the model is the least defensible part of the stack. The durable moat is the workflow — distribution, data, integrations and trust the model can't give you.

Daniel Roth · Jun 16, 2026
The Next Tech Moat Is Not the Model, It Is the Workflow
Table of contents
  1. Why the model isn't the moat
  2. What actually defends a business
  3. The strategic implication
  4. The counterargument, fairly
  5. Who should care
  6. Bottom line

There's a comforting story in tech that whoever has the best AI model wins. It's mostly wrong. As frontier models converge in capability and become commodities you can rent by the token, the model itself is becoming the least defensible part of the stack. The durable advantage — the real moat — is the workflow: the distribution, data, integrations, and trust that turn a model into something customers can't easily leave.

Why the model isn't the moat

Three forces erode model-based advantage:

  • Convergence. Leading models are clustering in capability; the gap between "best" and "good enough" keeps shrinking for most tasks.
  • Commoditization. Anyone can call a top model through an API. A capability available to everyone is, by definition, not a competitive advantage.
  • Speed of change. Today's best model is next quarter's baseline. Building your entire value on being on the best model is building on sand.

If your only edge is "we use the smartest model," a competitor rents the same one tomorrow — or the model provider ships your feature natively.

What actually defends a business

The moats that survive are the ones that don't come in an API:

  • Distribution. Reaching and keeping customers — channels, brand, and an existing user base — is expensive to replicate and doesn't depend on which model you use.
  • Proprietary data. Unique data that makes your AI better at your customers' problems, which competitors and model providers can't access.
  • Integrations and workflow ownership. Being embedded in how a customer actually works — connected to their systems, their data, their process — so switching means rebuilding their operations, not swapping an API key.
  • User trust. Reliability, safety, accountability, and a track record. In high-stakes uses, trust is harder to earn and more valuable than raw capability.

The strategic implication

If you're building on AI, the lesson is to invest where the model can't reach:

  • Own the workflow, not just the prompt. Solve the whole job end-to-end inside the customer's process.
  • Accumulate proprietary data as a byproduct of usage.
  • Build integrations that make you load-bearing infrastructure, not a removable layer.
  • Earn trust through reliability and accountability, especially where mistakes are costly.

The model is an ingredient. The meal — the workflow, the data, the integrations, the trust — is the business.

The counterargument, fairly

Model quality isn't irrelevant: a clearly better model can win for a while, and at the very frontier, capability still matters. But "for a while" is the key phrase. Capability advantages are temporary; workflow advantages compound. Bet on the thing that lasts.

Who should care

  • Founders deciding where to spend scarce effort — and what story to tell investors.
  • Investors separating durable AI businesses from thin wrappers.
  • Enterprises choosing vendors they'll depend on for years.

Bottom line

The next tech moat is not the model — it's the workflow. As models converge and commoditize, durable advantage comes from distribution, proprietary data, deep integrations, and earned trust: the things you can't rent by the token. Use the best model available, but build your business on what the model can't give you. Capability is borrowed; workflow ownership is owned.