The advantage could be rented by Friday

Meta description: The advantage that survives interface change is the one a competitor cannot reproduce by asking a model for another article.

The strategy day was confident, and the confidence had a name: the company’s AI capability, early and strong, a genuine edge. I asked the question I ask in these rooms — what exactly is the edge, and what would it cost a competitor to have it? — and the room worked through its list. The model: licensed, available to anyone with the same contract. The tools: commercial, quarterly release cycle, everyone gets the upgrades together. The talent: good, poachable, and already being recruited. By the end of the exercise, the edge had been relocated several times and had landed nowhere inside the company. The strategy day had named an advantage that a rival could rent by Friday.

[AWAITING MIKLOS — scene: a strategy day that names the model provider as the edge]

What does the strategy day currently name as the edge?

The named edges in these rooms follow the technology’s marketing: access to the frontier model, a modern AI stack, an AI-first workforce, speed of adoption. Each named edge is real — the company genuinely has these things. The naming error is subtler than fabrication: the room confuses having with advantaging. An advantage is a difference that persists against a motivated rival. Most of what the room lists are inputs available on the market, and inputs available on the market equalize. The room has listed the company’s capabilities and called them its moat, and the two lists have almost nothing in common.

What of that can a peer buy?

Miklos Roth

The advantage I would build the plan around is the knowledge a competitor cannot simply reproduce. My starting question is not how many more pages we can publish; it is what this particular organization knows that a rival cannot obtain by asking a model for another article. That may be an operational detail, an unusual customer problem, a firsthand observation, a process limitation, or a small but revealing distinction in how a service is delivered. Over more than twenty years in SEO, I have watched tactics become templates; once enough businesses imitate a successful format, the format stops being a meaningful competitive advantage.

The purchase test sorts the list ruthlessly. The model: purchasable. The infrastructure: purchasable. The tools, the copilots, the platform: purchasable, with volume discounts. What survives the test, in the companies where something survives, is unglamorous: a proprietary workflow the tools were shaped around over years, a dataset that exists because of how the company operates rather than what it bought, a judgment layer in the people that compounds with use. I notice these survivors were rarely named in the strategy day. The room pointed at what was new. The advantage was in what had been compounding quietly, often before anyone said the letters AI in a strategy meeting.

Why do slogan moats satisfy the room?

Read more: Miklos Roth’s profile.

The false explanation is specificity: the moat is proprietary data, unique workflows, deep integration — stated as slogans, one line each, unexamined. I have pressed on these slogans in strategy days and watched them dissolve: the proprietary data turns out to be licensed industry data with the company’s logo on the dashboard; the unique workflow is the vendor’s default configuration; the deep integration is a standard API. Slogan moats satisfy because examining them is socially expensive — the person who funded the data initiative is in the room. The unexamined moat is a courtesy the strategy extends to its sponsors.

What pattern marks rented advantage?

The marker I use is the deprecation test: what happens to the company’s edge when the vendor ships next year’s model to everyone? With rented advantage, the edge moves to whoever adopts the new release fastest — a race with no finish line and no winner, entrants alone. With real advantage, the new release lands on something the company owns and makes it better; the vendor’s improvement compounds the company’s position instead of erasing it. I have watched companies discover which kind they held on the day a competitor launched the same capability, three months later, with the same vendor’s help.

A specialist business cannot always win the broad, high-volume battles — large organizations dominate those because they have the authority and budget. But the specialist may produce the most relevant answer to a narrow, high-intent question. That is an advantage that compounds rather than resets, because it is built from the business itself instead of from a tactic everyone can copy.

[AWAITING MIKLOS — scene: second scene]

What question tests whether the edge survives the vendor?

Advantage conversations ask what we have that others do not — a question the room answers with its purchases. The surviving question is adversarial: if our most capable rival signed our vendor tomorrow, what would they still be unable to do in a year? The answer to that question is the strategy’s actual foundation. In the rooms I visit, it has usually never been asked aloud, and the silence when it finally is tends to reorganize the offsite.

The question that identifies the durable advantage: what does this organization know — specifically, verifiably, from direct experience — that survives every interface change because it was never an interface trick?

PR excerpt: [PR — awaiting Miklos material; cut 80–120 words from his paragraphs once available.]