Notifications
Clear all
Topic starter
12/06/2026 1:17 am
TL;DR: SaaS cost optimisation starts with visibility, because duplicate apps, forgotten auto-renewals, and over-tiered licences quietly drain budget and create unmanaged access paths, according to Zluri. The governance lesson is that spend control and identity control are now the same operating problem, especially where unsanctioned apps sit outside IT review.
NHIMG editorial — based on content published by Zluri: SaaS Management 5 Ways for SaaS Cost Optimization During Recession
By the numbers:
- Zluri says its platform discovers 100% of apps across the organisation using five discovery methods.
- By default, Zluri sends contract alerts 30, 15, 7, and 1 days before renewal, and payment alerts 7 and 1 days before renewal.
Questions worth separating out
Q: How should teams govern SaaS renewals to avoid wasted spend?
A: Treat renewals as a governance checkpoint, not an accounting event.
Q: Why do duplicate SaaS apps create identity and access risk?
A: Duplicate apps create multiple entitlement paths for the same business function, which makes ownership, offboarding, and audit review harder.
Q: How do organisations know if SaaS rightsizing is working?
A: Look for fewer duplicate licences, lower renewal rates for unused tiers, and a tighter link between role needs and feature consumption.
Practitioner guidance
- Build a single SaaS inventory Join procurement, finance, SSO, and endpoint data so every app has an owner, user set, and renewal date.
- Tie renewal review to usage evidence Require usage telemetry and business owner sign-off before any auto-renewal proceeds.
- Rightsize premium tiers by role Compare feature consumption by department and role before each renewal, then downgrade licences that carry unused premium features.
What's in the full article
Zluri's full blog post covers the operational detail this post intentionally leaves for the source:
- Discovery workflow detail across SSO, API, finance, browser, and endpoint signals.
- Renewal calendar behaviour for contract and payment alerts before cancellation decisions.
- Practical examples of duplicate app consolidation and licence downgrade decisions.
- Negotiation framing for longer-term SaaS contracts and volume pricing discussions.
👉 Read Zluri's guide to SaaS cost optimisation during recession →
SaaS sprawl and auto-renewals: what IAM teams need to know?
Explore further
12/06/2026 11:06 am
SaaS cost optimisation is identity governance in another form. The article treats app spend as a procurement problem, but the deeper issue is that every unmanaged subscription also creates unmanaged access. When employees can buy software directly, the organisation loses entitlement oversight, offboarding discipline, and visibility into who can still use what. The practitioner conclusion is that SaaS rationalisation must sit inside IAM and IGA, not beside them.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to The State of Secrets in AppSec.
- Organisations maintain an average of 6 distinct secrets manager instances, creating fragmentation that undermines centralised control, according to The State of Secrets in AppSec.
A question worth separating out:
Q: Who should own SaaS spend and access decisions?
A: Ownership should be shared, but responsibility must be explicit. Finance can track spend, procurement can negotiate terms, and IAM or IT can govern access and inventory. If those functions are disconnected, the organisation will keep paying for software that no longer matches user need or policy intent.
👉 Read our full editorial: SaaS sprawl creates cost waste and hidden access risk
