Skill: leooooooow/demo-script (version 1.1.0)

--- name: Demo Script Builder description: Create compelling product demo scripts for e-commerce videos, live presentations, and sales demos. Craft scripts that highlight value, overcome objections, and drive conversions. version: 2.0 category: Sales & Marketing --- # Demo Script Builder for E-Commerce Create professional, conversion-focused demo scripts for product videos, live sales presentations, and training materials. This skill guides you through structuring demos that showcase product benefits, address customer pain points, and drive purchasing decisions. ## Quick Reference Decision Matrix | Scenario | Demo Length | Focus | Script Type | |----------|------------|-------|------------| | Social media clip | 15-30 sec | Features & wow factor | Hook-driven | | Product page video | 60-90 sec | Problem/solution | Story-arc | | Live sales presentation | 5-10 min | Objection handling | Conversation guide | | Customer onboarding | 3-5 min | Setup & best practices | Tutorial | | Trade show/event | 2-3 min | Differentiation | Elevator pitch with demo | | Email sequence | 30-60 sec per video | Specific benefits | Modular segments | | Webinar | 15-20 min | Deep education | Educational + conversions |

path: references/output-template.md
content: # Demo Script Output Template

Use this template to structure your demo script. Fill in each section, then use the Demo Script Quality Checklist to review before recording or presenting.

---

## Demo Specification

**Product/Feature:** 

**Target Audience:** 

**Demo Length:** 

**Primary Goal:** (Purchase decision / Lead generation / Support reduction / Competitive positioning)

**Viewing Context:** (Mobile video / Email / In-person presentation / Sales call)

---

## Customer Problem & Hook

**Current Situation (Before):**
(2-3 sentences describing where the customer is today)

**Cost of Problem:**
(What is this costing them? Time, money, lost sales, frustration?)

**Desired Outcome (After):**
(What do they want to achieve?)

**Opening Hook (Your Promise):**
(1-2 sentences: problem + solution promise)

---

## Feature-to-Benefit Mapping

| Feature | What It Does | Customer Benefit | Proof Point (Metric/Quote/Example) |
|---------|-------------|------------------|-----------------------------------|
| | | | |
| | | | |
| | | | |


path: references/objection-handlers.md
content: # Objection Handlers for E-Commerce Demo Scripts

When prospects watch your demo, objections form in their minds. The best demos address these hesitations *before* they become deal-killers. This guide provides natural, conversational responses to 25+ common objections—insert them into your demo script where they logically fit rather than as a separate FAQ section.

---

## Price & Cost Objections

### Objection: "That's expensive / More than I want to spend"

**When to address:** Right after showing the core value proposition
**Script approach:** Lead with total cost of ownership, then ROI
**Sample response:**
```
"I hear you on budget. Here's how I think about it: 
This costs $X per month. But let's talk about what you're currently spending.

You're paying for [manual labor / spreadsheets / support tickets / lost sales]. 
That's costing you $Y annually.

Our customers see ROI in 3-4 months through reduced overhead and recovered sales. 
After that, it's pure savings. So the question isn't the cost—it's whether you can 
afford to wait another year doing this the hard way."
```

### Objection: "We need to check with our budget owner"

**When to address:** During closing conversation
**Script approach:** Make it easy to say yes to the conversation
**Sample response:**
```
"That makes total sense. Here's what I'd suggest: 
Let me send you a one-page ROI breakdown that shows exactly how we pay for ourselves.

When you share it with your budget owner, they'll have concrete numbers. 
Then we can all hop on a quick call—it's usually 20 minutes—and answer any questions. 

Does next Thursday work for you?"
```

### Objection: "We found a cheaper competitor"

**When to address:** When directly asked, not preemptively
**Script approach:** Shift from price to total value
**Sample response:**
```
"Great that you're comparing options. Price is one factor, but it's usually not the one 
that makes the difference in the first year. 

Let me ask you: Is their implementation as fast? Do they have the same integrations 
you need? What's their support like? Can they scale with you?

Most 'cheaper' options end up costing more when you factor in implementation, 
training, and what you lose by not having [key feature you have that they don't].

How about we set up a side-by-side comparison? I'll show you exactly where we win 
and where you'd need to make trade-offs with the other option."
```

---

## Product Capability Objections

### Objection: "Does it work with [specific platform/tool they use]?"

**When to address:** During the feature demo that touches on integrations
**Script approach:** Confident, specific integration list
**Sample response:**
```
"Yes, absolutely. We integrate with [list 5-7 specific tools they likely use].

[SHOW: Integration logos or settings screen]

If you use something we don't natively integrate with, we have a full API and 
Zapier connection, so we can connect to almost anything.

What systems do you currently use? I can tell you exactly how the integration works."
```



path: references/sales-messaging-framework.md
content: # Sales Messaging Framework: Feature-to-Benefit Translation

The core of a compelling demo is translating what your product *does* (features) into what it *means* for the customer (benefits). This framework helps you make that translation clear, consistent, and persuasive across all your demo scripts.

---

## The Feature-Benefit-Proof Formula

Every product feature should follow this structure in your demo:




path: assets/demo-script-checklist.md
content: # Demo Script Quality Checklist

Use this checklist to review your demo script before recording or presenting. A great demo hits most of these points. An excellent demo hits all of them.

---

## Section 1: Opening & Hook (10-15% of demo)

- [ ] **Opens with customer problem, not product features**
  - Does not start with "This is [Product Name]"
  - Starts with customer pain point or desired outcome
  - Example: "You lose 70% of sales at checkout" NOT "We have a fast checkout system"

- [ ] **Establishes emotional connection**
  - Acknowledges customer frustration or goal
  - Uses "you" language to make it personal


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector:  ()