demo-scriptlisted

# Writing the script ## Narration that works You are writing for a voice, not a page. - **Short sentences.** One idea each. The TTS will honour a comma; it will not rescue a subordinate clause. - **Say what the viewer is watching**, half a beat before they see it. "You start by creating a project" lands as the cursor moves toward the button. - **Benefit, then mechanism.** "Ship in one click" beats "click the deploy button". - **No feature lists.** Three things well beats nine things fast. - **Write the hook last.** It is easier once you know what the demo actually shows. - **Spell out anything you want pronounced.** "S3" not "S₃"; "dot dev" if it must be said aloud. Roughly **2.5 words per second**. A 60-second video is ~150 words total. That is much less than it sounds — cut accordingly. ### Shape of a 60-second demo | Beat | Time | Job | |---|---|---| | Hook | 0–8s | The problem, felt. Not the product name. | | Core action | 8–24s | The single best thing it does | | Context beat | 24–30s | B-roll, breathing room, credibility | | Payoff | 30–50s | The result, and why it matters | | Close | 50–60s | One clear next step | ### Presenter lines vs voiceover lines Both use the same voice, but they read differently. A presenter line is addressed to camera ("Let me show you what changed"). A voiceover line describes what is on screen ("Projects appear the moment they're created"). Do not write voiceover for a presenter shot; it sounds like someone reading a manual at y