All Posts

Nobody budgets for the token bill until it's too late

By Ryan Short

Nobody budgets for the token bill until it's too late

Here’s something worth sitting with: Uber blew through its entire 2026 AI budget in four months. Gone, on tokens, and they eventually had to cap employees at $1,500 a month per AI coding tool just to get spend under control. That’s not a rounding error. That’s a budget line turning into a horror story for finance teams everywhere, and it’s the kind of number that should make every engineering org take a hard look at how it’s actually spending on AI.

QA is racking up the same kind of bill, quietly. Every org running AI-driven testing is burning through tokens at a rate that’s climbing, not slowing down. And if you look at where the money’s really coming from, a lot of today’s “reasonable” AI pricing is being propped up by VC subsidy while investors try to buy adoption. That subsidy doesn’t last forever. When it goes, the real price shows up on your invoice, all at once, the way it just did for Uber.

The part most teams get wrong

They’re spending tokens to regenerate code every single time something small breaks: a locator shifts, a selector changes, whatever. Multiply that across a real test suite and you’re paying the AI to redo work it already did, over and over, forever. That’s the model most orgs, and most competitors, are running on right now.

What we built instead

We built Klarent to not do that. We spend tokens once, to generate the code, and then we maintain it. Self-healing catches the small breaks without a fresh generation call, and humans stay in the loop for the stuff that actually needs a person’s judgment. No regenerating a locator’s worth of code because a button moved three pixels. That’s the difference between a token bill that grows with your test suite forever, and one that doesn’t.

The AI cost curve is only going one direction right now, at least until the subsidies run dry. It’s worth figuring out where your QA spend actually goes before it’s your team writing the “we had to cap it” post.

Want to see what your test suite would actually cost on Klarent? Get in touch, we’re happy to run the numbers with you.

━━━━

More blogs