Topic starter
10/06/2026 11:30 pm
TL;DR: SaaS renewals often become reactive because usage data is fragmented, ownership is unclear, and offboarding gaps leave former employees and unused licenses on the books, according to 1Password. The governance problem is not negotiation skill but identity visibility, because renewal decisions are only as accurate as the access data behind them.
Editorial analysis by NHI Mgmt Group, based on content published by 1Password: “How to wrangle SaaS contract renewals”.
Key questions
Q: What breaks when SaaS renewals are handled without identity context?
A: Renewal decisions become detached from whether the app is still in use, who owns it and whether stale accounts remain.
Q: Why do unused SaaS licences keep showing up in mature environments?
A: Because usage data, procurement records, and identity assignments are often managed in separate systems.
Q: How should teams decide whether a SaaS app should be renewed or retired?
A: They should combine business ownership, feature usage, and contract terms in one review.
Practitioner guidance
- Map renewal decisions to identity and entitlement data Combine contract, usage, and account ownership records so each renewal has a current view of active users, dormant licences, and app ownership before notice periods begin.
- Tie renewal review to offboarding completion Require proof that former employee accounts and their licence assignments are removed before a contract is approved for renewal.
- Assign accountable owners for each SaaS app Name one business owner and one technical owner for every application so renewal, access review, and spend decisions do not fall between teams.
Bottom line: SaaS renewal waste usually comes from weak access governance, not weak vendor negotiation.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 21 hours ago by NHI Mgmt Group
12/06/2026 5:36 am
SaaS renewal management is a lifecycle control problem wearing a finance label: The article shows that renewal outcomes are determined by identity visibility, ownership clarity, and entitlement cleanup before procurement ever enters the picture. In mature programmes, renewal review is one checkpoint in a broader access governance cycle that spans joiner, mover, and leaver events. The practitioner lesson is that contract renewals should inherit identity truth, not replace it.
A few things that frame the scale:
- 1 in 3 organisations encountered suspicious AI agent activity in 2025, and 99.4% experienced a SaaS or AI ecosystem incident.
A question worth separating out:
Q: What should teams do when former employees still appear in renewal counts?
A: Treat that as an offboarding and access cleanup problem, not a billing quirk. Remove the stale accounts, reclaim the licences, and verify that entitlement records match current employment status before the contract is renewed. Otherwise, the organisation keeps paying for access that no longer exists.
👉 Read our full editorial: SaaS renewal management is really an access governance problem
This post was modified 21 hours ago by NHI Mgmt Group