Software Renewal 90-Day Countdown
What to Do in the Last 3 Months Before Any Major Renewal

Why the 90-Day Software Renewal Preparation Plan Matters

Enterprise software renewals are asymmetric events. The vendor's account team begins planning your renewal 6–12 months in advance. They have your usage data, your contract expiry date, your budget cycle, and — in most cases — a good model of how much friction switching would create for your organisation. When a procurement team starts the same process in the final 30 days, they are negotiating against a party that has had 11 extra months of preparation. The outcome reflects that asymmetry.

The 90-day preparation window is not arbitrary. It reflects the minimum time needed to complete four interdependent workstreams: licence position reconciliation (which takes 3–6 weeks for complex estates), competitive market evaluation (which requires at least 4 weeks for a credible RFI), internal stakeholder alignment (which must precede any vendor conversation), and contract analysis (which cannot be rushed without creating risk). Starting at day 60 means something does not get done. Starting at day 30 means at least two of these workstreams get compressed to the point of uselessness. As part of a broader understanding of enterprise software negotiation leverage, the preparation timeline is the single highest-impact variable under your control.

Days 90–61: Establish Your Licence Position

The first four weeks of your 90-day countdown should be entirely devoted to establishing what you own and what you actually use. This is your software licence position document — the reconciliation between contracted entitlements and deployed use. Without it, you enter renewal negotiations blind, unable to challenge usage claims your vendor may make or to quantify the scope reduction you might legitimately negotiate.

Run discovery tooling across your environment and cross-reference output against your contract inventory. For complex platforms like SAP (where indirect access exposure can be significant), Oracle (where virtualisation affects processor licence counts), and IBM (where PVU and sub-capacity calculations are notoriously opaque), this exercise alone regularly surfaces savings opportunities of 8–15% before any negotiation has begun. The licence position document is your factual baseline — everything that follows in the 90-day process depends on it.

In parallel, pull your contract from the repository and have legal review the following: auto-renewal notice windows (missing these triggers automatic renewal at current or increased pricing), price cap clauses, MFN provisions, audit rights the vendor holds, and termination for convenience provisions. For a comprehensive review of which clauses matter most, see our guide on enterprise software contract red lines.

Days 60–31: Build Competitive Leverage

The second month of your 90-day countdown is about creating credible alternatives. This does not require a full procurement exercise — in most cases, a well-constructed Request for Information to two or three competing vendors is sufficient to change your negotiating posture materially. The goal is not to switch; it is to demonstrate that switching is a rational option your organisation has evaluated.

The Competitive Evaluation Process

Issue your RFI at day 60. It should cover pricing structure and indicative cost for your current user count and use case profile, migration support and implementation timelines, data export and portability provisions, and reference customer contacts in your sector. Receive responses by day 45. By day 35, you should have a pricing comparison document that shows — with real numbers — what a migration would cost and what the 3-year total cost of ownership looks like under alternative platforms. Download our enterprise software renewal white papers for vendor-by-vendor competitive benchmarks.

This competitive evaluation data serves two purposes. First, it anchors your negotiation: you can cite a specific competitor quote that demonstrates the market rate. Second, it forces your current vendor to justify their pricing on market terms rather than renewal inertia. In our experience, this step alone produces 6–15% additional savings compared to renewals conducted without competitive evaluation. The tactics for responding effectively to vendor price increases that arrive during this phase are covered in detail in our guide to SaaS price increase negotiation.

Days 30–1: Negotiate and Close

The final month is execution. By day 30, you should have your licence position confirmed, your competitive pricing data assembled, your internal stakeholders aligned on walk-away positions, and your contract redline requests prioritised. What you should not be doing in the final 30 days is gathering data — that work must be complete.

Schedule the initial negotiation call with your vendor for day 28–25. Open with your licence position findings, not with pricing. Show the vendor that you have done the work: here is what we contracted, here is what we deployed, here is the delta. This immediately establishes that you are informed, that you have done the technical groundwork, and that any attempt to charge you for unused entitlements is documented and contestable.

Present your commercial position at the second call (day 21–18). This should include your counter to any proposed price increase (citing market data or contract caps where available), your preferred term structure (multi-year lock at current or reduced pricing versus annual with flexibility — see our guide on structuring multi-year enterprise software deals for the trade-offs), and any scope adjustments based on your licence position review.

Leave days 14–7 for legal review of the revised agreement. Never compress this window. Unfavourable contract terms accepted in the final days of a renewal — because legal did not have time to review — can cost more over the contract term than the rate you negotiated. To ensure you are never accepting terms that should be non-negotiable, our contract red lines framework covers the 20 clauses that must always be addressed. For complex renewals or where internal resources are constrained, book a confidential call with Redress Compliance — we can run this entire process on your behalf.