TL;DR: Cost control, license visibility, and access governance are converging as one operational problem in SaaS spend management tools, especially where shadow apps, unused subscriptions, and risky access create both waste and exposure, according to Zluri’s 2026 review. The real lesson is that spend optimisation now depends on identity control, not procurement alone.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Top 10 SaaS Spend Management Tools in 2026”.
Key questions
Q: What breaks when SaaS spend management is treated separately from identity governance?
A: The organisation can remove licences without removing accounts, or keep accounts active without any clear business need.
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: How do you know if SaaS license optimization is working?
A: You should see fewer duplicate applications, lower spend on unused seats, clearer application ownership, and cleaner recertification outcomes.
Practitioner guidance
- Map SaaS inventory to entitlement ownership Correlate discovery data from SSO, directories, finance systems, and app integrations so every application has a named owner and an access path you can review.
- Tie licence reviews to joiner-mover-leaver processes Use offboarding and mover events to reclaim unused seats, remove dormant access, and prevent licences from surviving the business need that justified them.
- Separate duplicate apps from required apps by business function Rationalise overlapping tools by mapping each one to a business outcome, then retire the redundant licence where two products cover the same workflow.
Bottom line: SaaS spend management is no longer just a procurement exercise because access governance now determines whether software is actually in use.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Spend management has become an identity governance problem wearing a finance label: once SaaS discovery, licence optimisation, and access control share the same workflow, procurement alone cannot explain or fix the control gap. The article reflects a broader market shift where app inventory, entitlement data, and lifecycle decisions all shape whether an organisation pays for software it should have already removed. Practitioners should treat SaaS cost control as a governance discipline, not a budgeting side task.
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: Should organisations treat SaaS spend tools as part of IGA or finance operations?
A: They should treat them as part of both, but with identity governance taking priority whenever access, ownership, or lifecycle decisions are involved. Finance teams care about cost efficiency, while IAM and IGA teams control who can still use the application and when that access should end. The strongest programmes connect those functions instead of running them as separate workstreams.
👉 Read our full editorial: SaaS spend management tools expose the identity gap in 2026