Demo Scripting

AI-generated demo scripts tailored to buyer persona, use case, and competitive situation. This skill produces screen-by-screen walkthroughs with talking points, anticipated questions, and competitive differentiation moments woven into the flow.

When to Use This Skill

Use this skill when the user:

• Needs a custom demo script for a specific prospect, persona, or use case
• Wants screen-by-screen click path instructions with contextual talking points
• Is preparing for a competitive demo and needs to highlight differentiators naturally
• Wants to anticipate questions at each stage of the demo and prepare responses
• Is building standardized demo playbooks for the sales team

What This Skill Does

Gather demo context: prospect's role, industry, specific pain points, competitive alternatives they are evaluating, and how much time is allocated. At minimum, you need the prospect's role and the time available. A 15-minute demo for a CTO is fundamentally different from a 45-minute demo for an end-user team.

Build the demo script in this structure:

Opening Hook (first 2-3 minutes) Start with a pain statement, not a product overview. Reference something specific the prospect shared in discovery: "You mentioned your reps spend 45 minutes after every call updating the CRM. Let me show you what that looks like when it happens automatically." If no discovery context is available, use a persona-based pain hypothesis and validate it before proceeding: "Most VP of Sales tell us their biggest pain is forecast accuracy — is that true for your team, or is there something else we should focus on today?"

Never open a demo with your company's history, mission statement, or team slide. The prospect agreed to a demo to see the product, not to hear your origin story.

Feature Sequence (core of the demo) Order features by relevance to the prospect's stated pain points, not by your product's navigation menu. For each feature:

• State the pain it addresses (tie back to discovery)
• Show the feature in action (click path instructions)
• Provide a talking point connecting the feature to a business outcome
• Note anticipated questions and prepared responses

Include 3-5 features maximum for a 30-minute demo. Showing more than that creates cognitive overload and dilutes impact. Select the features that map most directly to the prospect's top pain points.

Competitive Differentiation Moments If the prospect is evaluating competitors, weave differentiation into the demo naturally — do not create a "Why We're Better Than X" slide. Instead, when showing a feature that represents a competitive advantage, add a talking point like: "One thing our customers tell us they value is that this happens in real time during the call, not just in a post-call summary." This positions the advantage without naming the competitor.

Interactive Checkpoints Every 5-7 minutes, build in a checkpoint: "Does this match what your team needs?" or "How does your team handle this today?" Checkpoints serve two purposes: they confirm you are showing relevant content, and they give the prospect ownership of the demo direction. A demo without checkpoints is a monologue.

Closing and Next Steps (last 3-5 minutes) Summarize the 2-3 most impactful things shown, tied back to the prospect's specific pain. Propose a clear next step — not "What do you think?" but "Based on what we covered, the logical next step would be a technical deep-dive with your engineering team. Can we get that on the calendar for next week?"

Anti-Pattern: "The Feature Tour" Showing every feature in the product because "they might find something they like" is the fastest way to lose a demo. If you show 15 features, the prospect remembers zero. If you show 3 features connected to their pain, they remember all three. Ruthlessly cut features that do not map to stated pain points or evaluation criteria. If the user asks for a comprehensive product tour, push back: "A targeted demo will be more effective — which 3 use cases matter most to this prospect?"

Anti-Pattern: "Skipping Discovery Context" A demo without discovery is a generic product tour. Before generating the script, verify that the user has discovery context. If they say "I haven't had a discovery call yet," recommend running discovery first or, at minimum, gathering the prospect's top 2-3 priorities before the demo. Generate a list of pre-demo questions the user can send to the prospect in advance.

Time Management For each section of the demo, provide a time budget. If the total exceeds the allocated time, flag it and recommend cuts. Demos that run over time signal poor preparation and disrespect for the prospect's schedule.

Example Prompts

• "Create a 30-minute demo script for a VP of Sales who cares about coaching and pipeline visibility"
• "Build a competitive demo against Gong that highlights our real-time coaching advantage"
• "Generate a click path for demoing our integration with Salesforce to a RevOps buyer"
• "What questions will a CTO likely ask during the security section of our demo?"