The 2025 Annual State of FinOps report reveals that workload optimization and waste reduction continue to dominate organizational priorities. While earlier years emphasized empowering engineers, these themes are deeply interconnected: reducing waste has always been the ultimate goal. The real question has evolved from how to get engineers involved to how to drive ongoing action and measurable results.
From Spreadsheets to Systems
Early FinOps efforts focused heavily on visibility. Once teams understood their spending patterns, the conversation shifted toward identifying optimization opportunities and enabling engineering teams to act. But the execution often remains manual and fragmented.
As FinOps and engineering align more closely, organizations can build processes that identify waste, alert the right teams, implement fixes, track progress, and confirm savings. The maturity progression is clear: once basic remediation is in place, the next step is implementing systems and processes for continuous improvement.
Governance and policy are predicted to become top future priorities because once low-hanging fruit has been addressed, organizations need structured approaches to tackle both existing and emerging waste.
The Real Barrier: No Built-In Process
Many FinOps practitioners hit the same bottleneck despite having comprehensive dashboards: there is no structured workflow for addressing the inefficiencies they surface. In large, distributed organizations, the typical pattern looks like this:
- FinOps teams identify idle resources and unoptimized services
- Engineers receive lengthy spreadsheets or emails listing issues
- A handful of items get addressed; most tasks fade into backlogs
- Potential savings remain unrealized and untracked
The handoff from FinOps to engineering frequently breaks down without clear processes. Visibility is table stakes; the real work involves alerting, verifying, remediating, and measuring ROI. Without repeatable workflows that ensure both fixes and learning occur, organizations end up patching problems temporarily rather than solving them at their root.
A Maturing Practice Moving Closer to Engineering
Early FinOps practitioners were often siloed within finance or cost allocation functions. Bringing development teams into the fold represented a paradigm shift: if engineers understand cost implications, inefficiencies can be addressed at the source.
Organizations have largely moved past initial cultural resistance. FinOps has matured and positioned itself closer to engineering, allowing teams to tackle waste proactively. The conversation shifted from "please fix this" to "how do we integrate fixes into daily workflows?" This evolution explains why workload optimization remains central -- organizations now have the alignment needed to pursue continuous improvement.
Why Governance and Policy Are the Next Frontier
As organizations achieve consistent engineering engagement, recurring patterns emerge: certain inefficiencies repeat themselves. One-time fixes prove insufficient. Teams need tools and processes that teach best practices at scale.
Automation, guardrails, and self-service checks help maintain compliance and ensure issues stay resolved long-term. Many practitioners view governance as the logical progression after clearing the waste backlog -- implementing structure that prevents the same mistakes from recurring.
The Three-Stage Evolution of FinOps Action
Stage 1 -- Visibility: Early efforts focused on a simple premise: you cannot reduce waste if you cannot see it.
Stage 2 -- Visibility Plus Engineer Engagement: Once development teams participate, simply flagging underutilized resources is not enough. Engineers need clear context, ownership details, and risk assessments before they can act.
Stage 3 -- Structured Workflow: With data and team buy-in established, the focus shifts to implementing an ongoing process that sustains results over time.
Three Bottlenecks PointFive Addresses
No Built-In Workflow
Identifying waste is not the same as verifying, assigning, and fixing it. Without structured processes, tasks scatter across emails, spreadsheets, and chat threads. Teams lose visibility on completion status and cannot measure ROI.
Lack of Context and Ownership
Engineers need more than raw cost data -- they need actionable context. Manually correlating each cost spike with usage patterns demands substantial time, and the cost-benefit justification for a fix is not always obvious from the data alone.
Identifying Inefficiencies at Scale
Small inefficiencies -- say $50 per week on a single resource -- may not justify the engineering time to address individually. But discovering thousands of these issues across an entire cloud footprint transforms modest per-resource savings into significant aggregate results.
How PointFive Turns Insights into Remediation
PointFive integrates directly into existing engineering workflows through tools like Jira and Slack. Each ticket includes relevant context so engineers understand what is problematic, why it matters, and how to address it. The platform does not merely generate alerts -- it drives the full cycle of implementing fixes, measuring results, and building a record of confirmed savings.
The Road Ahead
Workload optimization and waste reduction have consistently been central to FinOps regardless of how the priorities are framed year to year. The 2025 landscape shows that organizations have made significant visibility progress. The challenge now is installing durable processes that ensure every cost insight leads to action.
Organizations should prioritize:
- Tighter engineering workflow integration so that cost insights reach developers where they already work
- Context-rich alerts that help developers understand the origin and impact of waste
- Scalable processes that eliminate recurring issues across the entire cloud estate
The end goal is a culture where efficiency is embedded in daily operations -- where problems are identified, fixed, measured, and prevented from recurring.