The FinOps operating model breaks cloud cost management into three repeating phases. Inform gives everyone visibility into what cloud costs and who is driving it. Optimize takes action to reduce that cost through rightsizing, waste removal, and commitments. Operate makes the practice continuous, with the governance and process that keep gains in place. The phases are not a one-time sequence; they run as a loop, and a mature practice is doing all three at once across different parts of its estate.
This article is part of our FinOps cluster. For the foundation, start with what is FinOps, a practical introduction for 2026, the pillar this guide links up to. The operating model maps cleanly onto our own See, Cut, Lock, Run method: See is Inform, Cut and Lock together are Optimize plus the govern step, and Run is Operate.
Inform: make cost visible and attributable
The Inform phase answers two questions: what does cloud cost, and who owns each part of it. That means cost and usage data normalized into a consistent view, tagging and account structure so spend maps to teams and products, and showback or chargeback so the owners see their own numbers. Without Inform, every later action is a guess, because you cannot reduce or govern spend you cannot see and attribute. This is where most organizations should start, and where many never fully finish, because tag coverage decays if it is not enforced.
Teams under cost pressure often want to jump straight to buying commitments or cutting resources. Without visibility and attribution first, those moves are blind. Inform is unglamorous, but it is the phase that makes everything after it deliberate rather than lucky.
Optimize: take action to reduce cost
The Optimize phase is where cost actually comes down. The sequence matters: rightsize and schedule first so you are not buying commitments on bloated baselines, clear idle and zombie resources, then commit with reservations and savings plans on the clean baseline that remains. Optimization spans every cluster of work, from compute rightsizing to storage tiering to commitment strategy. The discipline is to optimize on a clean baseline, because committing to oversized usage just locks in waste at a discount.
Operate: make it continuous
The Operate phase is what separates a one-off cleanup from a practice. It is the governance, process, and culture that keep spend optimized as the estate changes: budgets and anomaly alerts, a regular cost review, policies and guardrails, and engineers who consider cost as a normal design input. Without Operate, the savings from a single optimization pass erode within months as new resources spin up untagged and unmanaged. The sibling guide on FinOps maturity, crawl, walk, run explained covers how the Operate phase deepens as a practice matures.
The phases run as a loop, not a line
The biggest misunderstanding of the model is reading the three phases as a project plan you complete once. They are a continuous loop. New workloads constantly enter the Inform phase even while existing ones are being optimized and others are fully operated. A mature organization is informing on its newest spend, optimizing its recently visible spend, and operating its established spend, all at the same time. The maturity question is not which phase you are in but how well you run all three in parallel.
Want the operating model stood up, not just understood?
We implement Inform, Optimize, and Operate as a running loop in your organization, with the data, the actions, and the governance to keep it turning. On the performance model, you pay only from realized savings. No savings, no fee.
Talk about FinOps implementation →Which phase is your organization really in?
A quick diagnostic: if teams cannot see their own cloud spend, you are still establishing Inform. If they can see it but no one is systematically acting, you are between Inform and Optimize. If you optimize in bursts but spend creeps back, you have a weak Operate phase. If cost is a normal, continuous part of how teams build and run, you are operating the full loop. Most organizations overestimate where they are, usually because a strong Optimize burst masks a thin Operate phase. The sibling guide on how to build a FinOps team and operating structure covers staffing the loop.
| Phase | Core question | Our method step |
|---|---|---|
| Inform | What costs what, and who owns it? | See |
| Optimize | How do we reduce it, in the right order? | Cut |
| Operate | How do we keep it that way? | Lock + Run |
The Inform, Optimize, Operate model is the FinOps Foundation's published framework. Its phase definitions and capabilities are periodically revised, so confirm the current framework wording on the FinOps Foundation site before quoting it formally.
The FinOps Operating Model Blueprint turns these three phases into a concrete org design, capability map, and rollout plan you can adapt to your organization.
The short version
The FinOps operating model runs in three phases: Inform makes cost visible and attributable, Optimize reduces it in the right order, and Operate keeps it that way through governance and process. They run as a continuous loop, not a one-time sequence, and maturity is measured by how well you run all three at once. When you want the operating model implemented and running in your organization, that is what our FinOps implementation service delivers.