How to Prepare for a Renewal Call From Past Conversations (2027)

A CSM joins a renewal call with the account summary and the contract value. Nothing else. Five minutes in, the customer says: "We've raised the export bug three times." The champion who signed last year isn't on the invite and hasn't answered email in two months.

None of this was secret. It sat in three call recordings, two Zendesk tickets, a Slack thread and an AE's notes. Nobody pulled it together before the call. At BuildBetter, this is the renewal story we hear most often from CS teams: the record existed, but no one read it as a whole.

This guide covers five things. It defines renewal call preparation. It lays out a 60-day method you can run on a spreadsheet. It walks through one worked example with real numbers, lists the mistakes that lose renewals, and names the point where manual prep stops working.

What Renewal Call Preparation Actually Is

Renewal call preparation is the work of rebuilding the full history of a customer relationship before the renewal conversation. That history covers every conversation, support ticket and promise made during the contract term and the sales cycle before it. You use it to decide whether the call should rescue the account (intervention) or grow it (expansion), and you walk in with cited evidence of the value you delivered.

Two things often get mistaken for renewal prep:

• A QBR deck. A QBR reports usage and outcomes. Renewal prep reconciles what the customer asked for against what you actually delivered. A customer can have strong usage and still be furious about three undelivered asks.
• A CRM health score. A health score is a lagging, weighted summary of proxy signals such as logins, NPS and ticket counts. Prep goes back to the primary sources: what the customer actually said, and when they said it.

The output is a one-page renewal call brief with five parts:

1. Account facts and contract position: ARR, term, renewal date, notice period and effective decision date.
2. The asks ledger: every request and commitment, marked delivered or undelivered.
3. Champion and stakeholder status: who is engaged, who has gone quiet, who is new.
4. Sentiment trend: how the tone of conversations has moved across the term.
5. The decision and planned opening: intervention or expansion, and the first two sentences you will say.

The core rule: every claim in the brief should point to a source, such as a call date, a ticket number or an email. If you can't cite it, don't say it on the call.

Why Renewal Prep Breaks Down

Renewal prep breaks down because the evidence lives in five places and no one owns the job of reading all of them. Call recordings sit in one tool, tickets in Zendesk or Intercom, promises in AE notes or Slack, and contract terms in a PDF or a CRM field nobody updates.

The specific failure modes are predictable:

• Context is split across systems. No single person sees calls, tickets, Slack and contract terms side by side.
• Promises go unlogged. AEs commit to roadmap items or fixes during the sale. Those commitments never reach CS, so the customer remembers them and you don't. (See how to track commitments made on sales calls to capture them at the source.)
• Repeated issues look like separate issues. One bug raised on three calls and in two tickets reads as five small items unless someone groups them. Customers count the repetitions even when you don't.
• Champion decline is silent. Nobody announces they've stopped advocating for you. The signals are fewer attendees, slower replies, a new name on invites, or a title change on LinkedIn. B2B contact data is commonly estimated to decay 20–30% a year as people change roles, so over a 12-month term there's a real chance your champion has moved.
• Notice periods get missed. Many contracts require notice to cancel or renegotiate 30, 60 or 90 days before renewal, and some enterprise contracts use 120. If prep starts two weeks before the renewal date, the real deadline has already passed.
• CSMs prep from memory. With a large book, a CSM remembers the last call and the loudest complaint, not the pattern.

None of these require bad CSMs. They come from how the work is structured, which is why a fixed method helps.

The 60-Day Renewal Prep Method (Spreadsheet Edition)

This method is six steps any team can run today with a spreadsheet, the CRM, the help desk and whatever call recordings or notes exist. No purchase is required. It works as a customer success renewal playbook for a single account or a whole quarter's renewals.

Step 1: Start 60 days before the notice deadline, not the renewal date

Find the contract's notice period and work backward. Renewal date minus notice period equals the effective decision date. That is the last day the customer can cancel or force renegotiation before auto-renewal. Start prep 60 days before that date, and put both dates at the top of the sheet.

