The SaaS Renewal Call Script for a Save Call You're Six Weeks From Losing

1. 1

   Before You Dial: The Renewal Autopsy

   You cannot fake this on the call. Pull and read, don't skim: - Every ticket from the last 12 months: ID, open date, first response, resolution, sentiment. Flag anything over 48 hours to first touch. Memorise the three worst by number and date. - Seat-level utilisation by team, month over month. Not "adoption is around 40%" — "AEs are at 82% weekly active, SDR seats peaked at 34% in March, the 20 CS seats were never provisioned." Assume their CFO already has a version of this number. - CSM and AE turnover on your side. Three CSMs in eighteen months is your fault, and you name it before they do. - Every QBR commitment that never shipped: the warehouse sync, the training session rescheduled twice, the Salesforce write-back. - Org changes on their side. Did the VP of Sales who signed get promoted to CRO? Did the Head of Growth inherit the budget? Is the champion who built the workflow even invited to this call? - Escalations: did anything reach a VP? Did anyone put "this is unacceptable" in writing? Then write your one-page "what went wrong" summary before the call. You'll send it after, in their words.

2. 2

   Get Internal Alignment Before You Promise Anything

   Before you dial, get in writing from your own side: - Support leadership: what actually changed — new segment queue, named escalation engineer, 4-hour P1 SLA — and the date it took effect. - CS lead: exactly how many onboarding hours you can commit to their untrained SDR and CS seats, and which named CSM owns it. - Finance/deal desk: your floor on price, term and seat count, and whether you can issue service credits for the affected months rather than cutting rate. A remedy you improvise on the call and can't deliver is the second broken promise. That one ends the account, and it gets attributed to you personally.

3. 3

   Opening: Say It Before They Do (First 60 Seconds)

   Do not say "how have things been going?" They know you have the data on screen. "I know the contract's up on the 14th. I'm not here to talk about the renewal yet — I want to talk about this year first, because from where I'm sitting it wasn't the year we sold you. Here's what I can see. Ticket 41-882 went nine days without a first response in June, and 41-907 took six. You've had two CSM changes in fourteen months. And of the 180 seats you're paying for, 74 have ever been weekly active — your AEs adopted, your SDR team peaked at 34% in March, and the CS seats we sold you in the expansion were never even provisioned. That's my side of it. What am I missing, and what did it actually cost you?" Then stop. The silence after that is where the meeting is won.

4. 4

   The Listening Phase: Fifteen of Your Thirty Minutes

   No "but." No "to be fair." Do not defend a single ticket, including the ones where their admin genuinely broke the sync. Probes that work on a revenue leader: - "Who did you have to explain this to?" - "Did this come up in a board meeting or a QBR with your CEO?" - "When your VP of Demand Gen said the data was stale, what happened to the sequence?" - "You said you were flying blind for two weeks — tell me about those two weeks." Write it down visibly and read it back: "So: Q2 response times, the SDR rollout that never happened, the warehouse sync we promised in the March QBR and didn't ship, and you found out about the January outage from your own rep rather than from us. Anything else?" Ask "anything else?" twice. The second ask is where the political wound comes out — usually that they championed you internally and took heat for it.

5. 5

   The One Apology

   Once. Specific. No hedging. Then move. "The Q2 response times were a failure on our side. We reorganised support in April and your tickets got queued behind enterprise escalations. That's an explanation, not an excuse — you bought a 24-hour first-response SLA and we missed it eleven times between April and July. The SDR rollout is a separate failure and it's mine. I sold you 60 seats on a land-and-expand assumption and then nobody from my side ran the enablement session that was supposed to happen in February." Do not follow this with a discount. A price cut is not an apology, and they will read it as one.

6. 6

   Proof of Change: Their Data, Not Your Roadmap

   Company-wide stats carry nothing. Three things do: 1. Structural change with a date, shown in their own numbers: "We split the support queue by segment on September 1 and added a named escalation engineer for accounts your size. Your median first response since then is 3.2 hours across nine tickets — here's the list, check it against your own." 2. A reference account with the same wound: "There's a VP of RevOps at [Customer] who had the identical Q2 with us and stayed. I'll set up the call — twenty minutes, no one from my side on it." 3. Something already done, unasked: "I had the team clear the three open tickets in your queue last week. You'd have seen those close Thursday." If nothing has genuinely changed, say so and change what you control: your own coverage cadence, a named escalation path, an exec sponsor on your side. Do not manufacture progress. They will check.

