FinOps Teams Are Now Sitting in on Every Procurement Call
The biggest cloud savings now sit in commitments, so FinOps is joining the conversation before contracts are signed.
A few years ago, FinOps teams arrived after the contract was signed. Their job was to find waste in an architecture somebody else had already chosen. That sequence is reversing. In a growing number of enterprises, FinOps now has a seat on every significant procurement call — before the commitment is made.
Why the timing changed
The biggest cloud savings are no longer found in idle instances and forgotten storage. Those were cleaned up long ago. Today's large numbers sit in commitments: multi-year spend agreements, reserved capacity, marketplace purchases and the pricing terms attached to new AI services.
Once those are signed, there is very little left to optimise.
“By the time we saw the bill, the decision that caused it was eighteen months old. Now we see the decision.”
What FinOps brings to the table
In procurement conversations, FinOps practitioners add a perspective that neither engineering nor purchasing usually has on its own.
- Realistic usage forecasts based on actual consumption data, not vendor estimates
- Unit-cost modelling that ties spend to products or customers
- Exit and portability terms that preserve future negotiating leverage
The AI pricing problem
Generative AI has accelerated the shift. Token-based and capacity-based pricing models are new, volatile and hard to forecast. CIOs describe AI line items growing faster than any other part of the cloud bill, and procurement teams are leaning on FinOps to make sense of commitments they have never priced before.
The practical result is a closer partnership between finance, procurement and engineering — and a FinOps function whose influence now starts well before the first invoice arrives.