A practical planning framework for enterprise and mid-market teams preparing a material software renewal before supplier timing takes over the process.
These milestones are a commercial planning framework. The executed agreement, order forms and amendments control actual notice and renewal obligations. Notice requirements vary by contract. Calder provides commercial support, not legal advice; the client’s counsel should confirm legal notice requirements and final contract language.
For a material or business-critical agreement, 120 days before expiration is a useful planning target when the contract timeline allows it. The purpose is to create enough runway for contract review, usage analysis, stakeholder alignment and commercial preparation. Actual notice and renewal obligations are controlled by the executed agreement, order forms and amendments.
A SaaS renewal notice period is a contractual window that may require a buyer to communicate a renewal, non-renewal or other specified action before the current term ends. The required timing, permitted method and legal effect vary by agreement. Buyers should verify the executed contract and involve counsel where legal interpretation is required.
Around 90 days before a material renewal, teams should validate active users, utilization, product tiers, commitments and forward demand; identify the people who own requirements and approvals; and confirm the exact contractual notice mechanics. The goal is to understand what the business needs before supplier discussions accelerate.
A buyer position is the documented commercial stance the organization intends to carry into a supplier discussion. It typically combines verified current usage, forward requirements, existing contract economics, prior negotiated terms, approval boundaries, requested changes and acceptable concessions. The client retains final decision authority.
| Timing | Buyer objective | Documents / data | Stakeholders | Commercial questions | Supplier action | Risk if delayed |
|---|---|---|---|---|---|---|
| Day -120 | Establish the contractual baseline | Executed MSA, active order forms, amendments, addenda, renewal terms | Commercial owner, Procurement, Legal | What controls renewal, notice, quantities, tiers and current commitments? | Internal verification first | Missing an early notice requirement can narrow available options. |
| Day -90 | Confirm utilization and forward demand | Usage reports, assigned licenses, feature adoption, headcount and demand forecasts | IT / system owners, business leaders, FP&A | What is actually used? What should increase, stay flat or decrease next term? | Request supplier configuration or usage summaries where useful | Negotiating against incomplete internal facts can weaken the buyer position. |
| Day -60 | Finalize commercial objectives and required notice actions | Validated requirements, commercial baseline, draft client-approved communications | Executive sponsor, Procurement, Legal | Should quantities, tiers, commitment structure, payment terms or protections change? | Complete any notice action required by the executed agreement using the approved channel | A missed contractual deadline can reduce flexibility before negotiations mature. |
| Day -45 | Evaluate supplier response and realistic alternatives | Initial proposal, switching-cost inputs, alternative options, migration constraints | Procurement, IT, Engineering / Operations as relevant | What is negotiable, what is operationally required, and what alternatives are genuinely viable? | Begin or continue approved supplier discussions | Waiting too long to test alternatives can make late-stage choices less credible. |
| Day -30 | Align the counter-position | Financial comparison, requested changes, concession ranges, approval boundaries | CFO / Finance sponsor, CIO / IT sponsor, Procurement | What is the approved target? What can be conceded? What requires escalation? | Submit or discuss the approved counter-position | Internal disagreement late in the process can undermine negotiating consistency. |
| Day -14 | Stabilize commercial and legal language | Latest order form, redlines, payment schedule, approval record | Legal, Procurement, executive approver, technical owner | Are agreed pricing, quantities, protections and future renewal mechanics accurately documented? | Resolve remaining approved commercial issues | Last-minute changes can create administrative, commercial or legal review risk. |
| Day 0 | Execute and preserve the next-cycle record | Fully executed documents and final commercial summary | Authorized signatory, contract owner, system owner | When should the next review begin? What notice mechanics now control the next term? | Exchange executed documents and confirm ownership | Poor contract metadata can force the organization to reconstruct the same facts next cycle. |
Start by locating the executed agreement and identifying the actual notice mechanics. Then work backward from the renewal date to organize usage, forward demand, commercial objectives, stakeholder approvals and supplier conversations. A 120-day runway is useful because it creates working time; it does not override the contract.
Calculate planning checkpointsFor a material or business-critical agreement, 120 days before expiration is a useful planning target when the contract timeline allows it. The purpose is to create enough runway for contract review, usage analysis, stakeholder alignment and commercial preparation. Actual notice and renewal obligations are controlled by the executed agreement, order forms and amendments.
A SaaS renewal notice period is a contractual window that may require a buyer to communicate a renewal, non-renewal or other specified action before the current term ends. The required timing, permitted method and legal effect vary by agreement. Buyers should verify the executed contract and involve counsel where legal interpretation is required.
Around 90 days before a material renewal, teams should validate active users, utilization, product tiers, commitments and forward demand; identify the people who own requirements and approvals; and confirm the exact contractual notice mechanics. The goal is to understand what the business needs before supplier discussions accelerate.
A buyer position is the documented commercial stance the organization intends to carry into a supplier discussion. It typically combines verified current usage, forward requirements, existing contract economics, prior negotiated terms, approval boundaries, requested changes and acceptable concessions. The client retains final decision authority.
No. This is an operational planning framework for commercial preparation. The executed agreement controls actual rights and obligations, and the client’s legal counsel should confirm legal notice requirements and final contract language.
Calder can review the timeline, current commitment, rightsizing questions and buyer position while your team retains final authority.
Discuss a renewal