How to Run a Sales Demo That Converts: A Step-by-Step Structure, Script, and Checklist

Most sales demos fail in the same way. The rep shares their screen, says "let me show you around", and spends forty minutes touring features while the buyer quietly checks email. The product might be exactly right, but nobody in the room can say which of their problems it solves. A good demo is not a tour. It is a short, structured meeting that proves you understood the buyer's problems and shows, in their language, how those problems go away. This guide gives you the structure, the agenda, the scripts and the checklist to run one.

Quick answer: Run a sales demo in five parts: set the agenda and ask each attendee what they need (3 to 5 minutes), play back what you learned in discovery, show two or three workflows that solve the problems the buyer named using tell-show-tell, stop sharing for questions and objections, then book a dated next step before anyone leaves. Keep it to 30 minutes for one buyer or 45 for a buying group, and send a recap within 24 hours.

Key takeaways

• A demo comes after discovery, not instead of it. If you do not know the buyer's top three problems, you are not ready to demo.
• Show workflows, not features. Two or three stories tied to the buyer's own words beat a full product tour.
• Use tell-show-tell for every segment, and end each one with a check-in question.
• Remote demos fail on mechanics: share a window rather than your whole screen, silence notifications, use clean demo data and keep a backup ready.
• The demo is not over until a dated next step is on the calendar and the recap has gone out.

What is a sales demo?

A sales demo is a meeting in which a seller shows a prospect how the product solves the specific problems uncovered in discovery, using the prospect's workflows, data and vocabulary. It is not product training, which teaches someone to use what they have already bought, and it is not a trial, where the buyer explores alone.

The difference matters because each format has a different job. Here is how the demo sits alongside the meetings around it.

Where does the demo sit in the sales cycle?

The demo comes after discovery and before the proposal. Discovery tells you what hurts, who feels it and what it costs; the demo shows the cure for those specific pains; the proposal prices it. If you skipped discovery, the discovery call guide has the questions and structure to run it first.

The order matters more than it used to, because buyers now arrive having done much of their research alone. In a Gartner survey of 646 B2B buyers, published in March 2026, 67% said they prefer a rep-free buying experience. Gartner's conclusion from the same research is that buyers need "value clarity", which it describes as a clear understanding of how a solution improves outcomes in their specific role and business context. That is a good definition of what a demo is for. A buyer who could have watched your product video on their own has given you thirty minutes; the demo has to deliver something the video could not, which is their problem solved on screen.

There is also evidence that buyers still want a human at this point. A separate Gartner survey of 645 B2B buyers, published in May 2026, found that 69% prefer to validate AI-generated insights with sales reps. Buyers come to a demo to check what they think they already know. Treat it as a validation meeting, not an introduction.

What if the prospect asks for a demo on the first call?

It happens constantly, especially with inbound leads who booked from a "Book a demo" button. Do not refuse, and do not launch a full tour either. Run a discovery-first demo:

1. Spend the first eight to ten minutes on discovery questions: what prompted the request, how they handle it today, what is not working.
2. Show only the one or two workflows that match their answers.
3. Close by proposing a tailored demo for the wider team, built around what you just learned.

Answering an inbound request quickly matters as much as the format. A prospect who waits days for a reply has time to book a competitor, which is the argument of the speed-to-lead guide.

How do you prepare for a sales demo?

Preparation is what turns a tour into a tailored demo. Most of it is choosing what not to show. Work back from the meeting with this checklist.

Build the demo around stories, not features

A demo story is one end-to-end workflow that starts with a problem the buyer named and ends with the outcome they want. "Here is our reporting module" is a feature. "Here is what month-end looks like when the numbers are already reconciled" is a story.

For each story, write three lines before you build anything:

• The pain, in their words: "Approvals sit in a manager's inbox for a week."
• The workflow you will show: an invoice arriving, being routed, being approved from a phone.
• The outcome: "Nothing waits in an inbox; you can see who has it and for how long."

If you cannot write the first line from your discovery notes, that story does not belong in the demo.

Decide the next step before the demo, not during it

Know what you will ask for at the end: a technical session with IT, a trial with success criteria, a pricing call with the budget holder. A rep who decides the next step in the last two minutes usually ends up with "send me some information", which is not a next step. A clear meeting agenda sent in advance makes it easier, because everyone arrives knowing the call ends with a decision about what happens next.

What should a sales demo agenda look like?

Here is a minute-by-minute agenda for the two most common lengths. The 45-minute version adds a third story, usually for a second stakeholder, and a longer playback for a bigger room.

