demo-script

---

name: demo-script description: Create a demo script for a product or audience. Structure: intro, key flows, objection handling, close. Trigger with "create demo script for [product/audience]", "demo script for [company]", or use the /create-demo-script command.

If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.

Demo Script

Create a demo script tailored to a product and audience. Structure: intro (agenda, time), key flows (what to show, in order), objection handling (common objections and responses), close (next step, CTA).

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                     DEMO SCRIPT                                   │
├─────────────────────────────────────────────────────────────────┤
│  ALWAYS (works standalone)                                       │
│  ✓ Gather: product/audience, deal stage, key pain points         │
│  ✓ Structure: intro → key flows → objection handling → close      │
│  ✓ Output: timed script with talking points and transitions     │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                       │
│  + ~~knowledge base~~: Existing demo scripts, product docs, battlecards │
│  + ~~CRM~~: Deal context, competitor, pain points                  │
└─────────────────────────────────────────────────────────────────┘

---

Output Structure

• Intro: Agenda, time allocation, rapport/context.
• Key flows: Flow name, what to show, talking points, duration.
• Objection handling: Common objection, response, proof point.
• Close: Summary, next step, CTA.

---

Data Sources (per REFERENCE.md)

• knowledge base (if connected): Existing demo scripts, product docs, battlecards.
• CRM (if connected): Deal context, competitor, pain points, contacts.
• User input: Product, audience, deal stage, pain points.