Notifications
Clear all
Topic starter
12/06/2026 1:18 am
TL;DR: SaaS budget planning improves cost control by discovering app sprawl, tracking usage, and enforcing renewal discipline, according to Zluri. The identity lesson is broader: software budgets become governance problems when shadow IT, abandoned access, and unused entitlements are left unmanaged.
NHIMG editorial — based on content published by Zluri: SaaS Management Master SaaS Budget Planning, a guide for finance teams
Questions worth separating out
Q: How should security teams govern SaaS sprawl without losing access control?
A: Start with a single inventory that joins finance, identity, and app-discovery data.
Q: Why do unused SaaS licences matter to IAM teams?
A: Unused licences often indicate more than wasted spend.
Q: How can organisations tell whether SaaS budget controls are working?
A: Look for fewer orphaned subscriptions, lower duplicate app counts, and clean ownership records tied to each renewal.
Practitioner guidance
- Build a reconciled SaaS inventory Merge finance records, SSO logs, HR data, and application discovery feeds into one inventory so hidden subscriptions and unmanaged access paths surface together.
- Convert renewals into access reviews Require the business owner, IT, and IAM to review licences, users, and application necessity before every major renewal window.
- Close accounts and licences together During offboarding, verify that the subscription is removed, the account is disabled, and ownership is reassigned for any shared or critical SaaS application.
What's in the full article
Zluri's full blog post covers the operational detail this post intentionally leaves for the source:
- Step-by-step SaaS budgeting workflow for finance teams managing subscription-heavy environments
- Detailed explanation of Zluri's nine discovery methods for finding shadow IT across enterprise tools
- Examples of renewal alerts, usage analytics, and licence reclamation workflows in a SaaS management platform
- Walkthrough of how automated offboarding closes unused accounts and removes dormant licences
👉 Read Zluri's guide to SaaS budget planning and licence optimisation →
SaaS budget planning: what it means for IAM teams?
Explore further
12/06/2026 11:07 am
SaaS spend sprawl is often identity sprawl in disguise. When organisations lose track of applications, they usually lose track of the access paths attached to those applications as well. That means finance overspend and identity governance failure are often the same condition viewed from different teams. The practitioner conclusion is that budget planning needs identity inventory discipline, not just procurement discipline.
A few things that frame the scale:
- 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
A question worth separating out:
Q: Who should own SaaS offboarding decisions when a user leaves?
A: Ownership should be shared, but accountability should be explicit. HR triggers the event, IAM removes access, and the business owner confirms whether the app still has a valid purpose. The goal is to prevent a gap where the licence is cancelled but the account remains active, or vice versa.
👉 Read our full editorial: SaaS budget planning exposes shadow IT and offboarding gaps
