Course resource

Hook Formulas

The first line decides whether the rest gets read. These are the patterns that work, and how to generate them without producing clickbait.

Why most hooks fail

Three failure modes:

  1. The warm-up. "In today's fast-paced digital landscape..." — two sentences of throat-clearing before anything happens.
  2. The abstraction. "Communication is important." True, uninteresting, and about nobody.
  3. The overclaim. "This one trick changed everything." The reader has been burned by this exact sentence a hundred times.

A good hook is specific, is about something that actually happened, and creates a question the next line answers.

The twelve patterns

1. The number that does not fit

We spent ₹4 lakh on ads last quarter. Eleven customers came from them.

2. The reversal

Everyone told me to niche down. Going broader tripled our revenue.

3. The confession

I have been doing quarterly reviews wrong for six years. Here is what finally worked.

4. The overheard line

"We don't have a process problem, we have a Sanjay problem." That was the moment I knew the project was in trouble.

5. The before-and-after

Monday: four hours on the weekly report. Now: eleven minutes. Same report.

6. The uncomfortable question

If your best employee resigned tomorrow, how much of what they know would leave with them?

7. The specific moment

Tuesday, 4pm. The client asked one question and I realised nobody in the room knew the answer.

8. The contradiction of expertise

Three consultants told me to rebuild it. The actual fix was a spreadsheet.

9. The cost made concrete

That "quick" approval step costs us fourteen working days a month.

10. The thing nobody says

Most AI pilots do not fail technically. They fail because nobody wanted the thing that was automated.

11. The list with a twist

Five things I stopped doing this year. The last one doubled my output.

Use sparingly — this is the most worn pattern here.

12. The direct address

If you are still copying data between two spreadsheets by hand, this is for you.

The generation prompt

I am writing about [TOPIC] for [AUDIENCE] on [PLATFORM].

The specific things I know that most people do not:
- [FACT / NUMBER / INCIDENT FROM YOUR OWN EXPERIENCE]
- [ANOTHER]
- [ANOTHER]

Write 12 opening lines using these patterns: a surprising number, a reversal
of common advice, a confession of a mistake, a quoted line, a before-and-after,
an uncomfortable question.

Rules:
- Use MY specifics. Do not invent numbers or incidents.
- Under 15 words each.
- No "in today's world", no "imagine if", no rhetorical question that is
  really a statement.
- Each must make the reader need the next sentence.

Then tell me which three are strongest for [AUDIENCE] and why.

The "use my specifics" constraint is what separates a usable hook from generic copy. If you cannot supply three real specifics, you do not have a post yet.

Platform notes

Platform What the hook has to survive
LinkedIn Roughly two lines before "see more". The break must land mid-tension.
X / Twitter The whole first post is the hook.
Email Subject line plus preview text work as one unit — do not repeat the subject.
YouTube Title and thumbnail promise; the first five seconds must pay it off immediately.
Blog / SEO The hook competes with the reader's back button, not a feed. First paragraph must confirm they are in the right place.

The test

After writing a hook, ask three questions:

  1. Could this open a post by anyone in my field? If yes, it is not a hook, it is a category label.
  2. Does the next line pay it off? A hook that promises more than the piece delivers costs you the reader permanently.
  3. Would I say this out loud to someone? If it only works in writing, it is probably posturing.

The line not to cross

A hook creates curiosity about something true. Clickbait creates curiosity about something that is not there.

The cost is not moral disapproval — it is that the second time, they scroll past.

Your bank

Collect hooks that made you stop scrolling. Write down why.

Hook Where Why it worked Pattern
Back to dashboard