Some jurisdictions regulate auto-renewal notice in service contracts. New York General Obligations Law §5-903, for example, makes automatic renewal provisions unenforceable against the customer unless the provider sends written notice 15–30 days before the cancellation deadline. Check your own contracts with counsel; this is not legal advice.

Step 2: Pull every conversation, ticket and promise from the contract term

Build one tab with one row per touchpoint. Columns: date, source (call, ticket, email, Slack), who was involved, what was said or asked, link to the original.

Include the sales cycle that led to the current contract. That's where most promises were made. Set a fixed time budget of 60–90 minutes per account so the pull doesn't swallow the week.

Step 3: Build the asks ledger, delivered vs undelivered

On a second tab, list every distinct request or commitment. Merge duplicates and record how many times each was raised and on which dates. Give each one a status:

• Delivered: with evidence (release note, closed ticket, customer confirmation).
• Delivered-unconfirmed: shipped, but the customer never acknowledged it.
• In progress.
• Not delivered.

Rule: anything marked Delivered without evidence gets downgraded to Delivered-unconfirmed.

Step 4: Check champion activity and sentiment trend

For the champion, record the date of their last call attendance, their last reply, and the trend in response time. Note any role or title change and any new stakeholders appearing on invites. Gartner's research puts typical B2B buying groups at roughly 6 to 10 people, so a single-threaded account is exposed by default.

For sentiment, rate each conversation in the term as positive, neutral or negative based on what was actually said. Then compare the last three touchpoints with the first three. Direction matters more than any single score.

Step 5: Decide intervention or expansion

Use the matrix below. If any intervention trigger fires, the call is a save conversation and the expansion pitch waits. Intervention protects gross revenue retention (GRR); expansion grows net revenue retention (NRR). Get the first right before attempting the second.

Step 6: Prepare evidence of value, then plan the opening

List 3–5 delivered outcomes, each tied to a source. Use the customer's own words from past calls where possible. Then write the first two sentences of the call:

• Intervention: name the unresolved issue before the customer does.
• Expansion: open with the delivered asks.

Finally, write a parking list of what you will not raise on this call.

Customer renewal prep checklist

1. Calculate the effective decision date (renewal date minus notice period) and start 60 days before it.
2. Pull every call, ticket, email and Slack thread from the term and the prior sales cycle into one tab, with links.
3. Build the asks ledger: merge duplicates, count mentions, mark status with evidence.
4. Log champion activity, stakeholder changes and the sentiment trend.
5. Run the decision matrix: any intervention trigger means a save play first.
6. List cited proof of value, write your opening two sentences, and write your parking list.

Worked Example: A Renewal 41 Days Out With a 30-Day Notice Period

This is an illustrative scenario, not a customer case study.

Setup. A $48,000 ARR annual contract renews in 41 days. The notice period is 30 days, so the effective decision date is 11 days away. The CSM inherited the account four months ago. By the method's standard, prep is already 49 days late, which is common and is why the notice deadline matters more than the renewal date.

What Step 2 pulled: 14 calls (3 from the sales cycle), 9 support tickets and 1 Slack escalation thread, since closed.

What the asks ledger showed: 7 distinct asks.

• 3 Delivered with evidence.
• 1 Delivered-unconfirmed: an SSO change the customer never acknowledged.
• 3 Not delivered.

The worst undelivered ask was the CSV export bug, raised on calls in March, May and July and in 2 tickets. That's 5 mentions, and the only undelivered item raised more than once. Another undelivered ask: during the sales cycle, the AE promised a Salesforce field sync. It was never logged and never built.

Champion status. The VP who signed last attended a call 74 days ago. The last two calls were run by an ops manager who isn't in the CRM. Email reply time stretched from same-day to 6+ days.

Sentiment. The first 5 touchpoints were positive or neutral. 3 of the last 4 were negative, all mentioning the export bug.

