In short
- Ask questions that change what you will show, not questions that merely fill a CRM field.
- Separate the operating problem, technical constraints and approval decision.
- Give the specialist a one-page brief: situation, one workflow, proof to show, open questions and next decision.
- A request for a demo is interest. It becomes an evaluation when both sides know what the demonstration must establish.
What should discovery decide before you open the product?
The first question is not which screen the buyer wants. It is what would make this a useful meeting. A technical lead may need to establish compatibility; an operator may need to see a workflow; a budget owner may need to understand what changes if the project goes ahead. Those can all be legitimate, and they are different tests.
For equipment purchases, NIST asks buyers to consider financing, site requirements, connections, training, maintenance and end of life. APM describes a business case as a comparison of benefits, costs, risks and alternatives. Those are not a universal demo script. They are a reminder that the product is being judged inside a larger decision.
Which five questions change the demo?
Use these as a conversation, not a form. If a question does not change what you show or who needs to see it, leave it out.
Scroll the table sideways to see every column.
| Ask | Listen for | What changes |
|---|---|---|
| What has happened that makes this worth looking at now? | A change in work, capacity, cost or risk | Whether there is a real decision to support |
| Which part of the work must improve, and which part must stay as it is? | One actual workflow and its constraints | Which use case to demonstrate |
| What would rule an option out before price enters the conversation? | Integration, site, security or operating limits | Which specialist and proof are needed |
| Who will use it, who will check it, and who can approve it? | Distinct roles, not a generic stakeholder list | Whose question the next meeting must answer |
| What would the next meeting have to establish? | A test, document, comparison or decision gate | What evidence to prepare and what remains open |
How do you tell interest from an evaluation?
A request to “show us the platform” tells you somebody is curious. It does not tell you which decision the organisation is making. Ask what they plan to do after the demonstration. If the answer is “we will discuss it internally,” find out what that discussion must resolve and who will be in it. Do not pretend to know their approval route if they do not know it yet.
This matters most when the product is technically strong but hard to explain as a whole. A tour can establish that each component works and still leave the buyer to assemble the reason to act.
What goes in a one-page demo brief?
Put the buyer situation at the top, then one workflow to show, the constraint that could stop the project, the evidence each role needs, the open questions and the next decision. Keep source beside claim: what the buyer said, what your team inferred and what your team still has to verify. That is enough for the person running the demonstration to make a sensible choice when the conversation changes direction.
When should the technical specialist join?
Bring them in when an answer needs technical authority: architecture, installation conditions, safety, security, integration or a meaningful product limit. The seller can carry the commercial thread without guessing at the engineering. If the answer is not ready, assign it, record the condition to test and return with evidence.
A Strategem case study shows a related boundary. At an industrial equipment manufacturer, the team separated Opening, Setting and Closing so need and fit were established before the owner took the final call. That case supports the value of a visible handoff; it does not mean the team used the five questions on this page. Read the sales-cycle case and model for what actually happened.
What if the buyer cannot answer yet?
Keep the unknown on the page. You might need to show two short paths because the operating condition has not been decided. Or the next step might be a technical workshop rather than a proposal. The point of discovery is to choose the next useful piece of work, not to force certainty before anyone has tested the product.
The handoff test. Can the specialist explain in one sentence what this demo has to prove, and can the buyer say what they will do with that proof? If either answer is missing, revise the brief before adding more slides.
If the demo is clear in the room but the buyer’s argument falls apart later, the next problem may be what the buyer can carry to colleagues, not the demonstration itself.