Renewal Timeline: A 120-Day Checklist for SaaS CS Teams

Most renewals are not lost in the final negotiation. They are lost weeks earlier, when nobody noticed usage sliding or a champion leaving. This guide gives you a renewal timeline you can copy: what to do at 120, 90, 60, 45, 30, 14 and 7 days before the contract ends, who owns each step, and how to adjust it for account size and health.

Why a renewal timeline matters

One renewal-operations guide from Octave argues that the typical renewal process starts 30 to 60 days before contract end, which it calls far too late. Its reasoning: if you are still having strategic value conversations at T-30, the problems started upstream, and the close should be mostly administrative.

A second guide, the Rework renewal playbook, recommends starting internal preparation 120 to 90 days out and customer engagement at about 60 days. Treat these day counts as widely used conventions from vendor-written guides, not industry standards. The principle is what matters: leave enough time to fix problems, document value and negotiate without deadline pressure.

The renewal timeline at a glance

Use "T-" to mean days before the renewal date.

The phases above follow the milestones in the Rework playbook.

Step 1: Build one renewal calendar (T-120)

You cannot work a renewal you do not know is coming. Create a single list of every contract with these fields:

• Renewal date and notice period
• Annual contract value (ARR)
• Renewal owner
• Auto-renew or manual
• Price or term restrictions

Audit it every quarter. Octave suggests flagging end dates that are missing, already past, or more than 36 months out, since those are usually data-entry mistakes. A spreadsheet works for a small book of business; once you pass a few dozen accounts, you want dates, owners and alerts in the same system as the rest of your customer data.

Step 2: Run the internal readiness review (T-120 to T-90)

This is the most valuable step and the one customers never see. Before contacting anyone, answer these questions for each account:

1. Is usage rising, flat or falling over the last 90 days?
2. Did the customer reach the outcome they bought the product for? Can you prove it with data?
3. Who is the champion, the economic buyer and the day-to-day users? Has anyone changed role or left?
4. What is open: support tickets, unresolved feature requests, late invoices, a bad survey response?
5. Is there an expansion opportunity, or a reason there is not?

The Rework playbook also recommends verifying health with a fresh look at usage trends, recent conversations, goal progress and stakeholder changes rather than trusting a score from last quarter.

Spend effort according to risk. The same guide suggests red accounts may need renewal work starting around 180 days out, and enterprise deals can run 150 days or more, while small-business renewals may compress to 30 to 60 days. Calibrate these to your own sales cycle.

Copyable template: renewal brief

Account:
Renewal date / ARR / owner:
Health: Healthy / At Risk / Critical  (why, in one sentence)
Usage trend (90 days):
Goals the customer bought us for, and progress:
Champion / economic buyer / other stakeholders (status of each):
Open issues (tickets, invoices, feedback):
Value delivered (3 concrete, measurable points):
Risks and owners:
Expansion opportunity (or reason none):
Renewal strategy (flat, uplift, multi-year, downgrade):
Next action and date:

Keep it to one page. If you cannot fill in a line, that gap is your first task.

Step 3: Hold an internal kickoff (T-90)

Spend 20 to 30 minutes with the CSM, their manager and, for larger accounts, sales or an executive sponsor. Review the brief, agree the strategy and assign owners to every risk. For any risk, write the action, the owner and the date it will be verified. "Improve the relationship" is not an action; "CSM books a call with the new VP of Operations by the 15th" is.

Step 4: Open the conversation with a value review (T-60)

Send the renewal notice to the champion and the economic buyer, and book a value review meeting. This is not a sales pitch. Cover:

• What you set out to achieve together
• What the data shows (usage, outcomes, support history)
• What the customer wants to achieve next year
• The renewal process and rough timing

Float preliminary terms here so the proposal contains no surprises. Octave's advice applies: if value is still being debated at T-30, you started too late.

Step 5: Send the proposal and negotiate (T-45 to T-30)

Build a short proposal: executive summary, value delivered, terms and pricing, any expansion option, next steps. Get internal approvals before it goes out. Present it in a meeting, not just by email, and agree a concrete decision date.

Price changes are a common sticking point. The Rework playbook cites an annual increase of 3 to 10 percent and a 10 to 20 percent discount for two- to three-year commitments as typical market figures, though it gives no underlying source for them, so check them against your own deals before using them as targets.

Step 6: Finalize and close (T-14 to T-0)

• Generate the contract and get legal review early.
• Make signing easy: e-signature, clear instructions, named contacts.
• Confirm payment method, invoicing and purchase-order requirements.
• Follow up every 2 to 3 days while the contract is out, and daily in the final week.
• Escalate to executives only if the renewal is truly stuck.

Step 7: Close the loop (T+0)

After signature, record the final terms and next renewal date, thank the champion, note what you learned, and open the expansion conversation. This is also when next year's timeline starts.

Who should own the renewal?

Octave suggests a simple ownership rule of thumb by account size: customer success can usually own renewals below $50K ARR, a dedicated renewal manager fits the $50K to $200K range, and above $200K a senior account owner should lead. These thresholds are the author's suggestion, so adjust them to your team. Whatever you choose, name exactly one owner per renewal.

Handling at-risk renewals

When the T-90 review turns up trouble, match the response to the cause:

• Usage decline: run a re-engagement plan with a specific adoption target.
• Champion left: find the new owner of the problem and rebuild the relationship before the renewal conversation.
• Support frustration: resolve the open issues and show the customer the fix before discussing price.
• Budget pressure: show measurable value, then consider a smaller scope rather than losing the account.

Give each plan one owner and a date to check whether it worked. For more on spotting these signals early, see our post on why your customer success team needs its own CRM.

Renewal timeline checklist

• Every contract is on one calendar with date, owner and ARR
• Internal review done by T-90 using the renewal brief
• Internal kickoff held; every risk has an owner and a date
• Renewal notice and value review done by T-60
• Proposal approved internally and sent by T-45
• Proposal presented live and decision date agreed by T-30
• Contract out for signature by T-14
• Final terms, next date and lessons recorded at T+0

Try it in XPI CRM

In XPI CRM, renewals live on a board with stage probabilities and a forecast, and a playbook can start automatically a set number of days before the renewal date, creating the tasks above for the right owner. Marking a renewal Won updates the client's ARR, and the health score and alerts show which accounts need attention before the conversation starts. You can adapt the timeline in this guide to your own team. Start free — every feature included, no credit card, or browse the help guides first.