Renewal prep checklist: what to do at 90, 60 and 30 days
A renewal prep checklist for the 90, 60, and 30 days before a B2B SaaS renewal. Check usage, people, support, billing, and the next-term plan.
A renewal prep checklist for the 90, 60, and 30 days before a B2B SaaS renewal. Check usage, people, support, billing, and the next-term plan.
A renewal prep checklist is a dated set of checks a CSM or founder runs at 90, 60, and 30 days before a B2B SaaS renewal. At 90 days, record the usage trend, champion changes, and support pattern. At 60 days, confirm billing and seats, finish the stakeholder map, and draft the value recap. At 30 days, choose an expansion path or a risk plan, and book the decision.
The note that says they are not renewing, twelve days before the contract ends, is rarely a surprise to the customer. It is a surprise to you. On an annual contract they decide once. If the first serious look is the week you send the quote, you are closing a conversation that never started.
This 90/60/30 renewal playbook is that read of the account before the quote goes out. Ninety days is time to find a departed champion. Thirty days confirms the decision.
SaaS Capital's 2026 benchmarks for bootstrapped SaaS companies report this median from the firm's annual survey of more than 1,000 private B2B SaaS companies. The group is bootstrapped companies with $3 million to $20 million in annual recurring revenue. Gross revenue retention counts revenue kept from those same customers and ignores expansion. That 91% describes the peer group. It is not a forecast for your book.
A renewal prep checklist is one row per upcoming renewal, with a named owner and a latest date for each check. It is finished when you can say what changed, who can approve the spend, what the customer got, and what you will ask for next.
| Latest date | Job | Checks |
|---|---|---|
| 90 days | Read the account | Usage trend, champion and contact changes, support pattern |
| 60 days | Make the case | Billing and seat changes, stakeholder map, value recap |
| 30 days | Choose the path | Expansion plan or risk plan, then the decision meeting |
A renewal checklist that lives in someone's head is a rumor. One spreadsheet row per account, with a date in each finished cell, is enough at 50 to 500 accounts.
Do this week: export every renewal in the next 120 days from billing and sort by date. For anything already inside 90 days, start the 90-day checks today. Month-to-month customers have no 90-day date, so run the same checks every month, and again before you offer an annual plan.
At 90 days, write down what the account is doing, who still works there, and whether support went quiet because things work or because people stopped asking.
Compare the last 30 days with the prior 30 days on that account. Use active people, or the one action that means they got what they bought. Write the direction and the size. "Active people fell from 18 to 9" is a trend. "Down" is not. A drop against that 30-day average is a question.
12 early warning signs a customer is about to churn treats a drop of more than 30 percent against the account's own 30-day average as a starting flag. Use it as a prompt to look. On the same export, note whether new teammates are still being invited and whether the admin still shows up.
A champion is the person who wanted the product in place and who still replies. Record the name, the last reply date, and whether they still work there. A CRM contact who left in the spring is the renewal risk.
Also note a new manager, finance contact, or admin. The person you email still has to be able to move the renewal.
Pull this term's tickets and write what is still open, what was reopened, and whether the same problem appears twice. One how-to question is not a pattern. The same broken workflow in March and August is. Read one ticket before you summarize it: a bug needs a fix date, and silence after several how-to tickets means they may have stopped trying.
Day 60 turns the read into a billing note, a stakeholder map, and a value recap the customer can react to.
From the billing record, write down:
Example, with made-up numbers only, not a customer result: 20 seats paid and 11 people active is an unused-seat conversation. More active people than paid seats is an expansion fact. Write the figures.
A failed payment needs a direct way to update the card. Keep that separate from a note about a departed champion.
A stakeholder map is the short list of people who can change this renewal. Four roles are enough:
| Role | The question it answers |
|---|---|
| Champion | Who wants this renewal to succeed inside the account? |
| Admin | Who uses the product often enough to know if it works? |
| Economic buyer | Who can approve the spend? |
| Blocker | Who can stall the renewal, and what would stall it? |
An economic buyer can approve the invoice. At many smaller accounts that person is the founder or the champion, sometimes both. Every role needs a name and a last-contact date, or the word "unknown", with a date to fill it. If the only person on the map leaves at day 70, you still have time to ask who replaced them.
A value recap is the term in the customer's language, short enough to read aloud in about three minutes:
Send that note. Leave out any "hours saved" figure you cannot source from their account.
If a day-90 check failed, send the specific note in this window. The save email templates time a renewal-risk note at 45 to 60 days, and they tell you to name the signal. Name the drop, the open issue, or the missing champion. Then ask for one next step.
Day 30 is the decision meeting. The champion has seen the value recap, and any broken workflow from day 60 has an owner and a date.
An expansion plan is for a clean checklist: one offer tied to a fact on the sheet, such as a second team already in the product or more active people than paid seats.
A risk plan is for a failed check. Write the check, who you will talk to, the date, and a fallback: a shorter term, a smaller plan, or a pause while a fix ships. A smaller renewal you both accept is a cleaner record than a silent cancellation. Do not hide an unnamed problem behind a discount.
Meet the economic buyer with the champion if the buyer will attend. If not, the champion needs the ask and the fallback before they carry it inside their company. Send the recap ahead so the meeting corrects it.
Four beats are enough:
The same day, you should be able to tell your team what changed, who decides, what the customer got, and what you asked for. "We will circle back" is not a finished check. Write the open item and a date.
Match the action to the check. A usage drop gets a question about what changed. A departed champion gets a new name before any talk of price. A repeated support issue gets a fix date. A failed payment gets a way to update the card. "Just checking in" hands the diagnosis back to the customer.
Churn prediction for B2B SaaS: the complete guide shows how to put a reason next to an account and act on that reason. This checklist is that habit with dates. When several accounts renew in one month, sort by contract value and by how many checks failed. Start with the larger accounts that failed more than one check.
Name one owner. Where the founder still runs customer success, that owner is the founder. Each week they open renewals inside 90 days and fill the empty cells from billing, product analytics, the support desk, and the CRM.
When that read is too slow by hand, the questions do not change: which renewals need a person, what changed, and what the meeting should say. ChurnAI is customer intelligence for B2B SaaS, delivered through MCP in a compatible AI workspace, with the source evidence attached. MCP (Model Context Protocol) lets that workspace request customer context and receive an answer. A CSM can ask for account priorities, a meeting brief, or a follow-up draft grounded in product, billing, support, and CRM data, and review the draft before anyone sends it.
The free Pilot lasts 30 days, includes 200 profiles, and connects one source: Chargebee or Amplitude. During the Pilot, imported data is stored in ChurnAI Cloud. On paid plans, connected data is stored in the customer's cloud. In both cases ChurnAI processes the context an authorized request needs and returns it to the workspace you selected. Setup time depends on the source and on what you need to check.
Seven steps in ROI order, from fixing failed payments to running save calls, all doable this week in Stripe, your support desk, and your analytics.
Four copy-paste save email templates for usage drops, stuck tickets, renewal risk, and failed payments, plus timing rules and what to do when they reply.