Cost Optimization Just Got a Second Author

Cost Optimization Just Got a Second Author
A model rewrote its own GPU serving code, cut OpenAI’s inference cost, and got itself a price cut in the field — while nobody prompted it to think about money.
That’s not a caching trick. That’s not a router sending easy questions to a cheaper tier. That’s the thing traditionally done to a model — the entire FinOps-for-AI playbook — being done by one, autonomously, at the infrastructure layer. And it landed in the same week I was already forwarding myself an open-source tool that does the mirror-image job on AWS: scan the account, find the waste, hand you a ranked list with a dollar figure attached, no ticket, no Slack thread, no waiting on next quarter’s audit. Cost optimization didn’t get better tooling. It got a second author, on both sides of the meter, in the same seven days.
Your Agent's Model Tier Is Your Purchasing Power

Your agent lost you money last week, rated the experience five stars, and you agreed with it. That is not a bug in the agent. That is the entire shape of the market we just walked into. When a machine negotiates on your behalf and comes back with a worse deal than a better machine would have gotten, it does not return an error. It returns a plausible, satisfying, worse outcome — and then it tells you the deal was fair. And here is the cruelest part: you have no way to know it was wrong, because you never see the deal you didn’t get.
KPMG Didn't Buy AI for 276,000 People. It Bought a Control Plane.

KPMG didn’t buy AI for 276,000 people. It bought a control plane — and threw in a quarter-million seats to keep you looking the other way.
Read the June 9 announcement again. Everyone fixated on the headcount: more than 276,000 professionals getting Copilot. That’s the press release. The load-bearing noun is one clause down — Agent 365, the system KPMG adopts to “manage how AI agents are deployed, managed, monitored and updated,” giving it “centralized governance and control of AI agents operating across systems, data and business processes.”
The Subsidy Era of Agentic Coding Just Ended. Nobody Built FinOps for It.

The best deal in software just ended, and the replacement bill is non-deterministic.
For two years, flat-rate coding-agent pricing was the deal of the decade. Twenty bucks a month, point an agent at your codebase, let it churn. You were almost certainly consuming more value than you paid for. That wasn’t generosity. It was customer acquisition, financed by venture money, priced below cost on purpose. And in a two-week window this spring, three different vendors quietly clawed it back.
The $965 Billion Number Is a Distraction. Here's What Actually Matters.

The $965 billion number is a distraction. Here’s what actually matters.
Last week, Anthropic raised $65 billion and saw its valuation approach a trillion dollars. Every business publication on the planet covered the number. Almost none of them covered the insight.
The insight came from Simon Willison, posting on May 27 — one day before the funding closed — and it’s worth more to your business than any valuation figure: enterprise AI has found product-market fit. Not “gaining traction.” Not “showing promise.” Fit. The kind where customers stop subscribing and start paying by the token because they’re consuming so much that the subscription ceiling became a constraint on their business.
Your AI Agents Aren't Failing Because the Models Are Bad. You Just Never Built an Ops Team for Them.

The enterprise AI agent story of 2026 is a demo story. Somewhere between “watch this” and “we run this at 2am,” the wheels come off — and almost everyone is blaming the wrong part of the car.
Quick roadmap:
- The headline stat and why the usual diagnosis is wrong
- What actually kills agents in production (it’s not the model)
- What the teams that crossed the gap did differently
- The uncomfortable truth: you can’t buy your way out of this
The Number Nobody Wants to Explain
A March 2026 survey put enterprise agent pilots at roughly 78%. Production deployments below 15%. That is not a rounding error. That is a structural failure, happening industry-wide — across models, across vendors, across use cases.