How long should a sales demo be?

There is no reliable published benchmark for the ideal length, and figures you see quoted vary by product, deal size and audience. A practical rule: 30 minutes for one decision maker and a focused product, 45 minutes for a buying group or several workflows, and 60 minutes only when a technical team has asked for a deep dive. Plan for the screen share to end with at least five to ten minutes left. Finishing early is a gift; running over makes the next step feel like an imposition.

How do you run the demo, step by step?

Here is the flow from the moment you join to the moment the call ends, with the scripts that go with each step.

1. Open and set the agenda. State the time, the plan and the end point, then ask each attendee what they need.
2. Play back discovery. Summarize the problems you heard and ask the room to confirm, correct and rank them.
3. Run each story with tell-show-tell. One workflow per problem, with a check-in question after each.
4. Transition deliberately. Name what you just covered and what comes next, so nobody gets lost.
5. Stop sharing for questions. Faces on screen, not your product, while you discuss objections.
6. Agree the next step. Ask about their evaluation process, propose a specific next meeting and book it before anyone leaves.
7. Send the recap within 24 hours. Their priorities, what they saw, what you owe them, the next step.

Opening script

"Thanks for making the time, everyone. We have 30 minutes, and I'd like to keep the last ten for your questions and for agreeing what happens next. Here's the plan: two minutes playing back what I heard from Sam on our call last week, so you can correct me, then the two workflows that map to those problems, then it's over to you. Before I start, Priya and Tom, what would make this half hour worth it for you?"

If you record the call, say so in the opening: "I have our notetaker on so I can focus on you rather than typing. You'll see it in the participant list, and if anyone would rather I didn't record, tell me and I'll remove it." Whether you need consent, and from whom, depends on where the participants are; the guide to whether it is legal to record a meeting covers the rules.

Discovery playback script

"Here's what I heard. One: approvals take about a week because invoices wait in a manager's inbox. Two: month-end reporting takes two people three days. Three: you've had late-payment fees twice this quarter. Did I get that right? Has anything changed since we spoke? And of those three, which matters most to the people on this call?"

The playback does two jobs. It proves you listened, and it lets the room re-rank the priorities, which tells you which story to lead with. If someone says "actually, the bigger issue is...", you have just learned more than the whole demo would have taught you.

Tell-show-tell example

Tell-show-tell is a three-beat pattern for each demo segment: tell the buyer what they are about to see and why it matters to them, show it along one clean path, then tell them what they saw and check that it lands.

Tell (20 seconds):

"You said the biggest delay is invoices sitting in a manager's inbox, and that's where the late fees came from. I'm going to follow one invoice from the moment it arrives to the moment it's approved. Watch for where the waiting disappears."

Show (3 to 5 minutes):

"Here's an invoice arriving by email. It's over five thousand, so it routes to Priya automatically. She gets a reminder after 24 hours if she hasn't acted. And here she is approving it from her phone, in about ten seconds."

Stay on one path. Do not open side menus, settings or "one more thing". Every detour is a chance for the buyer to lose the thread.

Tell (30 seconds), then a check-in question

"So what you just saw: the invoice never sat in an inbox, the reminder went out without anyone chasing, and Tom can see the whole history in one place. Is that the delay you described, or is there a step in your process I've missed?"

Transition lines

Transitions are where demos lose people. Name what you finished, name what comes next, and connect it to a person in the room.

• "That covers the approval delay. The second thing you mentioned was month-end reporting, so let me show you that next."
• "Before I move on, does that match how your team works today?"
• "I'm going to skip the setup screens. They take ten minutes, once, and you'll never see them again. Here's what your team sees every day."
• "Tom, this next part is the one you asked about."
• "We have ten minutes left, so I'm going to stop sharing and hand it over to you."
• "What would you need to see to be confident this works for your team?"

Close and next-step script

"Based on what you've seen, how does this compare to the way you handle it today? ... When your team evaluates something like this, what usually happens next, and who else needs to be involved? ... Here's what I'd suggest. I'll send a recap and pricing for 25 users by tomorrow. Let's put 30 minutes on the calendar with your IT lead to go through the security questions. Does Tuesday or Thursday afternoon work?"

Book the meeting while everyone is still on the call. "I'll send over some times" is how a warm demo becomes a cold deal.

How do you tailor a demo to different personas?

Every attendee is asking a different version of "is this worth it?" Tailoring means showing each of them the part of the product that answers their version, which is exactly what Gartner means by value clarity: understanding how the solution improves outcomes in each person's own role.

