Keep terms
The capability is needed, usage is healthy, and the commercial position is acceptable.
Renewal discipline
Treat every renewal as a decision.
Bring usage, terms, timing, and alternatives together before the notice window closes.
Primary decision: Renegotiate.
Renegotiate
Use renewal timing, usage evidence, plan rightsizing, terms, caps, and credible alternatives to improve the deal.
Reduce or cut
Lower seats, remove add-ons, terminate unused products, or exit where the business job no longer exists.
Replace
Only if a viable alternative clears net economics and operational risk before the notice window closes.
AI-bundled uplifts
If the hike is packaged as AI, decide that line first.
Notice windows still govern timing. They do not tell you whether to accept a forced AI SKU, metered credits, or an outcome fee. Use the AI tax at SaaS renewals playbook to Keep, Cut, Renegotiate, or Replace the AI-tied spend.
Seat count at renewal
If last year's seats are the opening number, decide that line next.
Notice windows still govern timing. They do not tell you whether you can cut unused seats without a penalty. Use the true-up vs true-down playbook to rightsize at renewal or negotiate true-down rights when the paper is true-up-only. Use renewal usage evidence without a platform to assemble unused-seat proof from invoices, SSO, and admin exports before the window closes.
Packaging and SKU changes
If the quote is a new SKU, the notice window still governs timing.
Notice windows do not tell you whether a price cap survives a rename, a retired tier, or forced packaging. Use the forced SKU migration playbook for successor-SKU and as-is-path asks. Missing the window can lock the migration path.
Annual increase ceiling
If the fight is the rate, the notice window still governs timing.
Notice windows do not tell you how to choose a written uplift or escalation cap, or what to do if the paper is silent. Use the price uplift / escalation caps playbook to lock an annual renewal increase ceiling. Missing the window can lock an uncapped rate.
Middle and tail of the queue
If the top of the calendar has coverage, staff the rest next.
Notice windows still govern timing. They do not tell you who owns the middle and tail when a negotiation platform or SMP only absorbs the top. Use the mid-list renewal queue playbook to tier the calendar, name owners, and require Keep / Cut / Renegotiate / Replace before notice.
FP&A cost forecast
If finance still has no dollar view of the next 12 months, forecast next.
Notice windows still govern timing. They do not tell you what the next year of renewals will cost. Use the FP&A SaaS renewal cost forecast playbook to model uplift, seat change, and forecast-versus-actual variance before the invoice.
Committed obligation register
If finance still answers obligation from invoices, build the register next.
Notice windows still govern timing. They do not tell you committed value, notice deadline, and owner on one row. Use the SaaS renewal liability schedule playbook so decisions happen before notice, not after the invoice.
Notice of non-renewal
If the decision is framed and the window is still open, send next.
Notice windows still govern timing. They do not tell you how to draft the letter, where to deliver it, or what counts as proof. Use the SaaS notice of non-renewal playbook to send valid notice without closing renegotiation.
Review the renewal before it decides for you.
Bring the date, usage, and contract. We’ll help frame the decision.