Inform, Optimize and Operate are the three phases in which the FinOps Foundation's Framework describes the practice: Inform makes cost, usage and efficiency visible, allocates them and supports budgeting and forecasting, Optimize identifies, documents and prioritises options to improve usage or rate, and Operate puts the chosen options into practice and develops the practice itself. The Foundation describes the three as a loop a scope passes through continuously, not as a sequence completed once; the Framework is licensed CC BY 4.0, and this handbook keeps the Foundation's names, including the spelling Optimize. For the bill it means that every billing period feeds Inform with new data, and that every change made in Operate has to reappear in the next report, or it is not proven.
How it works
The Foundation arranges the work of a FinOps practice into three phases and describes FinOps as iterative work on the capabilities across them. Each phase takes something in and hands something on, and what it hands on is the next phase's starting point. What FinOps is as a whole is explained in What FinOps is.
Inform
Inform takes in the providers' billing data together with usage, utilisation and performance data and turns them into a picture of the current state: which costs arise, who owns them, how they develop. In the Foundation's description this covers cost allocation, reporting, KPIs and comparisons as well as budgeting and forecasting. The outputs are allocated cost, a cost report per owner, a forecast and unit metrics, which the next phase works from. The unallocated remainder is the most honest measure of how far Inform reaches.
Optimize
Optimize takes the picture from Inform and looks for ways to improve efficiency and value. The Foundation distinguishes two levers: usage, meaning fewer or better-fitting resources for the same outcome, which involves engineering above all, and rate, meaning commitments, negotiated discounts and the choice of vendor, which involves procurement and leadership. The output, as the Foundation describes it, is a documented list of options prioritised against the organisation's goals, whose remainder stays as a backlog for later cycles. Each option is a savings opportunity with an estimate, not yet a saving; rightsizing is the example for the usage lever.
Operate
Operate implements the options chosen in Optimize; whether they worked is checked, in the Foundation's description, back in Inform, which a practice keeps returning to for that reason. The Foundation takes the phase wider than "implement the changes": maturing the capabilities and evolving the practice itself belong to it as well. In a small company Operate carries three things: the decision on budget variances; guardrails that settle what is allowed without asking; and the handling of an anomaly, which has to be explained before it becomes the baseline. On top of that comes the cadence at which all of it is read and decided. How budgets and anomalies work mechanically is covered by Cloud budgets and Cost anomaly detection; the agenda of a monthly review belongs to Monthly cloud cost review: agenda and templates.
The loop
The Foundation describes teams cycling through the phases quickly and repeatedly, with different participants working in different phases and at different cadences at the same time. It follows that a practice is never "in" a phase; it has several scopes in different phases. Production may sit in Operate with a budget and a review while a new AI workload is only just in Inform, because nobody yet knows who owns its tokens. Declaring Inform finished is therefore a category error: every new billing period, every new account and every change implemented in Operate hands Inform new data, and a scope that leaves Inform comes back to it. The phases are neither project stages with an end date nor a maturity path; which capabilities sit in which phase is mapped in The four FinOps domains and their capabilities.
What it means for your cost
In the billing data and the reports, a company of 10 to 200 people sees each phase as an artefact of its own, and each artefact has a question it answers and a person who reads it.
| Phase | Question | Artefact | Owner | Chapter |
|---|---|---|---|---|
| Inform | What costs what, and who owns it? | allocated cost, cost report per owner, forecast, budget per scope | the person who pays the bill, with the engineering lead | Allocation and ownership, Reporting and analysis |
| Optimize | Where is the same outcome available for less? | prioritised list of savings opportunities, commitment options | engineering for usage, management for commitments | Optimisation and savings, Pricing models and commitments |
| Operate | Does the plan hold, and who reacts when it does not? | decision on budget variances, guardrails, anomaly alerts, monthly review | management for budget variances, engineering for anomalies | Budgets, forecasts and finance, Governance and the operating model |
The decision the loop drives is the same every month: which option from Optimize is implemented, which stays in the backlog, and which variance from Operate is accepted. Without Inform the decision has no numbers, without Operate it has no consequence, and without the next pass it has no proof that it worked: a saving is realised only when the following month's report shows it.
Where it goes wrong
- Phases as a project plan. Symptom: an initiative called "introduce FinOps" has the milestones Inform, Optimize and Operate and ends with the third. Cause: the loop was read as a sequence; after the project nobody feeds Inform with new data, and the next cost rise meets a practice without a cadence.
- Optimize without Inform. Symptom: a list of savings opportunities for resources whose owner is unknown, and nobody acts on them. Cause: the allocation is missing, so the option is addressed to nobody; Optimize works from the picture Inform provides, or not at all.
- Operate without the way back. Symptom: changes are implemented, but the following month's report does not show them, and the saving stays a claim. Cause: the effect was not measured against the metrics from Inform; the loop was not closed after Operate.
- Only the rate lever. Symptom: commitments cover the usage, but the usage itself was never questioned, and the commitment now binds resources nobody needs. Cause: Optimize was reduced to the rate, and the usage lever, which involves engineering above all, was missing.
Sources
Read on 2026-10-16. FinOps Foundation: FinOps Phases, FinOps Framework, FinOps Capabilities.