Topic starter
12/06/2026 1:20 am
TL;DR: SaaS optimization is presented as a way to reduce duplicated tools, unused licenses, and spend, while also improving visibility, security, and compliance across the application estate, according to Zluri. The deeper issue is that unmanaged SaaS growth is an identity governance problem, not just a procurement problem.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “SaaS Optimization: A Comprehensive Guide”.
Key questions
Q: What breaks when identity governance cannot see all SaaS applications?
A: Access reviews become partial, offboarding misses applications outside the core directory, and auditors see evidence gaps instead of defensible control.
Q: Why does SaaS sprawl create security risk as well as cost pressure?
A: SaaS sprawl increases the number of accounts, roles, permissions, and integrations that must be governed.
Q: How do teams know whether SaaS spend optimisation is actually working?
A: Look for contract data, usage data, and licence assignment data in the same workflow.
Practitioner guidance
- Centralise SaaS inventory and ownership Map every approved, unmanaged, and restricted app into one governed inventory with named business owners, IT owners, and renewal dates.
- Reconcile licences against actual usage Compare assigned licences, active usage, and duplicate app functions before each renewal cycle so unused entitlements do not persist by default.
- Tie shadow IT discovery to offboarding Require that newly discovered SaaS apps enter the same lifecycle path as sanctioned tools, including review, approval, or removal when no owner is confirmed.
Bottom line: SaaS optimisation is not just about reducing subscription spend. It is also about making the SaaS estate governable through clear ownership, visibility, and lifecycle control.
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 11:11 am
SaaS optimisation is ultimately a governance discipline, not a buying discipline. The article repeatedly ties usage analysis, licence management, and vendor renewal to control over the application estate. That is important because spend reduction does not automatically produce assurance if the organisation still cannot answer who owns each app, who uses it, and how access is removed. The practitioner conclusion is that cost and governance must be managed together.
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: How should organisations control SaaS spend without losing governance over access?
A: They should treat SaaS spend as part of identity and lifecycle governance, not just procurement. The practical model is to maintain a complete application inventory, assign ownership for every tool, review usage before renewal, and remove dormant access before it becomes recurring spend. That keeps budget control tied to accountable access decisions.
👉 Read our full editorial: SaaS optimization exposes the identity governance gap in shadow IT
This post was modified 4 days ago by NHI Mgmt Group