demo-specialist
Expert product demonstration specialist for SaaS and B2B software. Use when preparing demos, structuring demo presentations, tailoring to stakeholders, handling objections during demos, managing live vs sandbox environments, or improving demo conversion rates. Covers remote and in-person demos, multi-stakeholder presentations, technical deep-dives, and executive briefings.
What this skill does
# Demo Specialist
Strategic expertise for delivering product demonstrations that convert prospects into customers.
## Philosophy
A demo isn't a feature tour. It's a **story about your prospect's future** told through your product.
The best product demos:
1. **Start with their problem** — Not your solution
2. **Show, don't tell** — Features are boring; outcomes are compelling
3. **Match the audience** — Executives need different things than end-users
4. **Create urgency** — Show the cost of inaction
5. **End with a clear next step** — Never let momentum die
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `structure-*` — Demo flow, storytelling arc, timing
- `audience-*` — Stakeholder mapping, persona-based demos
- `technique-*` — Live demo execution, objection handling
- `environment-*` — Demo prep, sandbox vs live, technical setup
- `followup-*` — Post-demo actions, next steps
## Core Frameworks
### The Demo Hierarchy of Needs
```
┌─────────────────┐
│ CONVICTION │ ← "I need this NOW"
│ (Urgency) │
├─────────────────┤
│ VISION │ ← "I see how this transforms us"
│ (Future) │
├─────────────────┤
│ RELEVANCE │ ← "This solves MY problem"
│ (Personalized) │
├─────────────────┤
│ CREDIBILITY │ ← "This actually works"
│ (Proof) │
└─────────────────┘
```
### Demo Structure Arc
```
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ HOOK │───▶│ PROBLEM │───▶│ SOLUTION │───▶│ PROOF │───▶│ CLOSE │
│ (2 min) │ │ (5 min) │ │ (15 min) │ │ (5 min) │ │ (3 min) │
└──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
│ │ │ │ │
Attention Pain point Core value Social proof Next step
+ agenda validation demonstration + ROI case + timeline
```
### Stakeholder Demo Matrix
| Stakeholder | Primary Need | Demo Focus | Success Metric |
|-------------|--------------|------------|----------------|
| **Executive** | Strategic value, ROI | Business outcomes, dashboards | "How does this move our KPIs?" |
| **Manager** | Team efficiency, reporting | Workflows, collaboration | "How does this make my team faster?" |
| **End User** | Daily workflow, ease of use | UX, common tasks | "How does this make my job easier?" |
| **Technical** | Integration, security, scale | APIs, architecture, compliance | "How does this fit our stack?" |
| **Finance** | Cost, ROI, TCO | Pricing, value metrics | "What's the business case?" |
### The SHOW Framework
- **S**ituation — Confirm their current state
- **H**urdle — Highlight the specific challenge
- **O**utcome — Paint the future with your solution
- **W**ow — Demonstrate the "aha moment"
### Demo Types
| Type | Duration | Audience | Depth | Goal |
|------|----------|----------|-------|------|
| **Teaser** | 5-10 min | Cold leads | Surface | Generate interest |
| **Discovery Demo** | 15-20 min | Qualified leads | Moderate | Validate fit |
| **Full Demo** | 30-45 min | Buying committee | Deep | Advance deal |
| **Technical Deep-Dive** | 45-60 min | IT/Dev team | Very deep | Technical validation |
| **Executive Briefing** | 15-20 min | C-suite | Strategic | Executive buy-in |
| **POC Kickoff** | 60+ min | Project team | Implementation | Start evaluation |
## Environment Strategy
| Environment | Best For | Pros | Cons |
|-------------|----------|------|------|
| **Production** | Mature product, confidence | Real data, authentic | Risk of bugs/latency |
| **Sandbox** | Complex demos, new features | Controlled, safe | Less authentic |
| **Customer's Data** | Late-stage deals | Highly relevant | Requires prep |
| **Recorded** | Consistency, scale | Perfect execution | No interaction |
## Anti-Patterns
- **Feature dumping** — Showing everything instead of what matters
- **No discovery** — Demoing before understanding their needs
- **One-size-fits-all** — Same demo for every audience
- **Demo theater** — Overly scripted, no room for questions
- **Technical rabbit holes** — Getting lost in implementation details
- **No next step** — Ending without a clear action
- **Ignoring the room** — Not reading reactions and adjusting
- **Over-promising** — Showing roadmap items as current features
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".