Claude Skill

Demo Prep

Given prospect context, structures your demo: what to show first, skip, save for questions.

Download skill (.zip)Or download whole pack

What it does

Before a product demo, this skill takes prospect context (their pain, who's in the room, what stage of evaluation) and outputs a demo plan: opening 60 seconds, the 3 features that matter, what to skip, and the question that should drive the demo. Stops you from doing the generic feature tour.

When to use

✓Before a real prospect demo (not internal)
✓When you have specific context about the prospect
✓For complex products with many features where prioritizing matters

When not to use

✗You don't actually know what the prospect cares about — go back to discovery first
✗Standard demo where every prospect gets the same thing

Install

Download the .zip, then unzip into your Claude skills folder.

mkdir -p ~/.claude/skills
unzip ~/Downloads/demo-prep.zip -d ~/.claude/skills/

# Restart Claude Code session.
# Skill is now available — Claude will use it when relevant.

SKILL.md

---
name: demo-prep
description: Plans a product demo around prospect-specific context — what to show first, skip, and save for questions.
---

# Demo Prep

When the user has a demo coming up and provides prospect context, plan the demo around their specific situation.

## Required input

- **Prospect** — company + role of the people in the room
- **Their pain** — the specific problem driving the evaluation
- **Stage** — first demo, technical eval, final review, etc.
- **Competition** — what else they're considering
- **What you know** they care about (from discovery)

If the user gives generic input ("they want to see the product"), push back: the whole point is to NOT do a generic demo.

## Output structure

### Opening 60 seconds
Not "thanks for the time." Specifically: a 1-2 sentence framing that connects what you'll show to the pain you discussed.

### The 3 features to lead with
Each one:
- Feature name
- Specific scenario from THEIR business that demos it
- Why this connects to their pain (in their words)

### What to skip
Features that look impressive but don't connect to their pain. Naming what you're skipping helps you NOT include it.

### The question that should drive the demo
One question to ask in the first 5 minutes — their answer shapes the rest. Better than a tour.

### Anticipated objections
Based on their stage and competition, what concerns will likely surface? Have a 1-line answer ready for each.

### What to save for follow-up
Demo gold often gets used in the Q&A or sent as follow-up. Identify what NOT to demo live but to surface as proof points after.

## Constraints

- Demo plan should fit in your head, not on a slide deck
- If the user has 5 features they want to show, push back: 3 max. Anything else dilutes the message.
- Specific scenarios > generic capabilities. "Let me show you how we'd handle the Friday alert storm you mentioned" beats "here's our alerting feature."
- No "kitchen sink" demos. They lose deals.

Example prompts

Once installed, try these prompts in Claude:

Demo prep for VP Engineering at Datacore tomorrow. Their pain: alerting overload. Stage: technical evaluation, comparing us to two competitors. Help me plan.

Related prompts

Don't want to install a skill? These prompts in /prompts cover similar ground for one-shot use:

sales prompts