Databricks' Playbook for Cutting AI Coding Costs: The Right Model Swap Alone Saves 50%+
- AI coding clearly works — some teams at Databricks saw 10x throughput. But token bills are growing just as fast, and nearly every company scaling it has hit that wall.
- The biggest lever is switching models. Stripe's tests showed the new Opus wasn't better, just pricier, so they refused to roll it out internally.
- The most counterintuitive finding: no company uses hard caps as a daily tool. They keep the kill switch, but only as a last resort. Two very practical reasons why, below.
Efficiency Is Up, But the Bill Is Rising Faster
Databricks recently published a strikingly practical post-mortem on cost control: in AI-assisted coding, every internal speed metric has improved, with some teams seeing 10x output. But the bill has climbed exponentially alongside it.
That curve is unsustainable. Left unchecked, it eventually outpaces company revenue. It puts businesses in an awkward spot: they want to push AI adoption as far as possible and put the best tools in every employee's hands, but the total cost is eating into — and in some cases canceling out — the very efficiency gains AI was supposed to deliver.
The good news is that the companies who scaled AI first have figured out how to do both: give everyone frictionless access to AI tools while keeping per-seat costs locked in a roughly fixed range. The material here comes from Databricks' own experience, plus conversations with Stripe, Coinbase, Uber, and Ramp.
Four tactics, and what each one saves:
| Tactic | What it does | Savings |
|---|---|---|
| Switch to cheaper models | Open-source models + newer, more efficient ones | 50%+ |
| Smart routing | Dynamically dispatch between models and tools | ~30% |
| Spend governance | Cost visibility, overage alerts, budget tripwires | ~10% |
| Context optimization | Compression, trimming tool bloat, tuning caches | ~10% |
Some of this is off-the-shelf; the rest takes infrastructure work, especially on developer-local tools and multi-model traffic routing. Databricks has open-sourced or made freely available both key pieces of their own stack: Omnigent, the unified front-end for developers, and Unity AI Gateway, which manages the traffic.
Day-to-Day Coding Doesn't Need the Smartest Model
When people talk about "frontier models," they mean the smartest ones. Labs are racing to push the ceiling of intelligence; today's top models can crack math problems and surface novel security vulnerabilities.
But once AI is in the hands of thousands of developers across a company, a different frontier matters more: the efficiency frontier. It's the set of models that deliver a given level of intelligence at the lowest price.
You'd call Einstein for a genuinely hard physics problem. Renaming a component or filling in boilerplate doesn't need that brain — using Einstein there is just burning money. Most everyday coding falls in that second bucket: it needs a model that clears the engineering-quality bar, and a higher ceiling won't help.
So the real driver of your company's bill is what those "good enough" models cost. And this efficiency frontier is advancing much faster than the intelligence frontier: new models land almost weekly, and each dollar buys more usable intelligence than the batch before it.
Switching Models Saves the Most, but Public Benchmarks Can't Be Trusted
This is the biggest win of the four: rapidly moving to newer, more efficient models saves more than anything else. But to capture that, a company first has to know which new model is genuinely better than the one they're on.