Operations | Monitoring | ITSM | DevOps | Cloud

On June 18, OpenAI gave ChatGPT Enterprise admins new credit usage analytics and spend controls. It’s a single view of credit consumption broken down by user, product, and model, default workspace budgets, per-group limits, and a Cost API for pulling the data into their own systems. Two days earlier, Microsoft shipped Copilot Cowork with spending limits, budget allocation, usage alerts, and user-level caps. This is a step in the right direction.

Customer lifetime value (CLV) is the total revenue a business expects from a single customer over the entire relationship, minus the costs of serving them. The standard SaaS CLV formula: Average Revenue Per Account x Gross Margin % / Monthly Churn Rate. For a $500/month customer with 75% gross margin and 5% churn: CLV = $7,500. That number can swing materially once AI spend per customer is built into gross margin, something many SaaS companies still don't do.

Point A: 1835. Andrew Carnegie is born in a weaver’s cottage in Dunfermline, Scotland. The cottage has one main room, which the Carnegies share with another family. Point B: 1901. Andrew Carnegie becomes the richest man in the world when Carnegie Steel Company wins the Iron vs. Steel industrialists’ war, and he sells the company to J.P. Morgan for the modern equivalent of $450 billion.

The Anthropic Enterprise connector pulls per-user Claude Enterprise cost and usage into CloudZero, so you can allocate Claude spend to the teams that drove it.

The core of ROI is visibility. If you can clearly see … 1. What it costs to produce the thing you make, and 2. How much money it makes you … then calculating ROI is easy. But with AI, as with the cloud before it, getting that visibility is extremely challenging. Why? Because the cost data associated with each is inherently chaotic.

CloudZero Explorer now tracks your query history and lets you save up to 12 configurations and 10 favorite dimensions, so your most-used cost analyses are one click away.

Eight new Azure recommendation types now scan your environment for idle, unattached, and over-provisioned resources, then tell you exactly what to cut.

This is the first in a series we’re calling AI ROI Dispatches, where we share stories from CloudZero and our customers on tying AI spend to real business outcomes.

CloudZero now splits an Amazon Bedrock line item into spend by model and by the team, user, or project behind each call, straight from your AWS bill.

How to track expenses for a business: categorize expense types (operating, software, cloud, travel, capital), choose a tracking method (spreadsheet, accounting software, expense management tool, or cost intelligence platform), connect data sources (bank feeds, cloud billing APIs, SaaS invoices), assign ownership per cost center, set a reporting schedule, and audit quarterly.

The CloudZero VS Code Extension 2.0 adds a sidebar that brings CostFormation namespace management directly into your editor, so you never have to break flow for a browser tab.

In Explorer, you build a filter set and group-by to answer a cost question, and often that’s exactly the configuration you’d want to save for later. But saving it as a View meant navigating away from Explorer, opening the Views page, and rebuilding the same configuration from scratch: filter by filter, dimension by dimension. That friction was enough to discourage saving exploratory analysis as a View at all You can now save any Explorer analysis as a View in place.

AI pricing covers the cost structures and billing models providers use to charge for AI products: per-token APIs (GPT-4o at $2.50/1M input tokens), per-seat subscriptions (Copilot at $30/user/month), per-conversation billing (Agentforce at $2/conversation), and consumption-based GPU compute (H100 instances at $55.04/hour). There is no standard. The total AI cost is almost always higher than the sticker price.

Cost monitoring, exploration, investigation, and reporting used to live in separate places, so following a single cost question meant hopping between tools.

Your AI calls already emit OpenTelemetry: your LLM gateway exports it, and it’s the open standard your own services can speak. But you don’t have anywhere to turn those spans into spend you can allocate to an outcome. Now you can. CloudZero exposes an OpenTelemetry endpoint that doesn’t care what’s on the other end.

You can already split AI spend by team and by model. But that’s not what your CEO asks in the QBR. The question is what you got for it: what did it cost to ship that feature, to launch that campaign, to serve that customer. And is the AI bet behind it paying off? Now you can allocate AI spend to the outcomes you own: customer, product, feature, the strategic bet on the P&L. Not just the team that spent it.

