Most AI cost-cutting stories involve trading capability for savings. Databricks found a way to avoid that tradeoff: the company reports cutting per-task AI coding costs by as much as 90% in some scenarios while simultaneously increasing developer adoption.
The result came from four techniques stacked on top of each other, not a single silver bullet.
The Four Techniques
- Routing default traffic to cheaper and open-source models. Rather than defaulting every request to the most capable (and most expensive) model, Databricks shifted the baseline toward lower-cost alternatives where task complexity allowed.
- Automating model selection through routing. Instead of developers manually choosing a model, a routing layer picks the right one based on the task. Cheaper models handle simpler work. Heavier models only engage when needed.
- Progressive friction instead of hard caps. Rather than blocking developers when they hit a spend threshold, the system gives every developer visibility into their own usage. Friction rises as costs climb, but the work doesn’t stop.
- Cutting token overhead through context management. Reducing unnecessary tokens in context windows directly shrinks the per-task cost without changing what the model can do.
The Operator Takeaway
The 90% figure applies to specific scenarios, not across the board. But the directional pattern is worth copying regardless of your stack size.
The routing approach is the most transferable idea here. If your team defaults every AI request to the most powerful model available, you’re almost certainly overpaying for a large share of tasks. A lightweight routing layer that matches task complexity to model tier is a one-time build with compounding savings.
The progressive friction model is also worth noting. Hard budget caps tend to create adversarial behavior where developers game the system or avoid useful tools altogether. Visibility plus soft friction keeps people informed without blocking productive work.