You will rarely have all five in one room, and you should not try to serve all five in one demo. Lead with the persona whose problem is ranked first, give the second persona its own story, and move the rest to a follow-up session.

How do you run a demo over Zoom, Google Meet or Teams?

Remote demos fail on mechanics more often than on content. A notification from another client, a cluttered desktop or a frozen screen share can undo a well-built story. Run through this before every call.

Share a window or tab, not your whole screen

All three major platforms let you share a single application window instead of the whole desktop: see Zoom's screen-sharing guide, Google Meet's presenting help, which also recommends sharing a specific window or tab rather than the meeting window to avoid a mirror effect, and Microsoft's guide to presenting in Teams. Sharing one window means the buyer never sees your inbox, your other tabs or your desktop files, and you can glance at notes in another window without them knowing.

Silence everything

Turn notifications off at the operating-system level, not just in your chat app. macOS has a setting to pause notifications when you mirror or share the display, described in Apple's notification settings guide. If you share computer sound in Teams to play a video, Microsoft notes that all sound from your computer, notifications included, will be audible in the meeting, so mute chat sounds first.

Use a clean demo environment

• A separate browser profile for demos, with no bookmarks bar, no saved autocomplete entries and no other client names in the history.
• Demo data that looks like their world, never real customer data. Plausible names, their industry, numbers in the right range.
• A reset routine, so every demo starts from the same state rather than wherever the last one left off.
• Bigger text. Zoom the browser to 125 to 150 percent. Many buyers are watching on a laptop with your window shrunk to half the screen.

Prepare a backup

Keep a short screen recording or a set of screenshots for each story, and a second device signed in as an attendee so you can see what they see. If something breaks, say so in one sentence, switch to the backup and keep the story moving. Debugging live in front of a buying committee is the one thing worse than the glitch.

Camera and presence

Camera on at the start and end, and ideally throughout. Put it at eye level and look at it, not at the faces, when you make the key point of each story. Consider hiding self-view once you are framed: the Stanford researcher Jeremy Bailenson argued in a 2021 paper that constantly seeing your own video acts like "an all day mirror" that increases self-evaluation, and suggested that self-view be hidden once people know they are framed properly. He is clear that these are arguments still to be tested, not findings, but most presenters find it easier to focus on the buyer without their own face in the corner.

Record it, visibly

A recording lets you share the demo with stakeholders who missed it and review it later for coaching. Tell everyone at the start, and keep the recording visible rather than hidden. An AI notetaker that joins as a named participant does that by default.

How do you handle a demo with multiple stakeholders?

Multi-stakeholder demos are the norm in B2B, and they are harder than they look. A Gartner survey of 632 B2B buyers, published in May 2025, found that 74% of buyer teams showed "unhealthy conflict" during the decision process, and that buying groups which reach consensus were 2.5 times more likely to report a high-quality deal. Gartner put the size of buying groups at five to 16 people across as many as four functions.

That changes the job. In a group demo, you are not only showing the product; you are helping the buyers agree with each other. Here is how.

1. Map the room with your champion first. A 15-minute call beforehand: who is coming, what each person cares about, who has the final say, and where people disagree.
2. Ask everyone their goal at the start. Write each answer down where you can see it, and refer back to it by name during the demo.
3. Assign each story to a stakeholder. "Priya, this one is yours." People pay attention to the part that is about them.
4. Name disagreements neutrally. If the finance lead wants control and the team lead wants speed, say so: "It sounds like the priorities differ slightly. Shall I show how both would work?" Surfacing conflict in the demo beats discovering it in a stalled deal.
5. Move deep-dives to separate sessions. Security reviews and detailed integration questions belong with the people who care about them, not in front of the whole group.
6. Close on the decision process. Ask who else needs to see it, what the evaluation looks like and when they plan to decide.

How do you handle questions and objections during a demo?

Questions are the best part of a demo, because they tell you what the buyer is really thinking. Stop sharing when you take them, so the conversation is about faces rather than your product.

Use the same four moves for every objection:

1. Acknowledge it without arguing: "That's a fair concern."
2. Clarify what is behind it: "When you say it looks complicated, is that for you or for the team who'd use it daily?"
3. Answer briefly, or park it with a named owner and a date if it needs a specialist.
4. Confirm it landed: "Does that answer it, or is there more to it?"

A useful way to sort demo objections is into six families: pricing, timing, competitor, authority, need and trust. The sales objection handling guide has responses for each one.

