Topic starter
11/06/2026 11:43 pm
TL;DR: SaaS spend management becomes an identity governance problem when duplicate apps, unrevoked subscriptions, and unmanaged renewals let access and spending drift outside IT control, according to Zluri. The operational issue is not just cost control, but whether organisations can actually see, right-size, and retire application access before waste becomes risk.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “SaaS Spend Management: Win the Battle Against SaaS Overspending”.
Key questions
Q: How should teams govern SaaS licences when users can sign up outside IT?
A: Teams need a discovery-backed system of record that reconciles SSO, finance, HR, and app integrations into one view of subscriptions and access.
Q: Why do overlapping SaaS apps create more risk than simple budget waste?
A: Because each extra application adds its own identity boundary, permission model, and offboarding path.
Q: What breaks when SaaS licenses are not revoked after employees leave?
A: Unrevoked licenses keep billing active and preserve access longer than business need requires.
Practitioner guidance
- Centralize SaaS inventory and ownership Maintain one authoritative record for every subscription, named owner, business unit, user group, and renewal date so app access and spending can be governed together.
- Review renewals before auto-renewal dates Require a formal business justification before each renewal and cancel services that no longer have current usage or an approved owner.
- Use usage metrics to right-size licenses Compare active users, feature consumption, and contract entitlements to remove unused, sub-optimal, and inactive licenses before the next billing cycle.
Bottom line: SaaS overspending in this article is framed as a governance failure, because access, ownership, and renewals drift when app buying is decentralised.
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 8:31 am
SaaS spend management is now part of identity governance, not a separate procurement discipline. The article shows that app purchasing, subscription renewal, and license assignment all create governance obligations that IGA teams already understand from access lifecycle work. When employees can adopt tools independently, the organisation needs the same discipline it uses for entitlements, ownership, and recertification. The practitioner conclusion is straightforward: if you cannot govern the application estate, you cannot govern the access estate.
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 can organisations tell whether SaaS access governance is actually working?
A: They should look for three signals: low numbers of orphaned accounts, consistent entitlement recertification, and rapid revocation when users change roles or leave. If access remains valid across apps after a lifecycle event, governance is not working even if dashboards look complete.
👉 Read our full editorial: SaaS spend management exposes the identity governance gap
This post was modified 4 days ago by NHI Mgmt Group