Topic starter
12/06/2026 1:25 am
TL;DR: The real issue is not only cost control but whether identity and access programmes can see, rationalize, and lifecycle-manage SaaS entitlements well enough to prevent sprawl, according to Zluri. ROSS, or Return on SaaS Stack, is a framework for judging SaaS value through pricing, latent value, and future roadmap fit, while warning that unused subscriptions, hidden costs, and weak app interoperability waste spend and erode governance.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Software License Optimization: How to Maximize Your ROSS (Return on SaaS Stack)”.
Key questions
Q: How should IAM and governance teams measure SaaS stack value?
A: They should measure value across usage, workflow fit, renewal risk, and ownership clarity, not just subscription cost.
Q: Why do duplicate SaaS apps create identity governance risk?
A: Duplicate apps split ownership, permissions, and data flows across multiple systems that perform the same job.
Q: How should teams govern SaaS subscriptions that no one actively uses?
A: Treat them as lifecycle objects, not just cost items.
Practitioner guidance
- Map SaaS usage to entitlement ownership Build a current inventory of apps, licenses, and named owners so renewal decisions can be tied to actual use, department need, and business criticality.
- Identify duplicate tools by business function Compare apps serving the same use case, then decide which one should remain based on adoption, workflow fit, and migration friction rather than habit.
- Review hidden costs in renewal cycles Include data migration effort, feature bloat, add-on pricing, and integration overhead in every SaaS renewal review so the real cost of ownership is visible.
Bottom line: The article shows that software license optimisation is fundamentally a SaaS governance problem, because unused apps, duplicate tools, and hidden costs persist when ownership and lifecycle visibility are weak.
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:21 am
Software license optimisation is really SaaS governance under a financial label: the article shows that spend reduction, app rationalisation, and entitlement control are the same problem viewed from different angles. If teams cannot distinguish unused subscriptions from genuinely embedded business services, they will optimise cost while leaving access sprawl intact. The practitioner conclusion is that SaaS financial management and identity governance have to be assessed 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: When does SaaS value assessment become a lifecycle issue?
A: It becomes a lifecycle issue when apps outlive the teams, workflows, or integrations that justified them. At that point, the question is no longer just spend, but whether the application is still governed through inventory, ownership, access review, and offboarding. That is where rationalisation turns into identity discipline.
👉 Read our full editorial: Software license optimization exposes the SaaS governance gap
This post was modified 4 days ago by NHI Mgmt Group