Three rules for the live moment:

• If the product does not do it, say so. "No, we don't do that today. Here's how customers in your position handle it." A confident no builds more trust than a vague maybe that unravels in the trial.
• Answer pricing questions directly. If someone asks the price halfway through, give the structure or a range, then return to the demo. Dodging makes the price the only thing anyone remembers.
• Do not open new screens to answer an aside. Note it, answer it at the end or in the follow-up, and keep the story intact.

What should you do after a sales demo?

The demo is not finished until the recap is sent and the next step is on the calendar. Send a follow-up within 24 hours, and the same day if you can, while the details are fresh for everyone. The guide to follow-up emails after sales meetings has templates for every outcome; here is the one for a demo.

Demo recap email

Subject: Recap: today's demo and next steps

Hi [first name],

Thanks to you, [name] and [name] for the time today. Here's a short recap.

What you told us matters most:

• [Priority 1, in their words]
• [Priority 2, in their words]

What you saw:

• [Workflow 1]: [one-line outcome]
• [Workflow 2]: [one-line outcome]

What I owe you:

• [Answer to the open question], by [date]
• [Pricing or proposal], by [date]

Next step: [meeting] with [names] on [date and time]. The invite is on your calendar.

[Signature]

Then three internal jobs:

• Log it. Priorities, attendees, objections, next step, in the CRM, the same day.
• Debrief for five minutes with anyone else from your side who attended: what landed, what did not, who in the room is for or against.
• Brief the next meeting. If the next step is a technical session, the solutions engineer should know exactly what the buyer cares about before it starts.

How do you review demo recordings and coach?

Recorded demos are the best coaching material a sales team has, provided you review them with a method rather than a vague "how did it go?".

Talk ratio is different on demos

Talk-to-listen ratio is the share of a call the rep spends speaking. On a discovery call the prospect should talk more; on a demo the rep naturally talks more, because they are presenting. The talk-to-listen ratio guide explains why one number is never enough. For demos, two signals matter more than the ratio itself: the length of the longest monologue and whether the rep asks a check-in question after every story.

PepoSmart's coaching scorecard, whose formula is published on the product facts page, scores four components worth 25 points each: talk ratio, questions asked, filler words and engagement. Full talk-ratio marks go to a host share of 40 to 50 percent, and the engagement component loses points for monologues over 45, 60, 90 and 120 seconds and for a host talk share above 65, 75 or 85 percent. Because those bands reward balanced conversations, expect demos to score lower on talk ratio than discovery calls, and compare demos with demos rather than with discovery. The score measures conversational mechanics, not whether the demo was any good, so treat it as the reason to open the recording rather than a verdict.

A demo review rubric

A weekly coaching routine

1. Pick one demo per rep per week, mixing calls that moved forward with calls that stalled.
2. Have the rep review it first, watching the first five and the last five minutes before the coaching session.
3. Open the scorecard and check the longest monologue and the question count before the overall score.
4. Find one moment to praise and one to change, each with a timestamp.
5. Agree one behavior to try on the next demo, and check it the following week.

One behavior at a time works. A list of eight fixes from a single review mostly produces a nervous rep.

What are the most common sales demo mistakes?

• Demoing without discovery. You end up showing what you think is impressive rather than what they need.
• The full tour. Every feature, every menu, in the order the product was built. Show stories instead.
• Starting with setup screens. Lead with the outcome the buyer cares about; configuration can wait.
• Monologues. Ten minutes without a question means you have lost the room, even if nobody says so.
• Ignoring the quiet stakeholder. The person who says nothing for 30 minutes is often the one who says no afterwards. Ask them directly.
• Messy screens. Notifications, other clients' names and forty open tabs undermine trust in seconds.
• Bluffing. Claiming a feature exists, or will exist soon, when you are not sure. It comes out in the trial.
• Running over. Taking the last ten minutes of showing time from the next step.
• No next step. "Send me some information" is a polite exit, not a plan.
• A slow follow-up. A recap that arrives three days later tells the buyer how the rest of the relationship will go.

How does PepoSmart fit into the demo workflow?

PepoSmart is an AI scheduling and meeting-intelligence platform, and it covers the parts of a demo that happen around the call: booking it, preparing for it, recording it and following up. It does not run the demo for you. Here is how each step maps.

