Ask a mid-market IT director where their software overspend comes from and the answer is usually about price: the vendor pushed a rise, the tier was too high, the discount lapsed. Ask them to reconstruct how a specific renewal happened, and a different story appears. The contract renewed because the notice period expired. Nobody discovered that until the invoice arrived. By then the only available conversation was about next year.
That is not a negotiation failure. It is an administration failure, and it is worth separating the two because they have completely different fixes. Negotiation capability is expensive and scarce. Administration is neither — it is just work that has to happen on a date, and nobody's job description contains it.
What the notice period actually does
A typical enterprise software agreement renews automatically unless the customer gives notice a set period before the term ends — commonly 30, 60 or 90 days. The clause is unremarkable and usually negotiable at signature. Its effect is not.
Miss the window and the commercial position inverts completely. Before it, you are a customer deciding whether to continue, and the vendor's incentive is to keep you. After it, you are contractually committed for another term, and the vendor's incentive is to be pleasant about it. Every lever you had — competitive alternatives, downgrade, seat reduction, walking away — was attached to that date.
Building the register
Almost every organisation that has this problem also has the information needed to solve it, distributed across a contract folder, an AP ledger and several people's memories. Consolidation is a one-off project, and it is genuinely tedious, which is why it keeps not happening.
The register needs less than people expect. Per agreement:
- Vendor, product, and the internal owner — a named person, not a department.
- Term end date, and separately the notice deadline derived from the clause.
- Current annual value, and what it was at the previous two renewals.
- Licence metric and contracted quantity — seats, cores, endpoints, consumption tier.
- Whether the agreement contains an uplift cap, and what it is.
- Where the signed document actually lives.
The two columns that surprise people are the price history and the uplift cap. Price history turns a vendor's proposed increase from an assertion into a pattern you can point at. The uplift cap is frequently present, frequently forgotten, and frequently exceeded by the quoted increase — a discrepancy that is only found by somebody reading the contract before accepting the quote.
The cadence that makes it work
A register nobody works is a spreadsheet. What converts it into savings is a fixed rhythm, and the rhythm has to start earlier than feels necessary.
| When | What happens | Who |
|---|---|---|
| 180 days before term end | Renewal enters the active queue. Pull usage data and last two renewal prices. | Procurement |
| 150 days | Owner confirms: renew as-is, resize, replace, or retire. A decision, not a discussion. | Business owner |
| 120 days | If resizing or replacing, alternatives are approached. Vendor is told a review is underway. | Procurement |
| Notice deadline minus 14 days | Notice is served, or a positive decision to renew is recorded with the reason. | Procurement |
| Term end | Signed outcome filed, register updated with new price and next notice deadline. | Procurement |
Telling the vendor a review is underway is not a negotiating tactic so much as an honest statement, and it changes the shape of the conversation. A renewal the vendor believes is automatic gets an uplift. A renewal the vendor believes is contested gets an account manager.
Hardware and cloud are the same problem in different clothes
Software renewals are the most visible version because they arrive as a single invoice with a date on it. The same failure appears elsewhere with less warning.
- Support and maintenance contracts
- Hardware support renews on the same auto-renewal logic, often for equipment that has been decommissioned. Reconciling the supported asset list against the actual asset register is a routine exercise that is rarely routine.
- Cloud commitments
- Reserved capacity and committed-spend agreements have end dates and renewal decisions like anything else, but they arrive inside a consumption bill rather than as a renewal quote, so no one sees a date approaching.
- Per-seat tools bought on a card
- Below whatever threshold triggers procurement involvement, these renew invisibly and forever. They are individually trivial and collectively not.
Who should do this
The work splits cleanly, and recognising where it splits is what makes it staffable.
Deciding whether a platform is still the right one is an IT and business judgement that cannot be delegated anywhere. Deciding what to pay, and pushing back on an uplift, is a commercial judgement that needs someone senior in the room. But maintaining the register, pulling usage data, watching notice deadlines, reading the contract for the uplift cap, chasing the owner for a decision at the 150-day gate and filing the outcome — none of that requires either. It requires somebody whose job it is.
That is the honest case for putting this work outside your own team: not that it is difficult, but that it is relentless, date-driven and always less urgent than whatever the IT team is dealing with today. Which is precisely why it keeps not happening, and why the invoices keep arriving.
Common questions
What is an auto-renewal clause?
A term stating the agreement renews for a further period unless the customer gives notice a set number of days before the current term ends — commonly 30, 60 or 90. It is standard and usually negotiable at signature. Its practical effect is that all your commercial leverage is attached to a date, and it disappears the moment that date passes.
How far ahead should a software renewal be worked?
Start six months out. Work back from the notice deadline rather than the term end: a 90-day notice period plus a six-week internal review means preparation begins roughly seven and a half months into a twelve-month term. Diarising the renewal date rather than the notice deadline is the single most common version of this mistake.
What should a software renewal register contain?
Vendor, product, a named internal owner, term end date, the notice deadline derived from the clause, current annual value plus the previous two renewal prices, the licence metric and contracted quantity, any uplift cap in the agreement, and where the signed document lives. Price history and the uplift cap are the two columns most often missing and most often useful.
Why do renewals get missed when the contracts are all on file?
Because being on file is not the same as being diarised, and no one owns the date. Renewal administration is date-driven, repetitive and never the most urgent thing on an IT team's desk, so it loses to operational work every week until the invoice arrives. The fix is ownership and cadence, not better filing.
Does this apply to cloud and hardware support too?
Yes, and they are harder to see. Hardware support often renews for decommissioned equipment, and cloud commitments arrive inside a consumption bill rather than as a renewal quote, so nobody watches a date approach. Both need the same treatment: a register, an owner and a review that begins before the decision window closes.
Want this run for you?
We take on the transactional half of procurement — invoices, purchase orders, supplier data and indirect spend — inside your own systems and under your approval rules. Start with a free spend audit: we measure your volumes, cycle times and exception rates, and the report is yours whether or not you go further.
Book a free spend audit