7. 7

   Rebuild on What Actually Worked

   They still like one or two things. Find the human, not the feature. "You said the account-signal view is the one thing your AEs would miss. Who's actually in it every day, and what did it replace?" "If we disappeared on the 14th, whose Monday breaks?" "When your win rate on stage-three deals moved last quarter, was any of that this?" Then quantify it in their language, not yours — meetings booked per SDR per month on the accounts that were worked with the signal versus without, pipeline coverage going into the quarter, cycle length on sourced deals. If their pipeline coverage is sitting at 2.4x against a 3x plan, the question is which of their 40 tools is actually moving that number, and you want yours in that conversation with evidence. That power user is your remaining champion and was probably not invited to this call. Get their name.

8. 8

   The Competitor Who Quoted 28% Less

   Surface it yourself: "I'd assume [Competitor] has been in your inbox. I'd be surprised if they hadn't." - Never disparage. "What did you like about it?" — and mean it. - Find out how far it's gone: "Is that pricing in writing? Have they been through your security review? Has anyone scoped the migration with your RevOps lead?" A signed order form is a different conversation to a lunch. - Reframe from price to total switching cost, plainly: "The licence delta is the easy part. The expensive part is re-implementing against Salesforce and your warehouse with a RevOps team of one, retraining the AE group that did adopt, migrating fourteen months of history, and running blind on reporting through the quarter you're trying to fix coverage in. And you'd be inheriting a vendor you haven't had a bad quarter with yet." - Do not match the number here. Price is the last section of this call.

9. 9

   The Consolidation Mandate: Finance's Utilisation Report

   Assume the CFO's spend review is already running and your line is on it. Get in front of it rather than being surveyed by it. "Your finance team is going to ask for seat-level utilisation on every line in the stack, and on the current shape ours looks bad. So let me pre-empt it: I'd rather right-size you to the 90 seats you actually use than defend 180 and lose the whole line. The other half of that conversation is displacement. If our signal layer covers what you're paying the intent vendor for, that's two line items and one renewal you don't have to defend. Which contracts are up in the same window?" This reframes you from a line to cut into a line that removes other lines — and it kills the shelfware objection permanently.

10. 10

    The 90-Day Success Plan, Built Live

    Build it on the call, in their words, and send it inside 24 hours. Every line has four fields: what, who by name on both sides, by when, and what "done" looks like. "Let me build this with you rather than send you something. - SDR adoption: enablement for the 38 SDR seats that were never trained — run by [named CSM], week of the 14th, done = 25 of 38 weekly active by day 60 and meetings-per-SDR-per-month reported at the 60-day check. - Support: named escalation contact, direct line, 4-hour P1 SLA, effective at signature and written into the contract. - Expansion signal: your CS team gets the second-and-third-team alert inside existing logos, because that's an NRR conversation, not an outbound one. Done = a reviewed expansion list in your CRM by day 30. - Governance: 30/60/90 reviews, written usage report each time, first one dated the 12th. - What I can't do: the warehouse write-back isn't on the roadmap before Q3. I'm not going to pretend otherwise. Now — what goes on your side of this? Who owns the SDR enablement internally, and does your Director of Sales Development have to mandate attendance for it to happen?" A plan where only the vendor has obligations is a wish list. Adoption failed partly because nobody on their side owned it. Then tie a commercial consequence to it: a six-month break clause, quarterly-reviewed term, or SLA credits written in. Signing a credit clause is worth more than a discount because it proves you expect to be held to it.

11. 11

    Only Now: The Commercial Conversation

    Earn the transition out loud: "If we agree that plan is real, can I walk you through what renewal actually looks like?" - Structure before number: "Twelve months with a break at six, or twenty-four with price protection — which one do you need to survive your own board?" - Right-size seats rather than discount the whole line: "Take the 90 seats you use. That's a real reduction in spend, and it means your CFO's utilisation column reads 90% instead of 41%." - Trade every concession: a case study, a reference call with another VP of RevOps, multi-year, an earlier signature, an exec sponsor meeting. - For the bad year, use service credits, not rate: "Three months of credit for April through June. That's specific, it's finite, and it doesn't tell you my list price was always fiction."

12. 12

    Multi-Thread and Close

    Six weeks is tight and most stalled renewals die in procurement, not in the business. "Walk me through what happens between now and the 14th. Who signs — you, the CFO, or does it go to procurement? Does Legal need to see the SLA change? Has procurement already got [Competitor]'s quote?" "I want you, your CFO, and my VP of CS in a room for a 30-minute plan review. My exec should say what I've said, at their level." Book the next meeting on this call — never "I'll follow up." Temperature check, and take the honest answer over the polite one: "On a scale where 1 is you've already decided to leave and 10 is signed — where are we right now, and what specifically moves it?" Within 24 hours: the written 90-day plan, the ticket data you quoted, the reference intro, and the one-page summary of what they said went wrong in their words. That last document does more work than any proposal.