Decision: intervention. Four of the six triggers fire: a repeated unresolved ask, a champion inactive 74 days, a negative recent trend, and an undelivered sales-cycle promise. The planned 15-seat expansion pitch is shelved until after renewal.

The save play:

• Day 1: Get a committed fix date for the export bug from product and engineering before contacting the customer. "We're looking into it" would be a new vague promise; a committed date is evidence.
• Day 2: The CSM's manager emails the VP directly, names the export issue, and asks for 20 minutes before the decision date. Peer-to-peer outreach carries more weight than a sixth CSM follow-up.
• Stakeholders: Add the ops manager to the CRM and invite them as a co-stakeholder on the call.
• Salesforce sync: Acknowledge that it was promised and never scheduled, and give a realistic answer rather than a new open-ended commitment.
• SSO change: Confirm it in writing to close the Delivered-unconfirmed item.

Planned opening line:

"Before anything else, the export bug. You've raised it five times and we haven't fixed it. Here's the date engineering committed to."

What the prep changed. We won't invent an outcome. The change is that the CSM walked in owning the issue instead of being ambushed by it, and did so inside the notice window instead of after it. Whether the account renews still depends on engineering hitting the date.

Common Renewal Prep Mistakes

Most lost renewals trace back to a handful of avoidable prep mistakes, not to a single bad call.

• Starting from the renewal date instead of the notice deadline. Why it fails: the decision window closes before prep begins.
• Pitching expansion to an account with intervention signals. Why it fails: it tells the customer you weren't listening, and can turn a save into a downsell, which is revenue churn without logo churn.
• Counting a ticket as resolved without customer confirmation. Why it fails: the customer still thinks it's broken, and they'll say so on the call.
• Treating repeated mentions as separate low-priority items. Why it fails: five mentions of one bug is one high-priority pattern.
• Relying only on the champion. Why it fails: when they go quiet or leave, there is no second relationship to fall back on.
• Opening with usage dashboards. Why it fails: the customer wants to talk about a broken workflow, and charts read as deflection.
• Making new promises on the renewal call to close the gap. Why it fails: it restarts the cycle of undelivered asks that created the risk.

There are also limits no prep process removes. No prep tool, ours included, fixes an unfixed bug, builds an executive relationship you never had, or makes pricing match value that isn't there. Prep surfaces these problems early. People and product have to solve them.

The stakes justify the effort. Bain's Frederick Reichheld found that a 5% increase in retention can raise profits by 25% to 95%, and HBR notes acquiring a new customer can cost 5 to 25 times more than keeping one. Those are older, cross-industry figures, so treat them as directional.

When Manual Prep Stops Working (and the Tools That Help)

The spreadsheet method works for a small book, but past roughly 30 accounts per CSM, the 60–90 minute pull per account starts competing with live customer work. At that point CSMs skip Steps 2 and 3 and prep from memory, which brings back every failure mode above.

The bottleneck is gathering and reconciling sources. The Step 5 decision should stay human. Signs you've crossed the line:

• Prep regularly starts inside the notice window.
• The asks ledger only contains items the current CSM personally heard.
• AE promises keep surfacing for the first time on renewal calls.

1. BuildBetter call prep

BuildBetter builds a renewal brief that reconciles prior conversations, promises made, support activity, linked tickets, contracts and CRM context. Every claim shows its source, which mirrors the method's "cite it or don't say it" rule.

