Notifications
Clear all
Topic starter
12/06/2026 1:08 am
TL;DR: Unmanaged SaaS renewals create avoidable spend, missed cancellation windows, and operational disruption when usage, owners, and contract terms are not visible, according to Zluri. The deeper issue is governance: renewal control is really about knowing which applications, subscriptions, and entitlements still deserve to exist.
NHIMG editorial — based on content published by Zluri: Procurement How to Manage SaaS Renewals
By the numbers:
- Zluri says its nine discovery methods find 100% of SaaS apps in an organisation.
- Zluri says contract alerts can arrive 30 days, 15 days, and one day in advance.
- 50% of SaaS cost., ocurement team can help save up to 50% of SaaS cost.
Questions worth separating out
Q: How should teams manage SaaS renewals before notice windows close?
A: Teams should use a renewal calendar that starts review work before the cancellation deadline, not at the invoice stage.
Q: Why do unmanaged SaaS renewals create governance risk?
A: Unmanaged renewals let unused applications, stale contracts, and dormant access stay active because no one has a timely decision point.
Q: What breaks when SaaS ownership is not assigned?
A: Renewal decisions become reactive when no one is accountable for app usage, contract terms, and cancellation timing.
Practitioner guidance
- Build a live renewal inventory Maintain a current register of SaaS apps, owners, usage level, renewal date, cancellation terms, and payment schedule.
- Set review dates before notice windows close Trigger business, finance, and security review well ahead of cancellation deadlines so the team can terminate, renegotiate, or downgrade before auto-renewal locks in.
- Tie renewals to access and ownership reviews Check whether the application still has a named business owner, active users, and related identities or tokens before approving renewal.
What's in the full article
Zluri's full blog post covers the operational detail this post intentionally leaves for the source:
- The article's comparison of spreadsheet tracking versus SaaS management platforms for renewal handling.
- The nine discovery methods Zluri says it uses to find SaaS applications across the organisation.
- The alert cadence for contract and payment renewals, including the 30-day, 15-day, 7-day, and 1-day notifications.
- The procurement workflow details behind licensing, negotiation, and cost optimisation decisions.
👉 Read Zluri's guide to managing SaaS renewals and app lifecycle decisions →
SaaS renewals and unmanaged access sprawl: what teams miss?
Explore further
12/06/2026 10:51 am
SaaS renewal management is really identity and application lifecycle governance in disguise. The article frames renewals as procurement work, but the underlying control problem is whether the organisation still has a valid reason to keep an application, subscription, and associated access alive. That makes the renewal process part of lifecycle governance, not a separate administrative task. The practitioner implication is straightforward: if ownership and usage are unclear, lifecycle decisions will drift.
A few things that frame the scale:
- 71% of NHIs are not rotated within recommended time frames, increasing the risk of compromise over time, according to the Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which shows how quickly identity inventory problems become governance problems.
A question worth separating out:
Q: How do organisations know if SaaS renewal controls are working?
A: Look for fewer surprise renewals, fewer apps renewed without active use, and documented decisions for each high-value contract. A strong programme can explain why an app stayed, why it was downgraded, or why it was retired. If those answers are missing, the control is still largely manual.
👉 Read our full editorial: SaaS renewal management exposes the identity and spend gap
