6 min read

A Dependency Is a Dependency, Whatever the Contract Calls It

I watched a public company cut its AI bill in half while usage kept climbing, and it forced me to ask a harder question: which parts of my own intelligence are worth owning, and which are fine to rent by the token.

Days before one of enterprise software's loudest voices went on television to call renting your intelligence a mistake, a public company had already moved its money. No press release, no keynote, just a founder's post about a change in how it operates.

In late June, Brian Armstrong posted that Coinbase had cut its AI spend nearly in half while usage kept growing. Coinbase rebuilt how it consumes AI, making cheaper open-weight models the default through its own gateway, caching heavily, and routing each task to the cheapest capable model. The model switch was only one of five changes. Much of the saving came from caching, which just means reusing answers the company had already paid for instead of paying to generate them again. The reuse rate jumped from about 5 percent to 60 percent.

The loudest thing about the move was the invoice. The company had simply decided its intelligence was worth owning rather than renting in full.

You Cannot Outsource the Thing Your Business Runs On

Every public company answers to shareholders and a board, with a duty to run the business predictably. Leaders can tell you, nearly to the dollar, what next year will cost in salaries and rent. AI is becoming as central as either, and it is the only core input where the price, the supply, and the supplier's intentions all sit outside the company's control.

Rent all of your intelligence from one lab, and the first two are gone on day one. The lab decides what you pay, and can change it with a new model or a new pricing plan. It decides what stays available, and can retire the model your workflows were built on. And when a government steps in, the decision is not even the lab's. You already watched one switch off the most powerful model on the planet on a Friday night, for everyone at once.

The supplier's intentions are the part nobody prices in. A frontier lab is not a utility, content to sell power and stay out of your business. These are the most ambitious companies on earth, and they are climbing. Autocomplete became coding assistants, and coding assistants are becoming agents that do whole categories of knowledge work end to end. Every release moves them closer to the work their customers bill for, and the rent you pay helps fund the climb. If your industry is profitable, assume they have noticed.

A supplier who can reprice you, outbuild you, or lose the right to serve you overnight is a dependency, whatever the contract calls it. That is the case for owning your intelligence, at least the part that would hurt most to lose.

Good Enough Is a Price, Not an Insult

Before the strategy tripped me, the vocabulary did. Everyone just says open source and that confuses me, because most of these models are not open source the way people think. Open source hands you the recipe. Open weight hands you the finished dish. You never see how it was made, yet the dish is yours to keep, serve, and reheat as often as you like, on machines you choose, for nothing beyond the cost of running them. That is the kind of model Coinbase now defaults to.

Once the dish is free to own, the buying question changes. Good enough becomes a price, the discipline of paying frontier rates only for frontier work. GLM 5.2 lists around $1.40 per million input tokens, the unit AI usage is billed in. A frontier model runs closer to $5 for the same work, more than three times the price, while the cheaper model scores competitively on the benchmarks that matter. Across millions of calls a month, the frontier premium becomes a tax on work that never needed it.

GLM comes with an asterisk. Several of the strongest open-weight models come from Chinese labs, and US lawmakers are questioning how much to depend on them. Even Microsoft is navigating that tension in plain view. In early July, GitHub made a Chinese-origin open-weight model a lower-cost option inside Copilot, and Microsoft is weighing a self-hosted open model for parts of Copilot Cowork. The honest move is neither to wave that away nor to rush toward those models. Weights you download run where you put them and report back to no one. Who built the model and who controls it are two different questions, and the second one can always be you.

After the model choice comes routing, deciding which task goes to which model, the way Coinbase's gateway sends every job to the cheapest model that clears the bar. Skip that step and the bill finds you anyway. Uber burned through its whole 2026 AI coding budget in four months and now caps engineers at about $1,500 per tool a month. Every finance team is about to run the same experiment. Uber ran it first and learned, in real dollars, that making frontier the default does not survive a budget review.

Your Data Is the Alpha, and You Are Giving It Away

A cheaper bill is only half the argument, and it is the smaller half. The other half is what leaves the building with every request you send to a rented model.

Alex Karp, the CEO of Palantir, was the voice on television. He put it bluntly on CNBC in early July. Pay a frontier lab and you buy tokens while handing over your proprietary data, your workflows, and the judgment underneath them, the things that make your business worth paying for. The customers who understand this, he argued, want to "own the means of production." Take Karp with a grain of salt, since Palantir sells the sovereignty layer he says you need, and Forbes called the interview a sales pitch. The worry is still real, and it does not vanish because the person naming it has something to sell.

In my own industry, the stakes are high. After a decade-plus in healthcare, I know the rule that never bends. Patient data cannot wander. Protected health information, the identifying medical data the law restricts, cannot leave the systems cleared to hold it. That is why regulated organizations, in banking and telecom as much as healthcare, now run open-weight models on their own hardware. One university hospital in Europe has already published the receipt. It wired an open-weight model into its Epic records system, the software that holds the patient chart, ran it entirely inside the hospital's own network, and had more than a thousand clinicians using it within five months. For that hospital, the cheaper bill is beside the point. Owning the deployment is the only version the law allows.

Outside the regulated world, though, the honest numbers say the switch has not arrived. Open-source models' share of enterprise production usage actually fell last year, to 11 percent from 19, by Menlo Ventures' count, even as developers reached for open models more than ever. Owning your intelligence is not free. Self-hosting means buying the hardware, staffing the deployment, and answering the pager when it breaks. That trade is the consideration playing out right now, company by company, and the outcome is not settled.

Decide What to Own Before You Decide What to Rent

So what does an owner actually do on Monday? Build a portfolio, on purpose. Decide which workloads are hard enough to need the frontier, and route the rest to a model you own and can run without watching a meter. IDC projects that by 2028, 70 percent of leading AI-driven enterprises will route across several models rather than depend on one. The mature version of this is not a switch from renting to owning. It is knowing which is which.

I am in the middle of this myself, slowly building a stock research agent for my own use. The decision I keep circling is whether to run it on a model I own or a frontier API I rent. I want to control the costs and only tap into a frontier model when real inference and intelligence is needed. The project is slow, my time going to house matters more than code, and I have not made the call. I am evaluating these decisions in real time, separate from the news cycle. Not everything we share needs to be a finished product. Sharing the deciding is the more useful thing anyway. My own small agent and a hospital data center come down to the same question, own it or rent it.

You do not need to have made the switch to think like an owner. Coinbase changed how it buys, and I am still deciding. What changed was the question we walk in with, from which model is best to which parts are worth owning and which are fine to rent. Which models exist, what they cost, and whether they stay switched on are decided far from your desk. What you own, and what you rent, stays on your side of the screen, no matter how capable the tools get. Which of your workloads truly need the frontier, and which just need a model you control and can run a million times?

The question is the first thing worth owning.

Enjoy this? Get it in your inbox every Tuesday.

Practical AI workflows. No hype. No spam. Just receipts.

Subscribe Free

Before you go...

Get one practical AI workflow in your inbox every Tuesday. Free. No spam. Just receipts.

Subscribe Free