demo-script

# Demo Script ## The sample company This skill ships with example data for **Fieldstone AI**, a fictional 25-person AI strategy and build consultancy in Denver, CO (fieldstone.example, hello@fieldstone.example). Its services are AI strategy workshops, governance and risk, rapid prototyping, product design, and production AI builds. Its method has four steps: Frame, Prove, Build, Adopt. Worked examples use a fictional prospect, **Harbor Valley Credit Union**. To make it yours, replace: - **Company name** and contact details (Fieldstone AI, fieldstone.example). - **Services**: the five service lines above, used when framing the ask. - **Method**: Frame, Prove, Build, Adopt, swapped for your own. - **Voice**: the writing rules near the end of this file. - **Pricing placeholder**: a demo never states a price. If asked, `XXX`, scoped separately. ## Purpose Script a two-minute demo of a prototype, an MVP, or a batch run so the prospect sees the one thing that matters and knows what to say yes to. Two minutes is about 280 spoken words. ## When to use - A prototype or product exists and a prospect meeting is coming up. - The user is recording a short demo video for a prospect. - A Prove phase has finished and the result needs to land with an executive. ## Inputs 1. **What is being shown**: the product, prototype, or run, and what it does today. Only demo what works. Ask the user if unsure. 2. **The audience**: who will watch, their role, and the pain they named. Pull from the pre-call brief or meeting notes if they exist. 3. **The ask**: the single next step the user wants from them. ## Structure | Beat | Time | Content | |---|---|---| | Hook | 0:00 to 0:15 | Their problem in their words, with their number if they gave one | | Setup | 0:15 to 0:30 | What they are about to see, in one sentence | | Wow moment | 0:30 to 1:30 | The single moment the product does the hard part live | | Proof | 1:30 to 1:45 | What this means for them: time saved, step removed, risk lowered | | Ask | 1:45 to 2:00 | One specific next step with a date | ## Steps 1. Pick the one wow moment. If there are three candidates, demo one and mention none. 2. Write the hook from the prospect's own words. 3. Script the wow moment as screen actions plus spoken lines, side by side. 4. Cut every line that explains how the product was built. 5. Read it aloud against a timer. Over two minutes means cut, not speed up. 6. Write a fallback: what to say and show if the live step fails (a recording or a screenshot). ## Example (sample data) For Dana Reyes (COO, Harbor Valley Credit Union), demoing a document intake prototype: - **Hook.** "Today a new member waits 3 to 5 days while staff check documents by hand." - **Setup.** "Here is a new application going through the prototype." - **Wow moment.** Upload a sample ID and proof of address. The prototype reads both, flags a mismatched address, and drafts the note to the member. Say: "That check took a staff member a day. It took twenty seconds, and a person still approves it." - **Proof.** "Your staff review flagged cases instead of every application." - **Ask.** "Can we test it with two branches for two weeks starting the 4th?" Use sample documents only. Never demo with real member or customer data. ## Writing rules - Spoken language: short sentences, no jargon, no feature lists. - No em dashes or en dashes. No reflexive triads. No hype words. - Cut filler: "so basically," "as you can see," "just." ## Rules - Demo only what works today. Never fake a live result. - No pricing in the script. - The script is a draft for the user to rehearse and adjust. ## Related skills - discovery-call-prep: the brief that tells you who is watching and what they care about. - client-follow-up: the email after the demo. - sow-scoping: scope the Build phase once the demo lands. - release-notes: summarize what changed in the product before a repeat demo.