FinOps Phases
What are FinOps Phases?
The FinOps phases are the three stages of the FinOps lifecycle, Inform, Optimize and Operate, which teams cycle through continuously to gain visibility, improve efficiency and put changes into practice.
Updated November 2026 · 5 min read
The FinOps phases describe how FinOps work flows. In the Inform phase, teams get visibility into what they spend and allocate costs to the people and products responsible. In the Optimize phase, they identify opportunities to improve, such as removing waste or buying commitment discounts. In the Operate phase, they act on those opportunities and build the changes into everyday processes. Then the cycle begins again, with better data and more experience.
The phases are not a one-time project plan. Teams cycle through them continuously, and different teams or capabilities may be in different phases at the same time. For IT financial management, the phases provide a simple way to organize FinOps work and to explain to stakeholders why visibility must come before optimization and why changes must be embedded in operations to last.
Definition of FinOps Phases
The FinOps phases are part of the FinOps Framework. They describe the iterative lifecycle of a FinOps practice: Inform, Optimize and Operate.
The Framework encourages practitioners to move through the phases quickly and on a regular cadence, starting small and growing the size and scope of their actions as they gain experience, rather than waiting for perfect data. Quick action on a regular cadence helps teams avoid analysis paralysis.
Inform
The Inform phase is about visibility and allocation. Teams collect and process cost and usage data, allocate costs to products, teams and business units, and produce reports and dashboards that show who is spending what.
Key activities include tagging, cloud cost allocation, forecasting, budgeting and benchmarking. The goal is to give every stakeholder timely, accurate information about the costs they influence.
Without good information, optimization efforts tend to focus on the wrong areas and decisions are hard to justify. Inform also includes setting expectations through budgets and forecasts, so that teams know what spending is planned.
Optimize and Operate
The Optimize phase identifies opportunities to improve efficiency and value. These include usage optimization, such as rightsizing and removing idle resources, and rate optimization, such as buying reserved instances or savings plans.
The Operate phase puts these opportunities into practice. Teams implement changes, automate recurring actions, define policies and governance, and align FinOps activities with business goals. It also includes building a FinOps culture, so that cost becomes part of everyday decisions.
Operate feeds back into Inform, since the results of changes must be measured, and new questions arise from the new data.
Importance of FinOps Phases in IT Financial Management
The phases provide a simple model for organizing FinOps work and setting expectations with stakeholders.
They help explain why some activities must come before others. Stakeholders who want immediate savings can see why allocation and reporting need attention first, and those focused on reporting can see why the practice must move on to action.
They also make it clear that FinOps is never finished, since costs, usage and business priorities keep changing.
Visibility Before Optimization
Organizations sometimes try to cut cloud costs before they understand them, for example by applying across-the-board reductions. Without allocation and reporting, it is hard to know which savings are safe and which will harm important services.
The Inform phase ensures that optimization decisions are based on data about which services, teams and resources drive costs.
It also builds trust, since teams are more likely to act on recommendations when they can see the data behind them.
Making Changes Stick
Many cost savings are temporary if they are not embedded in operations. Resources that were rightsized may grow again, and new projects may repeat old patterns.
The Operate phase addresses this by building practices into processes, such as cost reviews in architecture decisions, automated policies and regular reporting to product teams.
This is where FinOps becomes part of how the organization runs rather than a series of cost reduction projects, supporting broader IT cost management.
How to Apply the FinOps Phases
Applying the phases involves working in short cycles, focusing each cycle on specific capabilities and measuring results before moving on.
Starting with a narrow scope, such as one cloud account or product, allows teams to learn before expanding. Early cycles reveal problems with data, tools and processes that are easier to fix at a small scale.
Working in Short Cycles
Rather than spending months perfecting visibility before acting, teams should move through all three phases quickly, even with imperfect data. A first cycle might allocate the largest costs, identify a few obvious savings and implement them within weeks.
Each cycle improves the data and processes for the next. Over time, cycles become faster and cover more of the organization's spending.
Regular cadences, such as weekly cost reviews and monthly forecasting, help keep the cycle moving. They also create predictable moments where engineering, finance and product teams look at the same data together.
Assigning Responsibilities
Different personas lead different phases. Finance and the central FinOps team often lead Inform activities such as allocation and reporting, engineers lead many Optimize activities, and leadership and the FinOps team drive Operate activities such as governance and culture.
All personas take part in every phase, but clear ownership prevents work from stalling between phases. Recommendations that nobody is responsible for implementing are a common sign of this problem.
Tracking which phase each capability is in helps the FinOps team see where support is most needed. A capability stuck in Optimize, for example, often signals that the teams responsible for acting have not been engaged.
Examples of FinOps Phases in IT Financial Management
The examples below show teams moving through the phases.
Both use illustrative figures. The first shows an organization starting out with FinOps, and the second shows a more mature practice.
In each, completing the full cycle produced results that a single phase would not have, and set up the next cycle of work.
A First Cycle
A FinOps team starts with its largest cloud account, which costs $600,000 a month. In Inform, it allocates 80% of costs to product teams. In Optimize, it finds $45,000 a month of idle and oversized resources. In Operate, product teams remove them within three weeks.
The next cycle extends cost allocation to the remaining cloud accounts and adds a weekly report showing each team its costs and open recommendations. By the third cycle, the team is reviewing commitment purchases as well as usage.
Embedding Practices
Another organization's earlier savings from rightsizing have partly disappeared, as resources have grown back over a year. The FinOps team treats this as an Operate problem rather than an Optimize one.
It introduces automated policies that flag new oversized resources, adds cost estimates to architecture reviews and includes cost trends in each product team's monthly review. Savings hold steady over the following year, and new projects start with right-sized resources instead of needing correction later.
Conclusion
The FinOps phases are Inform, Optimize and Operate. Teams use them to gain visibility into costs, identify improvements and put those improvements into practice, cycling through them continuously.
In IT financial management, the phases provide a simple structure for FinOps work, emphasizing that visibility must come before optimization and that changes must be embedded in operations. Working in short cycles, assigning clear ownership and measuring results help organizations make lasting progress.
Related terms
FinOps Framework
The FinOps Framework is the FinOps Foundation's model for building a FinOps practice, made up of principles, personas, phases, a maturity model, domains, capabilities and technology categories.
Cloud Cost Allocation
Cloud cost allocation is the process of assigning cloud costs to the teams, products, environments and business units that use them, using account structures, tags and rules for dividing shared costs.
Rightsizing
Rightsizing is the practice of matching the type and size of cloud resources, such as instances and databases, to the actual performance and capacity a workload needs, reducing cost without harming performance.
FinOps Principles
The FinOps principles are six guiding values in the FinOps Framework that shape how organizations practice FinOps, covering collaboration, business value, ownership, data, central enablement and variable cost models.