Hyperframes Sales Demo Builder

---
name: hyperframes-sales-demo-builder
description: Build a personalized product-demo or sales-walkthrough video in HyperFrames for a specific prospect or account — narrated screen-by-screen, branded to them, ending in a clear next step. Turns a generic demo into a "this was made for me" asset for outbound, follow-up, or deal acceleration. Use when you want to send a tailored video instead of booking another live call.
tools: Read, Write, Bash, Glob, Grep, WebSearch, WebFetch, Agent
model: inherit
---

# HyperFrames Sales Demo Builder

The best-converting sales video isn't a generic product tour — it's a two-minute walkthrough that names the prospect's company, shows the exact workflow they care about, and ends with one obvious next step. This skill builds that, repeatably, in HyperFrames.

Use it for: warm follow-up after a discovery call, breaking into a target account, re-engaging a stalled deal, or replacing a live demo with something the buyer can forward internally to the people who weren't on the call.

For composition/caption/TTS/render mechanics, invoke the `hyperframes`, `hyperframes-cli`, and `hyperframes-media` skills. This skill owns the personalization and the sales narrative.

## Step 1 — Gather the account context

- **Who** — the prospect/account, the persona of the viewer (champion vs. economic buyer — load from `icp-deep-scanner` personas if available). The same product gets a different demo for each.
- **Their problem** — the specific pain from discovery notes / CRM (read-only) / their public site. Personalize to *their* job, not a feature list.
- **The workflow to show** — the 2–3 moments that prove value for them, not the full product.
- **Proof** — the metric, customer, or before/after most relevant to their situation.
- **Next step** — book a call, start a trial, loop in a stakeholder.

**Security:** read CRM/notes read-only; never write to the CRM or send anything automatically. Don't put another customer's confidential data into this prospect's video. Secrets via env vars.

## Step 2 — Script the walkthrough

Structure that converts:
1. **Personalized open** — name them and their problem in the first 10 seconds ("{Name}, you mentioned {pain} — here's exactly how we'd handle that").
2. **The relevant workflow** — show the 2–3 moments that matter to *them*, narrated as their use case.
3. **Proof** — the most relevant result, briefly.
4. **One clear CTA** — a single next step, with urgency that's real, not manufactured.

Keep it under ~2–3 minutes. A demo they finish beats a thorough one they abandon.

## Step 3 — Build & brand the composition

- Author scene blocks per script beat (`hyperframes`).
- **Brand to the prospect where tasteful** — their logo on the open/close, their use-case language on screen. Reuse a `claude-design-system-architect` kit for your own brand consistency. No purple, no emoji unless branded.
- **Screen content** — use real product screens/recordings or clean mockups; annotate with motion to direct the eye to the value moment.
- **Captions** synced to VO (forwarded internally and watched muted).
- **Voiceover** — warm, conversational, first-name; generate via the HyperFrames media pipeline (or `edge-tts` neural voice). Consider a recorded human VO for high-value accounts.
- Lint + preview before delivery; render the final.

## Step 4 — Deliver
```markdown
# Sales demo: {Account} — {viewer persona}
- Personalized cold-open line
- Walkthrough script (beats)
- Composition path + render command
- Suggested send copy (email/LinkedIn) to accompany the video
- The single CTA
```

Offer to write the accompanying send copy via `cold-email-sequence-generator`, test the open line in `prospect-panel-simulator`, and produce a short 30s teaser cut via `hyperframes-ad-director`.

## Guardrails recap
Personalize to their problem, not your feature list · show only the 2–3 value moments · one CTA · never expose another customer's confidential data · read-only CRM, no auto-send · captions + brand always · lint/preview/render before claiming done.