The uncomfortable thing about your AI advantage
Here is a question I like to ask leadership teams who are proud of their new AI feature. If your competitor signed up for the same model API tomorrow afternoon, how much of your advantage would survive to the evening? For a lot of products the answer is: almost none. The impressive part, the intelligence, was rented, and the landlord rents to everyone. That is a deeply uncomfortable thing to sit with after you have spent a quarter and a budget building on top of it, but it is the right place to start, because it is the truth that decides who still has a business in three years.
I am not saying do not build on these models. You should, and the leverage is real. I am saying be clear-eyed about which part of what you built is actually yours. The model is the engine, and you can buy the same engine your rivals buy. Moats were never made of engines. They were made of the things that are hard to copy, and the model, by design, is the easiest thing in your stack to copy, because someone else already built it and is selling it to the whole market.
Convergence is quietly killing the model moat
For a while it looked like the frontier model itself might be the moat. One lab was clearly ahead, and being first to its capability felt like an edge. That window is closing. The capability gap between the leading closed models and the fast-following open ones keeps narrowing, and the price of yesterday's frontier keeps collapsing toward zero. What was a premium, differentiating capability this year becomes a cheap commodity that everyone can call next year.
The strategic consequence is stark. If your product's advantage is that it uses a slightly better model, you are defending a position that the market erodes on its own schedule, not yours. Convergence is not a risk you can out-execute. It is the baseline condition. Betting your differentiation on being half a step ahead on model quality is betting on staying ahead in a race where the whole field is being handed faster shoes every few months.
The moat was never the model
So where does durable advantage live, if not in the intelligence itself? In the things the model cannot bring with it when your competitor rents it. Your proprietary data, the kind that exists nowhere else and cannot be scraped. The feedback loop that makes your product quietly better every time someone uses it. The distribution you already have, the trust you have earned, the workflow you are embedded in. These are the assets that do not arrive bundled with an API key, and they are the ones worth building deliberately.
Of those, the one most teams underinvest in, and the one with the most compounding power, is the data and the loop around it. A competitor can match your model in an afternoon. Matching years of accumulated, well-captured, proprietary interaction data is not an afternoon's work, and in many cases it is not possible at all, because that data was generated by a position in the market they do not occupy. The model is rented and identical. The data is owned and specific. That asymmetry is the whole game.
The data flywheel, and why it is hard to copy
The reason data advantage compounds rather than just accumulating is the feedback loop, the flywheel people reference and fewer actually build. It works like this. Use generates data, the real signal of what users actually did, chose, corrected, and kept. That data makes the product measurably better, through better retrieval, better fine-tuning, better defaults, better judgment about what to show. A better product earns more use. More use generates more data. Each turn of the wheel widens the gap, and the gap widens faster the longer it has been turning.
What makes this so hard to copy is that it is not a feature you can clone. It is a position that took time and usage to earn, and a latecomer cannot buy back the turns of the wheel they missed. They can copy your interface overnight. They cannot copy the two years of real interactions that taught your system what good looks like in your specific domain. The flywheel is the rare kind of advantage that gets stronger precisely because it is being used, which is the opposite of a rented capability that gets weaker as everyone else rents the same one.
Data quality is the real bottleneck
There is a trap inside this, and it is worth naming because it wastes a lot of money. More data is not the goal. The goal is the right data, captured cleanly, labeled by real outcomes, and wired back into the product. I have seen teams sitting on enormous data lakes that confer no advantage whatsoever, because the data is noisy, unlabeled, disconnected from any outcome, and never flows back into anything that improves. Volume without a loop is a storage bill, not a moat.
The unglamorous work is where the advantage actually gets made. Capturing the right signal at the moment of truth, which usually means instrumenting the product to record not just what the model produced but whether the user accepted it, corrected it, or walked away. Curating ruthlessly, because a smaller set of high-quality, outcome-labeled examples beats a vast pile of ambiguous ones. Closing the loop, so the signal you captured measurably changes what the product does next time. None of this demos well. All of it is what separates a company with a data flywheel from a company with a data warehouse.
What a leader invests in
So I push the investment toward the parts that are actually defensible. I treat the feedback loop as core product infrastructure, not analytics, and I fund it like it matters, because it is the thing competitors cannot buy. I instrument outcomes deliberately, so that every real use leaves behind a labeled signal about whether it worked, which is the raw material the flywheel runs on. I treat our proprietary data as a product in its own right, with an owner, a quality bar, and a roadmap, rather than exhaust we happen to collect. And I stay deliberately unsentimental about the model layer, ready to swap providers as prices fall and capabilities converge, precisely because I am not pretending the model is where my advantage lives.
The mindset shift for a leadership team is to stop asking "which model should we use" as though it were the strategic question, and start asking "what do we uniquely know, what are we uniquely positioned to learn, and is our product wired to compound that." The first question has the same answer for you and your competitors. The second one is the only question whose answer is yours alone.
Where this goes
I think the next few years make this sharper, not softer. As the model layer commoditizes further, the companies that treated it as the differentiator will find their differentiation evaporating on the market's schedule, while the companies that used cheap, abundant intelligence to spin a proprietary data flywheel will find their advantage compounding. Intelligence is becoming a utility. Utilities are not where durable margins live. The durable position migrates to what sits around the utility: the data no one else has, the loop no one else can restart, the trust and distribution no one else has earned.
The leaders who get this right will not be the ones who chased the best model. They will be the ones who accepted plainly that the model is rented, and who spent their real effort building the one thing that is genuinely theirs. The model is a tool everyone can hold. The flywheel is a position only you can occupy, and only if you build it on purpose, starting now, while the wheel still has time to turn.
I am refining how I measure flywheel strength and would value comparing notes. If you are building on these models, what part of your advantage would actually survive your competitor renting the same one tomorrow.
I write a field-note series on shipping AI that actually works in production. The original of this piece, and the rest, live on my LinkedIn. Originally published on LinkedIn.
