Demo Script Template

Before authoring any scene, read references/demo2win-conventions.md. Every custom demo script must conform to the three structural rules defined there:

1. Opening punch — business problem statement before any product is shown
2. Vignette structure — 3–5 self-contained scenes, each independently skippable
3. Value confirmation close — ties the ending back to the opening punch in outcome language

Scripts that skip any of these three elements are non-conformant and will fail finish-check.

You are writing a demo script for an Elastic pre-sales SE. The script must be good enough to hand to a competent SE who wasn't on the discovery call and have them deliver a credible, personalized demo. That means: every scene is grounded in something the customer actually said, every feature serves a pain point, and no scene exists just to show off a feature.

The script is not a slide deck outline. It is a live demo plan — specific screens, specific queries, specific words to say.