Your usage dashboard reports the wrong month

In a product billed by usage, the customer's real question is never what they spent. It is what they are about to spend. Most usage screens in hosting, cloud and SaaS answer the first question well and the second one not at all.

That gap is where renewals quietly go wrong. A customer who cannot forecast their own bill cannot defend it internally, and someone who cannot defend a bill starts looking for a supplier whose costs are easier to explain. If you sell on consumption, the usage dashboard is not reporting. It is the screen where the price gets agreed again every month, without you in the room.

The cost question moved inside the product

Cost used to be settled before signature, on a pricing page and in a procurement call. With consumption pricing it is settled continuously, by people at the customer's end whose job is to account for what your product costs them.

The FinOps Foundation's 2026 State of FinOps, published in February and drawn from 1,192 practitioners who between them account for more than 83 billion dollars of annual cloud spend, is a fair picture of who those people are and what they are struggling with. Ninety-eight per cent of them now manage AI spend, up from 63 per cent in 2025 and 31 per cent in 2024. Across SaaS, licensing, data centre and data cloud platforms, the capability they rank first is allocation: working out which part of the business a given cost belongs to. Understanding the cost comes before reducing it.

Read that as a design brief rather than an industry statistic. Your customer has somebody whose week includes explaining your invoice to a finance director. Everything they need in order to do that well, or badly, sits on a screen you designed.

Last month is not the number anyone needs

Most usage screens are built outwards from the billing system, so they inherit its shape. Six invoices as a bar chart. Line items in a table. A total as at yesterday, with nothing to say about where it is heading. The data is accurate and the screen is useless, both at once.

The questions customers actually arrive with are different ones. Am I on course to go over this month. Which project caused the jump on the ninth. If I leave this environment running until the end of the quarter, what does that cost me. A dashboard that cannot answer those is asking the customer to do arithmetic on your behalf, in a spreadsheet, once a month, in a slightly worse mood each time.

An invoice explains what happened. A forecast is the only number a customer can act on.

AI made the meter harder to read

Consumption was hard enough to follow when the unit was a server. Tokens, requests and GPU time are worse. The unit is small, the volume is unstable, and the person who triggers the cost is rarely the person who sees it. In the same survey, the challenges named most often in managing AI spend are visibility into those costs, allocating them to business units and working out what they return. The most requested feature in tooling is granular monitoring of AI spend, down to tokens, requests and GPU utilisation.

So if your product has an AI feature with a variable cost behind it, the meter is part of the feature, not an accounting detail that follows later. Ship the capability without the counter and adoption stalls for reasons that look like indifference and are closer to caution. It is the same instinct behind why nobody uses our AI feature: people are slow to adopt anything whose consequences they cannot see in advance.

What the screen has to do

Four things, none of them technically hard:

• Forecast by default. Projected spend at month end, next to spend to date, with the assumption written in plain words underneath.
• Warn before the limit rather than at it. An alert that arrives with the invoice is notice of a decision already taken.
• Attribute cost to the things the customer recognises. Sites, projects, environments and teams, not internal product codes.
• Let the customer set their own ceiling, and say honestly what happens when it is reached.

Teams tend to hear all this as a billing project and send it to whoever owns billing. It belongs with whoever owns the product, because the usage screen is a product surface in the way that a control panel is: the place where customers form a view of whether you are straightforward to deal with. Nobody renews on the strength of an invoice. Plenty of people leave because of one.

The supplier who shows the bill arriving keeps the account through a bad month. The one who sends it as news gets discussed in a meeting it was never invited to.