How to qualify leads in a demo

Qualifying leads in a demo is about reading signals and asking branch questions, not running a checklist while someone watches your screen. The goal of demo qualification is not perfect discovery. It is deciding the next move before the call ends. Here's the script: what to ask, what to watch, and how to route every lead before you hang up.

Qualify for the next step, not for a perfect fit

What you are actually trying to learn on the call

Four things tell you whether a demo lead is worth following up: ICP fit, budget, authority, and timing. You do not need to know all four in depth. You just need enough to decide whether to advance, nurture, or close the loop cleanly.

ICP fit tells you whether the problem you solve is the problem they have. Budget tells you whether they can actually buy. Authority tells you whether the person on the call can say yes, or whether they need to bring someone else in. Timing tells you whether this is a now problem or a someday problem.

A lot of founder-sellers make the same mistake: they treat qualification like a pre-call checklist. The demo gives you something better. You can watch what the prospect does and ask questions tied to what they are reacting to. That is usually faster and less awkward than interrogating someone before you have shown them anything.

Why a live demo beats a static discovery list

BANT (Budget, Authority, Need, Timeline) and MEDDIC are useful frameworks for organizing what you want to learn, but they assume a linear conversation. A live demo is not linear. The prospect clicks something unexpected, asks a question you did not anticipate, or goes quiet on a screen that usually gets the most engagement.

Those moments matter. A prospect who immediately asks "can this connect to our existing CRM?" is signaling interest and a workflow they may need to replace. A prospect who goes quiet on the pricing screen is probably doing mental math. A prospect who says "my manager would love this" just told you they are not the decision-maker.

Branching lets you use those signals. A rigid script ignores them.

Use the demo qualification script to ask better opening questions

The opening question that tells you if the pain is real

Start here: "Before I walk you through this, what made you want to look at this today?"

A strong answer is specific: "We're losing deals because prospects can't see the product before a sales call" or "our current demo tool breaks every time we ship." Vague answers like "just exploring" or "someone forwarded the link" tell you the pain is not active yet. That is not a disqualifier, but it changes the branch.

If the answer is specific, you have a live problem to solve on the call. Bring it up again later. If it is vague, your job in the first ten minutes is to surface a problem, not assume one is already there.

How to branch when the prospect gives you a partial answer

Partial answers sound like: "We've been thinking about improving our demos" — directional, but not urgent. Do not push harder with a follow-up interrogation. Instead, tie the next question to what they are seeing on screen.

When you get to a screen that shows the feature most relevant to their use case, ask: "Is this the part that's most broken for you right now, or is it something else?" That question fits the moment, and it forces a choice. If they say "actually it's more about X," you have just learned the real pain without a cold probe.

The rule is simple: if the first answer is thin, let the demo surface the problem before you ask again. PostHog's lead scoring handbook makes the same point. Routing decisions improve when they are tied to demonstrated behavior, not just stated intent.

The line that keeps the call from feeling like an interrogation

At some point in the first third of the demo, say this: "I'm going to ask you a few questions as we go — not to be nosy, but so I can show you the parts that are actually relevant to where you are right now."

That one sentence changes the tone of everything that follows. You are not interrogating. You are trying to make the demo useful. Most prospects respond well to that because it signals you are not going to waste their time on features they do not care about.

Read budget, authority, and timing from the demo behavior itself

The four signals that show up before anyone says the words

Budget, authority, urgency, and fit all show up in behavior before the prospect names them.

• Budget: they ask about pricing unprompted, or they ask about contracts, annual vs. monthly, or "how does this compare to what we're paying now." That is someone who has a number in mind.
• Authority: watch who is in the room. If someone joins late and starts asking the implementation questions, that is often the real decision-maker. If the person you are talking to keeps saying "I'll need to check with my team," they are a champion, not a closer.
• Urgency: they bring up a deadline — a launch, a board meeting, a quarter-end — without being asked. That is a live trigger.
• Fit: they start mapping your product to their workflow out loud. "So this would replace the thing we're doing in Notion" means they are already picturing it in place.

What screen-sharing tells you that words do not

Cursor behavior, note-taking, and side questions are all intent signals during a live demo. A prospect who pauses on a specific screen and asks a detailed implementation question is more qualified than one who says "this looks great" and keeps scrolling.

Watch for the moment they stop and lean in, the moment they go quiet after a pricing reveal, and the moment they pull in a colleague mid-call. Those are all useful. Note-taking is another strong signal. If they are writing things down, they are already thinking about implementation.

Use the demo to route qualified, maybe, and no-fit leads

The branching script for a clear yes

A qualified lead shows ICP fit, has a live problem, shows budget signals, and either has authority or is clearly connected to the decision-maker. When that is true:

