SaaS product demo production

Use this skill to 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 is provider-independent: adapt it 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 not "show the UI." The 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.

Non-negotiables

Treat these as production constraints, not suggestions:

1. Start from audience, use case, and proof. A demo organized by the product navigation usually feels like a tour; a demo organized by the buyer's job feels like a solution.
2. Use only approved demo tenants, seeded mock data, synthetic data, or explicitly cleared customer data. Never capture live production accounts, real customer names, internal tickets, API keys, session tokens, email addresses, payment details, unreleased roadmap, admin consoles, or analytics that security/legal/client stakeholders have not approved.
3. Substantiate every objective claim before writing it into narration, captions, on-screen text, thumbnails, or ad copy. The FTC states that advertising claims should be truthful, non-deceptive, and evidence-based, and its substantiation policy expects a reasonable basis for express and implied objective claims before dissemination. Do not treat this skill as legal advice; escalate regulated, comparative, performance, financial, health, security, privacy, AI, or pricing claims to the appropriate reviewer.
4. Put required disclosures close to the claim they qualify. FTC .com Disclosures guidance emphasizes clear and conspicuous disclosure placement, proximity, prominence, duration, cadence, understandable language, and the overall net impression of the ad. If a platform or short cutdown cannot carry the disclosure clearly, change the claim or do not use that placement.
5. Caption prerecorded audio. WCAG SC 1.2.2 calls for captions on prerecorded synchronized media with audio. Caption dialogue, speaker changes, meaningful sound effects, and important non-speech audio. Prefer sidecar captions for platforms that support them; burn in captions only when the distribution context needs always-on readability.
6. Make important visual information available beyond the pixels. If the demo depends on on-screen changes, describe them in narration, provide a text alternative, or add audio description for accessibility-sensitive deliveries. WCAG SC 1.2.5 requires audio description for prerecorded video at Level AA unless the main audio already conveys the important visual information.
7. Keep text, callouts, subtitles, UI, and disclosure overlays legible. Use WCAG contrast discipline for all production graphics: aim for at least 4.5:1 for normal text, 3:1 for large text and non-text UI indicators, and never rely on color alone to convey meaning.
8. Re-check delivery specs at production time. Platform ad specs, safe zones, duration limits, caption support, and file limits change. Treat any platform-specific numbers in this skill as volatile examples verified on 2026-07-10, not permanent truth.