Govern SaaS and public cloud spend under one operating model, not two. The State of FinOps 2026 shows scope expanding from cloud to SaaS, AI infrastructure, and private estates precisely because they share failure modes: duplicate tooling, idle capacity, auto renewals, and spend nobody owns. The unifying move is a single taxonomy that maps both SaaS and cloud spend to the same cost centres and products, one accountable function that runs a single monthly review, and clear ownership of renewals and decommissions. The mechanics of the waste differ, contractual for SaaS, technical for cloud, but the discipline of attribute, review, and act is identical.
This sits in the governance, showback and chargeback cluster and links up to the FinOps operating model guide. Cloud names referenced as AWS, Azure, GCP, and OCI throughout.
Why govern them together?
Three reasons make the combined model worth the effort.
The leaks rhyme. Cloud wastes money on idle compute and uncommitted usage; SaaS wastes it on unused seats and overlapping tools. Both hide the same way, in spend that no single owner watches, and both reward the same fix, attribution plus a recurring review.
The overlap is invisible in silos. A SaaS observability product and a cloud native monitoring stack can both be paid for and largely duplicate each other. Only a combined view sees the duplication. The same is true of data tooling, security tools, and AI platforms that span both categories.
The board sees one technology bill. Leadership does not care whether a dollar of waste is SaaS or cloud; they care about total technology spend per unit of business. A combined operating model reports in that language, which is the language that gets decisions made.
What does the shared taxonomy look like?
The foundation is one allocation scheme both categories map to. Define cost centres, products, and teams once, then attribute every SaaS contract and every cloud account or tag to that scheme. Cloud attribution runs on the provider's structures, AWS accounts and tags, Azure subscriptions and tags, GCP projects and labels, OCI compartments, while SaaS attribution runs on contract owner, department, and seat assignment. Different inputs, same output: spend mapped to the same products and cost centres so the monthly view is apples to apples. The FOCUS billing standard helps normalise the cloud side; SaaS needs the same normalisation applied to contracts.
What does the combined review actually do?
One monthly review covers both, with different checks per category.
- Cloud checks. Idle and oversized resources, commitment coverage against forecast for Savings Plans, Reservations, CUDs, and Universal Credits, and anomaly follow up.
- SaaS checks. Seat utilization against licences paid, tools approaching auto renewal, and overlapping capabilities across contracts. Renewals get reviewed before the notice window closes, not after.
- Shared checks. Duplication across the boundary, total spend per product against budget, and decommission decisions for anything no team will claim.
The point of one meeting is that the owner of the cloud bill and the owner of the SaaS contracts sit in the same room with the same taxonomy, so the duplication and the unowned spend surface instead of falling between two processes.
A Fortune 500 services firm ran cloud cost reviews in engineering and SaaS renewals in procurement, with no shared view. Joining them under one taxonomy surfaced three overlaps in a single quarter: two observability tools doing the same job, one paid as SaaS and one running on cloud infrastructure; a data platform licensed by seat while most seats were inactive; and a security tool auto renewing at a headcount the company no longer had. Consolidating the overlaps, reclaiming idle seats before renewal, and tightening cloud commitment coverage cut combined technology spend materially. Figures are verified against billing data and anonymised.
Who owns it?
A single accountable function, usually FinOps working closely with procurement, owns the operating model: it sets the taxonomy, runs the one review, and holds renewal and decommission gates. Within that, engineering still owns cloud efficiency and software or business owners still own SaaS utilization; the governance function joins their data and forces the cross boundary decisions. This is the operating model maturity described in the FinOps operating model guide extended past cloud, and it is where the State of FinOps 2026 says the discipline is heading. Native tools, AWS Advisor, Azure Advisor, GCP Recommender, OCI Cost Analysis, and SaaS management platforms recommend, but the governance function decides.
Frequently asked questions
Build one operating model with us
We design the shared taxonomy, stand up the single review, and hand ownership of combined SaaS and cloud governance to the right function, on your side of the table with zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.