Run a monthly cloud and AI cost review that ends with decisions
Prepare a monthly FinOps review with a clear scope, explained changes, owners and follow-up actions. Includes a free PDF guide with a worked example.
1. Prepare a report people can trust
Before the meeting, choose the billing period, timezone, currency and cost basis. List the connected sources and the sources still missing. Record when each source was last updated. A complete-looking chart should not conceal an incomplete month.
Separate finalized periods from provisional ones. If a report changed after the last review, record the reason: late billing, credit, mapping correction or newly included source. Keep a dated copy of the report so decisions can be reconstructed.
2. Explain the changes that matter
Compare with a genuinely comparable period. Start with the largest absolute changes by provider and responsible team. Break each into workload growth, price or model changes, commitments, new scope and unexplained residuals.
Ask the relevant owner for evidence such as a deployment, usage measure or provider adjustment. Avoid turning a correlation into a diagnosis. If demand grew, report the business outcome alongside cost instead of automatically calling the increase waste.
3. Keep the meeting focused
Use a short agenda with a named decision maker for each issue. Send detail beforehand so the meeting is not spent navigating dashboards. Bring finance into questions about cost basis or allocation policy and engineering into workload investigations.
- Confirm report completeness and unresolved reconciliation items.
- Review material changes and current budget exposure.
- Review unallocated costs and disputed ownership.
- Choose a small set of actions with owners and review dates.
4. Make actions testable
Write the intended result, evidence needed and rollback condition. “Optimize AI” is not an action. “Evaluate shorter retrieval context on the agreed quality set, then compare accepted outcomes and billed cost” is specific enough to review.
Distinguish identified opportunity, approved action, implemented change and verified outcome. The amount suggested by a recommendation is not realized savings. Do not add overlapping opportunities together without checking their scopes.
5. Close the loop next month
Begin the next review with the previous decisions. Compare the agreed measures, explain changes in demand and keep unresolved work visible. Cancel actions whose assumptions no longer hold and record why.
The PDF guide below explains how to read a higher bill, check its cause and decide what to do. It includes a worked fictional example and practical checks. You can also read it online without a Fivemetrics account.
Sources & further reading
- FinOps Foundation: Reporting & Analytics
Framework reference for communicating cost information to decision makers; consulted 17 September 2026.