FinOps has given organizations a clear framework for managing cloud spend. Most teams start with the Inform phase — tagging, allocation, and dashboards that show where money is going. This visibility is essential, but it is also where many teams stall. Knowing your cloud costs is very different from reducing them or making optimization part of daily operations.

The FinOps lifecycle includes three phases: Inform, Optimize, and Operate. Adoption, however, often skews heavily toward the first. That’s mostly because the other two phases are harder. Optimize and Operate require cross-team coordination, trust in the safety of changes, and the ability to execute continuously in dynamic cloud environments.

FinOps Lifecycle Refresher

The FinOps Lifecycle has been around since the FinOps Foundation was formed in 2019, and the three phases have remained consistent — Inform, Optimize and Operate. These phases are detailed on the FinOps Foundation website, but here is a quick summary:

• Inform. Establish visibility into cloud spend through allocation, tagging, and reporting, so teams understand where money is going and who is responsible.
• Optimize. Identify and implement opportunities to reduce waste and improve efficiency, such as rightsizing, scaling adjustments, and smarter purchasing.
• Operate. Embed FinOps into daily processes, aligning engineering, finance, and business teams to continuously balance cost, performance, and speed.

It’s important to note that these phases aren’t linear in nature. On any given day, teams may work across all of them.

Why Teams Stall at Inform

Most organizations make solid progress in the Inform phase of FinOps by tagging resources, producing dashboards, and creating monthly reports. But moving beyond visibility into Optimize and Operate is where momentum often slows.

The first hurdle is that optimizations are complex and time-consuming. Rightsizing instances, adjusting scaling policies, and making reserved capacity decisions all require engineering input, which is difficult to prioritize against feature delivery. On top of that, the sheer volume of opportunities makes it challenging to decide what to tackle first. Even when teams act on the highest-priority items, the long tail of smaller opportunities often goes unaddressed, leaving significant potential savings unrealized.

There is also a cultural shift required. FinOps is inherently cross-functional, but finance, engineering, and operations do not always share the same priorities. Finance wants savings, engineering wants performance and reliability, and operations wants compliance and stability. Getting everyone aligned is no small task.

The nature of modern cloud environments makes things harder still. Dynamic, distributed architectures such as microservices, Kubernetes, and data platforms change constantly, so point-in-time recommendations (for example, monthly reports) are quickly outdated. By the time they are reviewed, workloads may have shifted and the recommendations no longer apply.

Even when opportunities are clear, teams may hesitate to act. Fear of unintended consequences such as user experience issues, creating downtime, or violating compliance requirements causes engineers to err on the side of inaction. In the 2025 State of FinOps report, concerns that recommended changes will cause damage was the number two reason cited for not acting on recommendations.

The Operate phase introduces additional challenges since it requires governance, policy enforcement, and compliance monitoring, which many teams struggle to implement consistently.

The result is that organizations end up with good visibility into cloud spend, but the real benefits of FinOps — sustained cost savings, better performance, and reduced toil — remain out of reach.

What it Takes to Move Forward

To move beyond Inform, organizations need more than just visibility. They need the ability to act on insights quickly, safely, and in a way that brings finance, engineering, and operations together around shared goals.

The first requirement is trust. Engineers must trust that any optimization will not jeopardize application performance, reliability, or availability. Without that assurance, recommendations are too risky to implement at scale.

The second requirement is alignment. FinOps is successful when finance, engineering, and operations agree on the guardrails for cost, performance, and compliance. Establishing policies and shared objectives reduces friction and builds trust across teams.

The third requirement is continuous execution. Cloud environments change daily, so optimizations must be applied in real time, not once a month in a cost review meeting. Point-in-time actions cannot keep pace with the dynamic nature of modern workloads.

When these three conditions are met — trust, alignment, and continuous execution — teams can finally progress into the Optimize and Operate phases of FinOps. This is where the real benefits emerge: meaningful cost savings, improved application performance, and reduced operational toil.

The Role of Autonomy

Meeting these requirements is difficult without help. Manual processes cannot keep up with the scale and speed of today’s cloud environments. This is where autonomous cloud management becomes essential.

Autonomy bridges the gap between knowing what needs to be done and actually doing it. Instead of generating lists of recommendations that may or may not get implemented, autonomous platforms act on opportunities in real time. They continuously rightsize resources, tune scaling parameters, and adjust policies to keep workloads efficient.

Importantly, autonomy does not mean giving up control. Guardrails and policies ensure that every action aligns with business objectives and compliance requirements. Teams can choose different modes of operation, from insight-only reporting to human-in-the-loop approvals to full autonomous execution, depending on their level of comfort and maturity.

By introducing autonomy into the FinOps practice, organizations can finally bring the Optimize and Operate phases to life. Optimization becomes continuous rather than episodic, and operations teams are no longer burdened with repetitive, low-value tasks. Finance sees savings realized, engineers maintain performance and reliability, and the business as a whole gains the ability to innovate faster with confidence.

Unlocking the Full Value of FinOps

FinOps was never meant to stop at visibility. The real promise of FinOps is unlocked when organizations Optimize and Operate, where visibility turns into continuous action. That transition has historically been difficult because of complexity, cultural alignment, and the speed of modern cloud environments.

Autonomy changes the equation. By enabling safe, continuous optimization under clear policies and guardrails, autonomous cloud management helps teams realize the outcomes FinOps was designed to deliver: lower costs, stronger performance, less toil, and better alignment between finance and engineering.

Teams that broaden their practice beyond Inform are not just reducing waste. They are creating a sustainable way to run cloud environments with confidence and agility. This is what it means to unlock the full value of FinOps.

‍