• Two brief types that map to Step 5: an Intervention view (sentiment drops, open tickets, escalation history, contract position) and an Account visit view (what's been discussed, asks already delivered, value).
• Evidence required: resolved items need completion evidence. Opening text the record doesn't support falls back to a neutral prompt instead of an invented claim.
• Follow-ups and handoffs: follow-ups are drafted from what happened on the call and sent from where the conversation started, with an auditable ledger of every send. The sales-to-CS handoff carries commitments forward, which addresses the unlogged AE promise problem.
• Access and integrations: available to your agent over MCP from Claude or ChatGPT. Connects to Zoom, Google Meet, Teams, Gong (import), Slack, HubSpot, Salesforce, Gmail, Outlook, Zendesk and Intercom.
• Pricing and compliance: you pay for data ingestion with unlimited seats. SOC 2 Type II, HIPAA and GDPR.

"Looking back, we were lucky to go with BuildBetter. A lot of other tools were extremely rigid." — James Wallis, Brex

2. BB Recorder

BB Recorder is for teams whose problem is that calls were never recorded at all. It's free, works 100% offline, needs no account, and records Zoom, Google Meet and Teams locally with no bot on the call. Transcription happens on device. You can optionally send a visible bot, or switch between bot and local mid-call. It runs on Mac, Windows (including ARM), iPhone and Android (beta), and you can upload recordings to a BuildBetter workspace later. Download BB Recorder.

The pairing is simple: BB Recorder captures the conversations, and BuildBetter turns them into renewal briefs, follow-ups and commitment tracking. For setup, see how to record Zoom, Meet and Teams calls locally. If you're weighing local recording against bot-based tools, read this comparison of recording approaches.

Consent: always tell participants a call is being recorded and get consent where the law or your policy requires it. Recording laws vary by jurisdiction, and the recording tool does not handle consent for you.

If your book is small and your sources already live in one place, the spreadsheet method is enough.

FAQ: Renewal Call Preparation

How far in advance should you prepare for a renewal call?

Start 60 days before the contract's notice deadline, not the renewal date. With a 30-day notice period, that's about 90 days before renewal. With a 90-day notice period, it's about 150 days before renewal.

What is a renewal notice period?

It's the contractual window before the end of the term in which the customer must give written notice to cancel or renegotiate. Otherwise the contract typically auto-renews. Common periods are 30, 60 or 90 days. Renewal date minus notice period gives you the effective decision date.

What should a renewal call brief include?

Five parts: (1) account facts and contract position, including the notice deadline; (2) an asks ledger marking every request as delivered or undelivered, with evidence; (3) champion and stakeholder status; (4) the sentiment trend across the term; (5) the intervention-or-expansion decision with a written opening. Every claim should cite a source.

How do you know whether a renewal needs a save play or an expansion pitch?

If any intervention signal is present, run a save play first and hold the expansion pitch. Intervention signals include a repeated unresolved ask (2+ mentions), a champion inactive for 45+ days, a negative sentiment trend in the last three touchpoints, an open escalation or P1 ticket, an undelivered sales-cycle promise, or a new decision-maker with no relationship.

What do you do when the champion has gone quiet before renewal?

Escalate peer-to-peer before the notice deadline (manager to VP, exec to exec). Identify who now runs the relationship day to day, add them to the CRM and invite them as a stakeholder. Check LinkedIn for a role change. Don't wait for the champion to resurface.

Should you bring up known problems on a renewal call?

Yes. Name the top unresolved issue in your opening, with a concrete next step. Customers who have raised an issue repeatedly will raise it anyway, and owning it first preserves credibility.

When does a spreadsheet stop being enough for renewal prep?

Roughly past 30 accounts per CSM, when the time needed to gather sources for each renewal pushes CSMs to prep from memory instead of from the record.

Sources and Further Reading

• Wikipedia, Customer success
• Wikipedia, Churn rate
• Amy Gallo, "The Value of Keeping the Right Customers," Harvard Business Review, 2014 (citing Frederick Reichheld, Bain & Company)
• Gartner, B2B buying journey research
• KeyBanc Capital Markets / Sapphire Ventures, Private SaaS Company Survey (check the latest edition for current GRR and NRR medians)
• BuildBetter, How to track commitments made on sales calls
• BuildBetter, How to record Zoom, Meet and Teams calls locally
• BuildBetter, BB Recorder vs Gong

Make churn optional.

Every renewal brief in this guide comes down to one thing: reading the full record before the customer reads it to you. BuildBetter pulls your calls, tickets, Slack threads, CRM and contracts into one cited brief, so your CSMs walk in knowing what was asked, what was delivered and what was promised.

Make churn optional. Book a demo →