saas-product-demo-production

What it does

Turn a software product brief into a production-ready demo video plan, script, capture direction, generated-media prompt set, edit plan, delivery matrix, and QA pass. It adapts to real screen recording, browser automation, synthetic screens, motion graphics, avatar narration, or AI video generation without assuming a specific tool. The core job is to make the right viewer understand a valuable workflow, trust the evidence, and know what to do next without exposing private data or overstating the product.

How it works

Follows a structured intake and production process:

• Start from audience, use case, and proof; choose one primary demo type (Feature launch, Sales demo, Product-led growth/website hero, Onboarding, Help-center explainer, Internal enablement).
• Gather intake data: product/feature details, audience, use case, funnel stage, distribution, required proof, compliance level, capture method, demo environment, deliverables.
• Frame the narrative around a specific viewer thought, using a persona and use-case template, then apply a story pattern (Problem-workflow-outcome; Task-steps-verification; Objection-proof-next steps).
• Prioritize features to prove the promise, show recognizable UI states, provide the shortest path to outcome, and add measurable proof.
• Plan data and privacy-safe environments using defined hierarchies and scrub rules; avoid real customer data unless explicitly approved.
• Choose capture method (real screen, browser automation, synthetic UI, motion graphics, or AI-generated footage) based on risk and truth of product behavior, and create a capture sheet with flow, viewport, state, steps, cursor path, callouts, safe zones, and privacy actions.
• Develop narration that states job, explains why steps matter, keeps obvious clicks silent, uses concrete UI nouns, and ends with a fitting CTA.

When to use it

Use when you need a production-ready plan and assets for a SaaS/digital-product demo that must be privacy-safe, substantiated, and accessible, with accommodations for captions, screen/cursor directions, CTA variants, and stakeholder approval. If the request lacks audience details, it advises deriving persona and usage context from asset destination.

What it can touch

The skill lists tools allowed: claude-code, codex, copilot, cursor. It instructs constructing a plan and script that can be executed with these tools and corresponding capture/edit workflows, without assuming a specific platform.

Caveats

Requires substantiated claims with evidence-based proof; avoid live production data unless explicitly approved; ensure captions, accessibility, and disclosure guidelines are observed; platform-specific specs are treated as volatile examples verified on 2026-07-10, not permanent truth.