Product Launch Video
Design and build cinematic, high-impact product launch videos that make viewers feel the product before they ever touch it.
This skill is not locked to one aesthetic. The visual style adapts to the product's DNA — what matters is that whatever direction is chosen, the execution reflects absolute top-tier standards in motion, lighting, composition, and visual storytelling.
Core Philosophy
Three principles govern every decision:
Intentionality Over Decoration. Every visual element, movement, and light source must have a purpose. Whether minimalist or maximalist, nothing exists merely to fill space. Everything drives the narrative, highlights a feature, or evokes a specific emotion.
Sensory Translation. A great launch video makes the viewer feel the product. Translate abstract concepts (speed, security, comfort) and physical traits (weight, texture, responsiveness) into visual and auditory experiences. If the product is fast, the viewer should feel velocity. If it's elegant, the viewer should feel refinement in every frame.
Mastery of Contrast. Great video thrives on juxtaposition. Use contrast in scale (macro detail vs. sweeping wide shots), pacing (frenetic energy vs. slow-motion reveals), lighting (shadow vs. highlight), and audio (silence vs. heavy beats) to create dynamic tension that holds attention.
When to Use
- Creating a product launch or announcement video
- Building a demo or feature walkthrough with cinematic quality
- Making a brand reveal or teaser trailer
- Producing animated product showcases with motion graphics
- Storyboarding and planning video structure for any product
- Turning product visuals, photos, or concepts into video narratives
Phase 0: Understand the Product
Before any visual work, deeply understand what you're showcasing. This shapes everything.
Ask the user (all at once, don't drip-feed questions):
- Product — What is the product? What does it do? What problem does it solve?
- Audience — Who watches this video? Developers? Consumers? Investors? Internal team?
- Core Message — What's the ONE thing the viewer should remember after watching?
- Tone — What should the viewer feel? (Impressed / Excited / Calm / Inspired / Empowered)
- Duration — How long? (15s teaser / 30s spot / 45-60s full launch / 90s+ deep dive)
- Assets — Do you have logos, product photos, screenshots, recordings, brand colors, or fonts?
- Voiceover — Should the video have narration? If yes, what language? Any preference on voice character (gender, tone, energy level)?
- Reference — Any videos you admire? (Apple keynote style, Nike product films, Stripe developer aesthetic, playful Notion vibes, luxury watch commercials, etc.)
- Publishing Context — Where will this video be posted? (Landing page, X/Twitter, LinkedIn, YouTube, Shorts/Reels/TikTok, investor deck, internal demo.) Aspect ratio, captions, and pacing depend on this.
If the user already provided context in the conversation, extract answers from what's there and confirm gaps.
GATE: Do not proceed to Phase 1 until you have answers (from the user or inferred from context) for all 9 questions above. If assets are provided, audit them — list every available asset and plan to use each one where it strengthens the narrative. Not every asset must appear, but none should be ignored without reason.
Phase 1: Establish the Aesthetic
This is the most important creative decision. The aesthetic must feel like it was designed for this specific product — not a generic template with the logo swapped in.
Step 1.1: Choose a Visual Direction
Based on the product's personality and the user's tone preference, propose 2-3 distinct aesthetic directions. Each direction should include:
-
Name — A short evocative label (e.g., "Midnight Precision," "Warm Analog," "Electric Pulse")
-
Mood — 2-3 sentence description of the emotional atmosphere
-
Color Palette — 4-5 colors with hex codes and roles (background, primary, accent, text, highlight)
-
Typography — Display + body font pairing from Google Fonts or Fontshare (never Inter, Roboto, Arial, or system fonts). The typeface must embody the product's personality:
- Elegant serifs (e.g., Playfair Display, Cormorant) → luxury, editorial, premium
- Bold grotesque sans-serifs (e.g., Space Grotesk, Satoshi) → tech, bold, modern
- Geometric sans-serifs (e.g., Plus Jakarta Sans, General Sans) → clean, trustworthy, SaaS
- Kinetic or variable fonts (e.g., Syne, Cabinet Grotesk) → youth culture, creative, playful
- Monospace or code fonts (e.g., JetBrains Mono, Fira Code) → developer tools, terminal aesthetic
The font is the brand voice made visible. A mismatch between product personality and typeface undermines every other design decision.
-
Motion Character — How things move (snappy springs, smooth glides, elastic bounces, cinematic slow reveals)
-
Signature Element — The ONE visual motif that makes this video distinctive (gradient mesh backgrounds, glass morphism cards, particle fields, geometric patterns, light streaks, cinematic photo treatments, product close-ups with callout labels, etc.)
Present these as concise cards, not walls of text. The user picks one or mixes elements.
Bad Examples (The "AI Slop" Checklist)
Avoid these dead giveaways of generic AI-generated video:
- Purple gradients on dark backgrounds (the #1 cliché)
- Inter/Roboto/system fonts for display text
- Uniform timing — everything entering at the same speed and delay
- Emoji as icons
- Flat, evenly-lit scenes with no depth or shadow
- Cookie-cutter card grids with identical animations
- Text that just "fades in" with no spatial relationship to the content
- Backgrounds that are just solid colors
GATE: Present 2-3 aesthetic directions to the user. Do not proceed to Phase 2 until the user has chosen or confirmed a direction. If the user says "just do it," pick the direction that best matches the product's personality and state your choice explicitly before moving on.
Phase 2: Storyboard
A storyboard is the blueprint. Every scene must justify its existence.
MANDATORY: Write out the full storyboard before writing any code. Save it as storyboard.json in the project root directory using the schema defined below. Verify against the Storyboard Review Checklist at the end of this section. No two consecutive showcase scenes may use the same layout or animation pattern.
The "Unlimited Visual Budget" Rule
When conceptualizing the storyboard, DO NOT limit your imagination to the raw assets the user provided.
- Treat user-provided 2D assets (raw screenshots, flat logos, basic photos) merely as conceptual seeds or base textures.
- Evaluate the narrative requirements. If the story demands additional visual variety, supplementary environments, or B-roll to build a richer ecosystem, storyboard them naturally.
- However, only introduce new generated assets if they actively serve the product's narrative and visual hierarchy. Do not generate assets merely for the sake of complexity.
Narrative Arc
Product launch videos follow a dramatic structure, even short ones:
| Act | Purpose | Typical Duration (30s video) |
|---|---|---|
| Hook | Grab attention. Pose a problem, show tension, or open with a striking visual. | 3-5s |
| Reveal | Introduce the product. The "hero moment." | 5-8s |
| Showcase | Demonstrate 2-4 key features. Each gets its own visual beat. | 12-18s |
| Climax | The most impressive moment — a full-screen demo, a dramatic stat, or a "wow" transition. | 3-5s |
| Close | Logo, tagline, CTA. Leave a lasting impression. | 3-5s |
For shorter videos (15s), compress to: Hook → Reveal → Close. For longer videos (60s+), expand Showcase with more feature beats and add a "social proof" or "vision" beat before the close.
Plan the video structure before writing a single line of code. A storyboard is the contract between creative vision and technical execution.
Publishing & Feed Rules
- Show the product early. In launch, demo, and social formats, the viewer should see the product, product interface, or unmistakable product artifact within the first 3 seconds. Abstract hooks are allowed only if they immediately resolve into the product.
- Design for muted playback. If the video may appear in a feed, assume many viewers will watch without sound. Key claims, scene beats, captions, and CTAs must be visible on screen, even when voiceover exists.
Video Metadata
Before building, document these decisions:
- Duration, FPS, Resolution — derived from Phase 0
- Publishing Context — derived from Phase 0. Note where the video will be posted and any constraints that affect pacing, captions, safe areas, or deliverables.
- Display Font + Body Font — from Phase 1 aesthetic direction (with weights)
- Color Palette — define roles, not just colors: background, surface (elevated elements), primary (headlines), muted (secondary text), accent (CTAs/highlights), highlight (special moments). Each role should have a clear usage rule.
Narrative Structures
Choose the structure that best fits the product's story:
- Problem → Solution — Best for products that solve a clear pain point. Open with the problem to create tension, reveal the product as the answer, showcase features, climax with a "wow" moment, close with CTA.
- Vision → Reality — Best for aspirational products or new categories. Paint the ideal future, acknowledge the gap, show how the product bridges it, prove with features, close.
- Montage → Focus — Best for feature-rich products or major updates. Rapid montage of many features, pause to slow down, deep dive into 2-3 key features, montage return for breadth, close.
- Teaser (15s or less) — Intrigue with abstract visuals, flash quick product glimpses, reveal logo + launch date.
Storyboard Schema
The storyboard is saved as storyboard.json in the project root. This is the single source of truth — it drives implementation, voiceover generation, and timing.
{
"meta": {
"title": "Product name and video type",
"durationSec": "Total video duration in seconds",
"fps": 30,
"width": 1920,
"height": 1080,
"narrativeStructure": "problem-solution | vision-reality | montage-focus | teaser",
"fonts": {
"display": { "family": "Google Fonts / Fontshare family name", "weights": ["700"] },
"body": { "family": "Google Fonts / Fontshare family name", "weights": ["400", "500"] }
},
"colors": {
"background": "#hex - base background",
"surface": "#hex - elevated elements like cards",
"primary": "#hex - headlines and key text",
"muted": "#hex - secondary text and labels",
"accent": "#hex - CTAs and highlights",
"highlight": "#hex - special moments and emphasis"
}
},
"voice": {
"enabled": "true if video has voiceover, false if music-only",
"gender": "male | female | neutral",
"age": "young adult | middle-aged | mature",
"tone": ["Array of traits for AI voice search: confident, warm, energetic, calm, authoritative, conversational, inspiring"],
"accent": "American | British | neutral | other",
"pace": "fast | moderate | slow"
},
"scenes": [
{