Vsl Storyboard Writer

VSL Storyboard Writer

Expert video sales letter and product marketing script writer specializing in high-converting video content that drives action. This skill bridges copywriting and video production, creating storyboard scripts ready for motion design implementation.

Philosophy

Great video sales scripts combine three elements:

1. Sales psychology — Understanding what drives decisions at each stage 2. Visual storytelling — Every scene advances both narrative and conversion 3. Production readiness — Scripts that motion designers can implement immediately

How This Skill Works

When invoked, this skill guides you through creating storyboard scripts that include:

• Hook-focused openings — Proven patterns to grab attention in 3-5 seconds
• Narrative flow — Story structures that build desire and urgency
• Scene-by-scene scripts — Visual descriptions, copy, timing, and rationale
• Conversion optimization — Strategic placement of social proof, objection handling, CTAs
• Motion design handoff — Format compatible with /motion-designer skill

The output is a complete storyboard script that feeds directly into the motion designer workflow for Remotion implementation.

Core Frameworks

VSL Formula Hierarchy

Choose framework based on video length and objective:

The 5-Second Hook Formula

First 5 seconds determine 80% of watch-through rate.

Hook Types: 1. Question Hook — "What if [desired outcome] was actually easy?" 2. Problem Hook — "Tired of [pain point]?" 3. Curiosity Hook — "This [simple thing] changed everything" 4. Pattern Interrupt — Unexpected visual or statement 5. Social Proof Hook — "10,000 teams already [outcome]" 6. Demonstration Hook — Show impressive result immediately

Video Length Guidelines

The AIDA Arc for VSL

Attention (0-15%):

• Hook with problem or question
• Pattern interrupt
• Relatable scenario

Interest (15-40%):

• Agitate the problem
• Show why current solutions fail
• Introduce unique mechanism

Desire (40-80%):

• Demonstrate solution in action
• Social proof and testimonials
• Paint the transformation
• Handle objections

Action (80-100%):

• Clear, specific offer
• Urgency or scarcity
• Risk reversal
• Multiple CTAs

The PAS Framework

Problem (0-25%):

• Identify specific, relatable pain point
• Use "you" language
• Visual: Show the struggle

Agitate (25-50%):

• Why this problem is getting worse
• Cost of inaction
• Failed alternatives
• Visual: Amplify the frustration

Solution (50-100%):

• Introduce your product/service
• Show it working
• Proof it works
• Easy next step
• Visual: Transformation moment

Storyboard Script Format

When creating a storyboard, use this structure:

1. Script Header

# [Video Title]

**Type**: [VSL / Explainer / Product Demo / Social Ad]
**Duration**: [Total seconds]
**Objective**: [Primary conversion goal]
**Target Audience**: [Specific persona]
**Framework**: [AIDA / PAS / Hook-CTA / etc.]

## Key Message
[Single sentence: What should viewers remember?]

## Desired Action
[Specific CTA: What should viewers do?]

2. Script Overview

## Story Arc

**Hook (0-Xs)**: [How we grab attention]
**Build (Xs-Ys)**: [How we build interest/desire]
**Peak (Ys-Zs)**: [Climax / main value proposition]
**Close (Zs-End)**: [CTA and resolution]

## Emotional Journey
Start: [Frustrated / Curious / Overwhelmed]
→ Middle: [Hopeful / Intrigued]
→ End: [Confident / Excited to act]

3. Scene-by-Scene Storyboard

For each scene:

## Scene N: [Scene Name] (Xs - Ys, Duration: Zs)

**Narrative Purpose**: [Why this scene exists in the story]

**On-Screen Copy**:
"[Exact text that appears on screen]"
[Additional text elements]

**Voiceover Script** (Optional):
"[Exact words spoken, if using VO]"

**Visual Description**:
[What viewers see - specific enough for motion designer]
- Background elements
- Main focal point
- Supporting visuals
- Text treatment

**Viewer Psychology**:
[What the viewer should think/feel at this moment]
- Emotional state we're creating
- Objection we're handling (if applicable)
- Desire we're building

**Sales Elements**:
[Any conversion tactics used]
- Social proof placement
- Scarcity/urgency indicator
- Risk reversal
- Benefit emphasis
- Objection handling

**Transition to Next**:
[How this scene flows to the next - why it makes sense]

**Motion Designer Notes**:
[Specific animation suggestions or requirements]
- Timing emphasis (fast/slow)
- Style notes (bold/subtle)
- Key moments to emphasize

4. Production Requirements

## Assets Needed
- [ ] Logo files
- [ ] Product screenshots/mockups
- [ ] Customer photos (if using testimonials)
- [ ] Data visualization elements
- [ ] Icons

## Copy Elements
- Headlines: [List all]
- Subheads: [List all]
- CTAs: [List all instances]
- Social proof quotes: [List all]

## Brand Guidelines
- Voice: [Professional / Casual / Technical / Friendly]
- Tone: [Urgent / Calm / Exciting / Authoritative]
- Restrictions: [Any copy or visual rules]

VSL Storyboard Template

Here's a complete template for quick reference:

# [Video Title]

**Type**: Product Demo VSL
**Duration**: 90 seconds
**Objective**: Trial signups
**Framework**: AIDA
**Target**: [Persona]

## Story Arc
Hook (0-5s): Problem question
Build (5-30s): Agitate pain, show solution
Peak (30-70s): Demo + social proof
Close (70-90s): CTA + urgency

---

## Scene 1: Hook (0-5s)

**On-Screen Copy**:
"Spending hours on [task]?"

**Visual**: [Description]
**Psychology**: Immediate identification with pain
**Sales Element**: Problem recognition
**Transition**: Visual chaos → order

---

## Scene 2: Agitation (5-15s)

**On-Screen Copy**:
"While your competitors move faster?"

**Visual**: [Description]
**Psychology**: FOMO, urgency of problem
**Sales Element**: Cost of inaction
**Transition**: Dark → light

---

[Continue for all scenes...]

Integration with Motion Designer

This skill produces storyboard scripts that the /motion-designer skill uses to create technical video specifications:

Storyboard Script (this skill) → Video Spec (motion-designer) → Remotion Implementation (dev)

When creating storyboards: 1. Focus on copy, messaging, and conversion strategy 2. Provide visual direction but not technical specs 3. Include timing guidance but not frame-by-frame details 4. Emphasize WHY each scene exists (narrative + conversion) 5. Let motion designer handle HOW to execute visually

Common Video Types

Short-Form Social (15-30s)

Formula: Hook → Value → CTA

Scene 1 (0-3s): Bold question or problem
Scene 2 (3-12s): Show solution in action (demo)
Scene 3 (12-20s): Single benefit + social proof number
Scene 4 (20-30s): Simple CTA

Product Explainer (60-90s)

Formula: Context → Demo → Benefits → CTA

Scene 1 (0-5s): Relatable problem hook
Scene 2 (5-15s): Why existing solutions fail
Scene 3 (15-30s): Introduce your solution
Scene 4 (30-50s): Show it working (3 key features)
Scene 5 (50-70s): Transformation / benefits
Scene 6 (70-80s): Social proof
Scene 7 (80-90s): Clear CTA

Full VSL (3-5min)

Formula: Story → Problem → Solution → Proof → Offer → Close

Act 1 - Setup (0-45s):
  - Personal story or customer story
  - Establish credibility
  - Introduce problem

Act 2 - Problem (45s-90s):
  - Deep dive into pain points
  - Why current solutions don't work
  - Cost of status quo

Act 3 - Solution (90s-180s):
  - Introduce product/service
  - Unique mechanism
  - How it works (demo)
  - Key benefits

Act 4 - Proof (180s-240s):
  - Case studies
  - Testimonials
  - Results/data
  - Objection handling

Act 5 - Offer (240s-270s):
  - What you get
  - Pricing
  - Bonuses
  - Guarantee

Act 6 - Close (270s-300s):
  - Urgency/scarcity
  - Final CTA
  - Reminder of transformation

Conversion Optimization Principles

Social Proof Placement

• Early social proof (15-25% mark): Build credibility before big claims
• Feature proof (40-60% mark): Testimonials after each key benefit
• Final proof (80-90% mark): Results-focused before CTA

Objection Handling Sequence

Common objections to address in order:

1. Does it work? → Demo + proof 2. Will it work for me? → Use cases / customer stories 3. Is it too complicated? → Show simplicity 4. Is it worth the money? → ROI / value equation 5. What if it doesn't work? → Guarantee / risk reversal

CTA Best Practices

• Frequency: Minimum 2 CTAs (mid-point teaser + final)
• Clarity: Specific action ("Start free trial" not "Learn more")
• Friction: Remove ("No credit card" if true)
• Urgency: Time or quantity limits (if genuine)

Anti-Patterns

Script-Level

• Feature dumping — List features without benefits or story
• No hook — Slow build that loses viewers immediately
• Unclear CTA — Vague next step or multiple competing CTAs
• All tell, no show — Talking about product instead of showing it
• Dishonest urgency — Fake countdown timers, false scarcity

Scene-Level

• Wall of text — Too much copy on screen at once
• Orphaned scenes — Scene doesn't advance narrative or conversion
• No breathing room — No time for messages to land
• Inconsistent tone — Voice shifts between scenes

Production

• Not production-ready — Vague visuals that motion designer must guess
• Missing timing — No scene durations or pacing guidance
• No assets list — Unclear what's needed to produce

Quality Checklist

Before finalizing a storyboard script:

Hook & Structure:

• [ ] Attention grabbed within 3-5 seconds
• [ ] Clear story arc (hook → build → peak → close)
• [ ] Framework appropriate for duration and goal
• [ ] Emotional journey intentional and clear

Copy & Messaging:

• [ ] Single, clear key message
• [ ] Benefits emphasized over features
• [ ] "You" language (viewer-focused)
• [ ] On-brand voice and tone
• [ ] No jargon or unexplained terms

Conversion Elements:

• [ ] Social proof strategically placed
• [ ] Main objections addressed
• [ ] Clear, specific CTA
• [ ] Urgency or scarcity (if appropriate)
• [ ] Risk reversal included

Production Readiness:

• [ ] All scene timings specified
• [ ] Visual descriptions clear and specific
• [ ] Required assets listed
• [ ] Motion designer notes included
• [ ] Narrative purpose explained for each scene

Integration:

• [ ] Format compatible with motion-designer skill
• [ ] Ready for handoff without clarification needed
• [ ] Technical constraints considered (duration, format)

When to Consult Rules

For detailed guidance on specific aspects:

• rules/vsl-hooks.md — Hook formulas and patterns
• rules/vsl-frameworks.md — Detailed framework applications
• rules/script-pacing.md — Timing and rhythm
• rules/social-proof-strategy.md — Testimonial and proof placement
• rules/objection-handling.md — Addressing buyer concerns
• rules/cta-optimization.md — Call-to-action best practices
• rules/visual-storytelling.md — Show don't tell principles
• rules/motion-designer-handoff.md — Production-ready formatting

Expert Tips

Script Writing

