Topic starter
11/06/2026 11:40 pm
TL;DR: SaaS sprawl drives duplicate apps, unused licenses, and abandoned subscriptions when ownership and offboarding are weak, according to Zluri. The governance lesson is that cost control and identity control are the same operational problem once app lifecycle and access visibility break down.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “How to Optimize Your SaaS Spend”.
Key questions
Q: What breaks when SaaS ownership is not assigned clearly?
A: Renewal decisions, access reviews, and cleanup tasks all lose accountability.
Q: Why do unused SaaS licences create identity risk as well as cost waste?
A: Unused licences often indicate that apps are still licensed after the people or teams that justified them have changed.
Q: What are the signs that SaaS spend controls are failing?
A: The most common signs are duplicate tools for the same use case, licences that remain unassigned after demand drops, and subscriptions that renew after the team stops using them.
Practitioner guidance
- Assign a named owner to every SaaS application Require a business and technical owner for each application so renewal, review, and termination decisions have an accountable identity behind them.
- Reconcile SaaS inventory against usage and procurement data Compare SSO, expense, and app usage records on a recurring basis to surface duplicates, dormant subscriptions, and tools with no active business need.
- Tie offboarding to app termination checks Make application closure part of employee and project offboarding so accounts, licences, and stored data are verified before the owner departs.
Bottom line: SaaS spend waste and identity governance failure often come from the same missing control: clear ownership tied to lifecycle decisions.
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:27 am
SaaS spend optimisation is an identity governance problem disguised as a finance problem. The article shows that duplicate apps, unused licences, and abandoned subscriptions all trace back to missing ownership and weak lifecycle control. When app approval, entitlement review, and offboarding are disconnected, spend waste and access residue become the same failure mode. Practitioners should treat SaaS cost control as part of IAM and IGA governance, not as a separate procurement exercise.
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 stop abandoned SaaS apps from lingering after offboarding?
A: They should make offboarding a required termination checkpoint for every app that stores data or grants access. That means the leaving employee or project owner cannot be closed out until the application, licence, and related data path are verified as closed. The goal is not just cost recovery. It is preventing residual access from surviving the lifecycle event.
👉 Read our full editorial: SaaS spend optimization exposes the identity governance gap
This post was modified 4 days ago by NHI Mgmt Group