The 12-Month Software Renewal Planning Cycle

This article is part of our Software Renewal Strategy: The Enterprise Optimization Guide. It covers the month-by-month renewal planning cycle in detail — providing a structured, repeatable process for preparing for and executing major enterprise software renewals.

The 12-month horizon is appropriate for renewals over $500K annually. For renewals between $100K–$500K, a 6–9 month horizon is sufficient. Below $100K, a 3–6 month horizon is typically adequate unless the contract is for a strategically critical system with limited alternatives.

Month 12–10: Strategic Assessment Phase

Key decisions at Month 12: Based on the strategic assessment, make a preliminary decision on your stance for this renewal. Three options:

• Renew and optimise: You plan to continue with this vendor but want better commercial terms. Proceed to the leverage-building phase.
• Competitive replacement: The strategic case for replacement is strong and alternatives are viable. Initiate an RFP process immediately — you need 6+ months for evaluation and migration planning.
• Consolidation or restructure: You want to significantly change the scope of what you buy from this vendor (reduce seats, change tier, exit specific modules). This requires a different commercial approach than a standard renewal.

Month 9–7: Intelligence Gathering and Leverage Development

Benchmarking: What Should You Be Paying?

Initiate a formal benchmarking exercise to establish market rates for the products you're renewing. The goal is to answer: what are comparable organisations (similar size, industry, product configuration) paying per unit? Sources include peer network data, analyst reports, procurement intelligence platforms, and advisory firm databases.

See our SaaS pricing benchmarking guide for a structured approach. For complex platforms (Oracle, SAP, Salesforce, ServiceNow), engaging an advisory firm with a proprietary benchmark database at this stage pays for itself quickly. See our rankings of IT negotiation consulting firms for independent evaluations of leading advisors.

BATNA Development: What Happens If You Walk?

Your BATNA — Best Alternative to a Negotiated Agreement — is your most powerful source of leverage. This phase is when you build it. If you are pursuing a competitive replacement, get formal bids from at least two alternatives by the end of month 7. If you are planning to renew but want competitive leverage, brief 2–3 competitive alternatives and request pricing, even if you have no current intention to switch.

The act of briefing competitive alternatives changes vendor behaviour. Account teams monitor competitive activity through channel networks and partner intel. When your Salesforce rep hears you've briefed Dynamics, their commercial behaviour changes — regardless of how committed to Salesforce your account actually is. See our guide to creating negotiation leverage before renewal for the mechanics.

Internal Alignment: Who Owns This Renewal?

Establish clear ownership and governance for the renewal before vendor engagement begins. Identify: the primary negotiator (typically procurement or commercial IT), the business sponsor (the executive who needs the software and has the budget), the technical evaluator (who can assess alternatives and articulate migration cost), and the executive sponsor (the executive who can call their counterpart at the vendor when discussions stall). Without pre-agreed governance, renewals stall on internal disagreements at exactly the wrong moment.

Month 6–4: Vendor Engagement and Initial Negotiation

The Opening Signal

Schedule a business review meeting with the vendor's account team and their commercial contacts. The purpose: share your usage analysis (which signals you know what you're using and may right-size), indicate that you've been conducting renewal preparation (which signals you're not passive), and invite them to bring their renewal commercial proposal to a follow-up meeting.

Do not reveal your benchmarking data or BATNA position at this stage. You want to see their opening offer before revealing what you know. Vendors typically open with their best achievable rate plus 15–25% buffer for negotiation. Seeing their opening offer tells you where the conversation starts.

Evaluating the Vendor's Proposal

When the vendor presents their renewal proposal, evaluate it against three benchmarks: (1) your current rate — are they proposing an increase, and by how much? (2) your market benchmark — how does their proposed rate compare to what comparable organisations pay? (3) your target rate — what is the commercially achievable rate based on your benchmarking and leverage position?

Document the gap clearly. If the vendor proposes $150/user and your benchmark suggests $110–120 is achievable, your negotiation target is clear and you have an 25–30% improvement opportunity to pursue.

Right-Sizing the Scope

Before engaging on price, establish the correct scope. If your usage audit revealed 40% licence utilisation, the renewal scope should reflect actual usage, not historical over-licensing. Request to reduce to the actual required licence count before discussing per-unit price. This has two commercial benefits: it reduces the direct cost immediately, and it demonstrates to the vendor that you've done the analytical work — which signals a prepared buyer and typically results in better commercial terms on the remaining scope.

Month 3–2: Active Negotiation Phase

Presenting Benchmarking Data

Present your benchmarking findings formally. Frame it as: "In preparing for this renewal, we benchmarked your pricing against comparable organisations in our peer group. We found that similar organisations are achieving rates of X–Y per unit, which is significantly below your current proposal. We want to understand how we can reach a more competitive commercial position." This framing is informational rather than adversarial, invites the vendor to respond commercially, and puts the burden on them to justify the pricing gap.

Deploying Competitive Leverage

If you have active competitive bids, this is the time to deploy them. Share that you've received competitive proposals that are commercially attractive. Avoid naming specific competitors or providing exact pricing from competitive bids — this would trigger a price match conversation that anchors to the competitor's price rather than the market rate you've benchmarked. Instead: "We've received competitive proposals that are meaningfully below your current pricing, and we're evaluating our options. We'd prefer to stay with you given the relationship, but the commercial gap needs to close."

