Sales · Upsell Call
The Upsell Script for Sales Customers: Turning an Account Review Into an Expansion Without Burning the Renewal
You are calling a VP of Sales or a Director of Sales Development who bought DrillCall eleven months ago to fix a five-month ramp, and who thinks this is a check-in. They are the hardest upsell audience alive, for one obvious reason: they close for a living. They have run the exact call you are about to run, they have coached reps out of the exact opening you were planning to use, and if you lead with "I wanted to walk you through something we just launched," they will give you a polite ten minutes and a "send me something" — and then use the recording in Friday's team huddle as an example of a rep pitching before discovery.
So don't. This call is won in the prep. Before you dial you need their seat count against weekly actives, their time-to-first-meeting across the last two onboarding classes, their 90-day wash-out rate, and one outcome number that came out of their dashboard or their QBR deck — not your benchmark slide. A sales leader will forgive a lot, but they will not forgive being asked "so how's everyone finding the platform?" when they know the usage data is sitting in your system. That single question demotes you from partner to vendor in one sentence.
The expansion you're going after is almost always the thing that got cut from the original scope. They bought drills for the SDR pod and deliberately left out live call scoring, or the AE discovery library, or the manager rubric, because it was too big a bite or because someone in the room said the word "surveillance." You are not selling something new. You are reopening a decision they already made once, with eleven months of their own data on the table — and you are asking for one pod, one quarter, co-termed to the existing renewal. Not the enterprise rollout your quota wants.
The upsell call script
Say it in your own words. The structure is the part that matters.
- 1
0. Pre-call usage audit — do not dial without these six lines filled in
Write these down on one page and have it open on the call: **Adoption** — "25 SDR drill seats licensed. 18 weekly active. The Austin pod is 9 of 9. The Denver pod is 2 of 8 and hasn't logged a drill since the March class." **Depth** — Which drill packs they run (cold open, gatekeeper, objection-at-the-door) and which they've never touched (discovery, multithreading, pricing pushback). Last login of the exec sponsor: "CRO logged in twice, both in week one." **Outcome — their number, not yours** — "Time-to-first-meeting on the January class was 19 days. The class before we started was 34." Or from their QBR deck verbatim: "'Ramp is the one thing that got better this year.' — their words, Q3 QBR, slide 6." **Commercials** — ACV, renewal date, who signed, whether that person is still in seat, discount level, and whether an add-on can be co-termed. **Support history** — Any open tickets, any escalation in the last 60 days. A P1 three weeks ago changes this whole call from expansion to repair. **Champion status** — Is the Director of Sales Development who championed this still running SDRs, or did they get moved to enablement in the reorg? Did your SDR Manager champion get promoted? The test: can you say one thing about their account they'd be mildly surprised you knew? If not, don't dial yet.
- 2
1. Frame the call in the first thirty seconds
"Thanks for the fifteen. Two things I want to cover. First — I pulled your drill usage across the last two quarters and there's a split in it I want to check with you, because I think it means something about Denver. Second, depending on what you tell me, there's a piece of the platform I think is relevant to it, and if it isn't I'll say so and we'll hang up early. Fair?" Do not sandbag. Do not ambush. Pre-committing to walking away lowers a sales leader's guard faster than any rapport attempt, because it's the move they teach their own reps.
- 3
2. Make them say out loud that the core product worked
"Before anything new — let me check my read on the result. When we started, your time-to-first-meeting was sitting around five weeks and the January class hit 19 days. Your 90-day wash-out went from five out of eleven to two out of nine. Does that match how it feels from where you sit, or am I reading the data optimistically?" Then shut up. Their correction is worth more than your number, because it tells you which metric they actually defend in front of the CRO. Write the sentence down exactly as they say it. That sentence is line one of the business case they'll forward internally. **If they can't confirm a result, stop the upsell.** "Then let's not talk about anything new today. Let's fix the fact that you're paying for something you can't point at in a board deck." That's not a lost call. That's the only version of this call that protects the renewal.
- 4
3. Say the underuse objection before they do
"Here's what I'd push back on if I were you: you've got 25 seats and 18 weekly actives, and the seven that are dark are all in Denver. If I were you I'd be asking why I'd buy anything else before I've used what I've got. So let me tell you what I think those seven are doing instead. They're not idle — Denver ran 4,200 dials last quarter and their manager reviewed maybe four calls a week. They're getting the same coaching your Austin pod got before we started, which is to say almost none, and their meetings-held rate is the one that's lagging. That's not an unused-seat problem, that's an unrouted-work problem. And if it turns out Denver just never onboarded properly, then the honest answer is you have an enablement gap, not a product gap, and I'll go fix that for free before I ask you for another dollar." Reframe unused capacity as unrouted work — or concede the point and go fix adoption. There is no third answer that leaves the relationship intact.
- 5
4. Find the seam — ask what got cut last time
Never lead with the module. Lead with where value leaks out of their week. - "After a rep finishes a drill run, what happens next? Who looks at it?" - "How many live calls is an SDR Manager with eight reps actually reviewing in a week right now — real number, not the number in the enablement doc?" - "When a talk track breaks, how do you find out? From a recording, or from the pipeline number three weeks later?" - "Who's asking you for coaching reporting that you can't produce today — is the CRO asking, or the board?" - "What did we deliberately leave out of scope last time because it was too big a bite?" That last one is the highest-yield question on the call. Nine times out of ten the answer is "we cut live call scoring because the team would've called it surveillance" or "we only did SDRs, we never did the AE discovery library." You're reopening a decision, not making a new one.
- 6
5. Build the case in their arithmetic — and say the price out loud
"Let me do the math with your numbers and you tell me where I'm being generous. **The unit:** you told me in the Q3 QBR that a 90-day wash-out costs you about $22k all-in — salary, seats, your manager's hours, and a territory that goes cold for six weeks. **The volume:** you hired 16 SDRs last year. Seven were gone inside 90 days. **The capture:** live scoring doesn't save the rep who was never going to make it. What it catches is the rep in month two running a broken open across 900 dials that nobody hears until the pipeline review. Say that's two of the seven — and I'd rather under-promise. That's $44k. **The net:** live call scoring is $2,400 a month on top of the $4,100 you're paying. So $28,800 against $44k, before we even talk about what it does to your calls-reviewed-per-manager number, which right now is four out of roughly 2,000. If you think two out of seven is generous, tell me what number you believe and we'll rerun it live." Handing a VP of Sales the pencil on your own assumptions is the difference between a business case and a pitch deck. They will respect it because it's what they'd want their AEs doing.
- 7
6. Cost the rollout in hours and names, not phases
"Bandwidth is the real objection here, not budget, so let me price it in your team's time. One 90-minute session with whoever owns the dialer integration — that's RevOps, probably 45 minutes of actual work. Then two hours a week for three weeks from one SDR Manager to tune the rubric so it matches what your top rep actually does, not what the enablement doc says she does. That's the whole ask. No project team, no steering committee. Our CS team writes the first rubric draft off your existing drill packs and runs the enablement session. If it takes more than that, I've mis-scoped it and I'll tell you." Put the absorbed work on the table here, as scope — not later, as a concession.
- 8
7. The ask — one pod, one quarter, reversible
"I don't want the whole team. Give me Denver for one quarter — eight reps, one manager. Success criteria you define, on this call, and I'll write them into the recap today. My suggestion: calls reviewed per manager per week goes from four to twenty, and time-to-first-meeting on the next Denver class comes in under 25 days. If we miss either one, we pull it out at the end of the quarter and you owe nothing further. If we hit it, we roll it to Austin and the AE side at your March renewal and co-term the whole thing, so you're negotiating one contract in March instead of two. Does that structure work, or would you scope the pilot differently?" Co-terming is the most underused unlock on this call. It kills a second procurement cycle and makes the add-on feel like an amendment rather than a new purchase.
- 9
8. The three guards
**"Budget's committed through the fiscal year."** Don't discount. "Committed to what, and when does it reset? Because if you're onboarding six SDRs in January, this problem gets bigger in Q1, not smaller. Is there a line item in the same budget that isn't earning — the intent tool with single-digit logins, or the contractor doing call QA? And could this come out of enablement's budget rather than yours, given the Director of Sales Enablement is the one who'd own the rubric?" Budget objections are usually timing and authority objections in a costume. A signed order form now with a January start date solves most of them. **"My managers are underwater."** This is almost always true. Never argue with it. "Then measure me on their calendar, not their login. If your SDR Manager is still spending 90 minutes a week on call review in April, it failed and we pull it." Then shrink the ask or move the start date past their known crunch — but get a date on the calendar, not a "circle back in Q3." **"We barely use what we have."** Section 3. Either you can show the dark seats are doing the work outside the system, or you concede and go fix onboarding first.
- 10
9. Check whether the buying committee still exists
"Last time this went through Priya in finance and you signed it yourself under the $25k threshold. Is that still the path, or has anything changed since the reorg?" If there's a new CFO, a new procurement policy, or a spend review that landed last quarter, you are running a fresh evaluation dressed as an expansion — and you need that on this call, not in week six when someone asks you for three competitive bids.
- 11
10. Recap email — write it for the person your champion forwards it to
Same day, seven lines, no attachments: 1. The result they confirmed, in their words: *"Ramp is the one thing that got better this year — 34 days to 19 on the January class."* 2. The gap they described: Denver, 4,200 dials, four calls reviewed a week. 3. The math with their assumptions: $22k per wash-out, 2 of 7 caught, $44k. 4. The price, plainly: $2,400/month. 5. The implementation ask: one 90-minute session plus two hours a week for three weeks from one manager. 6. Pilot scope and the success metric they set. 7. Named next step with a date. This email is the artifact. Your Director of Sales Development forwards it to the CRO without editing it, or you wrote it wrong.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Thanks for the fifteen, Marcus. Two things — first, I pulled your drill usage across both quarters and there's a split in it I want to check with you, because I think it says something about Denver. Second, depending on what you say there, there's a piece of the platform I think is relevant, and if it isn't I'll tell you and give you the time back. Fair?
Buyer
I'll be honest with you — the second you said 'depending on what you say,' I knew what this call is. I run a 40-rep org. I've made this call. If this pitch isn't clean I'm clipping it for Friday's huddle.
Rep
Then judge it the way you'd judge one of your AEs: did I do discovery before I pitched, did I quantify anything with your numbers instead of mine, did I ask for a real next step. If I whiff on any of those, use the clip. Can I check one thing first and you tell me if I've got it right?
Buyer
Go.
Rep
Your January SDR class hit first meeting at 19 days. The class before we started was 34. And your 90-day wash-out went from five of eleven to two of nine. Does that match how it feels on your side, or am I reading it optimistically?
Buyer
It's directionally right and I'm going to push back anyway, because that's not a clean attribution. We also swapped data providers in November and moved off the parallel dialer. Connect rate went from 1.8% to about 3%. So my reps had more live conversations to learn on. You want to tell me that ramp number is you — I'd tell one of my reps that's a correlation slide, not a business case.
Rep
That's fair and I'm not going to claim the whole delta. Here's the piece I'd defend: Austin ran the drill packs at 9 of 9 weekly and hit 19 days. Denver got the same new data and the same dialer change, ran 2 of 8 weekly, and came in at 31. Same list, same tooling, different drill usage. That's the only comparison I'd put in front of your CRO.
Buyer
Okay, that's a better answer. But you've just told me seven of my Denver seats are dark. So explain why I'd give you another dollar before I've used what I bought.
Rep
You shouldn't, if they're idle. But they're not — Denver ran 4,200 dials last quarter. Their manager, Kev, is reviewing about four calls a week out of that. So they're doing the work, just with no coaching loop on it. That's an unrouted-work problem, not an unused-seat problem. Which raises the question I actually wanted to ask: what did we deliberately cut from scope last time because it was too big a bite?
Buyer
Live scoring on real calls. And I killed it, not procurement. My best SDR goes completely off-script — she's got a gatekeeper move nobody wrote down — and the second I put a rubric on her live calls she'll think I'm surveilling her and I'll lose her to a competitor by March.
Rep
Agreed, and if it dings her for going off-script it's useless and you should rip it out. The reps you want it on are the ones in month two who don't have a script to go off yet. Actually — has anyone ever written down what she does on the gatekeeper, or is it still in her head?
Buyer
It's in her head. Which is a problem I've had for two years and haven't solved.
Rep
Then here's the honest version of the ask. Scoring her calls isn't the point — mining them is. We pull her three best gatekeeper handles, turn them into a drill pack, and score the month-two reps against her, not against a doc from enablement. Cost math, using your numbers: you told me in the Q3 QBR a 90-day wash-out runs you about $22k. Seven of sixteen hires last year. If this catches two of the seven — the ones running a broken open across 900 dials before anyone hears it — that's $44k. The module is $2,400 a month on top of your $4,100. So $28,800 against $44k. If two of seven sounds generous, give me your number and I'll rerun it right now.
Buyer
One out of seven. Maybe. And I don't have budget — we're locked until February and there's a spend review running that I don't control.
Rep
One of seven still clears it, barely, and I'll take that as the number. On budget — what changes in February? Because if you're onboarding a class in Q1, the coaching problem gets bigger then, not smaller, and Kev's still at four calls a week when they land.
Buyer
Six SDRs in January. Which is exactly why I don't have room for a rollout in January.
Rep
Then don't do a rollout. Denver only — eight reps, one manager, one quarter. Rollout is 90 minutes with RevOps for the dialer connection, then two hours a week from Kev for three weeks to tune the rubric off your top rep's calls. My CS team writes the first draft and runs the enablement session. Order form signed now, start date February 1, co-termed to your March renewal so you're negotiating one contract, not two. Success criteria you set — I'd suggest Kev's calls reviewed goes from four a week to twenty, and the January class hits first meeting under 25 days in Denver. Miss either, we pull it and you owe nothing further.
Buyer
Make it under 22 days on first meeting, and I want the top-rep drill pack built before the class starts, not after. And Priya's threshold changed — anything over $25k annual now needs her sign-off, so this one doesn't slide through on my signature like last time.
Rep
Under 22, pack built before day one, and I'll write the recap today so it's forwardable to Priya without you rewriting it — your ramp numbers, your $22k, your one-in-seven, the price, and the three weeks of Kev's time. Can you and I get twenty minutes with Priya before the fifteenth?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"We're not even using all 25 seats. Why would I buy a module?"” | "You shouldn't, if those seats are idle. But Denver ran 4,200 dials last quarter with seven dark seats — they're doing the work, just outside the system, with four calls reviewed a week between them. That's unrouted work, not wasted spend. And if I dig in and find Denver simply never onboarded properly, then you've got an enablement gap and not a product gap, and I'll go fix that on my dime before I ask you for anything." |
| “"That ramp improvement isn't you. We changed data providers and our connect rate doubled."” | "Fair, and I won't claim the whole delta. Here's the only slice I'd defend in front of your CRO: Austin and Denver got the same new data and the same dialer change. Austin ran 9 of 9 weekly on drills and hit first meeting at 19 days. Denver ran 2 of 8 and came in at 31. Same list, same tooling. If you want to run that comparison yourself against the raw dials-to-connects-to-meetings, I'll send you the export." |
| “"Scoring live calls is surveillance. My best rep goes off-script and that's why she's my best rep."” | "Agreed — if it dings her for going off-script it's useless and you should pull it. The reps this is for are the ones in month two who don't have a script to go off yet. Genuine question: has anyone written down what she actually does on the gatekeeper, or is it still in her head? Because the version of this I'd sell you isn't scoring her, it's mining her — turning her three best moves into the drill pack the new class runs against." |
| “"We already bought conversation intelligence. It sits there."” | "What happened with it — did nobody listen to the recordings, or did managers listen and nothing changed after? Those are different failures. Most teams tell me it's the second one: great transcripts, great dashboards, and an SDR Manager with eight reps and 90 minutes a week. Recordings tell you what happened. What does your team do today in the gap between 'that call went badly' and the next live dial? That gap is the only thing I'm selling into." |
| “"Kev is drowning. This becomes another thing he doesn't do."” | "That's almost certainly true, so let's measure me on his calendar rather than his login. If Kev is still at four calls reviewed a week in April, it failed and we pull it. The ask on him is two hours a week for three weeks to tune the rubric, then it runs off the calls his reps are already making. What's actually on his week right now — how much is pipeline inspection versus one-on-ones versus covering a desk?" |
| “"Budget's locked until February and there's a spend review running."” | "Understood, and I won't discount to get around it — that would just teach you to wait for the discount on every future expansion. Two questions instead. What changes in February, given you're onboarding six SDRs in January and Kev's coaching load goes up not down? And is there a line item in the same budget that isn't earning — the intent tool with single-digit weekly logins, for instance? If neither works, we sign an order form now with a February 1 start and co-term it to your March renewal." |
| “"Send me something and I'll look at it." (from a leader who says this for a living)” | "I'll send it either way, and I'll write it so you can forward it to Priya without rewriting it. But you and I both coach reps out of accepting that, so let me ask properly: is 'send me something' a no on the problem, or a no on the timing? If it's the problem — Kev at four calls a week doesn't bother you — tell me and I'll stop. If it's timing, give me a date for the twenty minutes with Priya and I'll build around it." |
Questions reps ask about this call
- What's the single biggest mistake in an upsell script for Sales customers?
Opening with the module. "I wanted to walk you through something we just launched" tells a VP of Sales that the call is about your roadmap, and they will hand you a polite ten minutes and a "send me something." The second-biggest is dialing without the usage audit and then asking "so how's the team finding the platform?" This buyer knows you have that data in your system, and asking them to narrate it back is the specific thing that demotes you from partner to vendor. Open instead with a usage pattern they'd be mildly surprised you knew — the pod that's 2 of 8 weekly active, the exec sponsor who logged in twice in week one.
- How do I open the call when they think it's a routine check-in?
Frame it honestly inside the first thirty seconds and pre-commit to walking away: "Two things — I pulled your usage from the last two quarters and there's a split I want to check with you, and then depending on what you say there's a piece of the platform I think is relevant, and I'll tell you if it isn't." Sales leaders respect this because it's the agenda-setting move they teach their own reps. Ambushing them costs credibility; so does sandbagging until minute twelve.
- The customer says they barely use what they already bought. Do I push through it?
No. You have two honest answers and there isn't a third. Either you can show that the unused capacity is doing the work outside your product — "those seven dark seats ran 4,200 dials last quarter with four calls reviewed between them" — which reframes it as unrouted work rather than wasted spend, or you concede the point and go fix adoption before you ask for another dollar. Arguing with the underuse objection is how a healthy account becomes an at-risk one.
- How do I build the value case for a buyer who quantifies things for a living?
Use their arithmetic and hand them the pencil. Unit: what one instance costs, sourced from their own QBR — "you told me a 90-day wash-out runs about $22k all-in." Volume: from their data — "seven of sixteen hires last year." Capture rate: deliberately conservative, and say so. Net: price stated out loud in the same breath as the value, never waiting for them to ask. Then finish with "if you think my capture rate is generous, give me your number and I'll rerun it live." Never quote your industry benchmark when you have their instance data in a dashboard.
- What should I actually ask for at the end of the call?
The smallest unit that proves the case: one pod, one quarter, success criteria they define on the call and you write down. For a sales org that usually means a specific pair of numbers — calls reviewed per manager per week going from four to twenty, and time-to-first-meeting on the next class landing under a stated number of days. Attach a pre-agreed decision date and co-term the add-on to the existing renewal. Co-terming removes a second procurement cycle and turns the purchase into an amendment rather than a new evaluation.
- When should I park the upsell entirely?
Park it if there's an open P1 or an unresolved escalation, if your champion just changed roles or got quietly sidelined in a reorg, if the renewal is inside 60 days with value questions still open, if usage is flat or declining and you can't explain why, or if a hiring freeze or spend review landed in the last quarter. Also park it if they can't confirm a result from the core product — at that point you're on a value-realization call, not an expansion call, and running the upsell anyway trades a renewable account for an incremental $30k you probably won't collect.