A demo runbook that follows the buyer, not the feature list
The demos that close start with discovery, show only what the buyer cares about, translate each feature into an outcome, and have answers ready for the objections that always come. This builder turns your inputs into a structured runbook so every rep delivers the same disciplined demo: ask first, show second, reinforce value at every step, and handle objections without improvising.
How it works
The tool assembles four sections in the order a strong demo runs. The discovery block holds the two or three questions you ask before showing anything, so you learn the buyer’s real pains and tailor the rest. The demo flow sequences the features to show, each paired with a value reinforcement line that turns the capability into the buyer’s outcome. The objection handling block prepares calm, evidence-based responses to the objections you expect — price, timing, switching cost, or a competitor. Each section is generated only from your inputs, so the runbook reflects your product and your market, not a generic template.
The anatomy of a strong demo
1. Pre-demo discovery (before you share your screen)
Discovery is the part most reps skip or rush, and it is also the highest-leverage part of the call. Effective discovery questions are open-ended and process-focused, not product-focused. You are not asking “do you need feature X?” — you are asking what their current world looks like and where the friction is.
Good discovery question patterns:
- “Walk me through how your team currently handles [process].”
- “What happens when [problem scenario] occurs?”
- “What has been the impact of [pain] on your team or metrics?”
Two or three well-chosen questions reveal which features to show and in what order. They also give you language the buyer used — and repeating their own words back in the demo makes value land harder.
2. Feature demonstration sequence
Show features in order of relevance to the pain you just uncovered — most critical first, supporting features later. Each feature demonstration should be short: show it, name what it does, then immediately transition to the value line.
A common mistake is lingering on features that impress the seller more than the buyer. If discovery revealed that the buyer’s pain is data entry errors, lead with automated validation — not the reporting dashboard you find most impressive.
3. Value reinforcement talking points
After each feature, connect it to an outcome the buyer named in discovery. The formula is: capability → because → buyer outcome. For example: “The auto-match handles reconciliation automatically — because your team said manual matching was taking three hours a week, and that time goes away.”
Written value lines prevent reps from winging this step and saying nothing beyond “pretty cool, right?” The script ensures the connection is made explicitly every time.
4. Objection handling
Prepare responses before the call for the four or five objections that come up consistently. A prepared response has four parts: acknowledge the concern honestly, ask a clarifying question to understand the specific version of it, answer with evidence, and propose a next step. Improvised objection responses tend to sound defensive; scripted responses sound grounded.
Tips and practical example
- Keep discovery to two or three open questions: “What does your invoicing process look like today?” opens far more than a yes/no question.
- Pair every feature with one value line. Capability without outcome is a feature tour, not a business conversation.
- Order features by the pain they relieve, starting with what the buyer told you matters most.
- For each objection, write the response as acknowledge → clarify → evidence → next step, so you never freeze on the call.
A finished demo script lets you walk in confident: you know what to ask, what to show, how to frame the value, and exactly what to say when the buyer pushes back. Teams that standardise on a script also build institutional knowledge — what objections come up, which responses land, and which features move deals.