Understaffed FinOps? Things Are About to Get Tough

If it still depends on heroics, it won’t scale.

If your FinOps team feels stretched, behind, or constantly reacting…

That’s not a maturity problem.

It’s the direction of the industry.

And both the 2025 and 2026 State of FinOps reports point to the same conclusion:

FinOps didn’t get more efficient.
It got bigger.

I’ve seen this before. In a previous role, software teams would tell me they were “Agile,” but when you looked closer, delivery depended on a few people pulling off last-minute saves. I called it the “heroic methodology.” FinOps is drifting in that direction. As scope expands across cloud, SaaS, AI, and more, many teams are still relying on manual effort and individual heroics to keep costs under control — late nights, one-off analyses, and constant firefighting.

That works — for a while.

But it doesn’t scale.

And that’s the real issue the reports are pointing to. The problem isn’t just that FinOps got bigger. It’s that the way most teams are still operating hasn’t changed to match it.

FinOps didn’t grow. It expanded sideways.

The 2026 State of FinOps report makes this clear:

• 98% of organizations now manage AI spend
• 90% manage SaaS
• 64% manage software licensing
• 48% include data center costs

(Source: FinOps Foundation, State of FinOps 2026 — data.finops.org)

This is no longer just cloud.

It’s technology spend across the enterprise.

And each of those domains comes with:

• Different pricing models
• Different owners
• Different optimization approaches

What used to be one system is now many.

AI didn’t replace work — it added more of it

The shift from 2025 to 2026 is sharp:

• In 2025, ~63% of teams were managing AI spend
• In 2026, that jumped to 98%

(Source: State of FinOps 2025 & 2026)

That’s not adoption.

That’s instant scope expansion.

And AI isn’t simple:

• Token-based pricing
• Unpredictable usage patterns
• Limited optimization maturity

It doesn’t reduce FinOps workload.

It multiplies it.

The job didn’t just get bigger — it got more complex

The 2025 report shows FinOps capabilities continuing to expand:

• Allocation
• Forecasting
• Optimization
• Governance
• Unit economics

The 2026 report builds on that:

• Moving toward technology value management
• Funding AI initiatives through savings
• Influencing decisions earlier in the lifecycle

(Source: FinOps Foundation 2025 & 2026 reports)

FinOps isn’t just measuring spend anymore.

It’s expected to shape it.

Optimization never went away

Even with all this expansion, the core work remains.

The 2025 report still shows:

• Optimization and waste reduction as the top priority

That didn’t disappear in 2026.

If anything, it became more critical — because now it’s expected to fund new initiatives like AI.

So the workload stacks:

• Ongoing cloud optimization
• New AI cost management
• Expanding SaaS and licensing oversight

Nothing gets replaced.

Everything gets added.

The hidden shift: from reporting to responsibility

The 2026 report signals a shift that’s easy to miss:

FinOps is moving from:

• Reporting on spend

To:

• Influencing and governing spend
• Connecting cost to business value
• Enabling investment decisions

That sounds like progress.

But it also means:

• More stakeholders
• More decisions
• More accountability

And significantly more work.

Why teams are feeling the pressure

Most FinOps teams are still operating in a familiar pattern:

• Aggregate data
• Build dashboards
• Identify savings
• Communicate recommendations

That model worked when:

• Scope was mostly cloud
• Optimization was the primary goal

It breaks down when:

• Spend spans cloud, SaaS, AI, and beyond
• Decisions need to happen in real time
• Governance matters as much as visibility

At that point, reporting alone isn’t enough.

Where the model starts to change

The direction the reports point to is subtle, but consistent:

• Less manual analysis
• More automation
• More integration across spend domains
• More control earlier in the lifecycle

In practice, that means:

• Optimization that doesn’t rely on constant human intervention
• Cost data that connects across cloud, SaaS, and application layers
• Decisions informed by both performance and cost — not one or the other

This is where many organizations start to realize:

The challenge isn’t just understanding spend — it’s acting on it consistently at scale

The gap most teams run into

There’s a growing disconnect between:

What FinOps is expected to do:

• Manage all technology spend
• Fund innovation
• Drive accountability

And how it’s still often executed:

• Fragmented tools
• Manual workflows
• Disconnected data

Bridging that gap typically requires:

• Bringing cost and performance together
• Automating optimization decisions where possible
• Extending visibility beyond just cloud billing data

Not as a rip-and-replace effort — but as a shift in how FinOps operates.

The bottom line

FinOps didn’t get easier.

It got:

• Broader
• More complex
• More central to business decisions

And the expectations are rising faster than the traditional model can handle.

Final thought

The question isn’t:

“Do we need more FinOps people?”

The better question is:

Are we still running FinOps like it’s a reporting function — when it’s clearly becoming a system for managing technology spend end-to-end?

If your FinOps team feels like it’s constantly catching up, it’s probably not a people problem.

It’s a sign the model hasn’t caught up yet.

Contact us at info@321gang.com.