How Do I Do Renewal Call Preparation in 30 Minutes?

Preparation is not reading everything about the account. It is answering four questions well enough to run the call: Will they renew? At what price and term? What will they ask for? And what did the product do for them, in a unit they use? Everything you pull should feed one of those. The wider process, from the 120-day mark to signature, is covered in SaaS renewal management; this page is the account review inside it.

The problem most CSMs describe is not a lack of data but its spread. Of 3,628 public G2 reviews of the three most-reviewed customer success platforms, 296 mention renewals and 531 describe the job as getting customer data into one place. Only 3 mention being prepared for a meeting. People buy the single view and still assemble the renewal picture by hand.

The 30-minute review works only if the account has been looked at before. A first look two weeks out leaves no time to fix what you find. The reviewers in our corpus who described their renewals as calm all did the same thing: alerts at fixed distances from the date, with a different job at each one.

1. 1

   90 days out: the risk read

   Ten minutes. Check usage trend by user, open escalations and whether the sponsor is still in post. If any of the three is wrong, this account moves to the top of the list now, while there is time to act. If all three are fine, note it and move on.

2. 2

   60 days out: the commercial read

   Fifteen minutes. Read the contract: term, price, uplift clause, notice period, auto-renew. Check billing for late payments, seat count against licensed count, and any downgrade in the last year. Decide what you will propose (flat, uplift, expansion) and what you will not concede.

3. 3

   30 days out: the full 30-minute review

   The checklist below. Produce the rating, the one number and the five questions. Book the call with the decision-maker on the invite, not only the champion.

4. 4

   Day before: the refresh

   Five minutes. Re-check tickets opened since the review, any usage change in the last week, and whether the sponsor has replied to anything. Update the rating if needed. Send a two-line agenda so the customer knows this is the renewal conversation.

Six sources, in the order that lets each one explain the next. Contract first because it sets what is possible. Billing second because money tells the truth before people do. Product third because it is the hardest to see and the most predictive. Support, CRM and your own history round out the picture.

The product column is where most renewals are lost and most preparation is thinnest. Account-level totals are not enough. A flat total can be one power user doing everything while the eight people who were trained have gone. Pull it by name, and compare it with the list of people who attended training. The scattered-data early warning page covers how to read each of these sources as a signal, months before the renewal.

Run it in this order with a timer. The minutes are generous for an account you know and tight for one you inherited; if you inherited it, take 45 the first time and 30 after. Write answers as single sentences in one note. That note is the brief for your manager, the renewals team, and your future self.

A reviewer in our corpus described the effect of having this in one place as feeling more prepared for meetings because of a single view of the customer: when the renewal date is, what adoption looks like, previous notes. That is the whole job of the checklist. The single view is what you are building by hand.

The example is red on the evidence, and the prep turned a surprise cancellation into a smaller, defended renewal with a path back to expansion. That trade is worth making. Before the call, put the renewal amount through the cost of churn calculator to see what the account is worth over three years; it changes what you are willing to give to keep it.

The rating is not a health score. It is a call-planning decision, and it has a simple rule. Green means usage is flat or up by user, the sponsor is in post and has spoken to you in the last quarter, no escalation is open, and payments are on time. Yellow means one of those is wrong. Red means two or more are wrong, or the sponsor has left, whatever else looks fine.

The sponsor rule is deliberate. A thread in our Reddit set asked whether executive trust matters when usage is strong and the product is delivering, and the replies described exactly the case in the worked example: everything green except the person who signs, and the renewal still at risk. If the decision-maker has changed and you have not met them, the account is red until you have.

The rating sets the agenda. Green calls are about the next 12 months and expansion. Yellow calls open with the one thing that is wrong, fix it or commit to a date, then move to renewal terms. Red calls are not renewal calls yet; they are recovery calls, and the renewal terms wait until the recovery has a named owner and a date. If a red account has also stopped replying, the re-engagement playbook comes before this checklist.

Preparation ends with questions, not slides. A renewal call run from a deck is a presentation the customer sits through; a renewal call run from five questions is a conversation the customer leads. The questions are the same shape every time and the content comes from the checklist.

1. What has changed on your side since we last spoke? (Asked first, before anything about the product, because the answer usually contains the real agenda.)
2. Here is what we see in the data (the one number and the usage trend). Does that match how the team experiences it?
3. Here is what we said the product was for at kickoff (the line from the deal notes). Is that still the job, or has it moved?
4. What would make the next 12 months clearly worth it to the person who signs?
5. What do you need from us to make that true, and by when?

Do not open with the price. Do not present features that shipped as if they were achievements; ask whether they were used. Do not ask "are you happy?", which gets a polite yes and no information. And do not finish without writing down owned next steps with dates, because that note is also the evidence trail that leadership increasingly asks CSMs to produce for their part in the renewal.

At 40 renewals, 30 minutes each is 20 hours a quarter, which is affordable. The problem is the 90-day and 60-day passes, which triple it. The fix is to run the early passes as a list, not as accounts: one usage report by user for every renewal in the window, sorted by trend; one support export for the same accounts; one CRM report of sponsor changes. Twenty minutes gives the risk read for all 40, and the full 30-minute review is then spent only on the yellow and red ones and on the green ones above a size you set.

That size line is the same tiering decision covered in the 150-accounts-per-CSM coverage model. Below the line, the renewal is an email with the one number and the terms, and the call happens only if the customer asks or the data is yellow. Above it, every account gets the full routine.

The routine matters more than the tooling. The CSMs who describe calm renewal seasons in our corpus are not the ones with the most dashboards. They are the ones who look at the same six things at the same three distances from the date, every time, and write one note.

GainTrace builds the six-view brief for every renewal in the window from your billing, product, support and CRM data, with usage by named user and the sponsor change already flagged, so the 30 minutes goes on the questions instead of the pulling. Revenue analytics shows the renewal book by date, amount and rating, and rescue playbooks start the recovery on the red accounts at 90 days, when there is still time.