Why Your Demo Isn't Closing (and the 3-Question Fix)

A sales demo is a live product walkthrough whose only job is to show a specific prospect exactly how your product solves the problem they came in with — not to showcase everything you have built.

TL;DR: Most demos fail at the close because discovery happens after the demo, not before it. Ask three questions before you share your screen: what are they trying to fix, what have they already tried, and what does success look like in concrete terms. Then demo exactly that — nothing more, nothing else.

What a demo is actually for

A demo is not a product tour. Its only job is to answer one unspoken question: does this solve the thing I actually came here about?

If the prospect cannot answer yes within the first five minutes of seeing the product, you have lost them — even if they stay politely for the rest of the session. Most technical founders approach demos as product showcases because that is how they think about their own work. They have spent months building something, and the instinct is to show all of it. But the prospect did not come to see what you built. They came because something in their current workflow is broken or slow or expensive, and they want to know whether your product fixes it.

When you open with "let me show you everything we can do," you have made the prospect responsible for doing their own mapping — connecting your feature list to their specific problem. That cognitive work is harder than it sounds, and most prospects will not do it under the social pressure of a live call.

The discovery gap

The core reason demos fail at the close is a discovery gap — the demo happened before you knew enough to make it relevant.

The broken sequence: the prospect books a call, you share your screen, you walk through everything you have built, they say "this looks impressive — I'll need to think about it," and then they disappear. The problem is not the product and not the prospect. The problem is that the demo was never connected to anything they said.

The fixed sequence: the prospect books a call, you spend 10-15 minutes on three questions before you touch your screen, you demo only what maps to their answers, they see their specific problem being solved, and you close with a concrete next step. The upfront investment in discovery costs you nothing and does more work than any individual feature you could have shown them.

Discovery also sends a signal that most sales processes fail to communicate: you are interested in their problem, not just in running a demo. That is a differentiation point on its own in a world where most SaaS demos are identical feature tours that ignore what the prospect actually said on the intake form.

The 3 questions to ask before you share your screen

These are the underlying questions, not script lines. The phrasing adapts to the conversation — what matters is getting genuine answers to all three.

Question 1: What specifically are you trying to fix?

Not "what are your biggest challenges" — that is too broad and produces a list rather than a problem. Not "what brought you here today" — that is too open and often yields a polite non-answer. You want the specific situation that caused them to book this call. "What's the thing that's breaking right now that you'd like to stop doing?" or "What made you reach out this week versus last month?" Pin it to something recent and concrete. Vague discovery produces vague demos.

Question 2: What have you already tried?

This is the most underrated question in the sequence, and most founders skip it. What they have already tried tells you three things simultaneously: the scope of the problem (serious enough to attempt a solution), what they value and prioritise (based on what they chose to try), and where prior solutions fell short — which is almost always where your product needs to demonstrate its value in the demo.

• If they tried a manual process: show exactly how your product eliminates those manual steps.
• If they tried a competitor: show the specific thing the competitor failed to do.
• If they tried nothing: flag this. Low prior investment often means the pain is not yet severe enough to generate a close — calibrate your expectations and your proposed next step accordingly.

Question 3: What does success look like in concrete terms?

Not "what outcome are you hoping for" — that gets vague answers about wanting things to be better or faster. You want a number or a description specific enough to know when it has been achieved. "What would you want to be able to say is true in 90 days that isn't true today?" Push for specifics. If they say "we want things to be faster," ask how much faster and how they would know. The answer to question 3 is the benchmark your demo needs to directly address.

The demo itself

Once you have the three answers, planning the demo takes thirty seconds. Open the view, trigger the workflow, or show the report that speaks directly to what they described. Demo only what maps to one of their three answers. Features that are not relevant to this person's problem add cognitive load, not value — and cognitive load at the moment of close is your enemy.

The length target for most demos is 20-30 minutes, not 60. A prospect who has seen exactly what they needed to see is far easier to close than one who has seen everything but is not sure what to prioritise. The length of a demo is not a signal of thoroughness — it is a signal of how well you understood the problem before you opened your screen.

What to do when discovery reveals a poor fit

Sometimes the three questions reveal that this prospect's problem is not what your product was built to solve. The right move is to stop the demo and say so directly.

"Based on what you've described, I'm not sure we're the right fit — the challenge you're working on is X, and we're primarily built for Y. I'd rather be honest with you now than take another 30 minutes of your time."

Prospects consistently respect this response. It demonstrates that you are not trying to push them through a funnel regardless of fit. It also shortens your sales cycles by removing prospects who would churn within 90 days anyway. A short, honest conversation about fit is more valuable than a full demo that ends in a polite six-week silence.

End with a concrete proposed next step

The most common close after a demo: "Any questions? Feel free to reach out if you want to move forward." That is not a close. That is an invitation to disappear politely.

Every demo should end with a specific proposed next step — not a question, a proposal. "Based on what you've described, the right next step is [X]. Can we do that now, or would [specific day] work better?" The next step could be a trial setup, a proposal sent that afternoon, a second call with a technical stakeholder, or a decision on the current call. Whatever it is, name it and propose it. Make the prospect's job a yes or a specific objection — not a decision about whether to engage at all.

Before and after: the same demo, two outcomes

BEFORE (feature tour, no discovery):

The founder shares their screen immediately after pleasantries. They start with the dashboard overview, move through each main feature, show integrations, demonstrate the export function. The session runs 55 minutes. The prospect says: "This is really impressive — I need to loop in my partner. I'll follow up." They do not follow up.

AFTER (3 questions first, targeted demo):

The founder opens with: "Before I show you anything — what specifically made you reach out this week?" The prospect mentions the team spends 6 hours every week pulling reports manually. The founder asks what they tried: "We set up Zapier but it kept breaking." What does success look like? "The report just runs itself on Monday morning and is in the inbox before we start work."

The founder opens the automation builder, sets up exactly that workflow in 4 minutes, shows the Monday morning email preview, and says: "Is that the thing?" The prospect says yes. The founder says: "We can have this live for your team by Thursday. Want to start setup now or confirm budget first?" Closed in 22 minutes.

Demo approach comparison

Approach	Discovery	Demo length	Typical outcome
Full feature tour, no discovery	None	50-60 min	"I'll think about it" — prospect disappears
Targeted demo, 3 questions first	10-15 min upfront	20-30 min	High close rate — they saw their problem solved
Discovery reveals poor fit	10 min	0 min demo	Short conversation, clear exit, no wasted time
Discovery skipped, wrong section shown	None	35 min	Polite decline, no proposed next step

Before the next demo, run the one-line version of what you sell through the Value Proposition Tester — named audience, concrete outcome, no jargon. If it does not survive one line, it will not survive a screen share. Free, runs in your browser, nothing to book.