Most enterprise software agreements are not lost in a competitive process. They are lost at renewal, in the six weeks before an expiry date, against a quote that arrived without warning and a vendor who knows exactly how little time is left. The purchase itself was governed. The renewal, which commits far more money over the years that follow, is often handled as an administrative task by whoever holds the contract file.
Why a renewal is the weakest moment in a technology contract
Three things are usually true at renewal, and each of them favours the vendor. No alternative has been priced, so the quoted figure has nothing to be compared against. No current reconciliation of entitlement against deployment exists, so the quantity on the quote goes unchallenged. And the expiry date is close enough that the practical choice has narrowed to accepting the terms or accepting an outage.
The money at stake is not marginal. Gartner forecasts Australian IT spending to reach A$172.3 billion in 2026, with software the largest single category. Most of that is renewal spend rather than new selection, which means the majority of an organisation’s technology commitment is decided in exactly the conditions described above.
Vendors have also been changing the shape of what they sell. Perpetual licences move to subscription. Editions are bundled so that a feature you use arrives inside a larger tier. Counting metrics shift between users, devices, cores and capacity. Each change is legitimate, and each resets a commercial position that was agreed years earlier under different assumptions. An organisation that does not re-examine the agreement is agreeing to whichever version of it the vendor has since built.
A renewal runs on a twelve-month runway
The practical fix is unglamorous. Treat the renewal as an event with a start date well before the end date, and give each stage an artefact.
Twelve months is not an arbitrary figure. Reconciling entitlement against deployment across a large estate takes weeks and usually surfaces questions that take longer. Pricing a credible alternative means running a real evaluation, not collecting an indicative quote. Both have to be finished before a commercial conversation is worth having, because the vendor’s opening position is calibrated to what it believes you can do about it.
Where the entitlement gap opens
The gap between what an organisation has paid for and what it actually runs is where renewal exposure lives. It is rarely a single number, and the components behave differently.
Two of these deserve particular attention in an Australian context. Indirect access, where another system reads or writes through an integration, is the gap most organisations discover during an audit rather than before one, because it is invisible in an install count. And unsupported versions are a security matter as well as a licensing one. Patching applications and operating systems sits inside the Essential Eight Maturity Model, so a deployment left past end of support is a control failure that a renewal decision either fixes or funds for another term.
The instrument that closes all five is a reconciliation you own. ISO/IEC 19770-1 sets out an IT asset management system for exactly this purpose. Certification is not the point for most organisations. Holding a defensible view of entitlement, deployment and usage, assembled from your own records rather than from a vendor’s reporting tool, is the point.
Five clauses that decide the next renewal
Price is negotiated once and applies to one term. The clauses below set the conditions for every renewal after this one, and they are far easier to move while the vendor is still competing for the signature.
Audit rights are worth reading closely rather than skimming. A clause permitting an audit on short notice, at your cost, with no limit on scope or method, converts a compliance question into an open-ended project the vendor controls. Notice periods, a defined scope, an agreed measurement method and a costs position are all standard requests. They are simply never volunteered.
Exit terms matter for a reason that has nothing to do with pessimism. A contract with no transition obligation and no named export format cannot be left, and an agreement you cannot leave is not one you can negotiate. The exit clause is what makes the next renewal a genuine decision.
The evidence that makes a renewal defensible
For Commonwealth entities the obligation is explicit. The Commonwealth Procurement Rules make value for money the core rule, which requires a comparison rather than an assertion, and whole-of-government software arrangements exist precisely so that individual agencies are not negotiating the same terms in isolation (see the Digital Transformation Agency’s whole-of-government software arrangements).
Private sector boards have no equivalent rulebook and increasingly ask the same question. A renewal that cannot be explained afterwards has the same problem as any other procurement decision made without a record, which we set out in how to manage procurement risk in IT and cybersecurity. The evidence pack for a renewal is short: the reconciliation, the alternative that was priced, the clauses that were sought and what happened to each, and the reason the final position was accepted.
When to test the market, and when not to
Not every renewal justifies a full competitive process. Running one has a real cost in internal effort, and a market test that everyone knows is theatre weakens your position rather than strengthening it.
A genuine test is worth running when the spend is material, when the vendor’s model has changed since you last agreed terms, when switching is technically feasible within the term, or when you have never priced an alternative for this category. Where none of those holds, the honest move is a well-prepared direct negotiation: the reconciliation still gets done, the clauses are still on the table, and the vendor is told plainly which parts of the agreement you intend to change. Our note on structured vendor comparison methods covers how to keep a shortlist comparable when a test is warranted.
The distinction that matters is preparation rather than process. A direct negotiation from a defensible baseline beats a competitive process run without one.
Common questions
When should a software renewal process start?
About twelve months before expiry for a material agreement. Reconciling entitlement against deployment takes weeks on a large estate, and pricing a credible alternative means running a real evaluation. Both need to be complete before commercial discussions begin, because the vendor’s opening position reflects what it believes you are able to do.
What is indirect access in software licensing?
Indirect access is consumption of a licensed product by people or systems that never touch it directly, usually through an integration with another application. It does not appear in an install or named-user count, which is why it is commonly identified during a vendor audit rather than before one.
Can audit clauses in a software agreement be negotiated?
Yes, and they routinely are. Reasonable positions include a notice period before an audit begins, a defined scope, an agreed measurement method, a limit on frequency, and costs borne by the auditing party unless a material shortfall is found. These are standard requests that are rarely offered without being asked for.
What is shelfware, and why does it survive renewals?
Shelfware is paid entitlement that nobody uses. It survives because renewal quantities are typically carried forward from the previous term rather than rebuilt from current usage, so an over-purchase made once is re-purchased every term until somebody measures consumption and reduces the count.
Does an unsupported software version create more than a licensing problem?
It does. Patching applications and operating systems is part of the Essential Eight Maturity Model, so a deployment running past end of support is a security control gap as well as a commercial one. A renewal decision either resolves that or funds it for another term.
Related guidance: what is strategic sourcing, vendor and supplier risk management, how to write a technology RFP, technology procurement services, and guided vendor evaluations.
Also relevant: strategic sourcing from a CFO perspective.
