Discovery / Demo Call Template

A discovery and demo call is the working first conversation where a seller qualifies the buyer, uncovers their real problem, and shows only the part of the product that solves it. The best ones feel like a focused diagnosis, not a feature firehose. Discover first, demo second, always.

When to use it

Run this whenever a qualified prospect is ready to evaluate. For complex deals you may split discovery and demo into two calls, but never demo cold: a demo with no discovery is a guess dressed up as a presentation. Reserve deep demos for buyers who have shown real pain and intent.

Who attends

The account executive leads discovery and next steps. A sales engineer can drive the technical demo for complex products. On the buyer side, push to include both the user who feels the pain and someone who can speak to the decision process and budget.

How to run it

Open by setting a two-way agenda so the buyer knows questions come before the demo. Spend real time in discovery, uncovering current state, pain, impact, decision process, and timeline. Then tailor the demo to exactly what they told you, showing two or three capabilities that map to their pain. Narrate outcomes, not clicks. Handle objections in the room, and never end without a concrete, dated next step.

Questions to ask

• What prompted you to take this call now?
• How are you handling this today, and where does it break down?
• What is the impact of leaving it the way it is?
• Who else is affected, and who is involved in a decision like this?
• If this works, what does success look like in six months?
• What is your timeline, and what would get in the way of acting on it?

Common mistakes

• Demoing before discovery, so the buyer sees features that solve no problem of theirs.
• Showing every capability instead of the two or three that matter to them.
• Talking past objections rather than surfacing and addressing them.
• Ending with maybe a follow-up instead of a specific dated next step.

Capture discovery answers and next steps so nothing slips between calls. Run it in OrgTP.