Software Renewal 90-Day Countdown: Week-by-Week Enterprise Action Plan

Why 90 Days Is the Minimum, Not the Target

Enterprise software contracts typically have auto-renewal clauses requiring cancellation notice 30 to 90 days before expiry. Many organisations set a reminder for 30 days before renewal and treat that as adequate preparation time. It is not. A 30-day window gives the vendor every advantage: there is no time to evaluate alternatives, no time to build a current licence position, no time to engage stakeholders, and no time to negotiate through multiple rounds. The vendor's renewal team knows this, and prices accordingly.

Ninety days is the minimum preparation period for any enterprise contract above £100,000 annually. For strategic contracts — Oracle ELA, SAP RISE, Microsoft EA, Salesforce ELA, ServiceNow platform agreements — 120 to 180 days is more appropriate. The reason is not that negotiations take that long; most enterprise renewals are agreed within four to six weeks of active negotiation. The reason is that the preparation before negotiations begin — licence position review, usage analysis, stakeholder alignment, competitive alternatives assessment — takes time, and doing it properly is what determines your starting position in the negotiating room.

Days 90–61: Foundation Work

Week 1 (Day 90–83): Assemble the Team and Retrieve the Contract

The first step is deceptively simple and consistently skipped: retrieve and read the current contract. Not a summary of the contract — the actual agreement, including all order forms, schedule amendments, and correspondence that may have modified the original terms. The current contract defines your baseline entitlements, your renewal rights, any price escalation clauses that will apply automatically at renewal, and the notice periods that govern your ability to cancel or modify the agreement. Many organisations enter renewal negotiations without a clear understanding of what they are actually renewing, which allows vendors to define the scope.

Assemble the renewal team at the same time. A well-functioning renewal team for an enterprise software contract includes: a commercial lead from procurement (who owns the negotiation process), a technical lead from IT (who can validate licence requirements against actual deployment needs), a finance representative (who can confirm budget parameters and approval thresholds), and a legal reviewer (for contract markup and risk assessment on non-standard terms). On complex renewals involving dedicated account teams at the vendor, consider whether external licensing expertise would add value — particularly for Oracle, IBM, and SAP renewals where the vendor's account team has deep institutional knowledge that most internal teams lack.

Week 2–3 (Day 82–67): Licence Position and Usage Review

The licence position review is the most commercially important preparation activity in the entire 90-day countdown. It answers two questions: what are you currently entitled to, and what are you actually using? The gap between those two answers determines where the negotiation starts. An organisation that discovers it is using only 65 percent of its Salesforce licences enters the renewal conversation in a very different position than one that has no idea what its utilisation rate is. The former can credibly propose a licence reduction and challenge the vendor to compete for the renewed commitment; the latter is at the mercy of the vendor's renewal proposal.

Collect usage data from every available source: vendor-provided usage dashboards (which every major SaaS vendor now provides, though the data may require interpretation), your SAM or ITAM tooling, endpoint management systems, and direct surveys of application owners. For on-premises software, compare licence entitlements against deployment discovery data. For cloud consumption agreements, pull usage reports from the cloud billing console and compare against committed spend thresholds. Document the results in a simple table: product, licences purchased, licences actively used, percentage utilisation, and estimated annual cost of unused capacity.

Week 4 (Day 66–60): Competitive Alternatives Assessment

The most powerful thing a renewal team can bring to a vendor negotiation is a credible alternative. Vendors who believe their customer has no viable alternative price accordingly. Vendors who understand their customer has done a genuine evaluation of the competitive landscape — and may actually be willing to switch — behave differently. You do not need to run a full RFP process to establish credibility; you need to demonstrate that you have evaluated the alternatives seriously enough that the risk of switching is real.

For each major renewal, identify two to three competitive alternatives and gather enough intelligence to construct a rough TCO comparison: licence costs, implementation costs, migration costs, and ongoing support costs. For some vendors — Oracle, IBM — switching costs are genuinely high and the competitive threat will be limited. For others — Salesforce, ServiceNow, many SaaS platforms — the competitive landscape is more fluid and the threat of switching is more credible. Even for high-switching-cost vendors, the existence of a documented alternative assessment changes the tone of the negotiation: you are negotiating from knowledge, not desperation.

Renewal Outcomes: What the Data Shows

Across 500+ enterprise renewals, Redress Compliance has tracked the relationship between preparation lead time and negotiation outcomes. The pattern is consistent across every major vendor:

For vendor-specific renewal support, see our Oracle licensing advisory specialists, Microsoft EA advisory specialists, SAP commercial advisory specialists, and IBM licensing advisory specialists.

Days 60–31: Preparation and Opening Position

Week 5–6 (Day 60–46): Benchmark Pricing and Opening Position

