Sales · Demo Call
The Sales Product Demo Script for Selling to People Who Sell for a Living
You're demoing to someone whose job is running demos. A VP of Sales who has sat in on 400 discovery calls this year. A Director of Sales Development who scores her reps on a rubric she wrote. A Managing Partner at an outsourced SDR shop who is on a client QBR at 2pm to explain why meetings-booked came in under SLA. They are not evaluating your product in the first four minutes. They are evaluating whether you did discovery before you pitched, whether you quantified anything, and whether you ask for a next step — because that is exactly what they grade their own team on.
This is the second call. They already said yes to seeing it. So they're not here to learn what it does; they're here to find where it breaks. The list in their head is short and specific: does this sit inside the dialer and the CRM my reps already live in, or is it a seventh tab. Who owns it when my enablement person goes on leave. What happens when it falls over at 8am Monday on the West Coast at the start of a power hour. And how long before I can point at a number — time-to-first-meeting, held meetings per SDR, cost per qualified meeting — and say this paid for itself.
Every interruption is either a buying question or a disqualification test. Run the rehearsed tour — setup screen, admin screen, dashboard — and you'll hear typing, then "yeah, no, that makes sense," said flat, and you've lost the room without them ever saying no. Below is the sales product demo script: what to do before you dial in, the opening contract, three workflows run as moments in their week, and cold answers to the four pressure lines. The demo you rehearsed is a resource. The call is won on the detours.
The demo call script
Say it in your own words. The structure is the part that matters.
- 1
Before the call — build the demo you're actually going to give
Send this in the confirmation email, three days out: "So I don't burn twenty minutes of Thursday showing you things that don't apply — three quick ones: 1) What are your reps dialing out of (Orum, Nooks, Salesloft Dial, ConnectAndSell, something else) and is your CRM Salesforce or HubSpot? 2) Do you have Gong or Chorus recording, and does everyone get recorded or just AEs? 3) Who's on the call besides you? If your RevOps lead is joining I'll build in fifteen minutes of architecture rather than making them sit through the rep experience." Then do the prep work they'll be able to see: - Build the persona off **their** ICP, not yours. If they sell warehouse automation to plant managers in the Midwest, the AI prospect is a plant manager in the Midwest, and it opens with the objection at the door they actually get. - Load their vocabulary: their SQL vs. SAL definition, their qualification framework, their meeting-booked criteria, their disco questions if they sent the talk track. - Pre-build the two screens tied to the pain they named last call. If they said "my month-two reps freeze on the pricing objection," that drill is the demo. Everything else is optional. - Decide what you will not show. Every screen you demo that they didn't ask for is a line item they now have to evaluate and defend internally. If they wouldn't send recordings, say so out loud on the call: "You didn't want to send call recordings before we'd signed anything — completely fair, I'd have said the same. So this persona is built from public stuff about your market. Tell me where it sounds wrong."
- 2
Opening — set the contract in 90 seconds, not an agenda slide
"Last time you told me three things. Connects are sitting under three percent, so a rep is burning something like 120 dials to get four real conversations. Time-to-first-meeting on a new hire is four to six weeks and time-to-quota is closer to five months. And your SDR manager has eight reps and about 90 minutes a week for call review, which is four calls out of the couple of thousand the team made. Did I get that right, or did I write it down wrong?" [Let them correct you. They will. That's the point.] "Anything shifted since we spoke? Headcount, budget, a client that got noisy?" "Two things before I share my screen. One — I'd rather you stop me than sit through something irrelevant. If you're thinking 'that won't work here,' say it in the moment, that's the useful part of this call. Two — what's the one thing that, if this can't do it, we don't need to keep talking? I'd rather demo in that order."
- 3
Workflow 1 — the month-two rep who has never heard the objection before
**Problem:** "So it's Tuesday, 9:15, power hour. You've got a rep who started six weeks ago. She gets a connect — one of the four she'll get today — and the guy opens with 'how did you get this number.' She's heard that twice, ever. Both times live, both times it cost her the call." **Screen — narrate as the rep, not as the software:** "She's in her dialer block. Before it starts, this fired into her Slack at 8:40. Six minutes. She hits it from her headset, same headset she's about to dial with. Here's the prospect." [Run it live. Let the AI be hostile.] **Consequence:** "She just heard that objection eleven times this week instead of twice this quarter. The first live one isn't the first one anymore." **Check:** "Is that when your reps actually get that objection — right at the open — or is it further in for you?"
- 4
Workflow 2 — the manager's Friday, not the manager's dashboard
**Problem:** "You said 90 minutes a week and four calls reviewed. So the question isn't 'do you have recordings' — you have thousands. It's that nobody can answer 'is my team actually running the playbook' with anything except a feeling, and you find out the talk track broke three weeks late, from the pipeline number." **Screen:** "This is what lands in your SDR manager's inbox Friday at 4. Not a dashboard she has to go log into. Eight reps, one row each. Column one is drills completed. Column two is the scorecard — and this scorecard is your rubric, the one you wrote, not a template I shipped. Here's the thing that matters: three of her eight reps are dropping the same qualification question. That's not four anecdotes, that's a pattern across 200 attempts." **Consequence:** "Her Monday one-on-ones stop being 'how's it going' and start being 'you and Dev and Priya are all skipping the budget question, we're doing that for ten minutes.'" **Check:** "Does your manager do one-on-ones Monday or Friday? Because I'd want this landing the day before, not the day after."
- 5
Workflow 3 — ramp, tied to a date on their calendar
**Problem:** "You said you're bringing on six SDRs in January. On today's math, that's four to six weeks before any of them books, five months before they're carrying, and roughly half wash out before they get there — call it eighteen to twenty-five grand each in salary, seats and manager hours, plus a territory that goes cold." **Screen:** "This is a ramp track. Week one is three drills: the open, the objection at the door, and the ask for the meeting. They don't get a live list until they clear the scorecard threshold you set. Here's what week one looks like from your side — every attempt, timestamped, scored." **Consequence:** "Your first-meeting date moves left. I'm not going to tell you by how much on this call — I'd want to measure your January class against your last one." **Check:** "What's your current bar for letting a new SDR on the phones live — is it a certification call with the manager, or is it just 'day nine, go'?"
- 6
Handling 'will it handle X?' — the highest-value moments on the call
Slow down and get the specific before you answer: - "Will it handle our qualification framework?" → "Tell me the actual case. Is it MEDDIC by the book, or is it your five questions and the third one is the one that predicts a held meeting?" - "Can it do multi-language?" → "Which language, for which team, and is that a today problem or a next-fiscal problem?" Then pick one of three, honestly: **Yes, and here it is** — go show it live, right now. Strongest thing that happens on a demo call. **Yes, but not how you'd expect** — "You don't do it on this screen. You do it here, and it's two extra clicks and someone has to paste the talk track in once. That's the ugly bit." Buyers forgive ugly. They don't forgive discovering ugly in month three. **No** — say no. "No. We don't score live customer calls today, and it's not on the roadmap this year." Then: "How often does that come up — is that a weekly thing or a once-a-quarter thing?" Half the time the deal-breaker is an edge case they raised because they thought of it. Never say "we can build that." To a VP of Sales that is the exact sentence their last vendor said before it slipped two quarters. And when you park something, park it visibly: "Writing it down — scorecard export into Salesforce as a custom object. I'll have a straight answer Thursday." Then Thursday.
- 7
Pressure line 1 — integration (what they're really asking: how much lands on RevOps?)
"Let me get ahead of the thing your RevOps lead is going to ask. We read from Gong over their API — call recordings and transcripts, read-only, and we only pull the calls in the folders you point us at. We write two things back: drill completion and scorecard, either into a Salesforce custom object or as a Slack digest, your call. We do not touch your dialer. We are not in the live-dial path — no number provisioning, no carrier, nothing that could affect spam-likely flagging on your DIDs. That's deliberate. SSO is Okta or Google. Provisioning is SCIM if you want it, CSV if you don't. And the thing I'd want to know if I were you: if you turn us off tomorrow, nothing stops. Your reps still dial, your recordings still record. We're additive, not in the pipe."
- 8
Pressure line 2 — who owns it on Monday
"Someone has to own the scorecard. That's real, and I'd rather say it now than at contract stage. Setup is about three hours total, and it's not IT work. It's one session where we take your talk track and turn it into the rubric, and about thirty minutes with your best rep — the one who goes off script and still wins — recording the version of the call you actually want cloned. That thirty minutes is the highest-leverage thing in the whole rollout, because right now that's in her head and nowhere else. Ongoing it's roughly two hours a month, and it belongs to your Director of Sales Enablement or the SDR manager, not RevOps. It's adding users and updating the rubric when the talk track changes. If your enablement person leaves, the handover is a one-hour walkthrough. The rubric is a document you own and can export."
- 9
Pressure line 3 — what actually happens when it breaks
"I'm not going to give you an uptime percentage, nobody ever bought because of a nine. Here's the failure mode. If our voice service degrades at 8am Monday during a power hour, your reps' dials are completely unaffected — we're not in that path. What they lose is the drill. It queues, they get it later, and the attempt history isn't lost. Worst case they run the drill in text mode, which is worse but not nothing. Support: P1 is a phone number, someone answers, seven to seven Pacific plus on-call. P3 is email, next business day, and I'm not going to pretend otherwise. You get a named CSM and my mobile stays live after the deal closes. If you want, ask me about our last incident and I'll walk you through it — what broke, how long, what we told customers."
- 10
Pressure line 4 — time-to-value, in three dates on their calendar
"Three dates, not one. **Live** — reps logged in and running their first drill: about five business days from kickoff. That's on us. **Useful** — one thing stops. For most teams the first one to move is your manager's call review: she goes from four calls a week to reading a pattern across a couple hundred scored attempts, and her Monday one-on-ones change. Two to three weeks. **Fully rolled out** — the January class ramps on the track and you have a first-meeting date to compare against your last cohort. That's the number I'd want you judging us on at ninety days: time-to-first-meeting, and held meetings per SDR per month for the new class versus the last one. What I need from you, in hours: the talk track document, a user list, thirty minutes with your top rep, and a Gong folder to read. Call it four hours of your enablement person's time in week one. If you get blindsided by your own workload, this stalls in week three — that's how these die. And I'd avoid going live in the last week of the quarter. Nobody's learning anything that week."
- 11
Recovering a room that's gone quiet
The signs: shorter answers, "mm-hm," a half-second delay, typing, camera off mid-call, "yeah, no, that makes sense" said flat. Stop the demo. In order of preference: "I've been talking for four minutes. Is this the part you care about, or should I jump somewhere else?" "Let me stop the tour. What's the thing you're worried about that I haven't touched?" "Do you want to drive? Tell me what to click." (Almost nobody does this. It works.) "I think I'm showing you the wrong things. Can I stop, take ten minutes to understand what actually matters to you, and come back Thursday with a demo built for that?" What does not work: talking faster, adding a feature, "one more thing I want to show you." A sales leader will clock that instantly — they watch their own reps do it.
- 12
Closing — gaps out loud, temperature, next thing on the calendar
"Let me summarise, including the parts that didn't land. Three things worked for you: the objection drill firing before the dial block, the Friday digest going to your SDR manager instead of another dashboard, and the ramp track gating the January class. Two open: whether the scorecard can export into Salesforce as a custom object, and what your security review needs. I'll have both by Thursday. Where does this sit for you now — worth pursuing, or is there something that's already ruled it out? I'd genuinely rather have a no today than chase you for four weeks." [If yes:] "Who else has to see it? I'd run a twenty-minute version for your RevOps lead that's only architecture, permissions and what we write back — nothing about the rep experience, they don't care. Can we get that on the calendar now while we're both here? What does the week of the 14th look like?" Send within 24 hours: the two open items with real answers, the four screens that mattered (not the whole recording), the security doc if RevOps was on, and a one-line list of what you need from them. Nothing generic. This buyer will read your follow-up email as a sample of your rep team's follow-up email.
- 13
Language that works vs. language that loses this buyer
| Instead of | Say | |---|---| | "Our AI-powered enablement platform..." | "This is what lands in your SDR manager's inbox Friday at 4." | | "We integrate with everything." | "We read from Gong over their API. We write drill scores back to a Salesforce custom object. We don't touch your dialer." | | "It's very intuitive." | "Your reps get one Slack message and a headset. There's no training session." | | "We can build that." | "No, not today, and not this year. How often does that come up?" | | "99.9% uptime." | "If we go down at 8am Monday, your dials are unaffected — we're not in that path. You lose the drill, not the data." | | "Most customers see ROI in 90 days." | "Judge us on your January class's time-to-first-meeting against your last cohort's." | | "Let me show you the dashboard." | "Let me show you the six minutes before a power hour." |
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before I share anything — last time you said connects are under three percent, so a rep's burning around 120 dials to get four real conversations, and your SDR manager has eight reps and about 90 minutes a week for call review. That's four calls out of a couple of thousand. Still accurate, or has something moved?
Buyer
It's accurate. And before you share your screen — I told you last time, I sell for a living. If the next thirty minutes is a tour, I'm clipping it and using it in Friday's call review as a what-not-to-do. So what's the one thing you're going to show me?
Rep
Fair, and I'd be right to be clipped. Judge me on the three things you grade your own reps on: did I do discovery before I pitched, did I quantify anything, did I ask for a next step. The one thing I'm going to show you is the six minutes before a power hour for a rep in her second month. But you tell me the order — what's the one thing that, if this can't do it, we don't keep talking?
Buyer
Adoption. We bought Gong eighteen months ago. Managers got dashboards. Nothing changed. There's a coaching doc that stopped getting updated in March. If this needs my SDR managers to remember to open a seventh tab, it's dead on arrival and I'd rather you didn't sell it to me.
Rep
Which failure was it, though — nobody listened to the recordings, or managers listened and nothing changed after? Those are different problems with different answers.
Buyer
The second one. They listened. There was just never a next move. She'd hear a bad call on Wednesday and the rep had made another 400 dials by the time she said anything.
Rep
Then let me start there and skip the rep screen. This is what lands in your manager's inbox Friday at 4 — not a dashboard, an email. Eight rows, one per rep. What she's looking at here is that three of her eight reps dropped the same qualification question across 200 attempts. That's a pattern, not four anecdotes. Does she run one-on-ones Monday or Friday?
Buyer
Monday. Stop for a second — whose voice is the prospect in these drills? Because if it's a robot that says 'that sounds interesting, tell me more,' my reps will laugh once and never open it again, and then you and I are both wasting each other's time.
Rep
Best way to answer that is to fail in front of you. Give me the worst one you get. Name the persona and the objection.
Buyer
CFO at a mid-market manufacturer. Objection at the door is 'how did you get this number.' And don't make it polite — the real ones aren't.
Rep
[runs it live, hostile] That's the drill. Your reps hit that objection maybe twice a month for real, because at a three percent connect rate the reps just aren't getting enough at-bats. Here they get forty in a week. Was that close, or is it softer than your reality?
Buyer
Closer than I expected. Here's my problem though. My best SDR goes completely off script and that's exactly why she's my best SDR. The second your scorecard dings her for that, the team stops trusting the number and we're back to a dashboard nobody opens.
Rep
Agreed, and if it dings her it's useless. So we don't score against a template I shipped — we build the rubric from her calls. Thirty minutes with her in week one. Which raises the actual question: what is she doing on discovery that your month-two class isn't? Has anyone ever written that down, or does it live in her head?
Buyer
It's in her head. Which is a problem I already knew about. What does this cost my SDR manager in time? Because she's underwater — half that 90 minutes is her covering an open desk.
Rep
First two weeks, about 45 minutes to sign off the rubric. After that it's the Friday email, fifteen minutes. And measure me on her calendar, not her login — if she's still spending 90 minutes a week on call review ninety days in, it failed and you should tell me so.
Buyer
And when your AI falls over at 8:05 on a Monday, mid power hour, West Coast?
Rep
Dials are unaffected. We're not in the live-dial path at all — no numbers, no carrier, nothing that touches your spam-likely flagging. What they lose is the drill; it queues and they run it later, and the attempt history isn't lost. P1 is a phone number and a human answers seven to seven Pacific.
Buyer
Alright. It's better than I thought. But I have no budget until the new fiscal. Come back in Q1.
Rep
Understood. What changes in Q1 that makes the ramp math better, though? You're bringing on six SDRs in January — that's six people at four to six weeks to first meeting and about half of them washing out before month nine. If we scope it now and start when the money's there, they ramp on the track. If we wait to start scoping in January, you're onboarding that class blind. What if we did the RevOps architecture call in the next two weeks and I hold pricing until your fiscal opens?
Buyer
Do that. Send me the security doc and I'll get RevOps on it. Twenty minutes, not an hour.
Rep
Twenty minutes, architecture and permissions only, nothing about the rep experience — he won't care. I've got two open items for you: Salesforce custom object export, and your security review requirements. Both answered by Thursday. What does the week of the 14th look like — I've got your calendar up, can we pick it now?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “I sell for a living. This demo better be perfect or I'm clipping it and using it as a training example for my team.” | 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 any of the three, use the clip — you'd be right to. But notice that's actually the pitch. Your reps get judged on those same three things and nobody's watching, because your manager sees four calls a week out of two thousand. Can I show you two screens and you tell me if they're the right two? |
| “My reps already juggle six tools. Adoption of a seventh will be zero.” | Then don't add a seventh — I'd rather you didn't. Walk me through what a rep actually touches between the dialer and the CRM in a power hour block. Because if this only works when a rep remembers to open a new tab, you're right and I'd lose the renewal in two quarters. The question I'd want answered before you sign anything is whether the rep has to change what they do — and the honest answer is one Slack message before the block they're already sitting down for. If that's still a seventh tab to you, say so and I'll stop. |
| “We've been pitched conversation intelligence four times. We bought one. It sat there.” | What happened with the one you bought — did nobody listen to the recordings, or did managers listen and nothing changed after? Those are two different failures and they need two different answers. Most teams I talk to had the second one: great transcripts, great dashboards, and an SDR manager with eight reps who still didn't have three hours a week to coach off them. Recordings tell you what happened. What does your team do today between 'that call went badly' and the next live dial? That gap is the only thing I'm trying to fill. |
| “Scoring calls against a playbook 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 your team will know within a week. The reps you want this on are the ones in month two who don't have a script to go off of yet. And here's the part I'd push on: what is she doing on discovery that the new class isn't? Has anyone written it down, or is it in her head? If she leaves in March you lose it. Thirty minutes with her in week one is how it stops living only in her head. |
| “My managers are already underwater. This becomes another thing they don't do.” | Then measure me on their calendar, not their login. If your SDR manager is still spending 90 minutes a week on call review ninety days in, it failed and you should say so on the QBR. What's actually on her week right now — how much is pipeline inspection, how much is one-on-ones, how much is covering an open desk? Because if it's mostly covering a desk, the real problem is the wash-out rate and I'd want to talk about the ramp track before I talk about coaching at all. |
| “We have no budget until the new fiscal year. Come back in Q1.” | Understood. What changes in Q1 that makes the ramp math better? If you're hiring six SDRs in January, the coaching problem gets bigger in Q1, not smaller — that's six people at four to six weeks to first meeting and roughly half not making it to month nine, at eighteen to twenty-five grand a head. I'd rather scope it now and start the day the money's there than have you onboarding a class blind. Can we do the RevOps architecture call this month and hold commercials until your fiscal opens? |
| “Can't I just do this with my managers doing more roleplay in the Monday meeting?” | You can, and some teams do it well. The honest version is: how often does that Monday roleplay actually happen when a client escalation lands at 9am? And how many reps get an at-bat in it — two out of eight, while the other six watch? The thing I'd point at is reps-per-week-at-bats. If your Monday roleplay gives each rep three attempts a month, that's the number to beat. If it's already giving them thirty, you don't need me. |
Questions reps ask about this call
- How long should a sales product demo script be when the buyer is a VP of Sales?
Plan for three workflows completely, not twelve partially. Sixty to ninety seconds of opening contract, then three problem-screen-consequence-check loops, then the four pressure lines — integration, ownership, failure mode, time-to-value — then close. If you talk for more than about ninety seconds straight, you've drifted into tour mode. Sales leaders are the fastest audience in the world to detect a rehearsed path, because they listen to their own reps run one every week.
- What should I do differently when demoing to a Director of Sales Enablement versus a Head of Revenue Operations?
Different demos, same hour. The Director of Sales Enablement wants to see the rubric — is it their talk track, who edits it, what happens when the messaging changes in Q2. The Head of Revenue Operations wants to know what you read, what you write, what object it lands on in Salesforce, whether SSO is Okta, and whether anything you do can affect the dialer. Split it: offer RevOps a separate twenty-minute call that is only architecture and permissions, and say out loud that it will contain nothing about the rep experience. That offer alone buys credibility.
- How do I answer 'will it handle X?' without over-promising?
Slow down and get the specific case first — 'will it handle our qualification framework' is unanswerable until you know whether that's MEDDIC by the book or their own five questions. Then answer one of three ways: yes and here it is live; yes but it's ugly and here's the workaround plainly; or no. Say no when it's no, then ask how often it comes up. Never say 'we can build that' or 'that's on the roadmap' — to a sales leader who has been burned by a vendor, that is the precise sentence that preceded a two-quarter slip.
- What metrics should I put inside the demo script itself?
Use the numbers they already report on, not market claims. Connect rate (under 3% on cold lists), dials-to-connects-to-meetings, meetings booked per SDR per month and held versus booked, time-to-first-meeting in weeks and time-to-full-quota, 90-day wash-out rate, calls reviewed per manager per week, and cost per qualified meeting. State them back as things you heard them say last call, then ask them to correct you. Getting corrected on their own number is a better opening than getting agreement on yours.
- The buyer went quiet halfway through my demo. What do I do?
Stop the demo. Do not push through and do not add features. Say one of: 'I've been talking for a while — is this the part you care about, or should I jump somewhere else?', or 'Let me stop the tour, what's the thing you're worried about that I haven't touched?', or hand them the mouse: 'Do you want to drive? Tell me what to click.' If it's badly off, cut the call honestly and offer to come back Thursday with a demo built for what actually matters. Losing twenty minutes to save the deal is a good trade. Talking faster is what loses it.
- What should the follow-up look like after a demo with a sales leader?
Within 24 hours, and remember this buyer will read your follow-up as a sample of what your own reps send. Include: the two or three open gaps with real answers (not 'checking internally'), the four screens that actually mattered rather than the full recording, the security and architecture doc if RevOps was on the call, and a short list of what you need from them with hours attached — talk track, user list, thirty minutes with their top rep. And the next meeting should already be on the calendar before you hang up. 'I'll follow up next week' is where demos go to die.