The 90-Day SaaS Renewal Checklist Finance Teams Actually Use

Why renewals are different from new purchases

A new SaaS purchase is a buyer's market: the vendor is competing for your attention, the procurement window is open-ended, and the AE has full discretion to discount. A renewal is a seller's market by default. The vendor knows your usage, your champion, your migration cost, and (if there's an auto-renewal clause) your decision deadline. Time is the single largest source of buyer leverage in a renewal — every week of runway widens the asymmetry. The 90-day checklist exists because that's roughly the window required to flip the leverage back: long enough to commission a real alternative quote, short enough to keep the work focused.

There's also an organizational dynamic. Most renewal failures aren't negotiation failures, they're handoff failures: the contract owner doesn't see the renewal email; the renewal email goes to a finance group inbox that nobody owns; legal review starts inside the notice window; the AE's manager isn't looped in until the last 48 hours. The 90-day cadence builds in handoff buffer at every step.

Definitions: terms you'll see in renewal docs

• ACV (Annual Contract Value): the dollar value of one year of the contract. Used as the headline number, but never the only number worth optimizing.
• TCV (Total Contract Value): ACV × term length. Multi-year deals trade ACV reductions for TCV commitments — sometimes a good trade, sometimes not.
• Net Retention: the metric your AE is measured on. Hitting it requires either expansion or holding price. This is why the AE pushes back on cuts.
• MFN (Most-Favored-Nation): a clause requiring the vendor to give you their best terms offered to comparable customers. Rare to win, but valuable as a trade chip.
• TFC (Termination for Convenience): the right to exit the contract early without cause. Almost never present by default; valuable enough to redline in.
• Auto-renewal trigger: the date by which you must give written notice of non-renewal. Typically 30–90 days before term end. Missing this date is the most expensive mistake in SaaS procurement.

If you wait until the renewal email lands in your inbox, you've already lost. By the time most SaaS contracts surface — usually 30 days out, sometimes less — the only lever you have left is whether to sign. The work that actually moves price, term, and protection happens in the 60 days before that. This is the checklist we run for every renewal at RenewalPad, and the one we recommend to finance teams managing $250K–$10M of annual software spend.

We've codified this from running renewal motions for ~140 mid-market companies between 2023 and 2025. The pattern is unambiguous: companies that start renewal work at T-90 days hit a median 16% effective reduction across negotiated lines. Companies that start at T-30 days hit 4%. Companies that miss the notice window land between 0% and a 7% increase. The runway is the variable that matters most.

Why the 90-day window matters

Three things compound the longer you wait: information asymmetry (the vendor knows your usage, you don't know their pricing floor), switching cost optics (a 30-day window makes 'just renew' the only practical option), and auto-renewal language. The 90-day window is the minimum runway to gather evidence, model alternatives, and write a counter-offer the other side has time to actually negotiate.

Day 90: discovery and evidence

1. Pull the executed contract, the order form, and any side letters. Identify the auto-renewal window and notice period — these are usually buried in section 9 or 10.
2. Export 12 months of usage: monthly active users, seat assignments, login frequency, and any consumption-based metrics (API calls, storage, GB ingested).
3. Map seats to your IdP (Okta, Google Workspace, Entra) and reconcile against HRIS to identify departed employees who still have licenses assigned.
4. Pull the last 12 months of invoices from your AP system. Note any mid-term true-ups, overage charges, or seat additions.
5. Identify the executive sponsor inside your company and the account team at the vendor. You will need both.

Day 60: benchmarks and alternatives

This is the phase that creates leverage. Without a credible alternative — even one you don't intend to use — the vendor has no reason to move price. Three sources of benchmark data we use:

• Anonymized peer pricing from a SaaS management platform (median per-seat at your size band).
• Direct quotes from 1–2 functional alternatives, even if migration is unrealistic. The quote is the leverage; the migration is optional.
• Public pricing pages for the same vendor in adjacent geographies — often 10–20% lower than your enterprise contract.

Day 30: counter-offer and term sheet

The counter-offer should be written, dollar-specific, and reference your evidence. The structure we use:

1. One-paragraph summary of the relationship (length, expansion, current ACV).
2. Three numbered asks, each with a one-line justification: per-seat price, seat count adjustment, and one structural protection (price cap, MFN, opt-out clause, or 18-month term).
3. A clear walk-away: 'If we cannot land here by [date], we will not be renewing in the current configuration.' Mean it.
4. An offered close date 14 days before the auto-renewal trigger.

Day 15: escalation and close

If you're past day 15 without movement, escalate inside the vendor — usually the AE's manager or the regional VP of sales. The right framing isn't adversarial: 'We want to renew. The current pricing won't clear our finance committee. Here's what does.' Most vendors have meaningful pricing discretion that only unlocks at the manager level.

Common mistakes

• Negotiating on per-seat price only. Term length, payment cadence, and price-cap language often save more than the rate.
• Letting auto-renewal trigger because the notice period was missed. Calendar this the day you sign, not the day you renew.
• Negotiating with the AE only. The AE has commission incentives that don't always align with yours.
• Skipping the walk-away. Every concession you've ever received was because the vendor believed you'd leave.
• Treating the contract as one number. Total Cost of Ownership rolls up per-seat rate × seat count × term, plus implementation, plus exit cost. Optimize the surface, not the headline.
• Sending the counter from a procurement-only email. Vendor account teams discount procurement-only emails as performative. Send from the tool owner with finance and procurement copied.

Anti-patterns we see

• Starting at T-30 with no benchmark, no alternative, and no calendar. The renewal will close at quoted price ± 3%.
• Outsourcing the negotiation to the AE without an internal counter-offer drafted. The AE will optimize for their commission, not yours.
• Treating every vendor the same. A $40K observability tool with three credible alternatives gets a different motion than a $400K Salesforce contract with no realistic switching path.
• Confusing 'we negotiated' with 'we got the best deal.' A 6% reduction off a 12% increase quote is still a 5% real increase. Anchor on prior-year cost, not on the renewal quote.

A worked example

A 280-person fintech we worked with had a $186K Salesforce Sales Cloud Enterprise renewal landing in March 2025. Original quote from the vendor: $214K, reflecting a 15% list increase plus 20 additional seats the AE pre-loaded. Here's how the 90-day cadence played out.

The 33% reduction is at the high end of what's achievable; the median across our customer base on first-cycle Salesforce renegotiations is closer to 17%. But the structural wins — the seat-count reset, the price cap, the term length — compound across cycles and were worth more than the headline number.

Sources and further reading

• Vendr 2024 SaaS Trends Report — median enterprise discount rates by category.
• Bessemer State of the Cloud — long-running benchmarks on net retention and seat-expansion behavior at SaaS vendors.
• Gartner CIO Survey 2024 — software spend growth and renewal pressure trends at mid-market.
• Internal RenewalPad data: 142 customer renewals between Q1 2023 and Q4 2025, anonymized.

Frequently asked questions