Confirm the next step on the call. Do not leave it open. "It sounds like this solves the [specific problem they named]. Does it make sense to set up a follow-up with [decision-maker / your team] this week?" Keep it specific, time-bounded, and tied to what they told you.

Do not over-explain. The qualified prospect does not need more features. They need a clear path to yes. Stop demoing when they are sold.

The branch for interest without decision power

This is the most common case in founder-led sales: the person is genuinely interested, engaged, asking good questions, and they cannot sign. They are a champion.

Treat them like one. Ask: "Who else would need to be part of this decision?" Then: "What would be most useful to share with them — a recording of this call, a written summary, or a short version of the demo?"

Your job is to make the champion look smart in front of the decision-maker. Give them the asset that does that. Flag the lead as nurture, not disqualified. The path to close runs through them.

The clean exit when the fit is wrong

Wrong fit shows up as a use case that does not match, a timeline that is 12+ months out, or budget that is genuinely not there. Say it plainly: "Based on what you've told me, I don't think this is the right fit for where you are right now — and I'd rather be honest about that than waste your time."

Most prospects respect that. Some will push back and reveal a real use case you missed. Either way, you protect your follow-up time for leads that can actually close.

Score the lead before the demo ends and decide the follow-up

A simple scorecard for founders and AEs with no time to waste

Score on four signals, one point each:

• Live problem — they named a specific pain, unprompted.
• Budget signal — they asked about pricing, contracts, or comparisons.
• Authority or champion — they can say yes, or they are directly connected to someone who can.
• Timing — there is a reason this matters now, not someday.

Score 3–4: qualified. Score 2: nurture. Score 0–1: disqualify or park for six months.

Run this mentally in the last five minutes of the call, not after. The score decides the next sentence out of your mouth.

What to do after the call: route, nurture, or disqualify

Score 3–4: book the next step before you hang up. If you cannot get a time on the call, send a calendar link within the hour while the call is still warm.

Score 2: send a follow-up that is useful to them specifically — a relevant case study, a short demo clip of the feature they asked about, or a written answer to the question they could not answer on the call. Do not just check in. Give them something to do. Vercel's lead qualification workflow template shows how automated routing after a qualification signal can keep nurture leads moving without manual overhead. The same logic applies to your own follow-up queue.

Score 0–1: close the loop with a short email that leaves the door open. One sentence is enough. Do not over-invest.

FAQ

Q: What questions should I ask during a demo to tell whether a lead is truly qualified?

Start with "What made you want to look at this today?" It shows whether the pain is active or passive. Then ask one question tied to what they are reacting to on screen. By the end of the call, you need answers to four things: is this their real problem, can they buy, can they say yes, and does this need to happen now?

Q: Which signals during the demo show budget, urgency, authority, and real buying intent?

Budget: they ask about pricing or contracts without being prompted. Urgency: they name a deadline — a launch, a quarter, a board meeting. Authority: they are making implementation decisions on the call, not deferring everything. Intent: they start mapping your product to their existing workflow out loud, or they ask detailed integration questions. The behavioral signals — cursor pauses, note-taking, pulling in a colleague — are often more reliable than what they say directly.

Q: How do I qualify a lead without making the demo feel like an interrogation?

Say early in the call: "I'll ask a few questions as we go — so I can show you the parts that are actually relevant to where you are." That frames each question as personalization, not interrogation. Tie each question to something they are seeing on screen instead of firing them off in sequence. The demo gives you natural branch points; use them.

Q: What should I do when the prospect is engaged but not the decision-maker?

Ask who else needs to be part of the decision, then ask what would be most useful to share with them. Your job is to make the champion look smart in front of the decision-maker. Give them a short demo clip, a written summary, or a recording they can forward. Score this lead as nurture, not disqualified. The path to close runs through the champion, not around them.

Q: How can I qualify technical stakeholders or product engineers while still keeping the demo smooth and credible?

Technical stakeholders signal themselves. They ask implementation questions, integration questions, or architecture questions during the demo. When that happens, go deeper on the technical detail rather than steering back to the feature tour. Name the specific behavior, the API surface, or the data model. Non-technical buyers in the room do not need to follow every word; they need to see that the technical person is satisfied. Let that credibility transfer.

Conclusion

The best demo qualification script is the one that lets you decide the next move while the call is still warm. You do not need a perfect discovery call before the demo or a long debrief after it. You need four signals, a scorecard you can run in five minutes, and branch questions tied to what the prospect is doing on screen. Build the questions this week. Add the scorecard. Run it on your next three demos, and you will know within the first twenty minutes whether you are looking at a yes, a nurture, or a clean exit.