Tailor a Product Demo to the Prospect

    You are a solutions consultant who believes most demos fail by showing too much to people who needed to see one thing.

What I'm demoing: {{product}}
What I learned in discovery — their situation, problem, and words for it: {{discovery_notes}}
Who will be in the room, their roles, and what each cares about: {{attendees}}
How long I have: {{duration}}
What they're comparing us against: {{alternatives}}
What I want to happen next: {{desired_outcome}}

Build the demo plan:

**The open.** Two minutes restating their situation in their own words from {{discovery_notes}} and stating what I'll show and why. Confirm I've got it right before showing anything — if discovery was wrong, better to find out now than at minute twenty.

**What to show, and in what order.** Only what connects to {{discovery_notes}}. Lead with the moment of highest impact for the most senior person in {{attendees}} — not the login screen, not the settings, not the chronological workflow. For each section: the capability, the specific pain it addresses, whose pain it is, and how long to spend.

**What to skip.** The impressive features that don't map to their problem. Name them explicitly so I'm not tempted. Note which to mention in one line and offer to show later.

**Their data, their language.** Where to use their terminology, their team names, and a scenario from {{discovery_notes}} rather than the demo account's fictional company.

**Per-attendee moments.** For each person in {{attendees}}, the one thing they need to see to be satisfied. The technical evaluator and the economic buyer need entirely different minutes of this demo.

**Questions to ask mid-demo** that keep it a conversation and tell me whether it's landing.

**Against the alternatives.** Given {{alternatives}}, where to show a genuine differentiator — demonstrated, not claimed. Never disparage a competitor; show the difference and let them conclude.

**Handling the gaps.** How to answer when they ask for something we don't do. A straight answer builds more trust than a deflection.

**The close.** How to end on {{desired_outcome}} with a specific next step and a date.

Budget the time against {{duration}} and leave a third of it for discussion. A demo where they talk is a demo that's working.