Home  ›  Blog  ›  Renewal Readiness
Strategy · Renewal

Renewal readiness — leverage is built 18 months out, not 18 days out.

Renewals are won or lost before the formal negotiation begins. The buyer who walks in with accurate licence position data, validated usage, identified shelfware, a credible alternative, and an internal sponsor aligned on outcome will negotiate against a different vendor than the buyer who walks in cold 60 days from contract expiry. Across 340+ engagements, the renewal cost variance between ‘ready’ and ‘not ready’ is consistently 20–40% of contract value.

Updated: June 2026 Reading time: 14 min Audience: CIO, CFO, Procurement, IT Asset Management
Enterprise renewal planning
Why timing dominates outcome

The leverage curve is front-loaded.

Vendor account teams forecast their fiscal year on incumbent renewals. The forecast is most malleable 12–18 months before contract expiry; it is locked 60–90 days before expiry; and the buyer’s practical alternatives are exhausted in the final 30 days. The leverage available to the buyer is a function of how much time is left to walk — not a function of how aggressive the procurement team is in the room. The framework below structures the eighteen months before a major renewal so that the leverage available at month 18 is preserved through to the negotiation itself.

The eighteen-month timeline is deliberate. Some discrete activities — licence position baseline, technical alternative scoping, executive sponsor alignment — take three to six months on their own. Sequencing them in parallel within an eighteen-month window produces a readiness state that vendors recognise and price for; compressing them into six months produces obvious gaps that vendors exploit.

Month 18–15 — Licence position baseline

The first ninety days of renewal readiness are about facts. What is actually deployed, against what is actually licensed, against what is actually used. The three numbers are routinely 30–50% different from each other — entitlements bought, entitlements deployed, entitlements active — and the differences are where renewal cost is set. The baseline is built from authoritative sources (deployment scans, vendor portal data, AD/SSO logs, financial records of historical purchases) not from vendor-supplied entitlement reports. That same baseline is the foundation of any serious license cost reduction — you cannot reclaim what you have not first measured against deployment.

Month 18–15 — Internal stakeholder map

In parallel: identify the internal stakeholders whose alignment will decide the renewal outcome. CIO, CFO, business sponsors of the affected systems, General Counsel, internal audit. The vendor account team will route to whichever stakeholder produces the path of least resistance; the buyer’s job is to ensure no stakeholder produces a different signal than the procurement-led narrative. A misaligned business sponsor will collapse the renewal leverage in a single conversation.

Month 15–12 — Usage and shelfware analysis

Convert the licence position baseline into a usage narrative. Of the licensed entitlements, which are actively used in the past 90 days? Which are dormant? Which are duplicated by adjacent SaaS subscriptions? Shelfware at 20–40% of total licensed entitlements is typical; in some categories (Salesforce, Adobe, ServiceNow) it is consistently 30–50%. The shelfware number is the single most powerful negotiation input — it provides the basis for a true-down request and the justification for a smaller renewal footprint.

Major renewal more than 12 months out?

Our renewal readiness engagements run in parallel with the buyer’s internal team and produce the data, narrative, and sequencing for the negotiation itself.

Contact Us →

Month 12–9 — Technical alternative scoping

For high-stakes renewals, the credibility of an alternative is the dominant leverage source. Month 12 to month 9 is when the alternative is scoped — technical fit, migration architecture, partner availability, indicative pricing. The output is not a decision to switch; it is a defensible alternative the buyer could execute if needed. The alternative is then a fact, not a threat, in the negotiation that follows.

Month 12–9 — Benchmark data acquisition

Independent price benchmarks for the relevant vendor and product mix. The benchmarks must come from sources the vendor cannot dismiss — market peer transactions of comparable size and structure, not vendor-supplied ‘industry averages’. The benchmark establishes the discount-from-list range the buyer should expect, which is then the anchor for the negotiation. Without benchmarks, the buyer is negotiating against the vendor’s narrative of ‘our best discount for this size of customer’.

Month 9–6 — Bid kick-off (if competitive)

If a competitive bid is part of the strategy, month 9 is the latest acceptable kick-off. Earlier is better. A bid that kicks off 6 months from renewal cannot run with credible alternatives in the timeframe; vendors recognise this and price accordingly. Reference our competitive bid framework for the operational steps.

Month 9–6 — Executive sponsor alignment

The CIO and CFO (and where relevant, the affected business sponsor) align on the renewal proposition: target spend, willingness to switch, acceptable risk envelope. Without this alignment, the vendor account team will identify the path of least resistance and route around procurement. The alignment is documented — not in a contract, but in an internal memo that captures the executive position and authorises the procurement team to negotiate accordingly.

Download the CIO Contract Governance Guide.

The full renewal readiness checklist, stakeholder map template, and timing sequence.

Get the guide →

Month 6–3 — Formal negotiation

The formal negotiation begins six months before renewal, not three. Vendor sales cycles need time to escalate, reprice, and approve — vendors are not capable of producing their best offer in a 30-day cycle. The opening proposal, technical and commercial questions, two or three iterative rounds, and best-and-final all fit comfortably in the six-month window. Compressed timelines produce vendor-template outcomes.

Month 3–1 — Best-and-final and structural redline

The last 60 days are structural, not commercial. Headline price is largely set by month 3; the work of the final 60 days is the protection clauses, audit language, true-down rights, and termination mechanics. This is where the contract that survives five years is built. Compressing it into the final 30 days, when the vendor knows expiry pressure is on the buyer, is the most common failure mode in enterprise renewal.

Month 1–0 — Signature and handover

The final 30 days are signature and operational handover — not negotiation. If material commercial terms are still open at this point, the buyer has lost. Vendors target the final week routinely; the disciplined buyer routes the vendor to closure earlier.

Eighteen months is the framework. Twelve is workable. Six is the floor.

If the renewal is more than 6 months away, readiness is the highest-ROI work in the procurement function.

Negotiation service →

Internal sequence

Three checks tell you whether your renewal readiness is real. First, does the licence position baseline reconcile the three numbers (purchased, deployed, used) within a defensible variance? Second, has the executive sponsor signed off on a target spend and a walk-away position? Third, would the technical alternative survive a CEO challenge as deployable? If any answer is no, the readiness is not yet complete.

FAQ

Common questions.

How early is too early to start renewal readiness?
Eighteen months out is standard for major renewals. Twenty-four months is reasonable for very large contracts (over $10M annual spend) or contracts with significant technical migration alternatives. Starting earlier than that risks the data becoming stale before the negotiation begins.
What if the renewal is only three months out?
The full eighteen-month framework cannot be compressed into three. Focus on the highest-leverage subset: licence position baseline, shelfware quantification, executive alignment on target spend. Skip the competitive bid — it is not credible in three months.
Is a competitive bid always necessary?
No. For some renewals (smaller contracts, single-product portfolios, low switching cost) a benchmark-anchored negotiation produces enough leverage. For high-stakes platform contracts, the credible alternative is typically the dominant leverage source.
Who should own the renewal readiness program?
Procurement should run it; the CIO sponsors it; the CFO endorses the target spend; IT Asset Management produces the licence position baseline. Without all four roles engaged, the program loses credibility.
How much does external renewal advisory typically cost?
Engagement models vary — fixed-fee project, success-fee against savings, monthly retainer. Typical fees are 5–15% of the savings achieved — sustainably positive ROI even at the lower end of the savings band.

Major renewal more than 6 months out?
Readiness is the highest-ROI work in the procurement function.

Renewal readiness engagements running 6 to 18 months pre-expiry. Former vendor licensing executives, working only for buyers.

The Compliance Brief

Weekly compliance intelligence for IT leaders.