All field notes

How-to ·

How to run a sales demo that follows discovery

How to run a sales demo: replay the buyer's problem, show the two or three workflows that fix it, check reactions as you go, and close on a next step.

To run a sales demo, open by replaying the buyer's problem from discovery, show only the two or three workflows that solve it, check the buyer's reaction after each one, and close on one dated next step.

What a demo is for

A demo is the meeting where the buyer sees whether your product solves the problem they described in discovery. It is the second or third conversation in most B2B deals, and it works only when it is built on what discovery found.

The account executive usually runs it. On a technical product, a sales engineer drives the screen while the account executive holds the story and the questions. A first demo runs 30 to 60 minutes, and about half the preparation should happen before anyone opens the product.

The most common way a demo fails is that it is the same for every buyer. A rep who clicks through every screen in the same order is showing the product, and the buyer has to do the work of finding their own problem in it. Most of them will not. A demo that follows discovery runs the other way: it starts from the buyer's problem and shows the shortest path from that problem to a fix. Where the line between the two meetings falls is covered in discovery call vs demo.

Who should be in the room

The buyer side of the room decides what the demo needs to prove. If discovery was with one operations lead and the demo has her, her finance director and someone from IT, three different questions are now in play. The operations lead wants to see the workflow. The finance director wants to know what it will save. IT wants to know what it touches.

Ask before the demo who is coming and what each person wants to see. A short email works: "To make the best use of the hour, could you tell me who'll join and what each person most wants to see?" If you cannot find out, start the demo by asking each person in turn. For a demo with a full buying committee, see how to run discovery with a buying committee, because the same rule applies: each person needs a reason to be there.

On your side, keep it small. The account executive, and a sales engineer if the product needs one. A manager or a product specialist joins only when a buyer has asked a question that needs them.

How to run the demo in seven steps

Each step below can be checked before the next one starts. If step one fails, the rest of the demo is guesswork.

A demo in three parts
  1. BeforePlan from discovery
    • Confirm the problem in writing
    • Pick two or three workflows
    • Build their data into it
  2. DuringShow and check
    • Replay the problem first
    • One workflow per problem
    • Ask after each one
  3. AfterCommit
    • Agree what was proven
    • One dated next step
    • Summary the same day
  1. Confirm the problem in writing before the demo. Send the buyer a short summary of what you heard in discovery: the problem, what it costs, who feels it and when it needs fixing. Ask them to correct it. A buyer who replies with changes has told you what the demo must show. The discovery call guide covers how to get those answers.
  2. Pick two or three workflows. Choose only the parts of the product that solve the problems in the summary. Most products have many features, and most buyers care about three. Write down what each workflow has to prove, in the buyer's terms, before you build anything.
  3. Build their world into the demo. Use their company name, their terms and data that looks like theirs. A logistics buyer should see depots and routes. A demo account full of fictional widgets makes the buyer translate everything you show.
  4. Open by replaying the problem. Spend the first five minutes saying back what you heard in discovery and asking whether it is still right. Then say what you will show: "I'll show you three things, each one tied to something you told me. Stop me whenever." Skip the company history and the logo slide.
  5. Show one workflow per problem, and stop after each. For each workflow, name the problem it addresses, show the shortest path through it, then stop and ask. "How does that compare with how your planners do it today?" is a better check than "Does that make sense?", because it gets the buyer talking about their own work.
  6. Handle questions when they come. If a question belongs to a later workflow, say so and come back to it. If it needs a feature you do not have, say that plainly and ask how much it matters. A buyer will forgive a gap. They will not forgive a dodge they catch later.
  7. Close on what was proven and one next step. Ask the room which of the problems the demo solved and which are still open. Then propose one next step with a date and named people: a technical review, a trial, a call with finance. Send a summary the same day listing what was shown, what is open and the date.

An example demo

This example is illustrative. A rep selling route planning software runs a demo for Arrowmere, a 600-person logistics firm, after a discovery call with the head of operations.

