A 90-day renewal playbook for annual SaaS contracts

An annual contract renews once a year, which means a customer only has to decide to leave once. If your team first hears about doubts a week before the end date, it is usually too late. A renewal playbook is a fixed sequence of steps that starts 90 days before each contract ends. It fits B2B and SaaS companies selling annual plans, from a handful of accounts to several hundred.

Why it works

Renewal decisions are made long before the paperwork. Budgets get set, competitors get evaluated, and champions change jobs months ahead. Starting early gives you time to fix problems, prove value and handle procurement steps that take weeks. It also stops renewals from piling up in the last days of a quarter, when your team is stretched and the customer holds all the leverage.

A written playbook also makes outcomes consistent. Every account gets the same checks and the same timeline, so you can spot where renewals stall and fix the process.

How to do it

1. Build a renewal calendar. Pull every contract end date into your CRM with an owner, the current contract value and notice period. Create a task 90 days ahead for each one.
2. Score health at day -90. Look at usage trends, active users against licences, support tickets, survey responses and champion changes. Label each renewal as safe, at risk or in danger.
3. Hold a value review. Meet the sponsor to recap results against their goals and ask about plans for next year. Listen for budget cuts, reorganisations or new tools.
4. Send the proposal around day -60. Lay out the renewal price, any changes in seats or plan, and two or three options such as a multi-year term. Explain any price change clearly.
5. Map the approval path. Ask who signs, what procurement needs, and whether security or legal will review. Send documents before they ask.
6. Run a weekly renewal review. Go through every open renewal in the next 90 days as a team. Agree a next step for each at-risk account.
7. Escalate by day -30. If a renewal is stalled, bring in an executive on your side to speak with theirs.
8. Close and log the outcome. Record the result, the final price, and the reason for any churn or downgrade. Review those reasons each quarter.

Example

A hypothetical marketing analytics platform loses several mid-sized accounts in one quarter, each discovered only when the customer declined to pay the new invoice. The team introduces a 90-day playbook. At day -90, one account shows that only a third of licensed seats are active and the original champion has left. The success manager books a meeting with the new marketing director, runs a training session for the team, and proposes renewing at a smaller seat count with an option to add seats mid-year. The customer renews, and the team adds “champion left” as a standard health flag.

Metrics to track

• Gross revenue retention. Revenue kept from renewing contracts, excluding upsells. This is the main outcome the playbook should protect.
• On-time renewal rate. The share of renewals signed before the contract end date.
• Renewals flagged early. The share of eventual churn or downgrades that were marked at risk at day -90. A high share means your health score works.
• Average days to close. Time from proposal to signature. Rising numbers point to procurement or pricing friction.
• Churn reasons. The count of lost renewals by reason, reviewed quarterly.

When it backfires

• Starting with the invoice. If the first renewal touch is a bill, the customer feels like a number. Lead with a value review.
• Hidden price rises. Surprising a customer with a higher price in the proposal invites a competitor evaluation. Flag changes in the value review.
• One-size timelines. Applying 90 days to a customer with a six-month procurement process leaves you short. Ask how they buy.
• Discounting by habit. Cutting price on every renewal trains customers to push back each year.
• Ignoring safe accounts. Accounts labelled safe still need a value review. Champions leave and budgets change with little warning.

Questions people ask

Who should own renewals, sales or customer success?

Either can work. What matters is that one named person owns each renewal date and its outcome. Many teams let customer success own standard renewals and bring in an account executive when there is a large upsell or a pricing change.

Is 90 days enough for large enterprise accounts?

Large customers with formal procurement may need 120 days or more, especially if security or legal reviews are involved. Ask early how long their approval process takes and start the clock from there.

Should we offer a discount to secure the renewal?

Avoid making discounts the default. Offer a multi-year term or prepayment in exchange for any price concession, and keep a record of what you gave so the next renewal does not start from a lower base by accident.