Scale · Sales Enablement Content
Write a Demo Script Template Library
Build a reusable demo script library so every rep runs the same proven sequence — tailored by persona.
managerrepAdvanced⏱ Lift demo→close conversion 10–20%
When to use
Use when demo conversion varies wildly by rep and there's no shared playbook for what a 'good' demo looks like. Build the master script once, then fork into 2–3 persona variants. Refresh after every quarterly win/loss review.
The prompt
You are a sales enablement editor at a digital marketing agency — every artifact you ship makes a rep faster on a real deal. You design demo scripts reps internalize, not read aloud. Agency: [AGENCY_NAME] — [SERVICES] | What you 'demo' (audit walk-through, sample strategy, portfolio, dashboard): [DEMO_ASSET] | Personas: [PERSONAS] | Goal of the demo (next-step booked, proposal ask, close): [DEMO_GOAL] | Common moments deals die: [DEMO_FAILURE_POINTS] Build a master demo script template + persona variants reps follow on a sales demo for [DEMO_ASSET]. - Master script: ≤1 page, 6–8 beats, each with time-box - Persona variants only change beats 3–5 (discovery + framing) - Include verbatim transition lines between beats - Mark explicit 'tell-don't-show' vs 'show-don't-tell' moments - Force a trial-close before the close-close - Reserve last beat for next-step calendaring, not Q&A Two deliverables: 1) Master demo script (beat-by-beat with time-box and verbatim transitions) 2) Persona variant table showing which beats swap for each persona
Variables
- [AGENCY_NAME] — Your agency name
- [SERVICES] — Services demoed
- [DEMO_ASSET] — What reps actually walk through
- [PERSONAS] — Top 2–3 personas reps demo to
- [DEMO_GOAL] — The clear conversion event for the demo
- [DEMO_FAILURE_POINTS] — Where demos usually fall apart
Example input
Demo asset: live audit of prospect's site + sample 90-day strategy doc | Personas: VP Marketing SaaS, Founder DTC, Director Demand Gen | Demo goal: proposal accepted within 48 hours | Failure points: rep talks for 35 min straight, no trial close, prospect leaves needing to 'think about it'
Example output
Master Demo Script (30 min) Beat 1 (0:00–2:00) — Recap discovery + agenda. Verbatim: 'Last call you said [X]. Today I'll show you [Y] and we'll agree on a next step before we hang up. Sound good?' Beat 2 (2:00–5:00) — Set the frame. Tell-don't-show. 'I'm going to show you 3 things, then ask you 3 questions, then we'll decide.' Beat 3 (5:00–12:00) — Live audit walkthrough. Show-don't-tell. Pause every 90 seconds for reaction. Beat 4 (12:00–20:00) — 90-day strategy doc. Show-don't-tell. Mark 2 'this is what's different about us' moments. Beat 5 (20:00–24:00) — Discovery deepen. 3 questions: 'What lands? What doesn't? What's missing?' Beat 6 (24:00–26:00) — Trial close. Verbatim: 'If we ran this exactly as scoped, would it move your number?' Beat 7 (26:00–28:00) — Pricing + next step. Verbatim: 'It's $9,500/mo, 6-mo min. I'll send the agreement today — what's your calendar look like Thursday for kickoff?' Beat 8 (28:00–30:00) — Calendar the next step. No 'I'll send some times'. Persona variants: - VP Marketing SaaS: Beat 3 leads with pipeline math; Beat 5 adds 'how will your CRO react?' - Founder DTC: Beat 3 leads with revenue impact + ROAS; Beat 5 adds 'what's your inventory position?' - Director Demand Gen: Beat 3 leads with attribution + MQL→SQL flow.
Pro tips
- Time-box beats and enforce them in role-plays — overrun beats kill the trial-close.
- Record 3 'A+' demos and clip the transitions; reps learn pacing faster from audio than docs.
- Forbid 'any questions?' as a closing line. Always end on a calendared next step.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts