Operations | Monitoring | ITSM | DevOps | Cloud

When spend moves, the first question is always “compared to what?” Answering it used to mean pulling up two tabs with two different date ranges and toggling between them, or squinting at a single delta number without the ability to customize what you’re comparing against. Compare Periods puts both periods in front of you at once, so a spike, a regression, or a shift shows up on the chart and in the cost table, without you doing the math yourself.

Only 22% of finance leaders can tie their AI spend to a business outcome, according to CloudZero’s 2026 finance survey. When AI ROI falls short, it usually isn’t because a company is doing too much AI. It’s that no one is watching which model runs which task, and that one choice accounts for a large part of the cost. Here’s why it happens.

Model Rightsizer is an open-source Claude Code sub-agent from CloudZero that scores each task on capability need versus cost pressure, then routes it to the smallest model that can handle it. In its first week, it cut Opus spend 75% while shifting 234x more work to Sonnet. Every Claude Code agent you run has to answer a question it usually never gets asked: does this task need the smartest model available, or are you paying Fable prices to rename a variable across three files?

Let’s say you want a Matches condition that picks up “prod”, “PROD”, and “Prod”, so you write ‘Matches: (?i)prod’ and check it in an online regex tester before publishing. It looks fine. Python accepts it, and so does JavaScript. Dimension Studio used to accept it too, and the rule is published. Then your data stops updating. The new pattern is what’s keeping it from materializing, but nothing tells you that.

Proving AI business value means sorting every AI investment into one of four buckets - revenue growth, cost avoidance, productivity gain, or risk reduction - then tracking spend at the unit level (per feature, customer, or team) so each dollar has a traceable return. Most companies measure one bucket well and leave the rest unattributed. That gap is why the same AI deployment can look like a $40M win and a public reversal at the same time.

For many teams, Budgets is the first page they open in the morning, and it should tell them where they stand at a glance. That’s easier now, with a redesigned Budgets page and a way to set a budget without leaving the app.

Codex pricing runs six tiers, from free to $200 a month, but the sticker price is not your real bill. OpenAI Codex pricing 2026 charges by the token, not the plan, a change that took effect in April. Plus is $20, Pro starts at $100, and everything past that depends on how many files you let the agent read. Most Codex pricing guides hand you a price list and call it done. That is like pricing a taxi ride by the door handle. The meter is what matters, and OpenAI put a real one on Codex this year.

Claude Opus 5 launched July 24, 2026 at $5 per million input tokens and $25 per million output tokens, identical to Opus 4.8. It delivers near Claude Fable 5 performance at half Fable's price and is now the default model on Claude Max. New effort settings let teams trade capability for token savings, which means two teams on identical pricing can now run up very different bills. Finance teams, that last part is your problem. Anthropic has shipped a model that costs exactly what the old one cost.

A savings number tells you money is on the table, but it doesn’t tell you whether the finding holds up, what it’s based on, or what to do next. In that gap, recommendations pile up unactioned. When you’re staring at thousands of them, a title and a dollar figure isn’t enough to decide which are safe to act on.

Creating an API key used to mean sorting through categories organized around our internal structure, not how you’d use them, so finding everything you needed for a specific job meant guessing, or having someone on our team walk you through it. Now you can tell what each permission actually does at a glance.