Topic starter
12/06/2026 12:48 am
TL;DR: Collaboration between CIOs and CFOs can improve technology investment decisions, reduce SaaS sprawl, and strengthen risk oversight by combining financial and technical perspectives, according to Zluri. For IAM teams, the real issue is governance coherence: access, spend, and control decisions break down when business and technology owners work from separate views.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “CIO CFO Collaboration - An Essential to SaaS Spend Management”.
Key questions
Q: How should organisations govern SaaS spend when CIO and CFO priorities differ?
A: Start with a shared governance model that links budget authority, application ownership, and access approval.
Q: Why do SaaS sprawl and identity governance fail in the same place?
A: They both depend on discovery happening before control.
Q: What do security teams get wrong about approval workflows for privileged access?
A: They often confuse approval volume with control quality.
Practitioner guidance
- Define joint SaaS ownership Assign named business, IT, and finance owners for every application so retention, replacement, and renewal decisions do not sit with a single function.
- Link procurement to approval workflows Require every new SaaS purchase to pass through an approval workflow that captures budget authority, technical fit, and access implications before onboarding.
- Rationalise overlapping applications Review applications for duplicate function, underuse, and unmanaged access paths, then retire or consolidate where the business case is weak.
Bottom line: SaaS sprawl is not only a cost issue because every extra application expands the access estate and the work of governing it.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
12/06/2026 10:17 am
Shared SaaS governance is now an identity governance requirement, not a finance-only discipline. Once SaaS decisions influence access paths, approval chains, and application ownership, finance and IAM can no longer work from separate records. The organisation’s control problem is coherence: one set of applications, one source of truth for ownership, and one view of who can introduce or retain software. Practitioners should treat SaaS governance as part of the broader identity control plane.
A few things that frame the scale:
- The average enterprise SaaS platform connects to 42 or more third-party applications through OAuth tokens, API keys, webhooks and automation platforms.
A question worth separating out:
Q: When should teams consolidate SaaS applications instead of renewing them?
A: When usage is low, functionality overlaps, or ownership is unclear, consolidation usually creates more value than renewal. The decision should weigh cost, control overhead, and the access surface created by keeping redundant tools in the estate.
👉 Read our full editorial: CIO and CFO collaboration shapes SaaS spend governance
This post was modified 4 days ago by NHI Mgmt Group