Domain 4 · Manage the FinOps Practice
A practice that scales with the bill.
FinOps Practice Operations is the part nobody writes a deck about: cadence, SLAs, review workflow. CloudMonitor ships cadence templates and workflow SLAs that suit the 60% of practices running a centralised model — and the 21% running hub-and-spoke (State of FinOps 2026).
The problem
A practice that depends on heroics.
Reviews drift to ad-hoc.
The monthly cost review starts strong and erodes into a quarterly afterthought. Without a cadence it depends on whoever's keenest that month.
SLAs live in heads.
Practitioners "know" what should be done in a week. New joiners don't. Engineering doesn't. The practice never industrialises.
Centre scales worse than the bill.
Three people, eight business units, a doubling cloud bill. The central FinOps team becomes a queue, not an enabler.
How CloudMonitor answers
Operations the practice can actually run.
Cadence templates.
Weekly anomaly review, monthly optimisation, quarterly assessment. Built-in, owner-routable, with the data each cadence needs already in place.
Workflow SLAs.
Each recommendation, anomaly, and budget breach has an SLA clock. Breaches escalate; closes get logged. The practice runs on something more than memory.
Hub-and-spoke ready.
RBAC at the cost-group level lets BU-embedded champions own their slice while the centre keeps oversight. The structure 21% of practices have moved to (State of FinOps 2026).
Centralised model supported.
For the 60% of practices that run centralised, everything routes to one queue with priority rules and saving-weighted ordering. The same product, sized for both shapes.
Outcomes
A practice that survives the next reorg.
60%
Centralised practices (State of FinOps 2026)
21%
Hub-and-spoke (State of FinOps 2026)
SLA
Per-workflow clocks, escalations logged
See cadence and SLAs running in the demo tenant.
Walk the templates, toggle centralised vs hub-and-spoke routing, inspect the audit log.