A monthly cloud cost review is the recurring meeting where cost owners explain what moved, decisions get made, and actions get assigned. Run well, it is the single highest leverage habit in cloud cost management: it converts the data your tooling produces into changes that lower the bill. Run badly, it becomes a chart parade where numbers are shown, nobody is on the hook, and nothing changes. The difference is structure. This guide walks through how to run the review step by step so it consistently produces decisions and follow through.
This article is part of our FinOps cluster and links up to the pillar, what is FinOps, a practical introduction for 2026. The person who usually runs this meeting is covered in the sibling guide on the role of the FinOps practitioner.
Step 1 · Get the right people in the room
The review fails when only finance shows up, because finance cannot change the architecture that drives cost. Invite the cost owners: the engineering leads accountable for the allocated spend, a finance partner, and the FinOps practitioner who runs the meeting. Keep it small enough that owners cannot hide. The point of the meeting is that the people who can act are present when the decision is made. If your spend is not allocated to owners yet, that is the prerequisite, and it comes before the meeting works at all.
Every line of spend discussed should have a named owner present who can explain it and commit to an action. If a cost has no owner, the meeting's first output is to assign one. A review full of spectators produces no decisions.
Step 2 · Open with the headline numbers
Start with the whole picture in two minutes: total spend this month versus last and versus forecast, and the trend in your key unit cost. Leading with the unit cost, not just the absolute bill, keeps the conversation honest, because spend that rises while serving more customers is not the same as spend that rises while serving the same load. For how to choose and present that unit, see our guide on cloud unit economics.
Step 3 · Explain the movement
The core of the meeting is variance: what changed and why. Walk the largest movers, up and down, and have each owner explain the driver. A spike from a launch is healthy; a spike from a forgotten test cluster is waste. This is also where anomalies surface for discussion if they were not already caught and resolved. The goal is that every material change has an explanation by the end of this segment, so nothing is left as an unexplained number.
Step 4 · Review the optimization pipeline
Next, look at the savings opportunities in flight: rightsizing, scheduling, idle cleanup, and commitment coverage. Each should have an owner and a status. This is where the meeting drives the continuous improvement that keeps a bill falling rather than drifting up, the discipline covered in our guide on reducing cloud waste continuously, not once. New opportunities identified this month get added; stalled ones get unblocked or killed.
| Agenda segment | Time | Output |
|---|---|---|
| Headline numbers and unit cost | 5 min | Shared picture of the month |
| Variance: explain the movers | 15 min | Every change explained |
| Optimization pipeline | 15 min | Owners and statuses confirmed |
| Decisions and actions | 10 min | Named actions with dates |
Want the review run for you, with the savings tracked?
We facilitate the monthly cost review, prepare the numbers, and chase the actions to closure as part of Managed FinOps or a fixed fee engagement. On the performance model, you pay only from realized savings.
Talk about FinOps implementation →Step 5 · Close with decisions and actions
End the meeting by converting discussion into a short list of named actions with owners and dates. This is the segment that separates a review that lowers the bill from one that does not. No action without a name and a date; no decision left implicit. The practitioner captures the list and circulates it the same day, so the next month's review opens by checking what was promised against what was done.
Make the follow through stick
The meeting is only as good as the follow up. Track the action list between reviews, not just at them, and start each session with the status of last month's commitments. When owners know the previous list will be checked in front of their peers, actions get done. This accountability loop is the cultural payoff of the cadence and connects directly to the operating model described in our guide on the FinOps operating model.
The FinOps Operating Model Blueprint includes a ready to use monthly review agenda, an action tracker template, and the metrics pack to put in front of owners.
The short version
A monthly cloud cost review works when the right owners are in the room, the meeting opens with unit cost, every movement is explained, the optimization pipeline is reviewed, and it closes with named actions and dates that get tracked to closure. It is the cadence that turns visibility into a falling bill. When you want the review facilitated and the actions chased for you, that is part of what our FinOps implementation service delivers.