With licence position and competitive alternatives in hand, the renewal team is ready to construct an opening position. The opening position has three components: the commercial ask (what you want to pay and on what terms), the scope ask (the licence configuration you want to renew, based on the usage review), and the contractual ask (the non-commercial terms you want to change from the existing agreement). Many organisations focus exclusively on the commercial ask and treat the contractual terms as non-negotiable. This is a mistake. Contractual terms — audit rights, price escalation caps, service credit provisions, exit rights — have financial value that compounds over the term of the agreement.

Benchmark pricing is the evidence base for the commercial ask. Internal benchmarks — comparing this year's price against last year's — are insufficient because they only measure the vendor's success at annual price increases, not whether you are paying a competitive market rate. Third-party benchmark data from Gartner, Forrester, or specialist advisors gives you an external reference point. When challenging a vendor's renewal quote, the statement "our benchmarking shows that comparable organisations are paying 18 percent less for equivalent entitlements" is significantly more powerful than "we think this is too expensive." One is an opinion; the other is a fact the vendor must respond to.

Week 7–8 (Day 45–31): Stakeholder Alignment and Internal Approval

A renewal negotiation that reaches the final stage only to stall because of internal approval delays is an negotiation that gives the vendor time to dig in. Secure internal alignment before negotiations begin: confirm the budget envelope with finance, the scope requirements with IT, and the decision-making authority with the business owner. Establish what the organisation will do if the vendor does not meet the opening position — whether that is accepting a compromise position, extending the negotiation, or genuinely triggering the competitive alternative assessment. Having a documented decision tree internally aligned before negotiations start prevents the vendor from exploiting internal indecision as negotiating leverage.

Also use this period to formally notify the vendor — in writing — that you are not auto-renewing the current agreement and that renewal is subject to negotiation. For many enterprise agreements, this notification serves as the formal trigger that prevents automatic renewal. Sending this notice 45 days before expiry is typically within the contractual window; confirm the exact period required in your current agreement. The act of sending this notice also signals to the vendor's renewal team that you are engaged and prepared, which itself can influence the commercial position they open with.

Days 30–1: Negotiation and Execution

Week 9–10 (Day 30–15): Active Negotiation

Enterprise software renewals typically go through two to four rounds of commercial negotiation. The vendor's first response to your opening position is almost never their best position — it is a probe to understand how much flexibility you have and how seriously you are pushing. Responding to the first counter with a clear explanation of your position — grounded in your licence position data, benchmark pricing, and competitive alternatives assessment — moves the negotiation forward more effectively than either accepting the counter too quickly or making an aggressive demand without evidence.

Maintain negotiating discipline throughout this phase. Do not negotiate individually on price, scope, and contractual terms — combine them into a package position that can be traded as a whole. A vendor who is willing to reduce price by 10 percent may be less willing to also provide audit protection provisions and price cap commitments. Packaging the asks together gives you more room to create a deal structure that meets your total objectives, and prevents the vendor from picking off individual asks one by one while preserving the overall commercial value of the agreement for themselves.

Pay particular attention to vendor fiscal year timing. Oracle's fiscal year ends May 31, SAP's ends December 31, Salesforce's ends January 31, and Microsoft's ends June 30. Vendors whose sales teams are working against quarter-end or year-end targets have a commercial incentive to close deals before those deadlines — which creates negotiating leverage for the customer who times their renewal accordingly. Knowing where your vendor is in their fiscal year, and whether your renewal coincides with a quarter-end pressure point, is one of the most consistently valuable pieces of commercial intelligence in any renewal negotiation.

Week 11–13 (Day 14–1): Contract Review and Execution

When commercial terms are agreed, legal review of the updated contract documentation should begin immediately. Delays between commercial agreement and legal execution give vendors an opportunity to reintroduce terms that were removed during negotiation, or to allow the commercial agreement to lapse while internal processes at the vendor reset. Establish a clear execution timeline — including who signs, at what authority level, and what the document management process is — before legal review begins.

Review the final contract documentation carefully for consistency with the negotiated commercial terms. Order forms, pricing schedules, and statement of work documents should all reflect the agreed position precisely. Common execution errors include: agreed discount rates not correctly reflected in order form pricing, annual price escalation percentages reverting to the vendor's standard rather than the negotiated cap, and optional renewal provisions (such as extension rights) that were verbally discussed but not included in the final documentation. Once signed, the contract is what it says — not what was agreed in conversation.

Vendor-Specific Timing Considerations

IBM fiscal year ends December 31. For IBM renewals — particularly ELAs covering IBM software, Cloud Pak bundles, and mainframe MIPS — December is both the most commercially flexible period (maximum end-of-year pressure on IBM's sales team) and the most congested (many customers renewing simultaneously, which can slow IBM's internal approval process). Starting an IBM renewal conversation in September gives you the full end-of-year window. For Microsoft, the June fiscal year-end creates Q4 (April to June) pressure that benefits customers who time their EA or MPSA renewal for that window. For Oracle, the May fiscal year-end creates a similar dynamic in Q4 (March to May), which is why the March to April window consistently produces Oracle's most competitive commercial positions. Salesforce's January year-end means that November and December are typically the most discount-receptive months for Enterprise Agreement negotiations.