Before. The rep emails a summary of discovery: routes are built by hand each evening in four depots, it takes planners about two hours a night, and late deliveries rise when a planner is out. A large retail customer is watching on-time delivery, and its contract renews in the spring. The head of operations replies with one correction: the IT lead will join and wants to see how orders get into the planner. The rep adds that as a third workflow.

Opening. The rep spends four minutes on the summary, then says: "I'll show you three things. How a depot plans tomorrow's routes from tonight's orders. What happens when a planner is out. And how orders come in from your system, which I know your IT lead wants to see."

Workflows. The first workflow uses a demo depot with the same number of vans as Arrowmere's largest. After it, the rep asks the head of operations how long that would have taken her planners. She says most of an evening. The second shows another depot's planner covering a colleague's routes. The third shows the order import, and the IT lead asks about security. The rep says she will send the security documentation and set up a call with their technical team.

Close. The rep asks which of the three problems the demo solved. The head of operations says the first two, and that the third depends on the IT review. The next step is a technical call the following week with the IT lead and the rep's sales engineer, and a trial in one depot if the review passes.

The rep showed three workflows in 40 minutes, and every one of them traced back to something the buyer had said.

Where demos go wrong

  1. The demo skips discovery. A buyer asks for a demo on the first call and the rep agrees. Without discovery, the rep cannot know which three workflows matter, so they show all of them. If a buyer insists on a demo first, keep it short and ask the discovery questions as you go.
  2. The rep talks for 30 minutes without a check. A buyer who has not spoken for ten minutes has stopped listening or is waiting for you to finish. Stop after each workflow and ask a question about their work.
  3. The demo shows features nobody asked about. Every extra feature costs attention and invites a question about something the buyer does not need. If it does not trace to the summary, leave it out and mention it in the follow-up.
  4. The demo ends with "any questions?". That question closes the meeting with no decision. Ask which problems were solved, then propose a dated next step.
  5. Nobody owns what happens after. Without a written summary and a named next step, the demo fades by the next week. The summary is what the buyer forwards to the people who were not there.

Practicing the demo

A demo is a performance with a script that changes for every buyer, and most reps rehearse it alone, if at all. The parts worth practicing are the opening replay, the check after each workflow and the close. Those are the moments a rep is most tempted to skip.

For a live deal, the useful preparation is talking through the plan for the specific demo: what discovery found, which workflows map to which problems, and what the close will ask for. Caty, our AI sales expert, works through a deal by voice or video on a call, in the team's own method, whether that is MEDDPICC, SPIN, Sandler or a house method. Start a call with Caty in one click before the demo and say the plan out loud. Teams selling with Gap Selling work the same plan with Keenan. For how this fits into running live deals across a team, see drive deal execution, or talk to us.

FAQ

How long should a sales demo be?

A first B2B sales demo usually runs 30 to 60 minutes. Plan to show two or three workflows and leave at least ten minutes for questions and the next step.

What should you do before a sales demo?

Send the buyer a written summary of what discovery found and ask them to correct it. Then choose the two or three workflows that solve those problems and build the buyer's terms into the demo.

How do you start a sales demo?

Open by replaying the buyer's problem from discovery and asking whether it is still right. Then say which workflows you will show and how each one connects to what they told you.

How do you keep buyers engaged in a demo?

Stop after each workflow and ask how it compares with how they work today. A question about their own process gets a longer answer than asking whether something makes sense.

What do you do if a buyer asks for a feature you do not have?

Say plainly that the product does not do it today and ask how much it matters to their decision. An honest answer early costs less than a gap discovered after the contract.

How do you end a sales demo?

Ask the buyer which of their problems the demo solved and which are still open, then propose one next step with a date and named people. Send a summary the same day.

Put an expert on your deals.

Talk to Keenan about a live deal for free, or talk to us about experts for your team, your product or your coaching business.

Talk to us