1. Rep

   Before we touch the renewal — I want to go through this year, because it wasn't the year we sold you. Ticket 41-882 sat nine days without a first response in June. 41-907 took six. You've had two CSM changes since last March. And of 180 seats, 74 have ever been weekly active — your AEs are at 82%, the SDR seats peaked at 34% and flatlined, and the CS seats from the expansion were never provisioned. What am I missing, and what did it cost you?

2. Buyer

   You're missing that my CFO already has that number. She pulled seat-level utilisation across all 41 GTM tools three weeks ago and yours is in the bottom quartile. The rule right now is that nothing renews unless I can name what comes out of the stack in writing. So you're not defending a bad quarter, you're defending a line item.

3. Rep

   Understood, and I'll come back to what comes out. First though — when the utilisation report landed, who did you have to explain this to?

4. Buyer

   The board, indirectly. NRR went from 118 to 103 over two quarters and I get asked every meeting whether that's product, CS coverage, or macro. In the March QBR I told my CEO this platform was part of the fix. Then June happened, my VP of Demand Gen was telling me the account data was stale while reply rates were already under 1%, and I looked like the guy who bought another top-of-funnel bet.

5. Rep

   Tell me about June. What actually broke in the week those tickets were open?

6. Buyer

   We were flying blind for about two weeks. The SDR team paused two sequences because nobody could tell whether the enrichment was current. Meetings-per-SDR dropped, coverage going into Q3 came in at 2.4x against a 3x plan, and my forecast call turned into an argument about whether the pipe was soft or the reps were sandbagging. Nobody could separate the two, which is its own problem.

7. Rep

   The Q2 response times were a failure on our side. We reorganised support in April and your tickets queued behind enterprise escalations — that's an explanation, not an excuse. You bought a 24-hour first response and we missed it eleven times between April and July. The SDR enablement that never ran is separately mine; I sold 60 seats and then didn't staff the training. Anything else on the list before I show you what's actually changed?

8. Buyer

   Yes — the warehouse write-back you committed to in the March QBR. Never shipped. And I'll be straight with you: [Competitor] has quoted us 28% under, in writing, with migration included, and they've already come back on the security questionnaire.

9. Rep

   I'd have been surprised if they hadn't. What did you like about them? And has anyone scoped the migration with your RevOps lead yet?

10. Buyer

    Honestly? The number. The demo was fine. And no, nobody's scoped anything, because my RevOps function is one person who is permanently underwater — she owns the CRM, the routing rules, the warehouse sync and the board reporting. If migration eats six weeks of her, that's six weeks of nothing else happening.

11. Rep

    Then the licence delta isn't the real number. Re-implementing against Salesforce and the warehouse, retraining the AE team that did adopt, moving fourteen months of history, and running degraded reporting through the exact quarter you're trying to rebuild coverage in — with one RevOps person. Before we get near price: if we disappeared on the 14th, whose Monday actually breaks?

12. Buyer

    Priya's, on the AE side. She built the account-signal view the whole enterprise team runs their Monday pipeline review off. But I'll tell you where my head is — we're pushing hard into PLG and sales-assist next year. Self-serve signups are healthy, conversion to paid is flat, and I don't have an agreed definition of a PQL or who owns the account when it crosses the line. An outbound signal tool isn't obviously how we grow anymore.

13. Rep

    Agreed, and I'm not going to pitch you cold spray. The question that matters for your NRR number is different: how many free workspaces are sitting inside logos where you already have two or three teams paying? That's a second-and-third-team signal, and it goes to your VP of Customer Success, not your SDRs. Expansion intelligence, not outbound. Would you let me run it against your closed-won and expansion list from the last two quarters — if it doesn't surface accounts you actually expanded into, I've saved you the argument.

14. Buyer

    That's a more interesting conversation than the one I expected. But it doesn't change the mandate. And if you can't get to their number, I don't have a story for my CFO.

15. Rep

    Here's my story for your CFO, and it isn't a discount. First, we right-size you from 180 seats to the 90 you use — real spend reduction, and your utilisation column reads 90% instead of 41%. Second, service credits for April through June, because that's what you're actually owed; a rate cut would just tell you my list price was fiction. Third, the SLA change and a six-month break clause written into the paper, so if the 90-day plan doesn't land you're not trapped. And the displacement line: if the expansion signal covers what your intent vendor does, when is that contract up?

16. Buyer

    February. Which is inconveniently good timing for you. Send me the plan and I'll circulate it.

