Rented Intelligence: Building on Borrowed Ground

AI's most powerful building tools are rented, not owned. The real risk isn't whether the technology works. It's whether the ground beneath you can shift.

Imagine Steve Jobs at eighteen years old today.

He walks into a world where the most powerful building tools in the history of technology are available to anyone with a laptop and a credit card. AI models that took billions of dollars and decades of research to create, accessible through an API. Compute that would have required a room full of hardware, running in the cloud for pennies. Frameworks, libraries, deployment infrastructure, all of it there, waiting, free or nearly free.

It would feel like Charlie finding the golden ticket. A world of pure imagination where creativity makes seemingly impossible things possible and where the only limits are his willingness to explore.

Steve Jobs at eighteen in today’s world would have no shortage of imagination, tools, or willingness. What he would need, more than anything else, is an understanding of whose factory he’s building in. Because Willy Wonka’s Chocolate Factory was a place of magic and wonder, but it was also surprisingly dangerous. The inventing room was full of things that hadn’t been fully tested. The chocolate river looked inviting right up until it wasn’t. It’s tempting to spend a weekend vibe coding and call it a business. But where you put down your flag matters as much as what you build. The space is likely leased, and some of the danger zones aren’t visible from inside the excitement.

Jobs may have still built on existing foundations. Many founders do, and it’s often the rational choice. As a founder, I understand the temptation. The tools are extraordinary. The speed is intoxicating. We can build things today that would have required entire engineering organizations a decade ago. But every strategic advantage comes with a tradeoff, and this one deserves more attention than it’s getting. Because the most important decision at this stage isn’t which foundation model to build on. It’s whether you understand what you agree to when you do.

My co-founder Craig has lived through every major technology cycle since the internet. When we were making the decisions that shaped how we build, he was the one asking the questions that weren’t fashionable yet. Not whether the technology works, but who controls it once it does. Not whether the capability is real, but who is left standing when the market consolidates. He believed in this cycle. He understood that we finally had the compute to make the promise real. What made him cautious wasn’t the technology. It was the dependency.

This forethought ultimately shaped our own architecture decisions. We wanted language models where they added value, but we were unwilling to make the core reasoning layer dependent on technology we did not control. That caution led us somewhere most builders weren’t going, which is what this piece is about.

The danger isn’t that the platforms fail.

The danger is that they succeed.

Because when platforms become powerful enough to define a market, they also gain the ability to redefine the terms for everyone building inside it.

The Kill Zone

In venture capital, the kill zone has a specific meaning. It describes the territory surrounding dominant platform companies where rational investors have quietly stopped funding startups, not because the ideas aren’t good, but because the risk of the platform deciding to build the same thing is too high to justify the bet.

The concept emerged from studying what happened to startups building in the orbit of Facebook, Google, and Amazon. The platforms didn’t need to out-innovate the startups. They just needed to decide the category was worth their attention. When that happened, the startup’s funding dried up, its users migrated to the native version, and its competitive window closed faster than any business plan had modeled.

In the current AI landscape, the kill zone has a sharper edge. The startups building on top of OpenAI, Anthropic, and Google aren’t just building near these platforms. They are building on top of them. Their core capability runs on infrastructure they don’t own. Their competitive differentiation sits on a foundation controlled by companies whose long-term incentives don’t permanently align with theirs.

Imagine building your entire business on Apple’s App Store, only to wake up and find Apple shipping your core feature in iOS.

The platforms are already moving. OpenAI consolidated ChatGPT, Codex, and its browser into a unified desktop application in early 2026, explicitly to compete more directly with enterprise AI providers who had built on its foundation.^[i]

Google’s entire I/O 2026 narrative centered on agentic AI embedded directly into its existing product ecosystem, reducing the need for third-party tools that had been built to fill exactly that gap.^[ii]

Anthropic acquired Stainless, a startup whose SDK generation tools were being used by OpenAI, Google, and Cloudflare, reshaping the developer tooling layer beneath an entire ecosystem of builders who had assumed that infrastructure was neutral.^[iii]

These are not incidental moves. They are a pattern. And the pattern has a direction.

Every time a platform extends its reach into the stack, the builders who depended on that layer discover that the relationship they thought they had was more conditional than they understood. The ground they built on was borrowed. And borrowed ground can be recalled.

The Thin Wrapper Problem

Not all AI startups face equal exposure. The vulnerability scales with how much of the company’s core value proposition lives inside the platform versus on top of it.

At one end of the spectrum are what the VC community calls thin-wrapper startups: companies whose primary contribution is a better interface, a smarter prompt, or a more polished user experience layered over a foundation model. The underlying intelligence is rented. The distribution is rented. In some cases, the data processing and memory capabilities are rented too. What the startup owns is the design and the go-to-market motion. When the platform decides to ship those same design choices natively, the thin-wrapper startup discovers that what it thought was a product was actually a feature.

This is not hypothetical. OpenAI’s move to consolidate its products into a unified desktop application was a direct response to the ecosystem of third-party tools that had built on top of its API to solve exactly the fragmentation problem users were experiencing. The startups that solved it first validated the market. The platform then captured it.

The more defensible position is to build proprietary workflows, domain-specific data advantages, or genuine integrations that create switching costs the platform can’t easily replicate. But even that position is becoming harder to hold as the platforms invest in vertical-specific offerings and enterprise partnerships that go deeper into specific industries.^[iv]

The VC community is noticing. A growing number of investors now require founders to articulate what they call their platform independence thesis: an explicit argument for why their business remains viable if the underlying model provider decides to compete directly. A year ago, that question was rarely asked. Now it is table stakes in term sheet conversations.