• Start with the CTA, work backwards (what journey gets them there?)
• Write for the ear if using voiceover (conversational, not formal)
• One message per scene (don't try to say everything everywhere)
• Test your hook independently (does it work as a standalone ad?)

Conversion Psychology

• Lead with transformation, not features
• Use specific numbers ("10,000 customers" not "thousands")
• Name the pain before naming the solution
• Create urgency through value, not fake scarcity

Production Planning

• Plan for silent viewing (60%+ watch without sound)
• Consider aspect ratios early (16:9, 9:16, 1:1)
• Budget 30% longer than you think for final duration
• Leave flexibility for motion designer creativity

Collaboration

• Provide examples of visual style you envision
• Reference other videos when helpful ("like X but for Y")
• Be clear about non-negotiables vs nice-to-haves
• Trust motion designer for technical execution

VSL Storyboard Writer Skill

Expert VSL (Video Sales Letter) and product marketing video storyboard writer skill for Claude Code.

Purpose

Creates production-ready storyboard scripts for video sales letters, product demos, explainer videos, and social media video content. Bridges the gap between marketing copywriting and video production, outputting scripts optimized for handoff to the motion-designer skill.

Integration

This skill works in a pipeline:

VSL Storyboard Writer → Motion Designer → Remotion Implementation

vsl-storyboard-writer produces:

• Complete storyboard scripts
• Scene-by-scene breakdowns
• Copy, messaging, and conversion strategy
• Visual direction and psychology
• Production requirements

motion-designer consumes the storyboard and produces:

• Technical video specifications
• Frame-by-frame animation details
• Remotion implementation guidance

When to Use

Invoke this skill when:

• "Write a video script"
• "Create a VSL"
• "Storyboard a sales video"
• "Script a product demo"
• Creating marketing video content
• Planning social media video ads

Structure

vsl-storyboard-writer/
├── SKILL.md                           # Main skill overview
├── README.md                          # This file
└── rules/
    ├── _storyboard-template.md        # Complete template for all scripts
    ├── vsl-hooks.md                   # Hook formulas and attention-grabbing
    ├── vsl-frameworks.md              # AIDA, PAS, and other VSL structures
    ├── cta-optimization.md            # Call-to-action best practices
    ├── script-pacing.md               # Timing and rhythm
    ├── social-proof-strategy.md       # Testimonials and credibility
    ├── objection-handling.md          # Addressing buyer concerns
    ├── visual-storytelling.md         # Show don't tell principles
    └── motion-designer-handoff.md     # Production-ready formatting

Key Frameworks Included

Hook Types

• Question hooks
• Problem hooks
• Curiosity hooks
• Social proof hooks
• Demonstration hooks
• Pattern interrupt hooks

VSL Formulas

• Hook-CTA: 15-30s social ads
• PAS: Problem → Agitate → Solution (30-90s)
• AIDA: Attention → Interest → Desire → Action (60-120s)
• The Explainer: Context → Mechanism → Benefits (60-180s)
• VSL Classic: Full sales video structure (3-10min)

Conversion Elements

• Strategic social proof placement
• Objection handling sequence
• CTA optimization
• Friction removal
• Urgency and scarcity (authentic only)

Output Format

Produces comprehensive storyboard scripts with:

1. Executive Summary: Goals, audience, framework 2. Story Arc Overview: Emotional journey and narrative flow 3. Scene-by-Scene Breakdown:

• Narrative purpose
• Viewer psychology
• On-screen copy
• Visual description
• Sales elements
• Motion designer notes
• Transitions

4. Asset Requirements: Copy, visuals, brand elements 5. Production Specifications: Platform, format, constraints

Example Use Cases

B2B SaaS Product Demo (90s)

Framework: AIDA Focus: Demo + Social proof + Trial CTA

Social Media Ad (30s)

Framework: Hook-CTA Focus: Fast hook + Quick demo + Clear action

Product Launch Video (3-5min)

Framework: VSL Classic Focus: Story + Problem + Solution + Proof + Offer

Explainer Video (60-120s)

Framework: The Explainer Focus: Education + Benefits + Credibility

Integration with Remotion

This skill creates scripts specifically designed for Remotion video production:

• Scene structure maps to <Sequence> components
• Timing specified in seconds (converted to frames by motion designer)
• Animation guidance compatible with spring() and interpolate()
• Asset requirements list what's needed for implementation

Quality Standards

All storyboards include:

• ✅ Attention-grabbing hook (first 3-5 seconds)
• ✅ Clear value proposition
• ✅ Specific, measurable claims
• ✅ Strategic social proof placement
• ✅ Objection handling woven throughout
• ✅ Strong, clear CTA
• ✅ Production-ready specifications
• ✅ Motion designer handoff format

Best Practices

1. Start with the CTA, work backwards: Know where viewers should end up 2. Show, don't tell: Use visuals to demonstrate, copy to reinforce 3. One message per scene: Don't try to communicate everything everywhere 4. Address objections implicitly: Show solutions, don't name fears 5. Test the hook independently: First 5 seconds should work as standalone ad 6. Leave room for creativity: Provide direction, not dictation 7. Be production-ready: Motion designer shouldn't need to guess

Related Skills

• motion-designer: Takes storyboard scripts and creates technical video specs
• gtm-copywriter: For email/content that supports video campaigns
• senior-product-marketer: For positioning and messaging strategy
• remotion-best-practices: For technical implementation guidance

Created

January 22, 2026

Version

1.0.0

Complete Storyboard Script Template

Impact: CRITICAL

This is the complete template for creating storyboard scripts ready for motion designer handoff. Use this structure for all video storyboards.

---

[Video Title]

Type: [VSL / Product Demo / Explainer / Social Ad / Brand Story] Duration: [X] seconds Objective: [Trial signups / Demo requests / Purchases / Awareness] Target Audience: [Specific persona with context] Framework: [AIDA / PAS / Hook-CTA / Explainer / VSL Classic]

---

Executive Summary

Key Message

[Single sentence: What should viewers remember after watching?]

Desired Action

[Specific CTA: What should viewers do next?]

Success Metrics

• Watch-through rate: [Target %]
• Click-through rate: [Target %]
• Conversion rate: [Target %]

---

Brand & Style Context

Voice: [Professional / Casual / Technical / Friendly] Tone: [Urgent / Calm / Exciting / Authoritative / Playful] Visual Style: [Modern / Minimal / Bold / Clean / Playful]

Brand Guidelines: [Link or brief description]

---

Production Constraints

• Aspect Ratio: [16:9 / 9:16 / 1:1]
• Silent-Viewing Required: [Yes / No]
• Platform: [LinkedIn / YouTube / Website / Instagram / Multiple]
• Deadline: [Date]

---

Story Arc Overview

Narrative Flow

Hook (0-Xs): [One sentence: How we grab attention]

Build (Xs-Ys): [One sentence: How we build interest/desire]

Peak (Ys-Zs): [One sentence: Main value proposition/climax]

Close (Zs-End): [One sentence: CTA and resolution]

Emotional Journey

Start: [Frustrated / Curious / Overwhelmed / Skeptical / etc.] → Middle: [Hopeful / Intrigued / Interested / Relieved] → End: [Confident / Excited / Ready to act]

---

Scene-by-Scene Storyboard

Scene 1: [Descriptive Scene Name] (0s - Xs, Duration: Xs)

Narrative Purpose: [Why this scene exists - what it accomplishes in the overall story]

Viewer Psychology: [What the viewer should think/feel at this moment] [Any objections being addressed]

On-Screen Copy:

[Exact text that appears on screen]
[Use line breaks to show multi-line text]
[Indicate hierarchy if needed:]
  PRIMARY HEADLINE
  Supporting subtext

Voiceover Script (if applicable):

[Exact words spoken]
[Use natural speech patterns]
[Conversational, not formal writing]

Visual Description:

Background:

• [Overall setting/environment description]
• [Color mood: dark/light, warm/cool, specific colors if important]
• [Any gradients, patterns, textures]

Main Elements:

• [Primary focal point - what immediately draws the eye]
• [Position: center/left/right, top/bottom/middle]
• [Approximate size: dominant/medium/small]
• [Key characteristics]

Supporting Elements:

• [Secondary visuals that support the story]
• [Icons, graphics, data visualizations]
• [Any subtle details that add context]

Text Treatment:

• [How text should feel: bold/elegant/technical/casual]
• [Any specific emphasis or hierarchy needed]
• [Animation style: fade in / slide / pop / etc.]

Sales Elements (if present): [Any conversion tactics used in this scene]

• Social proof: [Type - testimonial/logo/stat]
• Scarcity/Urgency: [What creates urgency if applicable]
• Benefit emphasis: [Key benefit being highlighted]
• Objection handling: [Which objection is addressed]
• Risk reversal: [Guarantee or friction removal]

Motion Designer Notes:

Pacing:

• [Fast / Medium / Slow - and why this pace is important]

Emphasis:

• [What moments need visual punctuation]
• [Where to sync with audio beat or music]
• [Key moments that should "pop"]

Style:

• [Bold / Subtle / Playful / Professional / Technical]
• [Reference if helpful: "Like X video at timestamp Y"]
• [Any specific animation techniques to use/avoid]

Transition to Next Scene: [How this scene flows to the next - the connecting tissue] [Why this transition makes narrative sense]

---

Scene 2: [Descriptive Scene Name] (Xs - Ys, Duration: Zs)

[Repeat full structure above for each scene]

---

Scene 3: [Descriptive Scene Name] (Xs - Ys, Duration: Zs)

[Continue for all scenes...]

---

Required Assets

Copy Elements

• [ ] Headline 1: "[Exact copy]"
• [ ] Headline 2: "[Exact copy]"
• [ ] Subhead: "[Exact copy]"
• [ ] CTA copy: "[Exact copy]"
• [ ] Social proof quote 1: "[Full quote with attribution]"
• [ ] Social proof quote 2: "[Full quote with attribution]"

Visual Assets

• [ ] Logo: [Format (SVG/PNG), size requirements]
• [ ] Product Screenshots:
• Screenshot 1: [Specific view/feature to show]
• Screenshot 2: [Specific view/feature to show]
• [ ] Customer Photos: [If using testimonials, how many, what type]
• [ ] Company Logos: [For social proof - which companies, format]
• [ ] Icons: [List specific icons needed]
• Icon 1: [Description]
• Icon 2: [Description]
• [ ] Data Visualizations: [Any charts, graphs needed]

Brand Assets

• [ ] Brand Colors:
• Primary: [#HEX] - [Color name]
• Secondary: [#HEX] - [Color name]
• Accent: [#HEX] - [Color name]
• Background: [#HEX] - [Color name]
• Text: [#HEX] - [Color name]
• [ ] Typography:
• Headline: [Font family, weight]
• Body: [Font family, weight]
• CTA: [Font family, weight]
• [ ] Logo Lockup: [Horizontal / Vertical / Icon only]

Audio (if specified)

• [ ] Background Music: [Style, mood, BPM, energy level]
• [ ] Voiceover: [Who provides, tone, accent, reading speed]
• [ ] Sound Effects: [Key SFX needed]
• SFX 1: [Type, timing: Xs]
• SFX 2: [Type, timing: Xs]

---

Visual References

Style Inspiration

Reference 1: [Video title or link]

• Timestamp: [X:XX]
• Why: [What we like - specific element, style, technique]

Reference 2: [Video title or link]

• Timestamp: [X:XX]
• Why: [What we like about this reference]

What to Avoid

• [Specific styles or techniques to stay away from]
• [Common mistakes in this category of video]
• [Anti-patterns for this industry/product type]

Competitive Context

• [How competitors are doing similar videos]
• [How we want to differentiate]
• [What to do better/different]

---

Review & Approval Process

Timeline

• Storyboard Review: [Date]
• Team reviews this script
• Approve messaging, timing, narrative flow

• Motion Design Spec: [Date]
• Motion designer creates technical spec
• Review animation approach and visual style

• First Cut Review: [Date]
• Review rendered video
• Provide feedback on execution

• Final Delivery: [Date]

Stakeholders

• Primary Reviewer: [Name, role]
• Final Approver: [Name, role]
• Other Reviewers: [Names, roles]

---

Notes & Special Considerations

[Any additional context, requirements, or special considerations]

[Technical constraints]

[Legal/compliance requirements]

[Localization needs]

[Accessibility requirements]

---

Quick Reference Summary

Total Scenes: [N] Total Duration: [X]s Key Moments:

• Hook: [Brief description of hook]
• Main Value Prop: [Scene name, timing]
• Social Proof: [Scene name, timing]
• CTA: [Scene name, timing]

Critical Success Factors: 1. [Most important element #1] 2. [Most important element #2] 3. [Most important element #3]

---

This storyboard script is ready for motion designer handoff. It includes all necessary context, specific visual direction, and production requirements while leaving room for creative execution.

---

Example: Abbreviated 30s Social Ad

For quick reference, here's a condensed example:

---

"Fast Deployment" Social Ad

Type: Social Ad Duration: 30 seconds Objective: Trial signups Framework: Hook-CTA

Story Arc

Hook (0-5s): Problem question Demo (5-22s): Solution in action CTA (22-30s): Clear next step

---

Scene 1: Hook (0-5s)

Narrative Purpose: Immediate pain point identification

On-Screen Copy:

Deployments taking hours?

Visual:

• Background: Dark, code editor with loading spinners
• Main: Progress bar stuck at 43%, clock showing 2 hours elapsed
• Person waiting, frustrated

Psychology: Instant recognition - "that's my problem"

Motion Notes: Fast pace, build tension

Transition: Dark frustration → light relief

---

Scene 2: Solution Demo (5-22s, Duration: 17s)

Narrative Purpose: Show product solving problem

On-Screen Copy:

Deploy in 90 seconds with Shipfast

Visual:

• Background: Clean, light interface
• Main: Simple command line: shipfast deploy
• Progress: 0s → 90s → "Deployed ✓"
• Split screen: Code → Live site

Psychology: "It's that simple?" + speed proof

Sales Element: Specific time claim (90s) with visual proof

Motion Notes: Medium pace, let demo breathe

Transition: Success moment → credibility

---

Scene 3: Social Proof (22-26s, Duration: 4s)

On-Screen Copy:

Join 8,000 developers shipping faster

Visual: Logos: Vercel, Railway, Fly.io

Psychology: FOMO + credibility

---

Scene 4: CTA (26-30s, Duration: 4s)

On-Screen Copy:

Start deploying faster
Free for 14 days • No credit card

Visual: Large CTA button, product in background

Psychology: Clear action, friction removed

---

Assets Needed:

• Logo: Shipfast SVG
• Product: Terminal screenshot
• Logos: Vercel, Railway, Fly.io (monochrome)

Style: Clean, technical, fast-paced

---

Call-to-Action Optimization

Impact: HIGH

The CTA is where conversion happens. Everything before it builds to this moment. A weak CTA wastes everything that came before.

CTA Placement Strategy

Primary CTA Timing

The Two-CTA Strategy

For videos over 60s, use multiple CTAs:

Soft CTA (Mid-video):

• Plant the seed
• Low pressure
• "Learn more" or "See how it works"

Hard CTA (End):

• Clear, specific action
• Remove friction
• Create urgency

CTA Component Anatomy

Complete CTA Structure

Primary Action (Required):
  "Start free trial"

Value Reinforcement (Required):
  "No credit card required"

Timeframe (Optional):
  "14-day trial"

Secondary Action (Optional):
  "Or watch demo"

Good Example

Scene: Final CTA (0-7s within CTA scene)

On-Screen Copy:
  Primary: "Start your free trial"
  Value: "No credit card • 5-minute setup"
  Secondary: "Or schedule a demo"

Visual:
  - Large, clear button: "Start Free Trial"
  - Small text below with friction reducers
  - Smaller "Schedule Demo" link below
  - Product screenshot in background (not logo)

Psychology:
  - Clear primary action (trial)
  - Removes objections (no CC, quick setup)
  - Offers alternative for those not ready (demo)
  - Shows product, not branding

Timing: 7 seconds (adequate time to read and process)

Bad Example

On-Screen: "Learn More"

Why it fails:
- Vague action (learn what? where?)
- No value communicated
- No urgency or next step clarity
- Could mean anything (blog post? whitepaper? product tour?)

Action Word Hierarchy

High-Converting Action Words

Free/No-Risk Actions (Highest conversion):

• "Start free trial"
• "Try free for 14 days"
• "Get instant access"
• "Download free"

Low-Commitment Actions (High conversion):

• "See how it works"
• "Watch demo"
• "Get pricing"
• "Calculate savings"

Medium-Commitment Actions (Medium conversion):

• "Schedule demo"
• "Talk to sales"
• "Request invite"
• "Join waitlist"

Purchase Actions (Lower conversion, higher intent):

• "Buy now"
• "Start plan"
• "Subscribe today"
• "Get started" (if paid)

Words to Avoid

❌ "Learn more" — Too vague ❌ "Submit" — Transactional, cold ❌ "Click here" — Web 1.0, no value ❌ "Sign up" — Feels like work ❌ "Register" — Bureaucratic

Friction Removal

Critical Friction Reducers

✅ "No credit card required"
✅ "Free forever" (if true)
✅ "Cancel anytime"
✅ "5-minute setup"
✅ "No installation needed"
✅ "Works with tools you use"
✅ "Free for 14 days"
✅ "30-day money-back guarantee"

Friction Reducer Placement

Good:
Primary: "Start free trial"
Friction: "No credit card required"

Bad:
Primary: "Sign up"
Friction: [none]

Urgency and Scarcity

Authentic Urgency

✅ Use when genuine:

• "Early access ends Friday"
• "100 spots left in beta"
• "Launch pricing expires in 3 days"
• "Cohort starts next Monday"

❌ Never use if fake:

• Fake countdown timers
• False "only 3 left" claims
• Perpetual "limited time" offers

Good Example (Authentic)

CTA Scene:
Primary: "Join the beta"
Urgency: "We're accepting 500 users this month"
Secondary: "Join 1,200 on the waitlist instead"

Psychology:
- Real scarcity (500 spots)
- Alternative offered (waitlist)
- Social proof built in (1,200 waiting)

Bad Example (Dishonest)

CTA: "Offer expires in 23:59:47"
[Timer resets for every viewer]

Why it fails:
- Dishonest (viewers know this)
- Damages trust
- Converts wrong customers

Visual CTA Best Practices

Button/Visual Design

Good CTA Visual:

Visual Elements:
- Primary CTA button: Large, high contrast, clear text
- Button color: Brand accent or high-visibility color
- Size: ~20% of screen real estate
- Position: Bottom third, centered
- Animation: Subtle pulse or glow
- Supporting text: Below button, smaller
- Background: Product in use (not logo)

Bad CTA Visual:

- Small button or text-only
- Low contrast (white text on light blue)
- Multiple competing CTAs same size
- Logo/branding instead of product
- No animation or draw to CTA

Text Hierarchy

Primary Action (Largest):
  "Start Free Trial"

Value Props (Medium):
  "No credit card • 5-min setup"

Secondary Action (Smallest):
  "Or schedule demo"

Multi-CTA Strategy

For complex or high-ticket products:

Primary/Secondary Pattern

Scene: CTA (8s total)

Primary (0-5s):
  "Start free trial"
  Most prominent, for ready buyers

Secondary (5-8s):
  "Or schedule a demo"
  For those needing human touch

Visual:
  Primary button: Large, animated
  Secondary link: Smaller, below

Psychology:
  Accommodate different readiness levels

CTA Reinforcement

Don't just state the CTA — reinforce why they should act:

Good Example

CTA Scene:
"Start your free trial"
"Join 8,000 teams shipping faster"
[Visual: Happy customers using product]

Reinforcement:
  Social proof reminder
  Benefit reminder (shipping faster)
  Shows real people (not just numbers)

Bad Example

CTA Scene:
"Start your free trial"
[Visual: Company logo]

Why it fails:
  No reinforcement of value
  Branding instead of benefit
  Nothing to build confidence

CTA Duration

Minimum Timing Rules

Principle: Longer videos = more time to process and act on CTA

Platform-Specific CTAs

Social Media (In-Feed)

CTA:
  "Link in bio"
  OR
  "Swipe up" (Stories)
  OR
  "Click to learn more" (with tracking link)

Visual:
  - Arrow pointing to action
  - Text overlay clear and bold

Landing Page Videos

CTA:
  "See pricing below"
  OR
  "Scroll to get started"

Connects video to page elements

Standalone Videos (YouTube, Vimeo)

CTA:
  "Visit [URL]"
  OR
  "Link in description"

Include clickable CTA in video description

CTA Voice and Tone

Match CTA tone to brand and audience:

B2B Professional

"Schedule a demo"
"Request pricing"
"Talk to our team"

Tone: Professional, consultative

B2C Casual

"Get started free"
"Try it now"
"Join thousands already saving"

Tone: Friendly, action-oriented

Technical/Developer

"Start building"
"Fork the repo"
"Read the docs"

Tone: Technical, direct

Testing CTAs

A/B Test Elements

Test one element at a time:

1. Action word: "Start free trial" vs "Get started free" 2. Friction reducer: "No CC" vs "Cancel anytime" 3. Urgency: With vs without limited offer 4. Secondary CTA: With vs without alternative 5. Visual: Button vs text link vs both

Performance Metrics

Track:

• Click-through rate (CTR)
• Conversion rate (completed action)
• Completion rate (started → finished)

Common CTA Mistakes

1. Multiple Primary CTAs

Bad:

"Start trial" (same size as)
"Schedule demo" (same size as)
"Download whitepaper"

Splits attention, reduces conversion on all.

Good:

Primary: "Start trial" (large)
Secondary: "Or schedule demo" (small)

2. CTA Too Early

Bad:

15s video:
  0-5s: Hook
  5-10s: CTA (before showing value)
  10-15s: Product demo

Good:

  0-5s: Hook
  5-12s: Product demo / value
  12-15s: CTA (after value shown)

3. Weak Action Words

Bad: "Learn more", "Click here", "Submit" Good: "Start free trial", "Get instant access", "Try free"

4. No Friction Removal

Bad: "Sign up now" Good: "Start free trial • No credit card required"

5. Dishonest Urgency

Bad: Fake countdown timer Good: Real launch deadline or genuine scarcity

Checklist

• [ ] Clear, specific action (not "learn more")
• [ ] Strong action word (start, get, try, join)
• [ ] Friction reducers included (no CC, free, quick setup)
• [ ] Primary CTA visually dominant
• [ ] Secondary CTA smaller (if present)
• [ ] Value reinforced (social proof or benefit reminder)
• [ ] Adequate time to read (minimum 3s)
• [ ] Urgency authentic (if used)
• [ ] Visual points to CTA (button, arrow, animation)
• [ ] Background shows product, not logo
• [ ] Tone matches brand and audience
• [ ] CTA appears after value established (80%+ into video)
• [ ] Multiple CTAs only if necessary, with clear hierarchy
• [ ] Platform-appropriate (link in bio, clickable button, etc.)
• [ ] Tested against alternatives

Motion Designer Handoff Format

Impact: CRITICAL

The storyboard script is the bridge between sales strategy and video production. It must be detailed enough for the motion designer to execute without guesswork, while leaving room for creative implementation.

The Handoff Philosophy

Your job (Storyboard Writer):

• WHY each scene exists (narrative purpose)
• WHAT appears on screen (copy, key visuals)
• WHAT we want viewers to think/feel (psychology)
• WHEN things happen (timing, pacing)

Motion Designer's job:

• HOW to execute visually (animation style, techniques)
• HOW to make it look good (design decisions)
• HOW to implement in Remotion (technical execution)

Document Structure for Handoff

1. Executive Summary

# [Video Title]

**Project Overview**:
- Type: [VSL / Product Demo / Explainer / Social Ad]
- Duration: [X] seconds
- Primary Goal: [Trial signups / Demo requests / Purchases]
- Target Audience: [Specific persona]

**Key Success Metrics**:
- Watch-through rate: [Target %]
- Click-through rate: [Target %]
- Conversion rate: [Target %]

**Brand Context**:
- Voice: [Professional / Casual / Technical / Friendly]
- Tone: [Urgent / Calm / Exciting / Authoritative]
- Visual Style: [Modern / Minimal / Bold / Playful]
  [Link to brand guidelines if available]

**Production Constraints**:
- Aspect Ratio: [16:9 / 9:16 / 1:1]
- Silent-viewing required: [Yes/No]
- Platform: [LinkedIn / YouTube / Website / Multiple]
- Deadline: [Date]

2. Story Arc Overview

## Narrative Flow

**Hook (0-Xs)**: [One sentence: How we grab attention]
**Build (Xs-Ys)**: [One sentence: How we build interest]
**Peak (Ys-Zs)**: [One sentence: Main value proposition]
**Close (Zs-End)**: [One sentence: CTA and resolution]

**Emotional Journey**:
Start: [Frustrated / Curious / Overwhelmed / etc.]
→ Middle: [Hopeful / Intrigued / Interested]
→ End: [Confident / Excited / Ready to act]

**Key Message**:
[Single sentence viewers should remember]

3. Scene-by-Scene Storyboard

For each scene, include these sections:

## Scene N: [Descriptive Name] (Xs - Ys, Duration: Zs)

**Narrative Purpose**:
[Why this scene exists - what it accomplishes in the story]

**Viewer Psychology**:
[What viewer should think/feel at this moment]
[Any objections being handled]

**On-Screen Copy**:
---
[Exact text that appears on screen]
[Use line breaks for multi-line text]
[Indicate hierarchy: MAIN / supporting]
---

**Voiceover Script** (if applicable):
---
[Exact words spoken]
[Use natural speech patterns, not formal writing]
---

**Visual Description**:
[Describe what viewers see - be specific but not technical]

Background:
  - [Overall setting/environment]
  - [Color mood: dark/light, warm/cool]

Main Elements:
  - [Primary focus - what draws the eye]
  - [Position: center/left/right, top/bottom]
  - [Approximate size: dominant/medium/small]

Supporting Elements:
  - [Secondary visuals that support the story]
  - [Any icons, graphics, data visualizations]

Text Treatment:
  - [How text should feel: bold/elegant/technical]
  - [Any specific emphasis needed]

**Sales Elements** (if present):
[Any conversion tactics used in this scene]
- Social proof: [Testimonial / Logo / Stat]
- Scarcity/Urgency: [What creates urgency]
- Benefit emphasis: [Key benefit highlighted]
- Objection handling: [Which objection addressed]

**Motion Designer Notes**:
[Specific guidance for execution]

Pacing:
  - [Fast/Medium/Slow - and why]

Emphasis:
  - [What moments need visual punctuation]
  - [Where to sync with audio/beat]

Style:
  - [Bold/Subtle/Playful/Professional]
  - [Any animation references: "like X video at timestamp Y"]

**Transition to Next Scene**:
[How this flows to next - the connecting tissue]

4. Asset List

## Required Assets

**Copy Elements**:
- [ ] All headlines: [List each]
- [ ] All body copy: [List each]
- [ ] CTA copy: [Exact wording]
- [ ] Social proof quotes: [Each testimonial]

**Visual Assets**:
- [ ] Logo: [Format, size requirements]
- [ ] Product screenshots: [Specific views needed]
  - Screenshot 1: [Description of what to show]
  - Screenshot 2: [Description]
- [ ] Customer photos: [If using, how many, type]
- [ ] Company logos: [For social proof, which ones]
- [ ] Icons: [List specific icons needed]

**Brand Assets**:
- [ ] Brand colors: [Primary, secondary, accent hex codes]
- [ ] Fonts: [Headline font, body font with weights]
- [ ] Logo lockup: [Horizontal / Vertical / Icon only]

**Audio** (if specified):
- [ ] Background music: [Style, mood, BPM]
- [ ] Voiceover: [Who provides, tone, accent]
- [ ] Sound effects: [Key SFX needed with timing]

5. Reference Examples

## Visual References

**Style Inspiration**:
- Video 1: [Link] - Timestamp: [X:XX]
  Why: [What we like about this]

- Video 2: [Link] - Timestamp: [X:XX]
  Why: [Specific element to reference]

**What to Avoid**:
- [Any specific styles or techniques to stay away from]
- [Common mistakes in this category]

**Competitive Context**:
- [How competitors are doing this]
- [How we want to differentiate]

Scene Description Best Practices

Good Scene Description

## Scene 3: Solution Reveal (15s - 25s, Duration: 10s)

**Narrative Purpose**:
The "a-ha" moment where viewers understand our unique approach. We're
showing that our solution is fundamentally different, not just another
tool in a crowded market.

**Viewer Psychology**:
Curiosity satisfaction ("oh, that's clever") combined with hope
("this could actually work for me"). We're building confidence that
our approach is both novel and practical.

**On-Screen Copy**:
---
One dashboard. Every platform.
Real attribution.
---

**Visual Description**:

Background:
  - Clean, light gradient (white to subtle blue)
  - Professional, uncluttered

Main Elements:
  - Center screen: Unified dashboard interface
  - Multiple marketing platform logos (Google, Facebook, LinkedIn)
    feeding data into the central dashboard
  - Visual "aha": All conflicting data becomes one clear number

Supporting Elements:
  - Small animated data streams flowing from platforms to dashboard
  - Single, prominent ROI number that's clearly accurate

Text Treatment:
  - "One dashboard. Every platform." - Bold, confident
  - "Real attribution." - Emphasized, this is the key promise

**Sales Elements**:
- Unique mechanism: Showing how we're different (unified data)
- Benefit: Implicit (no more confusion)

**Motion Designer Notes**:

Pacing: Medium to slow - let viewers absorb the concept

Emphasis:
  - The moment when multiple data sources consolidate into one
  - The final ROI number appearing (make this satisfying)

Style:
  - Clean, technical but not cold
  - Professional but approachable
  - Reference: Stripe product videos (clean UI demos)

**Transition to Next Scene**:
Dashboard established → zoom into specific feature demo
Natural progression from "what it is" to "how it works"

Bad Scene Description

Scene 3 (15-25s)

Copy: "One dashboard"

Visual: Show the product

Notes: Make it look good

[Why it fails: Too vague, no context, motion designer must guess
everything]

Timing Specifications

How to Specify Timing

Good:

Scene 1: Hook (0s - 5s, Duration: 5s)
Scene 2: Problem (5s - 15s, Duration: 10s)
Scene 3: Solution (15s - 30s, Duration: 15s)

Clear start, end, duration. Easy to understand.

Bad:

Scene 1: About 5 seconds
Scene 2: Then another 10-ish seconds
Scene 3: Rest of the video

Vague, hard to plan.

Timing Flexibility

Indicate where timing is flexible vs fixed:

Scene 4: Demo (20s - 35s, Duration: 15s)
  [Timing: FLEXIBLE - can adjust ±3s if needed for pacing]

Scene 8: CTA (85s - 90s, Duration: 5s)
  [Timing: FIXED - must end at 90s total]

Psychology and Objection Notes

Include viewer psychology and objection handling:

Good Example

**Viewer Psychology**:
At this point, viewers are thinking "this looks interesting but is it
too complicated for my team?" We need to address this directly without
stating it explicitly.

**Objection Handling**:
Complexity concern. Show the interface with minimal UI, emphasize
"5-minute setup" copy, and use social proof from non-technical role
("Even our sales team uses it daily" - VP Sales, CompanyX)

Why This Matters

Motion designer can make visual choices that support the psychology:

• Simple, clean visuals to counter complexity fears
• Emphasize ease-of-use visually
• Choose testimonial that speaks to accessibility

Copy Hierarchy

Make text hierarchy crystal clear:

**On-Screen Copy**:
---
PRIMARY (largest, main focus):
"One dashboard. Every platform."

SECONDARY (supporting):
"Real attribution across all your ads"

TERTIARY (detail, fine print):
"Connect Google, Facebook, LinkedIn, and 12+ platforms"
---

Visual Style Direction

Provide style direction without dictating techniques:

Good Style Direction

**Visual Style**:
- Clean and modern, not overly designed
- Technical enough to be credible, accessible enough to be approachable
- Color palette: Cool (blues, grays) with warm accent (orange) for CTAs
- Reference: Notion product videos - clean, minimal, friendly

**Avoid**:
- Corporate/cold (too much blue/gray)
- Overly playful (we're B2B, not B2C kids product)
- Busy/cluttered (defeats our "simplicity" message)

Bad Style Direction

**Visual Style**:
Use After Effects effect #47 with interpolation set to ease-in-out
cubic bezier at frames 30-45 with damping of 200.

[Why it fails: This is HOW to execute, not WHAT style to achieve.
Let motion designer choose techniques.]

Platform-Specific Notes

Include any platform requirements:

## Platform Requirements

**LinkedIn Feed**:
- Aspect ratio: 1:1 (square)
- Must work without sound (60%+ watch muted)
- Text must be large, readable on mobile
- Avoid tiny UI details (won't be visible)

**YouTube Pre-roll**:
- Aspect ratio: 16:9
- First 5s is unskippable, make it count
- CTA at end with verbal reinforcement

**Website Hero**:
- Aspect ratio: 16:9
- Autoplay, muted, loops
- No time limit, can be longer

Revision and Feedback Process

Include in handoff document:

## Review Process

**First Review** (Storyboard):
- Team reviews this storyboard script
- Approve messaging, timing, flow
- Due: [Date]

**Second Review** (Motion Design Spec):
- Motion designer creates detailed spec with technical details
- Review animation approach, visual style
- Due: [Date]

**Third Review** (First Cut):
- Review rendered video
- Feedback on execution
- Due: [Date]

**Final Delivery**:
- Due: [Date]

Checklist

Before handing off to motion designer:

Content Complete:

• [ ] Every scene has narrative purpose explained
• [ ] All on-screen copy is finalized
• [ ] Viewer psychology noted for each scene
• [ ] Transition logic explained
• [ ] Sales elements identified

Production Ready:

• [ ] Timings specified (start, end, duration)
• [ ] Visual descriptions are specific but not prescriptive
• [ ] Style direction provided with references
• [ ] Assets listed and available or sourced
• [ ] Platform requirements noted

Context Provided:

• [ ] Project overview with goals
• [ ] Target audience defined
• [ ] Brand voice and tone clear
• [ ] Visual reference examples included
• [ ] Success metrics defined

Handoff Quality:

• [ ] Motion designer can execute without guessing
• [ ] No conflicting instructions
• [ ] Timing adds up correctly
• [ ] No assumed knowledge (everything explained)
• [ ] Creative freedom preserved (not over-specified)

Review Process:

• [ ] Timeline and milestones clear
• [ ] Feedback process defined
• [ ] Key stakeholders identified
• [ ] Revision rounds planned

Objection Handling in Video Scripts

Impact: HIGH

Every viewer has doubts. Great VSL scripts address objections before they become blockers. The key is addressing concerns without explicitly stating them in a way that feels defensive.

Common Objection Categories

1. Does It Work? (Efficacy)

Viewer thinking: "This sounds good, but does it actually work?"

How to address:

• Demonstrate in action (show, don't claim)
• Specific results data
• Before/after comparisons
• Testimonials with measurable outcomes

Good Example:

Scene: Demo (30-45s)

Visual:
  - Live screen recording
  - Real workflow being completed
  - Timer showing: 2min 13s (vs "2 hours before")

On-Screen: "From draft to deployed in 2 minutes"

Psychology:
  Addresses efficacy through demonstration
  Specific timing proves it works
  Viewer sees it happen (not just claimed)

Bad Example:

On-Screen: "Yes, it really works! We promise!"

Why it fails:
  Defensive language
  No proof
  Raises suspicion by addressing doubt explicitly

2. Will It Work for Me? (Relevance)

Viewer thinking: "Looks good for others, but my situation is different"

How to address:

• Show diverse use cases
• Testimonials from relatable personas
• "Works with what you already use"
• Flexible/customizable messaging

Good Example:

Scene: Use Cases (35-50s)

Visual: Three quick examples
  - Small team (5 people)
  - Mid-size company (50 people)
  - Enterprise (500+ people)

On-Screen: "Scales from teams of 5 to 5,000"

Testimonials:
  "We're just 3 people" — Startup Founder
  "We manage 200 developers" — Engineering VP

Psychology:
  Shows range of applicability
  Viewers see themselves represented
  Addresses "not for me" objection

Bad Example:

On-Screen: "Works for everyone!"

Why it fails:
  Too generic
  Not believable
  No specific relevance signals

3. Is It Too Complicated? (Complexity)

Viewer thinking: "This looks powerful but probably hard to use"

How to address:

• Show simplicity in demo
• Time-to-value messaging ("5-minute setup")
• Simple UI visuals
• Non-technical testimonials

Good Example:

Scene: Ease-of-Use (25-35s)

Visual:
  - Clean, minimal interface
  - 3-step process shown quickly
  - Testimonial from non-technical role

On-Screen: "Up and running in 5 minutes"

Testimonial: "Even our sales team uses it daily"
— VP Sales (not technical role)

Psychology:
  Simple UI shown, not claimed
  Quick setup time specific
  Non-technical user proves accessibility

Bad Example:

On-Screen:
"Don't worry, it's not as complicated as it looks!
We have extensive documentation and support"

Why it fails:
  Highlights that it looks complicated
  Defensive tone
  "Extensive documentation" suggests complexity

4. Is It Worth the Money? (Value)

Viewer thinking: "Seems expensive / not sure if ROI is there"

How to address:

• ROI calculation shown
• Time/money saved metrics
• Cost of NOT solving problem
• Value equation (what you get)

Good Example:

Scene: Value Proposition (40-52s)

Visual:
  Before: $15k/month ad spend + no clarity = wasted budget
  After: $15k/month + full attribution = 3x ROI

On-Screen: "Know exactly where every dollar goes"

Data: "Average customer saves $47k in year 1"

Psychology:
  Shows cost of problem (wasted ad spend)
  Quantifies value (savings amount)
  Frames as investment, not cost

Bad Example:

On-Screen: "It's actually very affordable!"

Why it fails:
  Subjective (affordable to whom?)
  No context for value
  Sounds defensive

5. What If It Doesn't Work for Me? (Risk)

Viewer thinking: "What if I commit and it's not right?"

How to address:

• Money-back guarantee
• Free trial
• No credit card required
• Easy cancellation
• Implementation support

Good Example:

Scene: Risk Reversal (78-85s, before CTA)

Visual:
  - "14-day free trial" badge
  - "No credit card required"
  - "Cancel anytime"

On-Screen: "Try risk-free for 14 days"

Psychology:
  Removes financial risk
  Removes commitment friction
  Addressed implicitly (no "worried?" language)

Bad Example:

On-Screen:
"We know you might be worried about trying new software,
but don't worry, we have a refund policy"

Why it fails:
  Explicitly names the fear
  Wordy and defensive
  Weak language ("refund policy" vs "guarantee")

6. Do I Need This Now? (Urgency)

Viewer thinking: "I'll think about it and come back later"

How to address:

• Cost of delay (problem getting worse)
• Limited availability (if genuine)
• Competition moving faster
• Opportunity cost

Good Example:

Scene: Urgency (70-78s)

Visual:
  - Competitor data shown
  - Market moving fast
  - "Early access pricing ends Friday"

On-Screen: "Your competitors are already shipping faster"

Psychology:
  FOMO (competition is acting)
  Real deadline (pricing ends Friday)
  Not manipulative if genuine

Bad Example:

[Fake countdown timer]
"Only 3 left in stock!"
"Offer expires in 23:59:47"

Why it fails:
  Dishonest (resets for every viewer)
  Damages trust permanently
  Attracts wrong customers

Objection Handling Sequence

The Order Matters

Address objections in this typical sequence:

1. Does it work? (30-40% mark)
   Demonstrate, show results

2. Will it work for me? (40-50% mark)
   Use cases, flexible positioning

3. Is it too complicated? (50-60% mark)
   Show ease of use, quick setup

4. Is it worth it? (60-70% mark)
   ROI, value equation

5. What's the risk? (75-85% mark)
   Guarantee, trial, friction removal

6. Why now? (85-90% mark)
   Urgency, opportunity cost

Good Example (90s video)

Scene 1-3 (0-30s): Hook + Problem + Solution Intro
  [Build interest first]

Scene 4 (30-40s): Demo
  [Addresses: Does it work?]
  Shows product in action, working

Scene 5 (40-50s): Use Cases
  [Addresses: Will it work for me?]
  Shows 3 different team sizes using it

Scene 6 (50-58s): Quick Setup
  [Addresses: Too complicated?]
  "5-minute setup" + simple UI demo

Scene 7 (58-68s): ROI Data
  [Addresses: Worth the money?]
  "$47k average savings in year 1"

Scene 8 (68-78s): Social Proof
  [Reinforces: It works + Builds trust]
  Testimonials from recognizable companies

Scene 9 (78-85s): Risk Reversal
  [Addresses: What's the risk?]
  "14-day free trial, no credit card"

Scene 10 (85-90s): CTA with urgency
  [Addresses: Why now?]
  "Join 2,000 teams who switched this month"

Implicit vs Explicit Objection Handling

Implicit (Preferred)

Address the concern without naming it

Good:
  Show: Simple 3-step process
  Copy: "Up and running in 5 minutes"

Objection addressed: Complexity
Method: Shown and quantified
Never said: "We know you think this is complicated"

Explicit (Use Sparingly)

Name the objection directly

Use only when:
  - Major common objection
  - Industry-specific concern
  - Needs explicit addressing

Example:
  "No migration required"
  "Works with your existing stack"
  "GDPR compliant"

These explicitly name concerns but in positive frame

Bad Example (Too Explicit)

On-Screen:
"We know you're worried about:
- Price
- Complexity
- Whether it works
- Implementation time

But don't worry! We have solutions for all of these..."

Why it fails:
  Plants doubts viewer may not have had
  Defensive tone throughout
  Spends time on objections vs value

Industry-Specific Objections

B2B SaaS

Common objections: 1. Integration with existing tools 2. Security/compliance 3. Implementation time 4. Change management 5. Pricing/contract terms

How to address:

Scene: Enterprise Ready (55-65s)

Visual:
  - Integration logos (Slack, Salesforce, etc.)
  - Security badges (SOC 2, GDPR)
  - "Deploy in hours, not months"

On-Screen: "Works with tools you already use"

Testimonial: "Live in production same day"
— CTO, EnterpriseCompany

Addresses:
  ✓ Integration concerns (logos + "works with")
  ✓ Security (badges shown)
  ✓ Implementation (hours not months)
  ✓ Change management (same day live)

Consumer Product

Common objections: 1. Will it actually work? 2. Is it safe/legitimate? 3. Shipping/returns 4. Compared to alternatives 5. Worth the price?

How to address:

Scene: Trust Signals (40-50s)

Visual:
  - Real customer photos (not stock)
  - Star rating: 4.8/5 (12,000 reviews)
  - "Free returns, 30-day guarantee"
  - Comparison chart (vs alternatives)

Addresses:
  ✓ Efficacy (reviews + ratings)
  ✓ Trust (real customers)
  ✓ Risk (free returns, guarantee)
  ✓ Value (comparison shows advantages)

Developer Tools

Common objections: 1. Lock-in concerns 2. Learning curve 3. Performance impact 4. Open source alternatives 5. Vendor stability

How to address:

Scene: Technical Reassurance (45-60s)

Visual:
  - Code example showing simple API
  - "Export your data anytime"
  - Performance benchmark vs alternatives
  - GitHub stars: 15k+

On-Screen: "Open core, no lock-in"

Addresses:
  ✓ Lock-in (data export + open core)
  ✓ Learning curve (simple API shown)
  ✓ Performance (benchmarks)
  ✓ Stability (GitHub stars = community)

Objection Handling Through Visual Proof

Show, Don't Defend

Instead of saying: "It's not complicated" Show: Clean, simple interface in action

Instead of saying: "It really works" Show: Before/after results with data

Instead of saying: "It's worth the price" Show: ROI calculation with real numbers

Instead of saying: "It works for teams like yours" Show: Testimonial from someone exactly like viewer

Timing Objection Handling

Too Early

Bad:

0-15s: Hook + Problem
15-60s: Wall of objection handling
60-90s: Rushed CTA

Why it fails:
  Addresses objections before establishing value
  Defensive from the start
  Viewer hasn't seen why they should care

Just Right

Good:

0-30s: Hook + Problem + Solution intro
30-75s: Demo + Value + Objection handling woven in
75-90s: Final reassurance + CTA

Why it works:
  Value established first
  Objections addressed as they arise naturally
  Smooth flow, not defensive

Checklist

Objection Coverage:

• [ ] "Does it work?" addressed through demo/proof
• [ ] "Will it work for me?" addressed through use cases/testimonials
• [ ] "Too complicated?" addressed through simplicity signals
• [ ] "Worth the money?" addressed through value/ROI
• [ ] "What's the risk?" addressed through guarantee/trial
• [ ] "Why now?" addressed through urgency (if applicable)

Handling Method:

• [ ] Implicit handling preferred (show, don't name)
• [ ] Explicit only when necessary (compliance, integration)
• [ ] Positive framing (what we do vs what we're not)
• [ ] No defensive language ("don't worry", "we know you're concerned")

Timing:

• [ ] Objections addressed after value established (30%+ mark)
• [ ] Sequence follows natural customer journey
• [ ] Risk removal near CTA (80%+ mark)
• [ ] Not front-loaded defensively

Proof Quality:

• [ ] Demonstrated visually when possible
• [ ] Specific data/metrics used
• [ ] Testimonials are relevant and credible
• [ ] Claims are honest and verifiable

Industry Fit:

• [ ] Addresses category-specific concerns
• [ ] Uses appropriate proof types for audience
• [ ] Security/compliance addressed if B2B
• [ ] Trust signals appropriate for audience sophistication

Script Pacing and Timing

Impact: HIGH

Pacing determines whether viewers stay engaged or drop off. Great video scripts breathe - they know when to move fast and when to let moments land.

Pacing Principles

The 3-Second Rule

Viewers need time to: 1. See what's on screen (0.5s) 2. Read the text (1.5-2s) 3. Process the message (0.5-1s)

Minimum scene duration: 3 seconds for simple messages

Reading Time Formula

Reading time (seconds) = (Word count ÷ 3) + 1

Examples:
"Try free today" (3 words) = 2s minimum
"Transform your workflow in minutes" (5 words) = 2.7s minimum
"Join 10,000 teams already shipping faster" (6 words) = 3s minimum

Add +1s if visual is complex or if introducing new concept.

Scene Duration Guidelines

Micro-Scenes (2-5s)

Use for:

• Simple text statements
• Quick transitions
• Logo/branding moments
• Single product screenshots

Example:

Scene: Hook (0-3s)
Copy: "Tired of manual data entry?"
Visual: Person frustrated at spreadsheet
Duration: 3s

Why this works:
- Simple question (5 words = 2.7s minimum)
- Visual reinforces (not complex)
- 3s total is adequate

Short Scenes (5-10s)

Use for:

• Problem statements with context
• Single feature demonstrations
• Testimonial quotes
• Before/after comparisons

Example:

Scene: Problem Detail (5-13s, Duration: 8s)
Copy: "Your sales team spends 15 hours per week on admin tasks instead of selling"
Visual: Split screen showing time breakdown
Duration: 8s

Why this works:
- Longer copy (13 words = 5.3s to read)
- Visual requires processing (data breakdown)
- 8s allows message to land

Medium Scenes (10-20s)

Use for:

• Multi-step demonstrations
• Story sequences
• Multiple benefit highlights
• Complex transformations

Example:

Scene: Three-Step Demo (20-35s, Duration: 15s)
Step 1 (5s): "Connect your tools"
Step 2 (5s): "AI analyzes your data"
Step 3 (5s): "Get insights instantly"

Why this works:
- Three distinct moments need separation
- 5s each allows read + process + transition
- Total 15s feels complete, not rushed

Long Scenes (20-30s+)

Use for:

• Detailed product walkthroughs
• Story narratives
• Multiple testimonials in sequence
• Complex problem explanations

Only in videos 90s+. Shorter videos can't afford long scenes.

Pacing Patterns

Fast → Slow → Fast

Pattern: Open fast, slow down for key message, speed up to close

Hook (0-5s): FAST
  Quick cuts, energetic
  "Grab attention"

Build (5-20s): MEDIUM
  Moderate pace
  "Build understanding"

Peak (20-35s): SLOW
  Let key message land
  "This is important"

Close (35-45s): FAST
  Drive to action
  "Act now"

Good Example (45s video)

Scene 1: Hook (0-3s) - FAST
  Bold question, quick visual

Scene 2: Problem (3-10s) - MEDIUM
  7s to establish pain point

Scene 3: Solution Intro (10-18s) - MEDIUM
  8s to introduce product

Scene 4: Key Benefit (18-30s) - SLOW
  12s to show transformation (most important)

Scene 5: Social Proof (30-37s) - MEDIUM
  7s for testimonial

Scene 6: CTA (37-45s) - FAST
  8s clear call to action

Rhythm: Fast hook → steady build → slow emphasis → fast close

Bad Example

All scenes 5s each, same pace throughout

Why it fails:
- Robotic, no rhythm
- No emphasis on what matters
- Viewers tune out the monotony

Information Density

Text-to-Duration Ratio

Principle: Voiceover can contain more info than on-screen text (viewers can read faster than speech).

Good Example (Appropriate Density)

Scene: Feature Demo (10s)

On-Screen:
"Instant sync across devices"
(5 words)

Voiceover:
"Changes you make on desktop appear instantly on mobile. No manual sync, no delays."
(14 words)

Duration: 10s

Why this works:
- On-screen: Simple, readable
- VO: Adds context without overwhelming
- Both together < 20 words for 10s scene

Bad Example (Too Dense)

Scene: Feature Demo (8s)

On-Screen:
"Real-time synchronization across all devices and platforms with automatic conflict resolution and offline support"
(15 words)

Duration: 8s

Why it fails:
- 15 words needs ~6s just to read
- Only 2s to process
- Too much information for timeframe

Breathing Room

The Pause That Sells

After important claims, pause before moving on:

Good Example:

Scene 4: Key Claim (15-25s)
  Copy (15-20s): "10x faster than spreadsheets"
  Visual: Dramatic comparison
  [1-2s pause - no new text]
  Next element (22-25s): Social proof appears

Why it works: Pause lets claim sink in, creates emphasis

Bad Example:

Scene 4: Rushed (15-20s)
  Copy (15-17s): "10x faster"
  Copy (17-20s): "Used by 5,000 teams"
  [No pause between claims]

Why it fails: No time to process first claim before second claim

Transition Timing

Transition Pacing

Good Example

Hook (0-5s)
  → Quick fade (0.3s)
Problem (5-15s)
  → Medium transition (0.8s) [major section change]
Solution (15-35s)
  → Quick fade (0.3s)
Social Proof (35-42s)
  → Quick fade (0.3s)
CTA (42-50s)

Total transitions: 2.2s (4.4% of 50s video)

Rule: Transitions should be <5% of total video duration

Bad Example

Every transition: 2s long
10 scenes × 2s = 20s of transitions in 60s video (33%)

Why it fails: More time transitioning than communicating

Platform-Specific Pacing

Social Feed Videos (15-30s)

Pacing: FAST throughout

• Hook: 2-3s max
• Each scene: 3-6s
• Minimize transitions
• No slow moments (viewers scroll fast)

Good: 0-3s hook, 3-12s value, 12-18s proof, 18-30s CTA
Bad: 0-8s slow brand intro, then rushed content

Explainer Videos (60-90s)

Pacing: VARIED

• Can afford slower build
• 10-15s scenes for complex concepts
• Strategic pauses
• Build → peak → resolve rhythm

Good: 0-5s hook, 5-20s problem, 20-50s solution demo, 50-70s proof, 70-90s CTA
Bad: Same pace throughout, no emphasis

Long-Form VSL (3-10min)

Pacing: SLOW with punctuation

• Story can breathe
• 20-30s scenes for depth
• Dramatic pauses before reveals
• Multiple peaks and valleys

Good: Story arc with varying intensity, pauses for major claims
Bad: Monotonous presentation voice, no energy shifts

Rhythm and Beat

Musical Thinking

Think of your script like a song:

Verse (builds energy):

• Problem description
• Steady, building pace

Chorus (peak energy):

• Key benefit reveal
• Memorable, emphasized

Bridge (shift):

• Social proof
• Different energy, validates chorus

Outro (resolution):

• CTA
• Clear, decisive

Good Example (60s)

Verse 1 (0-15s): Problem + agitation
  Medium pace, building tension

Chorus 1 (15-25s): Solution reveal
  Emphasis, slower, let it land

Verse 2 (25-40s): How it works
  Medium pace, demonstrating

Chorus 2 (40-50s): Transformation
  Emphasis again, mirror first chorus

Outro (50-60s): CTA
  Fast, decisive

Pacing Anti-Patterns

1. Rushed Hook

Bad:

0-1.5s: Question appears and disappears

Viewers can't read it before it's gone.

Good:

0-4s: Question appears, holds, begins transition

2. Dead Air

Bad:

Long pause with nothing happening (3s+ of static screen)

Good:

Pauses include subtle animation, keeps visual interest

3. Uniform Scenes

Bad:

All scenes exactly 5s, perfectly uniform

Feels robotic, no emphasis.

Good:

Varied: 3s, 7s, 5s, 10s, 4s, 8s

Creates rhythm, emphasizes what matters.

4. Too Many Transitions

Bad:

Scene (2s) → Transition (1s) → Scene (2s) → Transition (1s)

50% transitions.

Good:

Scene (5s) → Quick transition (0.3s) → Scene (7s) → Quick transition (0.3s)

5% transitions.

Pacing Checklist

Before finalizing timing:

Reading Time:

• [ ] All text has minimum 3s on screen
• [ ] Complex ideas have +1-2s extra
• [ ] Reading time calculated (words ÷ 3 + 1)

Rhythm:

• [ ] Varied scene lengths (not all identical)
• [ ] Fast → Medium → Slow → Fast pattern (or similar)
• [ ] Key messages have breathing room
• [ ] No scene <2s (too fast to register)

Transitions:

• [ ] Transitions <5% of total duration
• [ ] Transition speed matches energy
• [ ] Major section changes have longer transitions

Emphasis:

• [ ] Most important scene is slowest/longest
• [ ] CTA has adequate time (min 5s)
• [ ] No dead air (always visual interest)

Platform:

• [ ] Pace matches platform (social=fast, long-form=varied)
• [ ] Silent viewing considered (text duration)
• [ ] Attention span respected (hook fast enough)

Information Density:

• [ ] Text-to-duration ratio appropriate
• [ ] On-screen text < 25 words per scene
• [ ] Voiceover (if used) < 60 words per scene
• [ ] Complex visuals have extra processing time

Social Proof Strategy and Placement

Impact: HIGH

Social proof builds trust and reduces risk. Strategic placement amplifies conversion, while poor placement wastes valuable credibility signals.

Types of Social Proof

1. Customer Count

Use when: Large numbers, growing fast

Good:
"Join 27,000 engineering teams"
"10,000+ developers building faster"
"2.3M projects created"

Bad:
"Thousands of happy customers"
"Many people use our product"

Why specificity matters: "27,000" is credible. "Thousands" could be 2,000.

2. Company Logos

Use when: Recognizable brands use your product

Good:
3-6 well-known logos (Airbnb, Stripe, Figma)
Caption: "Trusted by leading companies"

Bad:
20 tiny logos viewers can't read
Mix of unknown companies with 1-2 recognizable ones

Rule: 3-6 logos maximum. More dilutes impact.

3. Testimonial Quotes

Use when: Specific results, emotional impact, relatable stories

Good:
"Cut our onboarding time from 2 weeks to 2 days"
— Sarah Chen, VP Eng, TechCorp

Bad:
"Great product, very helpful!"
— John S.

Elements of strong testimonial:

• Specific outcome (2 weeks → 2 days)
• Full name and title (credibility)
• Company name (context)

4. User-Generated Results

Use when: Visible, measurable outcomes

Good:
"127,000 videos created this month"
"$14M in sales attributed"
"2.8M hours saved"

Bad:
"Lots of happy users"
"Great results"

5. Press/Media Mentions

Use when: Featured in recognizable publications

Good:
Logo badges: TechCrunch, Forbes, WSJ
"Featured in TechCrunch"

Bad:
Small, unknown blogs
"As seen in..." with 15 tiny logos

6. Expert Endorsements

Use when: Industry authority recommends you

Good:
"The future of design collaboration"
— Dylan Field, CEO, Figma

Bad:
Generic endorsement from unknown person

7. Awards and Recognition

Use when: Won relevant, credible awards

Good:
"ProductHunt #1 Product of the Day"
"G2 Leader 2024"
"Fast Company Innovation Award"

Bad:
Made-up awards
Self-given "Best in Category"

Strategic Placement

Early Social Proof (15-25% mark)

Purpose: Establish credibility before making big claims

What to use:

• Customer count
• Company logos
• Press mentions

Good Example (60s video):

Scene 3 (10-15s): After hook and problem, before solution
"Already trusted by 5,000 teams at companies like..."
[Logos: Stripe, Notion, Linear]

Why here: Builds credibility before we make claims about our solution

Bad Example:

Scene 1 (0-5s): Hook with logos immediately
[Logos plastered on screen from the start]

Why it fails: Wastes hook opportunity, feels like bragging before
establishing value

Feature Proof (40-60% mark)

Purpose: Validate each key claim with evidence

What to use:

• Specific testimonials
• Results data
• Before/after metrics

Good Example (90s video):

Scene 5 (35-45s): After demonstrating "Fast deployment" feature
"We deployed 5x more often after switching"
— Maria Santos, CTO, StartupCo

Why here: Immediately validates claim we just made

Bad Example:

Show 3 features (20-40s)
Then dump all testimonials at end (70-80s)

Why it fails: Testimonials disconnected from what they validate

Final Proof (80-90% mark)

Purpose: Remove final doubts before CTA

What to use:

• Impressive aggregate results
• Growth numbers
• Risk-reversal signals

Good Example (60s video):

Scene 7 (50-55s): Right before CTA
"127,000 projects shipped last month"
"14-day money-back guarantee"

Why here: Removes final objections (does it work? is it risky?)

Social Proof Combinations

The Three-Layer Approach

Layer different proof types for maximum impact:

Good Example:

Early (15s): Customer count
  "10,000 teams already shipping faster"
  [Establishes scale]

Middle (35s): Specific testimonial
  "Reduced deployment time from 2 hours to 5 minutes"
  — Engineering Lead
  [Validates specific benefit]

Late (55s): Growth signal
  "2,000 teams joined last month"
  [Shows momentum, FOMO]

Bad Example:

Dump everything at once:
"10,000 teams, featured in TechCrunch, 99% customer satisfaction,
loved by developers, award-winning platform"

Why it fails: Overwhelming, sounds desperate, nothing stands out

Format and Presentation

Testimonial Formatting

Good Format:

On-Screen:
  "This cut our demo prep time by 90%"

  — Alex Thompson
  VP Sales, CloudTech
  [Small headshot photo]

Visual:
  - Quote marks visible
  - Attribution below, smaller text
  - Photo adds credibility (real person)
  - Company context helps (CloudTech suggests B2B SaaS)

Bad Format:

On-Screen:
  Alex T. said our product is great!

Visual:
  - No quote marks
  - No context (who is Alex?)
  - Feels fake/generic

Logo Display

Good:

3-4 logos displayed:
  - Equal size
  - Monochrome or subtle color
  - Recognizable brands
  - Caption: "Trusted by" or "Used by"

Layout: Horizontal row, centered

Bad:

12 logos:
  - Different sizes
  - Mix of color and B&W
  - Crammed together
  - Unreadable at mobile size

Results Display

Good:

Large number: "127,000"
Context: "videos created"
Timeframe: "last month"

Visual: Number animated/counting up

Bad:

"Lots of videos created by many users over time"

Why it fails: No specific numbers, no impact

Social Proof for Different Stages

Awareness Stage (Cold Traffic)

Use: Broad credibility signals

✅ Customer count
✅ Company logos
✅ Press mentions

❌ Detailed case studies (too much, too soon)

Consideration Stage (Problem-Aware)

Use: Specific validation

✅ Testimonials with results
✅ Before/after metrics
✅ Use case stories

❌ Generic "great product" quotes

Decision Stage (Solution-Aware)

Use: Risk-removal proof

✅ Guarantees
✅ Trial/refund policy
✅ Success rates
✅ Implementation stats

❌ Just repeating earlier proof

Industry-Specific Social Proof

B2B SaaS

Most effective: 1. Company logos (peers) 2. Specific ROI/time-saved metrics 3. Title + company testimonials

Example:

"2,000 revenue teams using Acme"
[Logos: Salesforce, HubSpot, Gong]
"Closed 40% more deals in Q1" — VP Sales, TechCo

B2C Product

Most effective: 1. User count 2. User-generated content 3. Star ratings / reviews

Example:

"50,000 homes organized in 30 days"
[Photo montage: Real customer spaces]
"4.8 stars, 12,000 reviews"

Developer Tools

Most effective: 1. GitHub stars 2. Developer testimonials 3. Technical metrics

Example:

"15k+ GitHub stars"
"Our deploy time went from 45min to 3min" — Lead Engineer
"Used in 50k projects"

Social Proof Mistakes

1. Too Early / Too Much

Bad:

0-5s: Hook
5-30s: Wall of logos, testimonials, stats, awards

Why it fails: Bragging before establishing value

Good:

0-5s: Hook
5-15s: Problem
15-20s: Brief credibility (logos)
20-50s: Solution demo
50-55s: Specific testimonial

2. Generic / Vague

Bad:

"Customers love us!"
"Great product, highly recommended"
"Thousands of satisfied users"

Good:

"Reduced churn from 8% to 2% in 60 days"
"Saved our team 15 hours per week"
"10,347 teams actively using"

3. Unrelatable

Bad (For SMB product):

"Used by Google, Amazon, Microsoft"

Why it fails: SMBs think "this isn't for us"

Good:

"Used by 2,000 teams at 50-200 person companies"

4. Fake or Exaggerated

Bad:

Made-up testimonials
Stock photo "customers"
Inflated numbers

Why it fails: Kills trust permanently

Good:

Real testimonials
Real photos
Accurate numbers

5. Disconnected from Claims

Bad:

Claim (30s): "Deploy 10x faster"
Testimonial (50s): "Great customer support"

Why it fails: Testimonial doesn't validate claim

Good:

Claim (30s): "Deploy 10x faster"
Testimonial (35s): "Went from 2 hour deploys to 12 minutes"

Social Proof by Video Length

15-30s (Social Ads)

Include: 1 type only

Option A: Customer count + logos
Option B: Single powerful testimonial
Option C: Impressive results number

Don't try to fit multiple types

30-60s (Product Teasers)

Include: 2 types

Early (15s): Logos or customer count
Late (50s): Specific testimonial or results

60-120s (Explainers)

Include: 3 types

Early (20s): Logos (credibility)
Middle (50s): Testimonial (validation)
Late (100s): Results/guarantee (risk removal)

3-10min (VSL)

Include: 4-5 types throughout

Multiple testimonials (different aspects)
Case studies with detail
Various proof types woven throughout
Cumulative credibility building

Checklist

Selection:

• [ ] Social proof type matches audience stage
• [ ] Numbers are specific (27,000 not "thousands")
• [ ] Testimonials include name, title, company
• [ ] Testimonials describe specific outcomes
• [ ] Company logos are recognizable to target audience
• [ ] 3-6 logos maximum (not logo wall)

Placement:

• [ ] Not in the first 10% (let hook breathe)
• [ ] Placed near related claims (validates features)
• [ ] Final proof right before CTA (removes objections)
• [ ] Spaced throughout (not all dumped at end)
• [ ] Amount matches video length (more for longer)

Credibility:

• [ ] All proof is genuine and accurate
• [ ] Photos are real people (not stock)
• [ ] Testimonial quotes are real and attributed
• [ ] Numbers are up-to-date
• [ ] Claims can be verified

Presentation:

• [ ] Text is readable (size, duration)
• [ ] Logos are clear and appropriately sized
• [ ] Visual hierarchy draws attention to proof
• [ ] Testimonial format includes attribution
• [ ] Results shown with context and timeframe

Strategy:

• [ ] Builds credibility progressively
• [ ] Matches audience sophistication
• [ ] Supports conversion goal
• [ ] Doesn't feel like bragging
• [ ] Leaves room for product to be the hero

Visual Storytelling - Show Don't Tell

Impact: MEDIUM-HIGH

Video is a visual medium. When you can show something, don't tell it. Great VSL scripts use visuals to communicate half the message, with copy reinforcing what viewers see.

The Show/Tell Balance

The 60/40 Rule

In product videos, aim for:

• 60% shown visually (demo, transformation, before/after)
• 40% told with copy (context, benefits, CTA)

Good Example

Scene: Speed Feature (10s)

SHOW (60%):
  Visual: Split screen
    Left: Progress bar slowly filling (old way)
    Right: Instant completion (new way)
  Clock showing time: 45 minutes vs 2 minutes

TELL (40%):
  On-screen: "23x faster processing"

Why it works:
  Visual demonstrates speed difference
  Copy quantifies what viewers just saw
  Both reinforce same message

Bad Example

Scene: Speed Feature (10s)

SHOW:
  Generic product screenshot (static)

TELL:
  On-screen: "Our product processes data 23x faster than
  traditional solutions using advanced algorithms and
  optimized architecture"

Why it fails:
  90% telling, 10% showing
  Viewers don't see speed, just read claim
  No visual proof

Visual Story Techniques

1. Before/After Transformation

Most powerful visual storytelling technique for product videos

Good Example:

Scene: Transformation (12s)

Visual Sequence:
  Before (0-4s):
    - Cluttered, chaotic workspace
    - Multiple tabs, apps, sticky notes
    - Dark, messy colors (#666, #999)
    - Person looking stressed

  Transition (4-6s):
    - Smooth morph animation
    - Chaos organizing itself

  After (6-12s):
    - Clean, single interface
    - Organized, clear workflow
    - Bright, clean colors (#fff, #4A90E2)
    - Person relaxed, smiling

On-Screen: "One workspace. Everything organized."

Why it works:
  Story told primarily through visual contrast
  Copy reinforces but doesn't need to explain
  Emotional journey clear without words

2. Problem Visualization

Show the pain point, don't just describe it

Good Example:

Scene: Problem (8s)

Visual:
  - Designer switching between 12 different apps
  - Fast cuts showing app switching
  - Each switch shows loading spinner
  - Clock ticking, time wasting
  - Designer's frustration building

On-Screen: "47 tools. One project."

Why it works:
  Viewer feels the frustration visually
  Copy is minimal but memorable
  Exaggeration (47 tools) is visual, not just claim

Bad Example:

Scene: Problem (8s)

Visual:
  - Static image of person at desk

On-Screen:
  "Modern designers use too many disconnected tools which
  creates inefficiency and frustration in their workflow"

Why it fails:
  Entirely told, not shown
  Static visual adds nothing
  Paragraph of text does all the work

3. Demonstration in Action

Show the product working, not screenshots

Good Example:

Scene: Demo (15s)

Visual:
  - Mouse cursor enters frame
  - Types command: "/brand"
  - Instant dropdown with brand assets
  - Selects logo
  - Logo appears in design
  - All in real-time, no cuts

On-Screen: "Instant access to brand assets"

Why it works:
  Actual interaction shown
  Speed is visible, not claimed
  Viewer thinks "I could do that"

Bad Example:

Scene: Demo (15s)

Visual:
  - Static screenshot of interface
  - Red arrows pointing to features

On-Screen:
  "Click here to access brand assets which are available
  in the dropdown menu with fast loading times"

Why it fails:
  Screenshot doesn't demonstrate anything
  Have to imagine the interaction
  Text does all the explaining

4. Data Visualization

Make numbers visual, not just text

Good Example:

Scene: ROI Proof (10s)

Visual:
  - Bar graph animating
  - Before: Small bar (2 deals/month)
  - After: Large bar (7 deals/month)
  - Bars are actual product screenshots (deals in CRM)
  - Difference highlighted with motion

On-Screen: "3.5x more deals closed"

Why it works:
  Number becomes visual comparison
  Motion emphasizes growth
  Real product context (CRM deals)

Bad Example:

Scene: ROI Proof (10s)

Visual:
  - Plain background

On-Screen:
  "Teams using our product close 3.5x more deals per month
  compared to teams not using our product"

Why it fails:
  Pure text, no visual
  Claim without proof
  Missed opportunity to show growth

5. Metaphor and Analogy

Use visual metaphors for abstract concepts

Good Example:

Scene: Integration Feature (8s)

Visual:
  - Puzzle pieces scattered (individual tools)
  - Pieces snap together
  - Form complete picture
  - Picture reveals unified dashboard

On-Screen: "All your tools. One platform."

Why it works:
  Abstract concept (integration) made concrete
  Visual metaphor is clear
  Satisfying moment (puzzle completion)

Use sparingly: Metaphors can feel cheesy if overused

6. User Journey Visualization

Show the path, not just the destination

Good Example:

Scene: User Journey (20s)

Visual:
  Step 1 (0-6s): User signs up (form filling)
  Step 2 (6-12s): Connects first tool (OAuth flow)
  Step 3 (12-18s): First insight appears (data visualization)
  Step 4 (18-20s): User celebrates (visual success moment)

On-Screen:
  "From signup to insight in 5 minutes"

Why it works:
  Journey is shown, not described
  Each step is visual
  Time progression is clear

Visual Hierarchy

What to Show First

In each scene, establish visual hierarchy:

Primary (First 1s):
  What grabs attention immediately
  Usually: Key visual element or motion

Secondary (Next 1-2s):
  Supporting elements that add context

Tertiary (Final 1-2s):
  Details, text, fine print

Good Example:

Scene: Feature Reveal (5s)

Visual Hierarchy:
  Primary (0-1s):
    Large animation of data flowing into dashboard
    [Attention grabbed]

  Secondary (1-3s):
    Dashboard UI becomes clear
    Multiple data sources visible
    [Context established]

  Tertiary (3-5s):
    Text appears: "Real-time attribution"
    [Message reinforced]

Show Don't Tell Checklist

For each scene, ask:

Could This Be Shown?

❌ "Our platform is fast"
✅ [Show: Side-by-side speed comparison]

❌ "Users love our product"
✅ [Show: Real testimonial with face/name + company]

❌ "Save time on repetitive tasks"
✅ [Show: Time-lapse of task automated, clock showing time saved]

❌ "Works with all your tools"
✅ [Show: Logos flowing into central platform]

❌ "Simple three-step process"
✅ [Show: Three steps in action, numbered]

Is the Visual Carrying Its Weight?

Good (Visual adds value):

- Demonstrates functionality
- Shows transformation
- Provides proof
- Creates emotion
- Explains complex concept

Bad (Visual is decorative only):

- Generic stock footage
- Static logo
- Meaningless abstract shapes
- Unrelated B-roll

Integration with Copy

Copy Should Label, Not Describe

Good:

Visual: [Demo of instant sync across devices]
Copy: "Instant sync"

Copy labels what viewer sees

Bad:

Visual: [Static product logo]
Copy: "Our product provides instant synchronization across
all devices including desktop, mobile, and tablet platforms"

Copy does all the work

Copy Should Amplify, Not Repeat

Good:

Visual: [Before/after comparison showing 10x speed increase]
Copy: "10x faster processing"

Copy quantifies what visual shows

Bad:

Visual: [Before/after comparison showing 10x speed increase]
Copy: "You can see here that the processing is much faster
than before"

Copy states the obvious

Visual Storytelling by Video Type

Product Demo (Show-Heavy)

Ratio: 70% show / 30% tell

Focus:
  - Screen recordings
  - Live interactions
  - Before/after states
  - Real workflows

Brand Story (Emotion-Heavy)

Ratio: 50% show / 50% tell

Focus:
  - People and faces
  - Real moments
  - Emotional expressions
  - Journey visualization

Social Proof (Balance)

Ratio: 60% show / 40% tell

Focus:
  - Real customer photos
  - Actual results/data
  - Company logos
  - Success metrics visualized

Platform Considerations

Social Media (Silent Viewing)

Critical: 60%+ watch without sound

MUST show:
  - Text overlays (readable, large)
  - Visual demonstrations
  - Clear before/after
  - Obvious transformations

AVOID:
  - Requiring audio to understand
  - Subtle visual details
  - Complex explanations

Website Hero (Looping)

MUST show:
  - Product in action
  - Continuous loop (seamless)
  - Immediate value proposition
  - No beginning/end dependency

AVOID:
  - Linear narrative
  - Time-based progression
  - One-time reveals

Anti-Patterns

1. Lorem Ipsum Visuals

Bad:

Generic stock footage of:
- Person typing on laptop
- Coffee cup on desk
- Handshake
- City skyline

None of which relate to actual product

2. Static Screenshots

Bad:

10 seconds of motionless screenshot
While text explains what it does

Better:

3 seconds of animated interaction
Text labels the benefit

3. Text Dumping

Bad:

Paragraph of text on screen
Minimal or generic visual
Viewer must read everything

Better:

Single sentence on screen
Visual demonstrates the point
Text + visual reinforce each other

4. Explaining the Visual

Bad:

Visual: [Data flowing between apps]
Copy: "As you can see, data flows between your apps..."

Better:

Visual: [Data flowing between apps]
Copy: "Automatic sync across all platforms"

5. Disconnected Visual/Copy

Bad:

Visual: [Generic office space]
Copy: "Our AI analyzes your data in real-time"

Visual and copy unrelated

Better:

Visual: [AI model analyzing data, visualized]
Copy: "Real-time AI analysis"

Visual shows what copy says

Checklist

For each scene:

Show Don't Tell:

• [ ] Primary message shown visually (not just stated)
• [ ] Visual demonstrates/proves (not just decorates)
• [ ] Transformation visible (before/after, movement, change)
• [ ] Product shown working (not static screenshot)
• [ ] Data/numbers visualized (not just text)

Visual Effectiveness:

• [ ] Visual is specific to our product (not generic)
• [ ] Visual tells story even without sound
• [ ] Visual hierarchy clear (what to look at first)
• [ ] Motion directs attention appropriately
• [ ] Visual and copy reinforce each other

Avoids Anti-Patterns:

• [ ] No stock footage unrelated to product
• [ ] No static screenshots for extended duration
• [ ] No paragraph text blocks
• [ ] No copy explaining what's obvious visually
• [ ] No disconnected visual/copy pairs

Platform Appropriate:

• [ ] Works without sound (if social)
• [ ] Readable on mobile (if needed)
• [ ] Loops seamlessly (if hero video)
• [ ] Detail level matches viewing context

VSL Framework Applications

Impact: HIGH

Proven frameworks provide structure and ensure key conversion elements are included. Choose the right framework based on video length, audience awareness, and objective.

Framework Selection Matrix

Hook-CTA (15-30s Social Ads)

Formula: Problem Hook → Quick Solution Demo → Clear CTA

Structure

Hook (0-20%): 3-6s
  - Bold problem statement or question
  - Visual: Show pain point

Solution (20-70%): 6-21s
  - Quick demo or transformation
  - 1-2 key benefits
  - Visual: Product in action

CTA (70-100%): 21-30s
  - Clear next step
  - Remove friction
  - Visual: Button/link with value

Good Example (30s LinkedIn Ad)

Scene 1: Hook (0-5s)
On-Screen: "Sales team using 12 different tools?"
Visual: Desktop with 12 app windows open, chaotic
Psychology: Problem recognition

Scene 2: Solution Intro (5-12s)
On-Screen: "One platform. Everything connected."
Visual: All apps collapse into one clean interface
Psychology: Relief, simplicity appeal

Scene 3: Key Benefit (12-22s)
On-Screen: "Close deals 2x faster"
Visual: Sales dashboard showing won deals
Psychology: Specific outcome, aspirational

Scene 4: CTA (22-30s)
On-Screen: "Start free trial • No credit card"
Visual: Simple form, 2 fields visible
Psychology: Low friction, risk-free

Bad Example

0-10s: Company history and mission
10-20s: Feature list (no demo)
20-30s: Generic "Learn more" CTA

Why it fails:
- No hook (loses viewers immediately)
- Tell instead of show
- Vague CTA with no value

PAS Framework (30-90s)

Formula: Problem → Agitate → Solution

Most effective for cold traffic and problem-aware audiences.

Structure

Problem (0-25%): 9-23s
  - Identify specific pain point
  - Make it personal ("You")
  - Visual: Show the struggle

Agitate (25-50%): 23-45s
  - Why it's getting worse
  - Cost of inaction
  - Failed alternatives
  - Visual: Amplify frustration

Solution (50-100%): 45-90s
  - Introduce product
  - Show it working
  - Key benefits
  - Social proof
  - Clear CTA
  - Visual: Transformation

Good Example (60s Product Video)

PROBLEM (0-15s)
Scene 1 (0-8s): Set the Pain
On-Screen: "Spending $10k/month on ads with no idea what's working?"
Visual:
  - Marketing dashboard with red declining graphs
  - Money burning animation
  - Confused marketer staring at reports
Psychology: Immediate problem recognition + financial pain

Scene 2 (8-15s): Universal Truth
On-Screen: "Every platform shows different numbers"
Visual:
  - Split screen: Google Ads / Facebook / LinkedIn showing conflicting data
  - Same campaign, 3 different ROI calculations
Psychology: Validate their experience (they're not alone)

AGITATE (15-30s)
Scene 3 (15-23s): Cost of Inaction
On-Screen: "While your budget drains on underperforming campaigns"
Visual:
  - Money flowing down a drain
  - Competitors appearing in top search results
  - Clock ticking fast
Psychology: FOMO + urgency + financial loss

Scene 4 (23-30s): Failed Alternatives
On-Screen: "Spreadsheets? Manual. Agencies? Expensive."
Visual:
  - Person drowning in spreadsheet cells
  - Invoice for $5k/month agency fee
Psychology: Empathy (we know you've tried everything)

SOLUTION (30-60s)
Scene 5 (30-38s): Introduce Solution
On-Screen: "AdClarity shows truth across all platforms"
Visual:
  - Clean, unified dashboard appears
  - All platforms feeding into one source of truth
  - Light breaking through darkness
Psychology: Hope, relief, simplicity

Scene 6 (38-48s): Demo Key Features
On-Screen: "Real attribution. Actual ROI. One number."
Visual:
  - Quick demo: Campaign selected → Real conversion path shown → True ROI calculated
  - Simple, clear interface
Psychology: Confidence it works, not complicated

Scene 7 (48-55s): Social Proof
On-Screen: "2,400 marketers stopped guessing"
Visual:
  - Logos: Medium-sized B2B SaaS companies
  - Quote: "Finally know where every dollar goes" - CMO, TechCo
Psychology: Credibility, peer validation

Scene 8 (55-60s): CTA
On-Screen: "See your real ROI • 14-day free trial"
Visual:
  - Simple CTA button
  - "Connect in 2 minutes" subtext
Psychology: Clear value, low friction, quick setup

When to Use PAS

✅ Use when:

• Selling to cold or problem-aware audience
• Clear, painful problem exists
• Product is reactive (solves existing pain vs creates new desire)
• Emotional buying decision

❌ Don't use when:

• Selling to solution-aware audience (they know options exist)
• Novel product with no clear problem (use curiosity instead)
• Sophisticated audience that resents manipulation

AIDA Framework (60-120s)

Formula: Attention → Interest → Desire → Action

Most versatile framework. Works for product demos, explainers, sales videos.

Structure

Attention (0-15%): 9-18s
  - Hook with problem or question
  - Pattern interrupt
  - Set context
  - Visual: Grab attention

Interest (15-40%): 18-48s
  - Agitate problem OR show novel solution
  - Why this matters
  - Introduce product concept
  - Visual: Build intrigue

Desire (40-80%): 48-96s
  - Demo product in action
  - Key benefits with proof
  - Social proof / testimonials
  - Handle objections
  - Paint the transformation
  - Visual: Show outcomes

Action (80-100%): 96-120s
  - Clear offer
  - Risk reversal
  - Urgency (if authentic)
  - Strong CTA
  - Visual: Easy next step

Good Example (90s SaaS Demo)

ATTENTION (0-12s)
Scene 1 (0-5s): Hook
On-Screen: "Your design team uses 47 tools"
Visual: Chaotic desktop, countless apps
Psychology: Relatable exaggeration creates curiosity

Scene 2 (5-12s): Context
On-Screen: "Every project, a new login, new link, new chaos"
Visual: Designer frustrated, searching for files
Psychology: Validate the struggle

INTEREST (12-35s)
Scene 3 (12-20s): Why It Matters
On-Screen: "3 hours/week lost just finding things"
Visual: Clock showing wasted time, designer waiting
Psychology: Quantify the cost

Scene 4 (20-28s): Failed Solutions
On-Screen: "Wikis get outdated. Folders get messy."
Visual: Outdated wiki page, nested folders 10 levels deep
Psychology: Show why alternatives don't work

Scene 5 (28-35s): Introduce Concept
On-Screen: "What if everything lived where you already work?"
Visual: Clean Figma file with all resources embedded
Psychology: Novel solution, creates curiosity

DESIRE (35-75s)
Scene 6 (35-45s): Demo Feature 1
On-Screen: "Instant access to brand assets"
Visual: Designer types "/" → brand assets appear instantly
Psychology: Speed, simplicity, "I want that"

Scene 7 (45-55s): Demo Feature 2
On-Screen: "Design systems that actually stay in sync"
Visual: Component updated → all instances update across files
Psychology: Solves real pain point

Scene 8 (55-63s): Demo Feature 3
On-Screen: "Ship with developers, no handoff friction"
Visual: Designer shares → developer gets code → ships
Psychology: Collaboration benefit, complete workflow

Scene 9 (63-75s): Social Proof
On-Screen: "8,000 design teams already shipping faster"
Visual:
  - Logos: Airbnb, Shopify, Coinbase
  - Testimonial: "Cut handoff time by 80%" - Design Lead
Psychology: Credibility, FOMO, specific results

ACTION (75-90s)
Scene 10 (75-82s): Offer
On-Screen: "Try free for 30 days"
Visual: Pricing: Free → Pro tier highlighted
Psychology: Low risk, clear upgrade path

Scene 11 (82-90s): CTA
On-Screen: "Start designing • Import your files in 1-click"
Visual: Simple signup, show easy onboarding
Psychology: Specific action, removes setup concern

The Explainer Framework (60-180s)

Formula: Context → Mechanism → Benefits → Proof → CTA

Best for complex products, B2B, educational content.

Structure

Context (0-20%): 12-36s
  - Why this topic matters
  - Current state of the world
  - The problem or gap

How It Works (20-50%): 36-90s
  - Explain the mechanism
  - Demo the process
  - Show it's simple

Benefits (50-75%): 90-135s
  - Key outcomes
  - Use cases
  - Transformation

Proof (75-90%): 135-162s
  - Case studies
  - Data/results
  - Testimonials

CTA (90-100%): 162-180s
  - Clear next step
  - Resources

When to Use Explainer

✅ Use when:

• Product requires explanation (novel concept)
• B2B with long consideration
• Educational content that leads to action
• Building authority first

VSL Classic (3-10 minutes)

Formula: Story → Problem → Solution → Proof → Offer → Close

The traditional VSL formula for direct sales from video.

Structure

Story/Hook (0-10%): 18-60s
  - Personal story or customer story
  - Establish credibility
  - Create connection

Problem Deep-Dive (10-30%): 60-180s
  - Multiple pain points
  - Why current solutions fail
  - Cost of status quo

Solution (30-60%): 180-360s
  - Introduce product/service
  - Unique mechanism
  - Detailed demonstration
  - How it's different
  - Key benefits

Proof (60-80%): 360-480s
  - Multiple case studies
  - Before/after
  - Testimonials
  - Data and results
  - Objection handling

Offer (80-95%): 480-570s
  - What's included
  - Pricing breakdown
  - Bonuses
  - Guarantee
  - Comparison

Close (95-100%): 570-600s
  - Urgency/scarcity
  - Final CTA
  - Recap transformation
  - Remove final objections

Framework Customization Rules

1. Lengthen the proof section if trust is the main barrier 2. Extend the demo if product is visually compelling 3. Shorten problem agitation if audience is solution-aware 4. Add urgency only if it's genuine (launch, limited spots, etc.)

Hybrid Frameworks

Sometimes combine frameworks:

PAS + Social Proof Heavy

Problem (0-20%)
Agitate (20-35%)
Solution (35-50%)
Proof (50-80%) ← Extended proof section
CTA (80-100%)

Use when: Trust is the main barrier

AIDA + Story

Story Hook (0-10%)
Attention (10-20%)
Interest (20-40%)
Desire (40-80%)
Action (80-100%)

Use when: Emotional connection is key

Checklist

• [ ] Framework matches video duration
• [ ] Framework matches audience awareness level
• [ ] Framework matches conversion goal
• [ ] Hook happens within first 15% of video
• [ ] Problem clearly established before solution
• [ ] Demo/proof section is substantial (30%+ of video)
• [ ] Social proof placed strategically, not dumped at end
• [ ] CTA is clear and specific
• [ ] Each section transitions logically to next
• [ ] Timing percentages translate to actual seconds
• [ ] Framework serves the message (not forcing message into framework)

VSL Hook Formulas and Patterns

Impact: CRITICAL

The first 3-5 seconds determine whether viewers watch or scroll. In VSL and product videos, the hook is the most critical element. 80% of your video's success depends on nailing this moment.

Hook Performance Benchmarks

The 6 Hook Archetypes

1. Question Hook

When to use: Curiosity-driven products, universal problems

Formula: "What if [desired outcome] was [surprisingly easy/fast]?"

Good Example:

On-Screen Copy:
"What if video editing took 5 minutes instead of 5 hours?"

Visual: Split screen
  Left: Person frustrated at complex editing timeline
  Right: Same person smiling with simple interface

Psychology:
- Immediately relatable problem (time-consuming editing)
- Creates curiosity (how could it be that fast?)
- Implies transformation is possible

Timing: 0-4s

Bad Example:

"What is our video editing platform?"

Why it fails:
- Not a question viewers have
- No curiosity or desire triggered
- Company-focused, not viewer-focused

2. Problem Hook

When to use: Clear, painful problem your audience knows they have

Formula: "[Negative feeling] by [pain point] while [frustrating reality]?"

Good Example:

On-Screen Copy:
"Losing deals because your demos take too long to set up?"

Visual:
- Salesperson struggling with demo that won't load
- Impatient prospect checking phone
- Clock ticking

Psychology:
- Specific pain (demo setup time)
- Real consequence (losing deals)
- Immediate identification (prospect knows this feeling)

Timing: 0-3s

Bad Example:

"Demos can be challenging."

Why it fails:
- Too vague (what kind of challenges?)
- No urgency or emotion
- Sounds like corporate speak

3. Curiosity Hook

When to use: Innovative products, novel mechanisms, contrarian approaches

Formula: "This [simple/unexpected thing] [produced surprising result]"

Good Example:

On-Screen Copy:
"One calendar setting eliminated 40% of our meetings"

Visual:
- Simple calendar toggle switch
- Meetings disappearing from screen
- Person gaining hours back in calendar

Psychology:
- Curiosity gap (what's the setting?)
- Specific, believable result (40%, not 90%)
- Universal desire (fewer meetings)

Timing: 0-4s

Bad Example:

"You won't believe what happened next..."

Why it fails:
- Clickbait that creates distrust
- No specific value proposition
- Overused pattern viewers tune out

4. Social Proof Hook

When to use: Strong traction, well-known customers, impressive numbers

Formula: "[Impressive number] [authority figures/companies] already [specific outcome]"

Good Example:

On-Screen Copy:
"27,000 engineering teams ship code 3x faster"

Visual:
- Logos of recognizable tech companies
- Counter rapidly increasing
- Code being deployed

Psychology:
- Credibility through numbers (27k teams)
- Specific outcome (3x faster)
- FOMO (others are already benefiting)

Timing: 0-5s

Bad Example:

"Thousands of satisfied customers"

Why it fails:
- Vague (thousands could be 2,000 or 900,000)
- Generic (satisfied doesn't convey specific value)
- Sounds like every company ever

5. Demonstration Hook

When to use: Visual products, impressive results, "seeing is believing"

Formula: Show the impressive result immediately, explain later

Good Example:

On-Screen Copy:
[None at first - visual speaks]
"0 to production-ready app in 60 seconds"

Visual:
- Time-lapse of blank screen → full application
- Real-time counter showing: 00:00 to 01:00
- Actual working product at end

Psychology:
- Proof through demonstration
- Specific, measurable claim (60 seconds)
- "I want that" reaction

Timing: 0-6s (full demonstration)

Bad Example:

"Our platform is really fast"

Why it fails:
- Tell instead of show
- Subjective claim (how fast is "really fast"?)
- No proof or demonstration

6. Pattern Interrupt Hook

When to use: Crowded markets, need to break through noise, bold brand

Formula: Start with something unexpected, then connect to value

Good Example:

On-Screen Copy:
"Delete your entire marketing stack"
[pause]
"Keep this one tool instead"

Visual:
- Multiple app icons falling/deleting
- One app remaining, glowing
- Clean, simple interface

Psychology:
- Breaks expectation (usually adding tools, not deleting)
- Creates cognitive tension (wait, delete everything?)
- Promises simplification

Timing: 0-7s (includes pause for impact)

Bad Example:

Random unrelated visual: Cat wearing sunglasses
"Now let's talk about our CRM..."

Why it fails:
- Interrupt has no connection to value
- Feels gimmicky, not strategic
- Damages credibility

Hook Construction Rules

1. Relevance First

Good: "Tired of manually copying data between systems?"

• Specific problem
• Target audience knows immediately if this is for them

Bad: "Want to be more productive?"

• Too generic
• Could apply to anything

2. Specificity Over Vagueness

Good: "Cut your ad spend by 40% in 30 days"

• Specific metric (40%)
• Specific timeframe (30 days)

Bad: "Save money on advertising"

• No specifics
• Every tool claims this

3. "You" Language

Good: "You're spending 15 hours/week on reports"

• Addresses viewer directly
• Makes it personal

Bad: "Companies spend time on reports"

• Third person
• Not personal

4. One Hook, One Message

Good: Focus entirely on one pain point or benefit

Bad: "Are you tired of slow software, bad support, and high prices?"

• Too many messages
• Dilutes impact

Hook Testing Framework

Before finalizing a hook, test against these criteria:

The 3-Second Scroll Test

• [ ] Could this grab attention mid-scroll?
• [ ] Clear what it's about instantly?
• [ ] Obvious who it's for?

The Mute Test

• [ ] Works without sound?
• [ ] Visual alone conveys value?
• [ ] Text readable and impactful?

The Relevance Test

• [ ] Target audience immediately knows "this is for me"?
• [ ] Problem/benefit is specific, not generic?
• [ ] Passes the "so what?" test?

The Emotion Test

• [ ] Triggers an emotion (curiosity, frustration, hope, FOMO)?
• [ ] Emotion is appropriate for brand and product?
• [ ] Not manipulative or dishonest?

Hook + Scene 2 Combinations

The hook sets up expectations. Scene 2 must deliver on the promise.

Good Combination

Hook (0-3s): "Spending 20 hours/week in meetings?"
Scene 2 (3-10s): Show calendar before/after with hours reclaimed

Hook creates problem awareness
Scene 2 shows transformation is possible

Bad Combination

Hook (0-3s): "Want better meetings?"
Scene 2 (3-10s): Logo animation and company name

Hook asks question
Scene 2 ignores it, shows branding instead

Hook Length Guidelines

Principle: Shorter videos need faster hooks. Longer videos can build slightly more.

Industry-Specific Hook Examples

SaaS B2B

Problem Hook:
"Sales reps spending 4 hours/day on admin instead of selling?"

Social Proof Hook:
"1,200 sales teams closed 35% more deals last quarter"

Curiosity Hook:
"One Slack integration eliminated our CRM data entry"

Consumer Product

Demonstration Hook:
[Show transformation: messy → organized in 10 seconds]

Question Hook:
"What if getting organized actually took 5 minutes?"

Social Proof Hook:
"50,000 homes decluttered in 30 days"

Education/Course

Problem Hook:
"Stuck in tutorial hell, building nothing real?"

Social Proof Hook:
"2,000 developers landed jobs after this 8-week program"

Curiosity Hook:
"This learning method works backwards from real projects"

App/Mobile

Demonstration Hook:
[Show app in action: problem → solved in seconds]

Question Hook:
"What if tracking calories didn't feel like homework?"

Pattern Interrupt Hook:
"Delete your fitness apps. Keep this one."

Advanced Hook Techniques

The Double Hook

Use two hooks in sequence when needed:

Hook 1 (0-2s): Visual pattern interrupt
  [Fast-motion chaos]

Hook 2 (2-5s): Problem question
  "Drowning in project management tools?"

Technique: Visual grabs attention, copy creates relevance

The Silent Hook

Designed for muted autoplay:

Visual Hook (0-4s):
  - Bold text: "20 hours/week" → "2 hours/week"
  - No explanation needed
  - Numbers + transformation clear visually

Perfect for social feed autoplay

The Stat Stack Hook

Build credibility through rapid stats:

Hook (0-6s):
"40,000 videos created
12 million views generated
$2.3M in revenue attributed"

Visual: Numbers counting up rapidly
Then: "All from one platform"

Overwhelm with proof, then promise simplicity

Checklist

• [ ] Grabs attention within 3 seconds
• [ ] Immediately clear who it's for
• [ ] Specific problem or benefit (not generic)
• [ ] Uses "you" language (viewer-focused)
• [ ] Triggers emotion (curiosity, frustration, hope)
• [ ] Works without sound (visual + text)
• [ ] Promises what rest of video delivers
• [ ] Appropriate length for total video duration
• [ ] Honest (no false promises or clickbait)
• [ ] One clear message (not multiple competing ideas)
• [ ] Tested against scroll/mute/relevance/emotion tests
• [ ] Scene 2 delivers on hook's promise