The SaaS Renewal Preparation Checklist
What to actually check at 180, 90, and 30 days out, built from watching hundreds of renewals from the vendor's side of the table.
The accounts that negotiate well are rarely the ones with the sharpest negotiator on the call. They're the ones who did a specific, unglamorous set of homework before the call ever happened. This checklist is that homework, organized by how much runway you have left.
Picture two accounts heading into the same renewal. One shows up with a spreadsheet showing exactly which departments are using the tool, how usage trended over the year, and two competitor quotes already in hand. The vendor has almost no room to maneuver on that call, and knows it before the call starts. The other account shows up with none of that, and the room to maneuver runs entirely the other way. This checklist exists so yours looks like the first one. A shared renewal tracker with notice deadlines keeps these dates visible to every owner.
180 days out: find out what you're actually dealing with
At six months, the goal is simply to know the facts, not to negotiate yet.
- Locate the actual contract, not the invoice, and confirm the renewal date and the notice period
- Confirm who owns the relationship internally, and if nobody clearly does, assign someone now
- Pull real usage data: active users in the last 90 days, not seats purchased
- Note any price escalator clause and what index or list price it's tied to
- Flag whether this renewal is large enough to warrant evaluating an alternative vendor
If you only do one thing at this stage, find the notice period. It's the one date that, if missed, removes every other option below.
90 days out: build your position
- Right-size the seat count based on the usage data from the 180-day step
- If usage is light or the spend is significant, identify at least one credible alternative and get a rough quote, even if you don't intend to switch
- Document any service issues, support delays, or unmet commitments from the current vendor, they're legitimate negotiation points
- Decide internally what outcome you actually want: lower price, better terms, reduced seats, or a genuine intent to leave
- Loop in whoever approves the budget so there's no last-minute approval bottleneck later
30 days out: open the conversation from strength
At one month, you should be initiating the renewal conversation, not reacting to the vendor's notice.
- Reach out to the account team first, with your usage data and, if relevant, your alternative in hand
- Ask directly for a breakdown of any proposed increase rather than accepting a single bundled number
- Confirm the notice period hasn't already passed before you finalize anything, this is the last checkpoint
- Get any agreed changes in writing before the renewal date, verbal agreements on a call don't hold if the auto-renewal clause fires first
- Once the terms are settled, update your internal record: new terms, new notice period, any change to the escalator clause
Then close the loop properly. Note anything you'd do differently next cycle while it's still fresh, and reset the 180-day clock immediately rather than waiting for the next invoice to remind you that the whole process starts again.
Once this evidence is complete, the SaaS renewal playbook for buyers shows how to turn it into an approved opening, target, fallback and walk-away point.
Common questions
Keep reading
What finance, IT, and procurement should review at 180, 90, and 30 days before a SaaS contract renews, and why the timing itself is the leverage.
In-depth GuideThe SaaS Renewal Playbook: A Step-by-Step Guide for BuyersA complete buyer-side SaaS renewal playbook with nine steps, decision and negotiation templates, a worked example and closing checklist.