17. Rep

    I'll send it tonight — the plan, the ticket data I quoted, and a one-page summary of what you told me went wrong, in your words. But circulate to whom, and what do they need to see? If it's your CFO she wants cost per active seat and what comes out of the stack. If it's your RevOps lead she wants the objects we write to and the implementation hours. And I want you, her, and my VP of CS in a room for thirty minutes on the 8th — my exec should say to you what I've said. Does the 8th work?

18. Buyer

    The 8th at four. CFO probably won't come, RevOps will. And to answer the question you're about to ask — two weeks ago I was a 2. Right now I'm a 5, and what moves it is 25 of those 38 SDR seats being live by day 60 with a name against it.

How should a SaaS renewal call script open when the customer has already half-decided to leave?

With your failures, by ticket number and date, before they raise them. "Ticket 41-882 sat nine days in June, you've had two CSM changes, and 74 of your 180 seats have ever been weekly active." Then hand them the floor and stop talking. Opening with "how's everything been going?" when you have that data on screen reads as unprepared or evasive, and they'll spend the rest of the call working out which.

Should I offer a discount if the customer genuinely had a bad year with us?

No. A price cut is not an apology — it reframes twelve months of service failures as a pricing dispute, tells them list price was always negotiable, and resets your floor permanently. The honest instruments are service credits for the affected months (specific and finite), right-sizing seats to actual usage, and writing an SLA credit clause into the contract. A signed credit clause proves you expect to be held to it, which a discount never does.

How do I handle it when finance has pulled seat-level utilisation and our line looks bad?

Get in front of it rather than being audited. Volunteer the number first, then propose right-sizing — 180 seats to the 90 they actually use gives the CFO a genuine spend reduction and turns your utilisation column from 41% to 90%. Then work the displacement angle: name which other contract in the stack you'd expect to come out, and when it renews. You want to be the line that removes lines, not the line being removed.

What actually goes in the 90-day success plan?

Four fields per row: what, who by name on both sides, by when, and what "done" looks like in a number. "Enablement for the 38 untrained SDR seats, run by [CSM], week of the 14th, done = 25 weekly active by day 60." Include at least one line the customer owns — an internal sponsor, mandated attendance from their Director of Sales Development, a data cleanup — because adoption failed last time partly because nobody on their side owned it. And include the thing you can't do, stated plainly.

The champion who signed last year is still on the call — is that enough to close the renewal?

Usually not. Their title, budget authority or manager may have changed since signature, and procurement has often had the competitor's quote for weeks. Ask directly: "Walk me through what happens between now and the 14th — who signs, does this go to procurement, does Legal need to see the SLA change?" Then get the economic buyer and your own exec sponsor into a 30-minute plan review. Renewals stall in procurement far more often than they're lost in the business conversation.

How long should I spend listening before I talk about what we've fixed?

On a thirty-minute call, at least fifteen minutes. If you say "so here's what we've changed" while they're still describing the damage, you retroactively convert your acknowledgement into a sales technique and they'll hear everything after it that way. Ask "anything else?" twice, ask who they had to explain it to internally, then apologise once, specifically, and only then move to proof — using their own usage and response-time data, not company-wide stats.

• All SaaS playbooksEvery call type for SaaS, in one place.

Other SaaS calls

• Cold CallThe SaaS Cold Call Script for Reps Dialling CROs, VPs of Sales and RevOps Leaders
• Demo CallThe SaaS Product Demo Script for Selling Into a Revenue Team That's Already Cutting Tools
• Discovery CallDiscovery Call Questions for SaaS: A 25-Minute Diagnostic Playbook for CROs, RevOps and Growth Buyers
• Manager Coaching CallSales Coaching Roleplay for SaaS Teams: The 1:1 After Two Missed Quarters
• Pricing Negotiation CallThe SaaS Pricing Negotiation Script: Holding Price After the Technical Win
• Upsell CallThe Upsell Script for SaaS Customers That Survives a Seat Utilization Report
• Warm CallWarm Call Script for SaaS: Cashing a Referral With a CRO in Four Minutes

The same call in a neighbouring market

• Renewal Call for InsuranceInsurance Renewal Call Script: Saving a Claims Platform Account at a Carrier That's Already Halfway Out
• Renewal Call for HealthcareHealthcare Renewal Call Script: Saving a Clinical Documentation Account After a Bad Year

Related reading

• Renewal Call vs Upsell Call: Running Both at Once Is How You Lose BothRenewals restore confidence, upsells extend it. Run them on the same call and the customer hears you asking for more money for the thing that already disappointed them.
• "Can We Just Do Month-to-Month?" — The Short-Term Ask and What It's Really Telling YouA month-to-month request is a confidence problem, not a contract term — here's how to diagnose it and three trades that get you back to an annual deal.