On this page
A curiosity hook earns its place when the next shot answers it. If the payoff needs excuses, rewrite the hook.
Name the question the viewer should have
“You will not believe this” creates no useful expectation. “Where did I save that?” creates a question a search feature can answer. The second is easier to write, film and evaluate because the payoff is specific.
Start from the recording, not a list of dramatic phrases. Describe the state before the action and the state after it. The gap between those states is usually enough material for an opening.
Eight weak-to-useful rewrites
These are writing exercises, not claims that one line outperforms another. Choose the more specific version only when the product actually performs the shown action.
| Vague or inflated | More specific | Proof the next shot needs |
|---|---|---|
| “This changes everything” | “Put these notes in one view” | The notes appear together |
| “Nobody knows this secret” | “Here is the control I missed” | A visible, usable control |
| “The easiest app ever” | “Find this file from one search” | The actual query and correct result |
| “Never waste time again” | “Skip this repeated step” | A supported shorter sequence |
| “This is magic” | “Watch the list regroup” | The grouping action and result |
| “You need this now” | “Need only the overdue items?” | The filter returns those items |
| “It does all your work” | “Export this view as a file” | A successful export |
| “I cannot believe my results” | “Compare the two layouts” | The two real layouts side by side |
Worked example: rewrite one vague hook in four steps
Take a proposed opening for an invoicing app: “This fixed my whole workflow.” It is vague, it promises more than one shot can show, and over a stranger’s face it also reads as a personal claim. Here is one way to rewrite it.
Each step narrows the line until the next shot can answer it. If you cannot finish step four, the problem is the recording, not the wording.
- Write the before state in plain words: a list of invoices with paid and unpaid ones mixed together.
- Write the after state: only the unpaid invoices, sorted by due date.
- Turn the gap into a question a viewer could ask themselves: “Which invoices are still unpaid?”
- Check the next shot: the filter is tapped, the list shrinks and the due dates are readable. If the filter needs a setup step first, show it or name it.
Keep the reveal near the question
Do not add a long logo animation or a second unrelated reaction between the question and the answer. Cut into the action while the question is still fresh. If setup is necessary, reduce it to what the viewer needs to understand.
A reveal can be quiet. A folder opening to the right item is enough if that is what the opening promised. Resist adding a stronger claim merely because the expression in the stock clip is dramatic.
Specific questions that still overpromise
A concrete question is not automatically honest. Read the hook again and look for a word that widens the promise beyond what the demo shows.
| Pattern | Example line | Narrower version |
|---|---|---|
| Implied speed | “Done in two seconds?” when processing takes longer | Name the task, not the time |
| Implied coverage | “Find any file?” when search covers one folder | “Find this file” |
| Implied outcome | “Get paid faster?” | “See who still owes you” |
| Hidden prerequisite | “One tap to sync?” after a separate setup | Show or mention the setup |
Check for a hidden testimonial
Putting “I saved hours with this” over someone’s face attributes an experience to that person. A stock reaction cannot substantiate it. Rewrite the line as a product instruction or show documented evidence with an appropriate participant.
Watch the edit once as a stranger. Write down what you would believe about the person, the product and the result. If any of those beliefs would be false, change the sequence before testing it.
- The question names a real task.
- The demo answers that task directly.
- Necessary prerequisites are not concealed.
- The caption does not invent a personal experience.
- The closing instruction is proportional to the result.
Questions & answers
Is curiosity itself misleading?
No. A clear question followed by a truthful demonstration can be useful. The problem is an expectation the video does not fulfill.
Should I reveal the result immediately?
A result-first edit is one option. A question-first edit also works as a structure when the answer follows without unnecessary delay.
Does a curiosity hook have to be written as a question?
No. “Here is the control I missed” or “Watch the list regroup” leave a gap without a question mark. The rule is the same: the next shot has to close the gap it opens.
How long should the hook stay on screen?
Long enough to read once at normal speed while the reaction is clear, then cut into the answer. If viewers need to pause to read it, shorten the line before extending the shot.
Can I reuse one hook across several products?
Only if each product shows the same kind of payoff. A line written for a search result will feel misleading over a settings screen, even when the reaction clip stays the same.
Find the opening for your next edit.
See the public samples, then unlock the library when you’re ready to work with the originals.
Explore the library