The SaaS Renewal Timeline Every Company Should Follow
What finance, IT, and procurement should actually be reviewing at 180, 90, and 30 days before a SaaS contract renews, and why the timing itself is the leverage.
I spent years on the vendor side of enterprise software, and the single biggest differentiator between accounts that negotiated well and accounts that didn't wasn't sophistication, it was timing. Every tactic in a negotiation only works if there's still time left to use it. This guide lays out the timeline that actually preserves that time.
The renewal timeline
- 180 days: visibility
- 90 days: build the case
- 30 days: open the conversation
- Notice deadline
- Renewal date
Facts, not decisions
- Exact dates from the contract
- Usage, not seat count
- Named relationship owner
Build the case
- Right-size on usage
- One alternative quote
- Documented service issues
Negotiate from strength
- Reach out first
- Ask for a breakdown
- Get it in writing
Why the timeline matters more than the tactics
A notice period is, functionally, a deadline for your options, not just your obligations. Most companies structure their renewal attention around the renewal date itself, which is almost always the wrong anchor. By the time the renewal date is close, the notice period, the one date that actually determines whether you have choices left, has usually already passed.
180 days: visibility, not action
At six months out, the job is simply to know what you're dealing with:
- Confirm the exact renewal date and the exact notice period from the actual contract
- Confirm current usage, not seat count
- Confirm who owns the relationship
- Flag whether this renewal is significant enough to warrant deeper preparation
Nothing here requires a decision yet. It requires facts, and facts have a shelf life, they need to be current, not from the last time someone happened to look.
90 days: build the case
At three months out, turn the facts from 180 days into an actual position:
- Right-size based on usage
- Get at least a rough quote from one alternative, even if switching isn't the goal
- Document any service issues from the past year
- Decide internally what outcome you're actually aiming for
30 days: negotiate from strength, not from urgency
At one month out, you should already be initiating the conversation, not waiting for the vendor's notice to arrive:
- Reach out first, with your case already built
- Ask for a breakdown of any proposed changes
- Confirm, one more time, that the notice period hasn't already closed
- Get anything agreed in writing before the renewal date fires
Why compressing this timeline doesn't work
I watched plenty of teams try to run this entire process in the two or three weeks before a renewal. It's possible to gather some of the facts that fast. It's not possible to seriously evaluate an alternative, right-size based on real usage confirmation, and negotiate from a position of strength, all inside a notice window that's already closing. Compressed timelines don't produce worse tactics, they produce no real leverage at all, regardless of how the tactics are executed.