Claude Mythos is now available to the public through Claude Fable 5, released June 9, 2026. Claude Fable 5 pricing is $10 per million input tokens and $50 per million output tokens, exactly 2x Claude Opus 4.8 ($5/$25). Claude Mythos 5 (the restricted Project Glasswing version) has identical pricing. Prompt caching cuts input spend by 90%. Batch API pricing is $5/$25 (50% off). In April 2026, Anthropic announced a model it said was too dangerous to release.

AI spend has no ceiling. An engineer can burn $5,000 in an hour, and a team that spins up an agent on Friday can loop it on a bad prompt all weekend. You find out when the bill lands: the money is already gone, the damage pieced back together from logs. Cloud spend had a natural limit. Tokens don’t. Now you see it as it happens. Connect a source and the calls stream in within seconds. Within minutes they’re broken out by model, provider, agent, and user.

This edition of the Pulse is shifting lanes. We’re calling it the AI Economics Pulse now, because the question on every finance leader’s mind is whether AI spend and the returns on it can be made to pair at all. That question came to a head over the last few weeks. The bills came due, and they came due in public. Uber burned through its entire 2026 AI budget in four months and capped employee spending on Claude Code and Cursor at $1,500 a month.

Your engineers run Claude Code. Your designers are in Cowork. Half the company has Claude open in a browser tab, and a few are on Cursor. It’s on their laptops, each person authenticated a different way, and none of it touches your gateway. The only record you get is one lump-sum bill at the end of the month. Now you can capture it where it happens – on the laptop.

Something unusual happened in the first half of 2026: the most productive AI coding tool on the market became the most financially dangerous. And the companies that discovered this the hard way read like a Fortune 50 roll call.

One dimension gives you a list. Two gives you a story. Now you can slice by two dimensions simultaneously, right in CloudZero Explorer.

You’re funding AI across four billing relationships – Anthropic direct, OpenAI, Claude through Bedrock, Claude through Vertex – and the spend climbs every month. When your CEO asks what it’s producing, you have a number and no answer. Not which product it built, which customer it served, or which bet it’s paying off. And you’re being asked to approve more of it.

Org admins can now see each user’s last login directly in Settings > Users, making it easy to spot inactive accounts, manage licenses, and run security reviews without opening a support ticket.

CostFormation is how your organization models cost allocation. As more teams adopt it, protecting that logic matters. RBAC for CostFormation Namespaces lets you scope access at the namespace level, so the right people can view and edit Dimensions, and everyone else can’t.

CloudZero originated as a way to make sense of your cloud costs. Costs spread across bills with billions of line items belonging to resources that might or might not have been tagged (or taggable), spun up by engineers working across teams, on different microservices, features, and products, that served a wide range of customers. Kubernetes. Multi-cloud. Check, check, check.

Every quarter, the same scene plays out in boardrooms across the Fortune 500. The CEO asks: “What is the return on everything the company is spending on AI?” The CTO talks about productivity gains and developer velocity. The CFO points at a cloud bill that doubled but cannot isolate which line items are AI. The board nods politely and tables the discussion until next quarter, when the same question will produce the same non-answer. (If this sounds familiar, you are not alone. Keep reading.)

Anthropic shipped Claude Opus 4.8 on May 28, 2026, exactly 41 days after Opus 4.7. The SERP was empty for two days after launch. Not because nobody cared. Because engineering managers and finance teams were doing the math on whether the bill changes.

Customizability. Feature velocity. Performance. Capabilities that are critically important to all B2B software users. And capabilities in which CloudZero’s brand-new platform specializes. Pitching a total frontend overhaul didn’t necessarily make me CloudZero’s most popular new PM. But it’s made CloudZero faster, more customizable for a wider range of personas, and easier to update with the new features that matter most to our customers. And, if I may say, it also looks beautiful.

CloudZero continues to ship new features and enhancements at a fast pace. We’re publishing these product update posts to keep you up to date on our velocity and how we’re adding customer value.

CloudZero continues to ship new features and enhancements at a fast pace. We’re publishing these product update posts to keep you up to date on our velocity and how we’re adding customer value.

AI spend is going parabolic, and the labels on the bill (OpenAI, Anthropic, Gemini) are about all a CXO gets to work with. The hard part of tying that spend to outcomes is structural. A major portion of AI spend isn’t COGS. It’s the spend on coding agents producing the software, the spend on building marketing content, the spend on custom sales tooling, the spend on Intercom agents and Sybill analysis.