Every software contract eventually comes to a decision point: renew as it is, renew differently, or walk away. That decision is where most of the money in software asset management is won or lost. Yet in many organizations renewals are handled when the invoice arrives, long after the real deadline has passed.
Renewal management turns that around. It gives every agreement an owner, a deadline and a decision made on evidence. This playbook shows how.
Why renewals matter so much
A renewal is the one moment in a contract's life when everything is negotiable at once: volume, edition, price, term and protections. Between renewals, most of those are fixed. That is why the same organization can save 20% on a contract one year and nothing the next: the difference is whether anyone prepared.
Renewals are where software savings are realized. Everything else in SAM is preparation for that moment.
When renewals are handled late, the pattern is predictable. The vendor sends a quote close to the deadline, the business owner confirms the tool is still needed, procurement asks for a discount, and the agreement renews at roughly the same volume with a small price concession, if any.
The 120-day playbook
T−120: Flag and assign
Every agreement above a value threshold appears on the renewal calendar 120 days before its notice deadline. Name an owner, confirm the contract value, the renewal and notice dates, and any auto-renewal clause. See building a renewal calendar.
T−90: Gather evidence
Pull utilization for each product in the agreement, the number of inactive users, price history, budget plans and any satisfaction issues. Our guide to using usage data as leverage explains what to collect.
The renewal evidence pack
T−60: Decide the direction
With evidence in hand, choose one of four directions:
| Direction | When it fits |
|---|---|
| Renew as is | Well used, fairly priced, no better alternative |
| Renew smaller | Material shelfware or over-specified tiers |
| Renegotiate | Good fit, but price or terms out of line |
| Replace or retire | Poor fit, low use, or a better option exists |
T−30: Negotiate
Negotiate volume, price, term length, price protection and flexibility. See how to negotiate a software renewal.
T−0: Act before the deadline
Send the decision in writing before the notice deadline. If negotiation is not finished and the agreement auto-renews, consider sending notice to protect your position, after checking what notice means under that contract.
Make it a routine
Review the next 120 days of renewals with owners. Nothing enters the last 30 days without a direction.
Report renewals decided on time and savings achieved. See SAM KPIs.
Review the largest agreements a full year ahead, when term strategy and co-terming can still be planned.
How MI One helps
Frequently asked questions
Which renewals deserve the full playbook?
Set a value threshold, for example agreements above a set annual amount, and use a lighter checklist below it.
Who should own a renewal?
The person accountable for the product's value, usually in IT or the business, supported by procurement for negotiation.
What if we miss the notice deadline?
Ask the vendor anyway. Some will negotiate, but expect less flexibility. Then fix the process so it does not happen again.