Skip to content
Flows
Launch Beginner · 45-75 minutes

Demo Video Script

Script a tight product demo video: hook, narrative arc, screen directions, and CTA - ready to record.

Start Route · 5 steps

The route

5 steps to Done

  1. 01

    Choose format and story

    One video, one audience, one story - decide before scripting.

    Preview prompt + verify gate ▾

    Plan my demo video. I will describe the product and where the video will live below. Recommend: the right length (30s hook video vs 90s standard vs 3min deep demo) with reasoning; the ONE user story to follow (a named persona with a concrete task, start to finish); and the magic moment - the single most impressive beat - with where it should land in the timeline (before 40%). List what NOT to show. PRODUCT AND PLACEMENT: [describe here]

    • Length matches the placement
    • The story is one persona, one task
    • The magic moment is identified
  2. 02

    Write the hook and opening

    Viewers decide in 5 seconds - open with the pain or the payoff.

    Preview prompt + verify gate ▾

    Write the demo opening. Produce 3 hook options for the first 5 seconds: a pain cold-open ('Here is the mess this replaces'), a payoff-first open (show the end result, then rewind), and a bold-claim open. Each with: exact narration line and exact first screen shown. Then recommend one and write the transition from hook into the story setup (5-15 seconds) naming the persona and task in one sentence.

    • Each hook works in 5 seconds
    • The chosen open shows something real
    • The setup is one sentence
  3. 03

    Script the core demo beats

    The middle must show, not tell - every beat pairs action and line.

    Preview prompt + verify gate ▾

    Script the core demo (the middle 60-70%). Produce timestamped beats where each beat has: the exact screen action (what I click/type - specific), the narration line (add context the screen cannot show - never describe what is visible), and any zoom/highlight callouts. Follow the user story to the magic moment, land it with a beat of silence or emphasis, then complete the task's payoff. Keep narration lines under 15 words each.

    • Narration adds context, never describes the visible
    • The magic moment gets emphasis
    • Actions are click-by-click specific
  4. 04

    Write the close and CTA

    End with proof and one clear action.

    Preview prompt + verify gate ▾

    Write the demo close (final 10-20%). Produce: the result recap in one line (what the persona now has, tied to the opening pain); an optional proof beat (a number, a second quick example, or a testimonial line); the CTA - one action, spoken and on-screen (try it, sign up, link) with any friction-remover (free, no card); and the final frame contents (product name, URL, CTA). No new features in the close.

    • The recap mirrors the opening pain
    • Exactly one CTA
    • The final frame has name, URL, action
  5. 05

    Prepare the recording checklist

    Great scripts die to sloppy recordings - prep the environment.

    Preview prompt + verify gate ▾

    Create my recording checklist: demo data preparation (realistic names/content matching the persona - list exactly what to create, no 'test 123'); app state reset steps so the flow starts clean; environment (resolution 1920x1080 or as needed, browser zoom, hide bookmarks/notifications/dock, close other tabs); audio notes (mic check line, room, pace - read narration at conversational speed); and a dry-run instruction: perform the click path once silent, once narrated, before recording for real.

    • Demo data is specified realistically
    • Notifications and clutter are handled
    • A dry run precedes recording