Demo Script

Demo

Click to play with sound.

---
name: Demo Script
description: Structures a product demo around the buyer's specific use case and pain, not a feature tour. Use before any live demo to align the narrative to what the buyer actually cares about.
---

# Demo Script

A feature tour is not a demo. Buyers do not care about features — they care about outcomes. The job of a demo is to make the buyer see themselves solving a specific problem they described in discovery. Every screen shown should connect directly to something the buyer said.

## Before building the script

Pull the discovery notes and identify: (1) the primary pain the buyer named, (2) the current workaround they are using, and (3) the metric or outcome they care about improving. The demo script is built around these three things, not around what the product team considers impressive.

If these three things are not known, the demo should not happen yet. Run discovery first.

## Script structure

Open with a 60-second situation recap, not with a product login. 'Based on what you shared last week, your team spends about eight hours a week on X and the biggest pain is Y. Today I want to show you specifically how that looks different.' This signals the rep was listening and sets a clear frame.

Then walk through three to four moments, not features. A 'moment' is a before-and-after narrative: here is the painful thing your team does today, here is how it works with the product, here is what changes for the person doing it. For each moment: (1) name the role affected, (2) show the painful current state briefly if possible, (3) show the product solving it, (4) connect back to the metric or outcome the buyer named.

Close the demo before showing everything. Save one strong moment for questions or a follow-up. Ending on 'and there's so much more' is weak — ending on 'what would be most useful to dig into next?' is strong.

## What to skip
… install to load the full skill