A monthly FinOps cadence that works has three properties most reviews lack: a fixed agenda that covers variance against forecast, commitment coverage and utilization, open optimization actions and their realized savings, and anomalies; the right people in the room, those who can actually change the spend; and a rule that every item ends in a decision with an owner and a date, not a discussion. The test of a cadence is simple. If last month's review produced no decisions that changed this month's bill, it was a status update, and status updates do not need a meeting. The cadence exists to convert numbers into action on a reliable rhythm.
This article sits in the FinOps foundations cluster and links up to the cross cloud cloud cost optimization guide. It applies across AWS, Azure, GCP, and OCI, which differ in the instruments but not in the rhythm.
Why do most cost reviews fail?
Reviews fail in recognisable ways. They become a presentation of a dashboard nobody disputes and nobody acts on. They fill with observers who cannot make decisions, so the people who can hedge rather than commit. They report total spend went up or down without the why, so there is nothing to decide. And they end without owners or dates, so the same issues reappear next month, slightly worse. The underlying failure is that the review reports the past instead of deciding the future. A cadence that works is built to produce decisions, and everything in its design serves that.
What is the fixed agenda?
The same four items, in the same order, every month. Familiarity is a feature: a predictable agenda means people arrive prepared and the meeting moves.
| Agenda item | What is reviewed | Decision it produces |
|---|---|---|
| Variance | Actual versus forecast, with the reasons for each material gap | Accept the variance, correct the forecast, or assign a fix |
| Commitments | Coverage and utilization of Savings Plans, Reservations, CUDs, Universal Credits against forecast | Buy, hold, or adjust coverage; flag renewals approaching |
| Open actions | The optimization backlog and the realized savings of closed items | Reprioritise, unblock, or close each action |
| Anomalies | Spend spikes and new cost lines since last review | Assign an owner to investigate or confirm expected |
Variance comes first because it frames everything else: it tells you whether the plan is holding. Commitments come next because they are the biggest lever and carry the most risk, the use it or lose it structure of enterprise agreements means an unwatched commitment is money lost. Open actions keep the optimization backlog moving and tie back to the realized savings the program reports. Anomalies catch the new problems before they compound.
Who needs to be in the room?
Keep it small and keep it to people who can decide. The core is four roles: the FinOps lead who owns the agenda and drives to decisions; the engineering owners of the largest spend, who can actually change it; finance, who owns the forecast and the budget; and procurement when commitments or renewals are on the table. Everyone else belongs on the distribution list. A review of eight decision makers beats a review of twenty observers, because the observers dilute accountability, they let the people who can act defer to consensus that never forms. If a team's spend is material, its owner is in the room; if it is not, its numbers go in the pack and its owner reads the minutes.
What metrics drive the cadence?
A handful of living numbers, not a wall of charts. Variance against forecast is the headline. Commitment coverage and utilization tell you whether the biggest lever is working. Realized savings, measured against a baseline rather than identified savings, tell you whether the program is actually cutting the bill. Tag coverage tells you whether allocation can be trusted. And a small set of unit economics figures, cost per customer or per product, tell you whether spend is growing with the business or ahead of it. These are the numbers a CIO reports upward, and they are the numbers the cadence is accountable for moving. The discipline of measuring realized rather than identified savings is what keeps the cadence honest over time.
A European SaaS company held a monthly cloud cost meeting that ran ninety minutes, walked through a long dashboard, and changed nothing; spend kept climbing. Rebuilding the cadence fixed it without new tooling. The agenda was cut to the four fixed items, the room was reduced to the FinOps lead, the three biggest engineering owners, finance, and procurement, and a rule was set that every item ended in a logged decision with an owner and a date. Within two cycles, commitment utilization that had been drifting was corrected, two stalled optimization actions were unblocked, and an anomaly that would have run for a quarter was caught in the first month. The standing rhythm was a meaningful part of holding the 31 percent median reduction the program had achieved in the first 90 days. Figures are verified against billing data and anonymised.
How does the cadence connect to the rest of the program?
The monthly cadence is the operating heartbeat that the rest of the FinOps program runs on. It depends on trustworthy allocation underneath it, because variance and unit economics are meaningless without accurate attribution. It feeds the savings ledger, because the open actions item is where realized savings get reviewed and decay gets caught. And it sits between the quarterly commitment planning, where the big enterprise agreement decisions are made, and the daily anomaly alerts, which surface the spikes the monthly review then assigns. Run weekly only if spend volatility demands it; for most organisations monthly is the right grain, frequent enough to catch problems while they are small, infrequent enough that each meeting has real decisions to make. The full operating model is in the FinOps operating model guide.
Frequently asked questions
Stand up a cadence that moves the bill with us
We design the agenda, set the room and the decision discipline, and wire the cadence into your forecast, commitments, and savings ledger so the monthly review actually changes the spend, independent and on your side of the table. Talk it through with a senior analyst.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.