Booking the demo. A round-robin event spreads inbound demo requests across the team, choosing a host who is free at that time and taking into account their calendar conflicts, meeting limits and recent assignments. Round-robin needs team seats, which come with every paid plan (Starter and above); the round-robin scheduling guide explains the setup. Intake questions on the booking page (single line, multi-line, radio, checkbox, dropdown or phone number) can ask the one thing you need before the demo, such as "What would you most like to see?". Confirmation and reminder emails with reschedule and cancel links go out on every plan, with reminder timings set per event, which is the core of the guide to reducing no-shows. A Zoom, Google Meet or Teams meeting is created for each booking, so the joining link is on the calendar invite.

Preparing. AI call prep assembles a briefing for an upcoming meeting from the meetings PepoSmart recorded with that contact: previous summaries, the sentiment trend, commitments still open and suggested talking points. If the discovery call was recorded, one click on the upcoming demo puts that history in front of you before you join. It is available on Starter and above, and CRM deal context on the sheet needs Professional and above.

Recording. The AI meeting notes notetaker joins Zoom, Google Meet and Microsoft Teams as a visible participant and produces a recording, a speaker-labelled transcript, a summary with a timestamped view, action items with an owner and priority, a sentiment and buyer-intent read and a coaching scorecard. If someone removes it from the call by mistake, it can be re-invited with "Rejoin notetaker", and the parts are stitched into one transcript. Objections are flagged in the same six categories listed above.

Following up. After the call, an AI follow-up email draft is generated from the transcript, matched to what you promised, with placeholders for anything the AI cannot know. You review, edit and send it; nothing goes out without you. On Professional and above, the meeting and approved action items sync to a connected CRM such as HubSpot or Salesforce, and suggested deal-stage changes wait for your approval. The sales solution page shows the whole flow.

What PepoSmart does not do

Being clear about the limits saves you a wasted trial.

• It does not build or host your demo. There is no demo-environment, sandbox or interactive product-tour builder. Your demo still runs in your own product.
• It cannot record phone or in-person demos. The notetaker joins online meetings only: Zoom, Google Meet and Microsoft Teams.
• Recordings are not unlimited. Every plan, including Free, includes 2 AI recordings for the lifetime of the account. Beyond those, paid plans buy credit packs (10 recordings for $19, 20 for $27 or 40 for $39), and each credit is valid for 30 days. On Free, recordings are deleted after 7 days. Current details are on the pricing page.
• The score is not a judgment of the demo. It measures talk ratio, questions, filler words and engagement. It cannot tell you whether the product fit or whether the deal will close.
• Objection detection is a prompt, not a verdict. It can miss implicit objections and flag phrases that were not meant as one.
• Call prep needs history. For a brand-new contact with no recorded meetings there is little to brief you on beyond the booking details.
• Consent is your responsibility. The notetaker is visible, but any notice or consent your jurisdiction or organization requires is up to the host.

We also do not publish a figure for how much any of this raises demo conversion, because a defensible number needs a controlled study we have not run. And a live demo is not always the right tool. For a low-priced, simple product, a recorded walkthrough or a free trial may serve buyers better than a meeting, especially given how many now prefer to buy without a rep.

Printable sales demo checklist

Copy this into your notes before every demo.

Before

• Discovery done, and the top three problems written down in the buyer's words
• Attendees and roles confirmed; champion briefed on who cares about what
• Two or three stories built: pain, workflow, outcome
• Demo data realistic and anonymized; account reset to its starting state
• Dry run done, timed, out loud
• Backup recording or screenshots ready for every story
• Next step decided: what you will ask for at the end
• Reminder sent with the joining link

One hour before

• Notifications off at the operating-system level
• Unneeded apps and tabs closed; demo browser profile open
• Browser zoomed to 125 to 150 percent
• Audio, camera and window sharing tested

During

• Agenda, end time and each attendee's goal agreed
• Discovery played back and priorities ranked
• Tell-show-tell for every story, with a check-in question
• Screen share stopped for questions
• Objections clarified before answering
• Next step booked before anyone left

Within 24 hours

• Recap sent: priorities, what they saw, what you owe, the next step
• CRM updated
• Five-minute internal debrief done
• Recording reviewed for one coaching point

Summary

A sales demo that moves deals forward is short, specific and built on discovery: an agreed agenda, a playback of the buyer's problems, two or three stories told with tell-show-tell, an honest Q&A with the screen share off, and a dated next step booked on the call. Get the remote mechanics right, treat multi-stakeholder demos as consensus-building rather than presenting, and send the recap within 24 hours. Then review the recording and pick one thing to improve. If you want the booking, recording and follow-up handled around your demos, create a free PepoSmart account and see the pricing page for which features come with each plan.