There is another dimension to why technology consolidates that goes beyond competitive pressure. Not because dominant platforms force it, but because fragmentation carries its own cost, one paid daily by the people being asked to work across an expanding stack of disconnected tools. That story belongs to the next piece in this series, where I explore why so many promising point solutions are quietly becoming part of the problem they were built to solve.

The Enterprise Dilemma

The platform risk conversation in AI tends to focus on startups. But enterprises face a version of the same exposure, and in many ways the stakes are higher because dependency becomes embedded across people, processes, and customers.

What happens when critical business capabilities depend on providers whose incentives can change faster than your ability to adapt?

Consider what enterprise AI adoption actually looks like at scale. A company selects a foundation model provider. It builds internal workflows, customer-facing products, and operational processes on top of that provider’s API. It trains its people to work with those tools. It integrates them into its existing technology stack. It makes commitments to its own customers based on the capabilities those tools provide.

Then the provider reprices, deprecates the model version the enterprise built on, or launches a competing product in the enterprise’s own industry. None of those scenarios require a catastrophic failure. They simply require the platform to make a rational decision in its own interest. And each of these scenarios has already occurred in the current market. OpenAI deprecated its Assistants API in August 2025, with shutdown scheduled for 2026, forcing enterprises that had built on it to migrate to a new architecture on a timeline they didn’t choose.^[v]

The enterprise that built on that foundation didn’t lose its business. But it absorbed costs that never appeared in the original business case: migration, retraining, disruption to the people doing the work, and credibility spent with its own stakeholders on someone else’s timeline. Leaders who had promised capability delivered disruption instead. Employees who had been trained on one system were asked to start over on another. The business kept moving, but it moved carrying weight it hadn’t planned for.

This is what borrowed ground costs when it shifts. Not always catastrophe. Often something quieter and harder to quantify: the accumulated weight of decisions made on someone else’s terms.

What the Relationship Actually Costs

There is an asymmetry in platform relationships that rarely gets named in the conversations where it matters most.

The platform knows the enterprise’s usage patterns, its most valuable workflows, its integration dependencies, and the switching costs it has accumulated over time. The enterprise knows the platform’s published pricing, its publicly stated roadmap, and whatever its sales team chose to share. Every conversation about what the relationship costs and what happens when it changes takes place in that gap.

That gap is not neutral. It tilts every negotiation, every pricing conversation, and every decision about what comes next toward the party with more information. The enterprise that has built deeply on a platform has already made its most important concession before it sits down to talk.

What makes this more complicated is that the platforms are not operating from a position of stability. As the previous pieces in this series explored, the entire frontier AI industry is still finding its path to profitability. The pressure to capture more of the value their ecosystems create is not a future risk. It is the present reality of every major provider. The enterprises and founders who validated those markets may find themselves on the wrong side of that math at exactly the moment they are most dependent.

This is not a moral failure on anyone’s part. It is the natural consequence of building interdependence into a market that is still sorting out its own economics. But it is a risk that deserves to be understood before the dependency is built, not after.

What Defensible Actually Means

What, then, does defensible mean in a market where the most powerful foundations are controlled by companies whose interests and yours will not always align?

Defensibility in this environment is not about having a better prompt. It is not about a more elegant interface. It is about whether the value you create can survive a change in the foundation beneath it.

For the startup, that means proprietary data, genuine workflow integration, and switching costs that belong to the customer relationship rather than to the platform.

For the enterprise, it means architecture choices that don’t create single points of dependency, and governance frameworks that account for platform risk alongside security risk.

For anyone building infrastructure rather than applications, it means understanding that the most durable position in this market is not the one closest to the frontier model. It is the one closest to the human being doing the work.

And for anyone building something intended to last, it means sitting with a question that the pace of this market makes easy to skip. Not am I building on something. Every builder builds on something. Jobs built on chips he didn’t fabricate. The transformer itself was built on decades of work that came before it. The question is sharper than that: does the thing I’m building on have interests of its own?

A protocol doesn’t decide to compete with you. It doesn’t reprice you or get withdrawn on a timeline you didn’t choose. But a platform owned by a company navigating its own survival can do all three. The distinction is not whether you depend on something. It is whether what you depend on can change its mind about you.

Steve Jobs at eighteen would have had more tools available to him than any builder in history. The factory is real, and it is extraordinary. The mistake would be assuming that because the factory feels permanent, it is. What Craig understood, and what ultimately shaped how we built, is that the most important question is not whether the tools work. They clearly do. It is whether the ground beneath them belongs to you.

The foundations beneath AI’s extraordinary buildout are less stable than most people realize. Not just physically and economically, as the first two pieces in this series explored, but structurally. The platforms that feel permanent are still finding their path to profitability. The incentives are still shifting. The boundaries are still being redrawn.

None of that makes the factory less remarkable.

It simply means builders should understand whose factory they are building in.

Because the most important question isn’t whether the factory is magical.

It’s who owns the keys.

In the next piece, we look at the other side of this consolidation story: what happens when every problem gets a new AI tool, and why the fragmentation those tools create may become its own hidden tax.

Endnotes

ⁱ https://www.mexc.com/news/969584

ⁱⁱ https://jeffreystop.com/news/2026-05-22-0900-ai-tech-news/

ⁱⁱⁱ https://thenewstack.io/anthropic-stainless-sdk-acquisition/

^iv https://www.mindstudio.ai/blog/google-vs-openai-vs-anthropic-momentum-2026-narrative

^v https://www.buildmvpfast.com/blog/which-ai-platform-startups-build-on-2026