zerotoneroAcademy · Lesson 2 of 9 · 8 min
Hooks that stop the scroll
The first one to three seconds decide whether anyone sees the rest. Learn to open on the payoff, not the preamble.
The hook is the first one to three seconds of your video, and its only job is to earn the next few seconds. In a feed, nobody chose to watch you. They are mid-thumb-flick, and your first frame has to give them a reason to stop. Everything you worked hard on later in the video only exists if the hook works.
The most common developer hook is a greeting: 'Hey, so I've been building this app for a while...'. It feels polite, but in a feed it reads as 'nothing is happening yet'. Same for logo animations and title cards. Cut them. Start on the most interesting frame you have, already in motion.
A good hook usually does one of a few things. It names a specific pain ('This is every subscription I forgot I was paying for'). It shows a surprising result first and explains later. It makes a bold, checkable claim the rest of the video backs up. Or it calls out a specific person ('If you track habits in a notes app, stop scrolling'). Specific beats clever almost every time.
A hook has a visual half and a verbal half, and they should agree. If you say 'look at this' while the screen shows your face, you have half a hook. Pair the line with a frame that shows the thing: the cluttered list, the broken streak, the before-and-after. Add the hook as a text overlay too, because plenty of people scroll with sound off.
Write at least five hooks for every video, then pick one. Read each out loud and ask: would a stranger know what this is about by second two? Is there a reason to keep watching? Is it true? A hook that overpromises might stop the scroll, but the viewer feels tricked by second ten and leaves anyway.
Finally, the hook is a promise and the rest of the video is the delivery. If the hook says 'I found three forgotten subscriptions in a minute', the proof beat needs to show exactly that. The tighter that loop, the more the video feels worth watching to the end.
Key points
- Open on the payoff or the pain, already in motion. No greetings, no logo intros.
- Visual and verbal hook should say the same thing, plus a text overlay for sound-off viewers.
- Specific beats clever: a concrete pain or result over a vague category.
- Write five hooks, keep the one a stranger would understand by second two.
- The hook is a promise; the proof beat has to deliver it.
Good: Payoff first, explain later
A made-up budgeting app that finds forgotten subscriptions. Frame one is already the interesting part.
- 0s Frame one is the payoff: a long, slightly embarrassing list. No intro, no logo.
- 1s Text overlay states the hook for people scrolling on mute.
- 2s The problem lands by second 2, while curiosity is still high.
- 10s The proof delivers exactly what the hook promised.
Bad: The polite warm-up
Same app, but the video spends its first five seconds saying hello. The best visual is buried at second 10.
- 0s Logo animation as the first frame. The thumb keeps scrolling.
- 3s Three seconds in and there is still no reason to stay.
- 6s 'It's a budgeting app' is a category, not a hook.
- 10s This list should have been frame one.
Common mistakes
- Opening with a greeting, your name, or 'so today I want to show you'.
- Starting on a logo animation or title card.
- Naming the category (budgeting app) instead of the pain or payoff.
- A verbal hook over a visual that shows nothing related.
- Clickbait hooks the rest of the video does not deliver on.
- No text overlay, so the hook is lost on anyone watching muted.