Sales · Renewal Call
The Sales Renewal Call Script for a Save Call: When Your Sales-Leader Customer Has Already Half Left
Your customer is a Director of Sales Development who bought fourteen seats last February on the promise that it would pull time-to-first-meeting in from five weeks to three and stop the 90-day wash-outs. Since then: two CSM changes on your side, a Q2 stretch where your support queue went dark for nine days during their end-of-quarter push, an Outreach write-back you promised in the April QBR that still isn't shipped, and a usage report showing the Enterprise AE pod at 78% weekly active while the SDR floor — the reason they bought — peaked at 34% in March and flattened. A competitor rep has been in their CRO's inbox with a number 30% under yours and an offer to migrate the scorecard library for free.
This is not a renewal call. The paperwork is the last five minutes, not the first five. And this buyer is harder than most, because this buyer sells for a living. They run save-call frameworks in their own enablement deck. They will recognise the autopsy open the moment you use it, and they'll say so. That's fine — the play still works, you just don't get style points for it. What they cannot fake indifference to is a rep who walks in with ticket 41-882's response times, their own weekly-active split by pod, and a 90-day plan with named humans and dates on both sides of the table.
Use this sales renewal call script as a running order, not a monologue. Roughly half the call belongs to them talking about the bad year. If you spend less than fifteen minutes there on a thirty-minute call, you rushed the only part that matters. Lead with the discount and you confirm the thing they already suspect: that you only show up when money is due.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial: the renewal autopsy (60 minutes, no shortcuts)
Do not open a deck until you can answer these out loud from memory: • Every ticket in the last 12 months — ID, open date, first response time, resolution. Know the three worst by number. Flag anything over 48 hours to first touch. • Weekly active users by pod, month over month. Not "adoption is 43%." It's "Enterprise AEs at 78%, the SDR floor peaked at 34% in March, Mid-Market never onboarded." • Drills assigned vs. drills completed by manager. If their SDR Manager stopped assigning in April, you need to know that before they tell you. • CSM/AE turnover on your side. Two CSMs in nine months is your fault and you name it before they do. • Every QBR commitment you didn't deliver — the CRM write-back, the objection-library build, the training session rescheduled twice. • Org changes on their side. Did the Director of Sales Development who signed still own the budget? Did the SDR floor shrink from 14 reps to 8? Is there a new CRO? • Their outcome numbers before and after: time-to-first-meeting for the last two hire classes, 90-day wash-out rate, calls reviewed per manager per week, meetings booked per SDR per month, held vs. booked. Then get internal alignment in writing: what Support leadership will actually commit to (named escalation contact, response SLA), what your CS lead can staff for the SDR floor onboarding, and your true floor on price, term and seat count. Never improvise a remedy on this call. The second broken promise ends the account, and it gets attributed to you personally.
- 2
Opening: name it before they have to (first 45 seconds)
"[Name], the contract's up on the 14th. I'm not going to talk about the renewal for the first twenty minutes of this — 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 sat nine days without a first response in June, and that was your end-of-quarter push. You've had two CSMs in nine months, which means you re-explained your comp plan and your pod structure twice to people who should have already known it. The Outreach write-back I committed to in the April QBR hasn't shipped. And the part that matters most: your Enterprise AE pod is at 78% weekly active, and the SDR floor — the reason you bought this — peaked at 34% in March and has been flat since. That's my side of it. What am I missing, and what did it actually cost you?" Then stop. Do not fill the silence. The meeting is won in the four seconds after that question.
- 3
The listening phase: let it be worse than you thought (15+ minutes)
Rules: no "but." No "to be fair." No defending the one ticket where their team genuinely never replied to your CSM. You may be right, and you will lose the renewal being right. Questions to use, in roughly this order: "Tell me about those nine days. What were you doing instead?" "When the SDR floor stopped logging in — was that a product problem, a manager-bandwidth problem, or did the reps just not believe in it?" "You sold this internally to somebody. Who did you have to explain it to when the numbers didn't move?" "Did this come up in your leadership review, or in a board deck?" "How many of the January class made it to day 90?" Follow the emotional word. If they say "we were basically flying blind on that class," say: "Tell me about that class." Write it down visibly, then read it back: "So: nine days of silence in Q2 during your quarter-end, two CSM handovers, the write-back I promised in April, and the SDR floor never got past a third of the licenses you're paying for. Anything else?" Ask "anything else?" a second time. The second one is where the real wound shows up — usually something political, like a RevOps lead pulling the login report in front of the CRO.
- 4
The apology: once, specific, unhedged
"The Q2 response times were a failure on our side. We reorganised support in May and your tickets queued behind enterprise escalations. That's an explanation, not an excuse — you're on a 24-hour first-response SLA and we missed it eleven times between April and July. And the SDR floor rollout: I let that run on your SDR Manager's time when she was covering two desks. That was mine to catch and I didn't." One apology. No "sorry things haven't been perfect." A generic apology tells them you still haven't looked. Then move — do not apologise again later in the call, it starts to read as a discount you're softening them up for.
- 5
Proof of change: their data, not your company dashboard
"Three things I want to show you, and none of them are a roadmap slide. One — we hired into support in August and split the queue by segment. Your median first response since September 1 is 3.2 hours across nine tickets. That's your account, not a company average. I'll send the list. Two — I had the team close out the three tickets that were still sitting open in your queue last Thursday, before this call. You should have seen those come through. Three — [Customer], an outsourced SDR agency running six pods, had the same problem you had: the AE pod adopted, the SDR floor didn't. Their Managing Partner is willing to take a 20-minute call with you and tell you exactly what they changed. I'll make the intro, and I won't be on it." If nothing has genuinely changed, say that instead and change what you control: your own coverage cadence, a named escalation path, an exec sponsor on the account. Do not manufacture progress. This buyer will check.
- 6
Rebuild on what works: find the pod that stuck
"You said the objection drills are the one thing the AE team would miss. Who's actually using those, and what did they replace?" "Before the drills, how many calls a week was [Manager] reviewing for that pod? And now?" "Your March AE class — what was time-to-first-meeting on that group versus the class before it?" "If this went away on the 14th, whose Monday breaks?" That last name is your remaining champion and they are almost certainly not on this call. Get them on the next one. Quantify in their language, out loud: "So the AE pod went from four calls reviewed a manager a week to every rep getting a scored rep before a live call, and the March class hit first meeting in 19 days against five weeks for the class before it. That's the piece we're protecting."
- 7
Surfacing the competitor before they ambush you with it
"I'd assume you've been talking to [Competitor] — I'd be surprised if you hadn't. What did you like about it?" Listen properly. Then scope how far it's gone: "Is that pricing in writing or a verbal? Has your CRO seen it? Have they scoped the migration on your scorecard library, or is that a line in the proposal?" "Has Security looked at it yet? Last time you had a vendor review it took your InfoSec team six weeks." Reframe from price to switching cost, plainly: "Here's the comparison I'd want if I were you, and I'll lose it on price either way. The $13k gap is real. Against it: rebuilding the objection library your AE pod uses, retraining the one team that did adopt, six to eight weeks where your ramp reporting is broken while you're onboarding a January class, and the risk that you inherit a new vendor's version of the same support problem with none of the goodwill and none of the history I'm sitting here answering for. I'm not going to tell you they're bad. I'm telling you the number on the page isn't the number." Do not match on price here. Price is the last five minutes.
- 8
The 90-day plan: build it live, in their words
"Can we build the next 90 days on this call rather than me sending you something? Four columns: what, who by name on both sides, by when, and what done looks like." Drive to lines like these: • SDR floor adoption: onboarding for the 9 SDRs who never got trained. Run by [CSM name], week of the 14th. Done = 7 of 9 completing two assigned drills a week by day 60. • Manager workflow: drills auto-assigned off the dialer so [SDR Manager] isn't the bottleneck. Live by day 30. Done = she isn't manually assigning anything. • Support: named escalation contact, direct line, 4-hour first response on P1. Effective at signature, written into the contract. • Governance: 30/60/90 reviews with a written usage report by pod, first one dated the 12th. • What I can't do: the Outreach write-back is not shipping before Q3. I'm not going to pretend otherwise, and I'm not going to price it in. Then turn it around: "What goes on your side of this? Because last year every line was mine, and that's part of why it died. I need [SDR Manager] to own drill assignment for one pod, and I need a mandate from you that says this is part of the ramp plan, not an optional tool." Tie a commercial consequence to it: "I'll write a break clause at month six against those adoption numbers. If 7 of 9 SDRs aren't active by day 60, you walk with no penalty. An SLA I sign up to be held against is worth more to you than a discount."
- 9
Only now: the commercial five minutes
Earn the transition out loud: "If we agree that plan is real, can I walk you through what a renewal would look like?" Structure before number: "You're paying for 14 seats and 8 of them logged in last week. I'd rather right-size to 9 than discount 14 — that kills the shelfware conversation permanently instead of parking it for a year. Twelve months with a six-month break clause against the adoption milestones, and I'll write service credits for the four months of Q2 where we missed your SLA. Credits, not a price cut. A price cut isn't an apology, and if I discount you 30% today I've told you the number was always fake." Anything further is traded, never given: a reference call for [Competitor]'s target segment, a two-year term, a case study on ramp, an intro to the sister agency, signature before month end.
- 10
Multi-thread and close — six weeks is tight
"Walk me through what happens between here and signature. Who else signs — does your CRO sign, or is that you now? Does this go to procurement, and do they already have [Competitor]'s quote?" "I want thirty minutes with you, [SDR Manager] and [CRO] to review this plan, and I'll bring [your exec sponsor]. Not a pitch — he's going to say the same thing I said about Q2, and he should be the one saying it. Does Thursday the 9th or Monday the 13th work? I'll send the invite before I hang up." Temperature check, and take the honest answer: "On a scale where 1 is you've already decided to leave and 10 is you're signing — where are we right now, and what specifically moves it a point?" Within 24 hours, send four things: the 90-day plan with names and dates, the ticket data you quoted, the reference intro, and a one-page summary of what they told you went wrong — in their words. That last document does more work than any proposal you'll ever build.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Priya, contract's up on the 14th. I'm not going to talk about the renewal for the first twenty minutes — I want to talk about this year, because it wasn't the year we sold you. Ticket 41-882 sat nine days without a first response in June, in your quarter-end push. You've had two CSMs in nine months. The Outreach write-back I committed to in April hasn't shipped. And your Enterprise AE pod is at 78% weekly active while the SDR floor peaked at 34% in March and has been flat since. That's my side. What am I missing, and what did it cost you?
Buyer
I'll give you the homework. But I want you to know I recognise the play. Open with the autopsy, name the failures before the customer does, earn the right to pitch — that's page four of my own save-call deck. My CSMs at my last company ran it. It's a good play. You don't get extra credit for running it on someone who teaches it.
Rep
Fair. Then judge it the way you'd judge one of your reps: did I do discovery before I pitched, did I quantify anything, did I ask for a next step. If I whiff on those, clip it. So — the nine days in June. What were you doing instead?
Buyer
What I was doing was explaining to my CRO why I'd spent 41 grand on a ramp tool and lost three of the six SDRs in the January class before day 90. I sold this internally as the thing that pulls time-to-first-meeting from five weeks to under three. I put it in a board slide. Then Marcus in RevOps pulls the login report in a Tuesday leadership meeting and it shows 6 of 14 seats active. In front of everybody.
Rep
That's the part I didn't have. So it wasn't just support — you took heat personally for choosing us, in a room. Anything else that I should have on this list before I respond to any of it?
Buyer
Yeah. Dana — my SDR manager — stopped assigning drills in April. Not because she didn't like it. She was covering two desks after Kyle left, she's got eight reps, she's got maybe ninety minutes a week for call review and she's using all of it on live recordings, not on a platform that asks her to build assignments. Your product needed her to have time she doesn't have.
Rep
So: nine days of silence in Q2 at quarter-end, two CSM handovers, the write-back I promised in April, the login report in front of your CRO, and a rollout that quietly depended on Dana having bandwidth she never had. Anything else?
Buyer
That's the list. And before you get to the plan — Sharpen quoted me $28k against your $41k, it's in writing, my CRO has seen it, and they've said they'll migrate our objection library free. So whatever comes next has to survive a thirteen-thousand-dollar gap.
Rep
Let me take the failures first and I'll come to Sharpen. Q2 was ours. We reorganised support in May and your tickets queued behind enterprise escalations — that's an explanation, not an excuse. You pay for a 24-hour first response and we missed it eleven times between April and July. And the SDR rollout: I let it run on Dana's time when she was covering two desks. That was mine to catch. Since September your median first response is 3.2 hours across nine tickets, and I closed the three that were still open in your queue last Thursday before this call. What I'd like to know is what the AE pod is getting that the SDR floor isn't.
Buyer
The AEs use it. Rob runs objection drills before anything above 50k, and the March AE class hit first meeting in nineteen days against about five weeks for the class before. That I'll defend. But one pod of six AEs is not a 41-thousand-dollar line item, and I'm not renewing fourteen seats so six people can practise.
Rep
Agreed, and I'm not going to ask you to. Nine seats, not fourteen — right-sized to what actually logs in. I'd rather be right than big, because otherwise Marcus pulls the same report next October. And the SDR floor fix isn't more training, it's removing Dana from the loop: drills auto-assigned off the dialer, so she never opens our tool to assign anything. Live by day 30, and the measure of done is 7 of the 9 SDRs completing two drills a week by day 60. If we miss that, you walk at month six with no penalty. I'll write the break clause in.
Buyer
You're asking me to sign twelve more months on a promise from a vendor whose last four promises I can list from memory. Give me the plan and 30% and I'll take it to my CRO. Otherwise it's a straight price conversation and you lose it.
Rep
I'm not going to discount 30% and here's why, honestly: a price cut isn't an apology, and if I hand you one now I've told you the number was always soft — you'd be right to never believe a price of mine again. What I will do is service credits for the four months we missed your SLA. That's specific, it's finite, it's tied to the thing that actually went wrong. Plus the seat reduction, plus a 4-hour P1 SLA with a named escalation contact written into the contract, plus the break clause. If you want the number lower after that, trade me something — a reference call, or a two-year term.
Buyer
The credits I can defend upward. The break clause I actually like more than the discount, which annoys me. But my CRO has Sharpen's quote and he's going to ask me why I'm paying more for the vendor that went dark in Q2.
Rep
Then he should hear that from me, not you — you shouldn't have to carry my bad quarter into that meeting. Thirty minutes with you, Dana and your CRO, and I'll bring our VP of Support. He'll walk through what changed in the queue and he'll say the eleven-misses number out loud. Thursday the 9th or Monday the 13th? I'll send it before we hang up. And separately — I'll introduce you to the Managing Partner at Northline, an outsourced SDR shop that had exactly your split: AE pod adopted, SDR floor didn't. I won't be on that call.
Buyer
Thursday the 9th, after eleven. Bring the ticket list and the adoption numbers by pod — Marcus will want the raw export, not a slide. And be straight with me: if the 7-of-9 doesn't happen by day 60, I'm using the break clause.
Rep
That's the deal, and I'd rather you use it than renew angry again. Last question so I know where I actually stand: on a scale where 1 is you've already decided to leave and 10 is you're signing — where are we, and what moves it one point?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “I sell for a living. I know exactly what you're doing right now — you led with the failures because that's the save-call play. I've taught that play.” | You're right, and running it on you doesn't earn me anything. So judge it the way you'd judge one of your reps on a scorecard: did I do discovery before I pitched, did I quantify anything with your numbers rather than mine, did I ask for a real next step. If I miss on any of the three, clip it and use it in Monday's enablement session — you'd be right to. What I'd rather you judge is the 90-day plan, because that's the part with names and dates on it that you can hold me to. |
| “My reps already juggle six tools. Yours was the seventh and it died in month three — which is exactly what I told you would happen when I bought it.” | You did tell me, and you were right. So the version I'm proposing isn't a seventh tab — drills get assigned automatically off the calls they're already making in the dialer, and Dana never opens our platform to assign anything. If a rep has to remember to go somewhere new, we're back in the same hole and I'd lose you again in two quarters. Before you decide anything: walk me through what actually happens today between the dialer and the CRM after a rep hangs up. If the answer means we still need a human to remember something, I'll tell you not to renew. |
| “My SDR manager has eight reps and about ninety minutes a week for call review. Whatever you build, she doesn't have the time to run it.” | Then measure me on her calendar, not her login. If Dana is still spending ninety minutes a week doing manual call review at day 90, the plan failed and you use the break clause. What's actually on her week right now — how much is pipeline inspection, how much is one-on-ones, how much is covering Kyle's old desk? Because the fix has to come out of one of those three, and I'd rather pick the right one with you now than guess. |
| “Sharpen is at $28k against your $41k, it's in writing, and they'll migrate our objection library for free.” | That's a real gap and I'm not going to tell you they're a bad product. Two questions: has your InfoSec team looked at them yet — last review took you six weeks — and has anyone scoped the migration, or is 'free migration' a line in the proposal? Here's the comparison I'd want in your seat: $13k against rebuilding the library Rob's AE pod actually uses, retraining the one team that did adopt, and six to eight weeks with broken ramp reporting while you're onboarding a January class. Plus the risk you get a new vendor's version of the Q2 problem with none of the history and no goodwill to spend. If the numbers still say switch, they say switch. |
| “We cut the SDR floor from fourteen to eight. I can't take fourteen seats back to my CRO no matter what you do with the price.” | Then don't. Nine seats — the eight reps plus Dana — and we right-size rather than discount. That's deliberate: if I cut 30% off fourteen seats, Marcus pulls the login report next October and you're in this meeting again. Reducing to actual usage kills the shelfware argument permanently. If the floor goes back to fourteen in Q2 when you hire, we add seats at the same per-seat rate — I'll write it in so a hiring class doesn't turn into a renegotiation. |
| “Budget's frozen until the new fiscal year. Come back in January and we'll talk.” | Understood — but the contract lapses on the 14th, so 'come back in January' means the AE pod loses it for six weeks in the middle of your Q1 kickoff. What changes in January that makes this easier? If you're onboarding six SDRs that month, the ramp problem is bigger in Q1, not smaller — that's the class where time-to-quota and the 90-day wash-out either move or don't. I'd rather structure a short bridge on the current terms to the new fiscal year than have you ramp a class blind and then buy something in March. |
| “Scoring calls against a playbook sounds like surveillance, and my best rep goes off-script — that's exactly why she's my best rep.” | If it dings her for going off-script it's useless and you should cancel. The reps it's for are the ones in month two who don't have a script to go off yet, and who currently learn by burning live connects at a 2-4% connect rate. Here's the more interesting question: what is your top rep doing on discovery that the January class isn't? Has anyone ever written that down, or is it in her head and leaving with her? |
Questions reps ask about this call
- What's the difference between a renewal call script and a save call script?
A renewal call assumes the customer is staying and the conversation is about term, seats and price. A save call assumes they're half gone. In a save call the paperwork is the last five minutes, not the first five, and 40-50% of the call belongs to the customer describing what went wrong. If you open a save call with 'so what would it take to get this done,' you confirm the suspicion that you only appear when money is due. Use this sales renewal call script as the save version: autopsy, listening, one apology, proof, 90-day plan, then commercials.
- How do I open a sales renewal call when the year genuinely went badly?
Name it first, with specifics they can verify. Ticket numbers and dates, CSM turnover on your side, weekly active users broken out by pod, the QBR commitment you didn't deliver. Then hand them the floor with 'that's what I can see — what am I missing, and what did it cost you?' and stop talking. Never open with 'how's everything been going?' when you have a screen full of nine-day response times in front of you; it reads as unprepared or evasive, and a sales leader will spend the rest of the call testing which one.
- Should I offer a discount to save an at-risk renewal?
Not as an apology. A price cut reframes a service failure as a pricing dispute, tells them your list price was always negotiable, and permanently resets your floor. Two better instruments: service credits for the specific months you missed SLA — finite, specific, tied to the actual failure — and right-sizing seats to real usage, which kills the shelfware objection instead of parking it for a year. Any further discount should be traded for a reference call, a longer term, an earlier signature or an exec sponsor meeting.
- How much of the call should be listening?
On a thirty-minute save call, at least fifteen minutes before you say anything that sounds like a solution. The instant you say 'so what we've done is…' while they're still describing the damage, you've retroactively converted your acknowledgement into a sales technique — and a VP of Sales or Director of Sales Development will spot that faster than anyone. Ask 'anything else?' twice. The second ask usually surfaces the political cost, like a RevOps lead pulling the login report in front of the CRO.
- What goes into the 90-day plan, and why does it matter more than the proposal?
Four fields on every line: what, who by name on both sides, by when, and what 'done' looks like in a number they already track — 7 of 9 SDRs completing two drills a week by day 60, first response under four hours on P1, time-to-first-meeting for the January class. Include the thing you can't do and say so plainly. Critically, put obligations on their side too: a manager who owns assignment, a mandate that this is part of the ramp plan. A plan where every action belongs to the vendor is a wish list, and that's part of why adoption died the first time.
- Who else needs to be on the call besides my champion?
Whoever signs now, not whoever signed last time. Budget authority moves: the Director of Sales Development who bought fourteen seats may now need the CRO to approve nine. Ask directly — 'who signs, does this go to procurement, and does procurement already have the competitor's quote?' Then get the champion, the frontline SDR Manager whose team didn't adopt, and the economic buyer into one 30-minute plan review with your own exec sponsor present. An exec-to-exec acknowledgement of a bad quarter is worth more than anything you can say alone, and most stalled renewals die in procurement rather than in the business.