Executive Escalation

If the vendor's account team reaches their authority ceiling and cannot move to your target rate, escalate. Your executive sponsor should contact their counterpart at the vendor (VP of Sales, Commercial Director, CRO). Executive-to-executive conversations unlock authority that account teams lack. Prepare a briefing for your executive sponsor: what the gap is, what you've tried, why you need their intervention, and what outcome you're asking them to drive toward.

Contract Terms, Not Just Price

While negotiating price, concurrently negotiate the key contract terms that protect you in future renewal cycles:

• Price escalation cap: CPI-indexed or capped at 3–5% per annum for the contract term. Without this, your negotiated rate erodes at the next renewal.
• Flex-down rights: The ability to reduce licence count mid-term if headcount decreases or usage falls. Particularly important for SaaS with per-seat pricing.
• Exit rights: Termination for convenience provisions, minimum notice periods, and data export guarantees.
• Audit rights: Restrictions on vendor-initiated audits during the contract term — particularly important for Oracle, SAP, and IBM.

See our software contract red flags guide and contract negotiation checklist for a comprehensive review framework.

Month 1: Close and Documentation

Auto-Renewal Deadline Management

If the negotiation is not yet closed and the contract contains an auto-renewal clause, manage the notice deadline carefully. Most auto-renewal clauses require 30–90 days' notice before expiry to opt out of automatic renewal. If your negotiation has not closed to your satisfaction and you are approaching this deadline, send a formal opt-out notice to preserve your flexibility — even if you expect to renew. An auto-renewal triggered mid-negotiation gives the vendor significant leverage to hold the agreed terms.

Final Agreement Review

Before signing, conduct a final review of the agreed commercial and legal terms against your negotiation objectives. Verify that all verbal commitments are reflected in the written agreement — commercial terms agreed verbally but not documented are unenforceable. Check: pricing and discount structure, escalation cap wording, licence count and tier, support terms, renewal notice requirements, termination rights, and audit restrictions.

Renewal Documentation

Document the renewal outcome comprehensively for institutional memory:

• Vendor's initial proposal (price, terms)
• Your counter-proposal and the benchmarking data used
• Final agreed terms and the delta from the vendor's opening position
• Cost avoidance calculated vs auto-renewal scenario
• Key tactics that worked and those that did not
• Next renewal date and immediate actions to set (calendar reminder at T-12 months)

See our guide to renewal cost avoidance documentation for the methodology for calculating and reporting the commercial outcome of the renewal programme.

The 90-Day Renewal Preparation Checklist

For renewals where the full 12-month window has been missed, this compressed 90-day checklist captures the highest-priority actions:

• Confirm renewal date and auto-renewal notice deadline — trigger opt-out notice immediately if needed
• Pull contract and read escalation, audit, and exit clauses
• Conduct express usage audit — login data and active user count
• Request competitive pricing from at least one credible alternative
• Source benchmarking data from at least two external sources
• Establish internal governance: negotiator, business sponsor, executive sponsor
• Request vendor's renewal proposal — do not accept the first offer
• Present benchmarking gap to vendor account team
• Deploy competitive leverage — signal evaluation activity
• Negotiate price escalation cap alongside per-unit price
• Escalate to executive level if account team cannot move to target rate
• Final legal review of agreed terms before signing
• Document outcome and set T-12 reminder for next cycle

Renewal Preparation by Contract Size

Contract Value	Preparation Horizon	Benchmarking Approach	Advisory Support	Executive Involvement
Over $2M annually	12+ months	Full advisory database benchmarking	Strongly recommended	CIO / CFO direct involvement
$500K–$2M	9–12 months	Peer network + analyst benchmarks	Consider for complex vendors	VP level sponsor
$100K–$500K	6–9 months	Peer network + NPI/ISG reports	Internal sufficient	Director level sponsor
$25K–$100K	3–6 months	Peer network informally	Internal sufficient	Manager sign-off
Under $25K	1–3 months	List price reference only	Auto-renewal review	Procurement team only

Building the Capability: Institutionalising the Renewal Cycle

The 12-month renewal planning cycle works as a one-off approach. It becomes transformational when institutionalised as a standard operating procedure across your entire software portfolio.

The key to institutionalisation is a rolling renewal calendar — a forward-looking view of every significant contract, its expiry date, and the T-12 trigger date that initiates the preparation cycle. This calendar should be reviewed at least quarterly by the IT and procurement leadership team, with renewal milestones tracked and progress reported.

Many organisations also benefit from a dedicated renewal programme lead — someone who owns the forward calendar, coordinates the preparation process for major renewals, maintains benchmarking data, and manages the advisory relationships that support high-value negotiations. For organisations with $10M+ in annual software spend, this role typically delivers 10–20× its cost in achieved savings.

For a complete overview of the strategic framework, see our Software Renewal Strategy: The Enterprise Optimization Guide. For guidance on the techniques used during active negotiation, see creating negotiation leverage, handling aggressive vendor tactics, and our IT contract negotiation strategy guide.