Flowmatic 1000 hooks, reverse-engineered

The LinkedIn
Hook Guide

Built from 1000 top-performing LinkedIn hooks. No theory. Only what the data showed.

What's inside - After analyzing top 1000 hooks
01What a hook actually is
05What the data showed
02The two-line architecture
06What kills a hook
03The 7 hook types
07The synthesized patterns
044 questions before writing
08The pre-write checklist
steal it · use it · stick it on your wall

Done for you

 We run the entire LinkedIn system for our clients — Our systems can add anywhere between $40k - $80k (at least) to your business. Book a call here if you want to see how.

01

What a hook actually is

A hook isn't a headline. It's not a teaser. It's a psychological event that happens in the reader's brain in under 2 seconds, before they've consciously decided whether to keep reading.

Here's the thing most people get wrong: the scroll doesn't stop because something was interesting. It stops because something was unfinished. The brain is wired to close open loops. Every hook that works opens one. Every hook that fails either closes it too early or never opens one at all.


You have two lines, sometimes three, before "see more" cuts the post off. Those lines are the entire job. Everything else is secondary.

The one rule that overrides everything else

The hook must end with something unresolved.

If the reader can leave after line 2 without feeling like they're missing something, the hook failed. Incompleteness is the mechanism. The moment the hook answers its own question, the reader has permission to scroll. This is the only rule that applies universally — every industry, every content type, every audience size. No exceptions.

02

The two-line architecture

Line 1 creates the condition

Line 1 must do exactly one of the following. No warming up, no setup:

  • Name the specific problem the reader is currently living with
  • State a result the reader wants and doesn't have yet
  • Make a claim that contradicts something they currently believe
  • Open a story at its point of highest tension

Under 15 words. Shorter almost always wins. If you can't make the point in 15 words, the idea isn't clear enough yet — sharpen the idea first, then write the line. No context. No background. No "as someone who…". Drop into the middle of something already in motion.

Line 2 makes it personal or escalates it

Line 2 does different work than line 1. It doesn't start a new thought. It doesn't resolve the tension. It arrives in a different emotional register than line 1 left.

If line 1 does this Line 2 does this
Names a problemSharpens it, or names the cost of it
Makes a claimSignals the explanation is worth reading, without giving it
Opens a storyAdds the detail that raises the stakes
States a resultDenies the method, or contrasts with the reader's reality
Names an emotionEscalates it, or reveals what caused it

The pivot between line 1 and line 2 is what stops the scroll. It's a structural decision, not a stylistic one. The reader gets a beat to land on then something unexpected arrives.

Line 3 · use sparingly Maximum three lines before "see more". Two is the target. A third line only works if it deepens the tension. If you're using line 3 to add context, cut it.
03

The 7 hook types that dominated the dataset

These are the specific constructions that appeared most in the highest-performing posts, ordered by how reliably they perform. All examples are stripped to their structure so you can apply them to any niche.

1

The "Not Because" Denial

The single most powerful hook mechanism in the entire dataset. By far.

StructureName the problem your reader has → deny the explanation they've been using for it → leave the real reason unspoken until the body.

Why it worksOn three levels at once:

  1. It validates the reader's pain. Yes, this problem is real. They feel seen.
  2. It dismantles their current excuse which creates relief and confusion at the same time. The shame they were carrying dissolves for a second.
  3. It creates an information debt. The reader owes themselves the real explanation. They cannot leave without it.

That relief-confusion combo is the most powerful emotional state a hook can create. One emotion resolves the shame, the other creates a question they urgently need answered. They keep reading in a completely different emotional state than they started in.

Examples · structure only
"Most [role] quit [activity] too early. / Not because it 'doesn't work.'"
"If you haven't made progress with [goal]… / It's not because you're not [expected trait]."
"Most [role] aren't [negative outcome] because they lack skill. / They're [negative outcome] because [real reason]."
TEMPLATE → [Group] [have problem]. Not because [the excuse they're using].

Line 2 can either complete the diagnosis or leave a pure open loop. Both work — the pure open loop ("Not because it doesn't work", full stop) creates slightly more tension because the real answer isn't hinted at at all.

2

The IF Filter

The highest-comment posts are dominated by this one.

Structure"If [hyper-specific situation the reader is currently in]…" → line 2 creates urgency specifically for that reader.

When the right reader sees their exact situation described in line 1, line 2 lands with disproportionate weight. They're no longer reading as a general audience member, they're reading as someone who was specifically addressed. The "if" is a filter and a magnet at the same time: it excludes the wrong people and makes the right people feel found.

Specific enough: the situation should be described so precisely that the reader who fits it feels slightly exposed. "If you're a professional" is too broad. "If you've been at this for 6 months and still haven't [specific result]" is the right level.

What line 2 must do: name a fear, signal insider knowledge ("here's the part most people skip"), or create urgency ("this is what's costing you").

Hidden mechanism, the word "already": "If you've already decided to [action]…" assumes momentum, which is flattering. The reader who is still deciding reads it as though they've decided, because they want to be the person who has. Identity elevation through one word.

Examples
"If you've [done X] and still [haven't gotten result] / [this is what's actually happening]."
"If your goal is to [specific milestone] / This is the part most people avoid."
TEMPLATE → If [specific situation the reader is currently in], [urgent signal or denied explanation].
3

Result With Denied Method

Creates the "then how?" question every single time.

StructureState a specific, real result → deny the methods the reader assumes produced it.

The result creates desire. The denial of the expected method creates the open loop. The reader's brain immediately generates the question "then how?" — that question is the entire mechanism.

The result must be specific. "I made a lot of money" creates evaluation. "$0 for the first 4 months, then…" creates curiosity. The specificity makes it feel real before the reader has decided whether to trust you.

The "I realized one thing" variation: specific result + deliberate vagueness about the insight. Works because the specificity of the result makes the vagueness feel tantalising instead of evasive. A nobody writing "I realized one thing" lands flat; someone with a concrete result writing it makes the reader assume the insight is earned.

Examples
"Making [$X] with my [business] / didn't come from [expected method]."
"One of my clients [achieved result] / while [seemingly impossible circumstance]."
TEMPLATE → [Specific result]. Not from [expected method].
4

The Audience Mirror

The hooks with the most comments use this.

StructureDescribe the reader's current experience in enough detail that they feel seen, not just informed.

It's not about what you did, it's about reflecting the reader's current experience back at them. Recognition is more visceral than curiosity. When the hook names the exact loop the reader is in right now (not a category of experience, but the specific cycle), they stop because the post feels written about them.

The loop visualization: one of the highest performers used "learn → tweak → wait → repeat" with arrows. The visual format stands out in a text-heavy feed, and the cycle is instantly recognisable to anyone stuck in it. Naming the loop is more precise than naming the feeling.

Examples
"When I started [thing], / I spent months in the same loop you're probably in right now."
"[Action] → [what it leads to] → [next action] → [back to start]."
TEMPLATE → [Describe the reader's current state or loop specifically enough that they recognise themselves] / [signal that you've been there, or know what comes next].
5

Confession With Counterintuitive Outcome

The #1 highest-performing hook in the dataset used this.

StructureAdmit something that sounds like failure → add a second element that contradicts what the reader expects to follow.

Confession is the most trust-efficient opener on LinkedIn because it bypasses the reader's cynicism about self-promotion. Lead with a failure and the reader's defense drops. Then the counterintuitive element creates a gap they urgently need to understand.

Two simultaneous questions get created: "why did they admit that?" and "what does the second part mean?" Two questions in two lines is a strong hook.

Examples
"I made $0 for the first [timeframe] of my [business]. / I didn't change [expected thing] to fix it."
"One of my clients got offered [$X] to do [work]. / I told them to walk away from it."
TEMPLATE → [Admission of failure or uncomfortable truth]. [The action that contradicts what's expected].
6

"Everyone Says X / But Let's Be Honest"

The conspiracy of honesty.

StructureName the dominant narrative in your space → signal you're about to say the thing the narrative prevents people from saying.

"But let's be honest" positions you as someone with access to a truth social norms keep quiet — and positions the reader as someone mature enough to handle it. The flattery is implicit, and it keeps them reading. The reader who continues feels let in on something real instead of consuming content. Works specifically for contrarian and opinion posts.

Variations
"Everyone's [doing X]. / But let's be honest…"
"Nobody talks about [uncomfortable reality]."
"The honest answer to [common question] is one most people don't want to hear."
TEMPLATE → [Dominant narrative in your space]. / But let's be honest.
7

Milestone + Disarming Pivot

Converts flex into intimacy.

StructureState a real achievement → pivot immediately to something humble, subversive, or unexpected.

Line 1 creates an expectation of self-promotion. When line 2 denies that expectation, it creates warmth the reader didn't anticipate. Their first instinct was to scroll past a flex post — the pivot catches them off guard and flips their emotional orientation.

The pivot options
Admission — "I realised I've never actually [done basic thing]"
Subversion — "But this is something most [audience] don't realize"
Reframe — "But the thing that actually got me here surprised me"
TEMPLATE → [Real achievement]. / But [unexpected pivot, admission, or thing most people don't know].
Newsletter Liking this so far? I break down systems like this every week in my newsletter. One email, no fluff, straight sauce. Subscribe here.
04

The 4 questions to answer before writing any hook

Skip these and you'll write a generic hook every time.

1
What is the open loop this hook will create? What question can the reader only answer by reading on? If you can answer it inside the hook itself, you've closed the loop too early.
2
What does the reader currently believe that is wrong, incomplete, or keeping them stuck? The most powerful hooks in the dataset targeted a specific belief the reader was holding. Knowing that belief tells you exactly what line 1 or 2 needs to deny.
3
What is the most specific, concrete thing that can land in line 1? A number. A dollar figure. A named situation. A timeframe. Specificity does credibility work before the reader has consciously evaluated you.
4
What happens in line 2 that line 1 doesn't prepare them for? The pivot, the escalation, the denial. Line 2 should arrive in a different emotional register than line 1 left. That shift is what stops the scroll.
05

What the data showed

About specificity

Specificity bypasses the reader's evaluation mechanism. The brain treats specific data as evidence of reality. Vague claims create skepticism; specific data skips it entirely.

Vague · fails Specific · works
"This changed everything""This one shift got me from 0 to [result] in [timeframe]"
"Here are some tips""After [X] posts, here are the [N] things every top performer does differently"
"I built a successful business""$0 to [$X] in [timeframe]. Not from ads. Not from going viral."
"Most people get this wrong""Most [role] quit [activity] too early. Not because it doesn't work."

The number doesn't need to be large — it needs to be exact. "17 clients" beats "many clients". "$3,200" beats "a few thousand". Exactness signals something real happened, not a rounded estimate of a vague memory.

About the reader's identity

The most-commented hooks didn't talk at the reader. They made the reader feel like they were in the situation already. The reader doesn't respond to "this might apply to you" — they respond to finding themselves already inside the scenario before they had the chance to opt out.

Language that implicates rather than introduces:

  • "If you've been [doing X] and still haven't [gotten result]…" → they're already in
  • "The problem isn't [what you thought it was]…" → their assumption is already being addressed
  • "Most [people in your situation]…" → they're already classified
  • "You already know what to do." → they're already being spoken to directly

The difference is between content the reader consumes about other people and content the reader finds themselves inside. The latter generates comments. The former generates views.

About emotion

Naming the emotion the reader is currently carrying is more powerful than promising information. The hooks that named private, rarely-articulated experiences (doubt before a first client, loneliness in the early stage, the feeling of being ready but not moving) generated engagement way beyond their follower count. The reader who sees their private experience named publicly doesn't just feel curious they feel found. And people who feel found respond.

This isn't emotional manipulation; it's emotional accuracy. The question isn't "what emotion will make them click?" It's "what is the reader actually feeling right now that nobody is naming?" Find the most honest answer and put it in the hook.

06

What kills a hook

Check every hook against this list before you post. No exceptions.

Starting with context or background. "As someone who has been in [field] for X years…" is setup, not a hook. Context belongs in the body. The hook starts at the point of tension.
The credential drop. "As a [title]…" signals self-promotion, not usefulness. Credibility comes from specificity and outcomes, not titles.
Vagueness. "Here are some tips" and "this changed everything" give the reader zero reason to stop. Replace every vague phrase with a number, a named situation, or a specific outcome.
Closing the loop too early. If the hook answers its own question, the reader has permission to leave.
Manufactured urgency. "You NEED to read this" is manipulative without cause. Urgency is earned through what's at stake, not through tone.
Generic list openers. "5 ways to improve X" tells the reader nothing about why these five are different from the thousand other posts making the same promise. "5 things I changed after [specific failure] that produced [specific result]" earns the read.
Questions without stakes. "What do you think about [topic]?" is small talk. A question only works if it names a tension the reader is actively sitting with.
Humble bragging without a pivot. "Can't believe we hit [milestone], so grateful" is noise unless line 2 immediately changes the reader's emotional orientation.
Re-announcing the hook in the body. The body moves forward from the hook, not back to it. Restating line 1 kills the momentum you just created.
The continuity rule

The hook creates a specific tension. The body must resolve that exact tension not a related one, not a broader version of it.

  • Hook names a problem → body deepens the diagnosis or starts resolving it
  • Hook opens a story → body continues that story before extracting any lesson
  • Hook makes a contrarian claim → body delivers the explanation immediately

The continuity test: read the last word of your hook and the first word of your body as a single sentence. If they don't flow, the body has drifted from what the hook promised.

07

The patterns that emerged from the 1000. 

After going through all the hooks, these are the things that were true of the highest performers:

The "not because" denial was the single most dominant pattern. It showed up in lead-magnet hooks, how-to hooks, contrarian hooks, storytelling hooks. Nothing created forward momentum as reliably. If you only internalize one structure from this entire guide, it's this one.
The IF filter combined with "not because" produced the highest engagement. The hooks with the most comments almost universally combined the two: a hyper-specific situation filter in line 1, followed by a denial of the expected explanation in line 2. "If you're in [specific situation]… it's not because [expected reason]." Validates the reader, filters the audience, dismantles the excuse, and opens the loop — all in two lines.
Specificity of the situation mattered more than specificity of the result. Hooks that named the exact circumstance ("if you've watched 50+ tutorials and still have no clients") outperformed hooks that named big results without situational context. The result without the situation is just a flex. The situation without the result is still a hook.
The highest performers combined two unexpected things. The #1 hook in the dataset had "I made $0 for the first 4 months" AND "I didn't change the business model to fix it". Two things that don't belong together. The reader's brain can't process both at once and is forced to keep reading to reconcile them.
Short beats long in line 1. Always. Every hook that opened with a line over 15 words underperformed hooks that front-loaded the same info in 8 to 12. It's not about style, it's about processing speed: the reader scans line 1 in a fraction of a second. Too long to process at scanning speed = scrolled past.
The emotion doesn't need to be performed. Hooks that named emotions directly ("that honestly pissed me off", "I was genuinely angry at myself") outperformed hooks that implied emotion through subject matter. Direct naming reads as authentic. Implied emotion reads as content.
08

The pre-write checklist

Before writing
What is the open loop this hook will create?
What does the reader currently believe that is wrong or incomplete?
What is the most specific thing that can go in line 1?
What will line 2 do that line 1 doesn't prepare them for?
After writing
Is line 1 under 15 words?
Does line 2 arrive in a different emotional register than line 1 left?
Does the hook close its own loop? (If yes, rewrite.)
No em dashes, no "here are", no context or background?
If it's a question, does it name a tension the reader is actively sitting with?
Does the body continue from where the hook left off?
One last thing

Hooks are just 10% of the game. The other 90% is the system behind them.

What to post, when to post, what your data says, and how all of it connects to actual pipeline. That's the part most people never build and it's exactly what we do for our clients, done for you, end to end.

Want to work with us? We position you as an authority in your niche and get qualified calls booked to your calendar.  Book a call with me 
In case you want to say hi -  Follow me on LinkedIn
Join the newsletter - this is where i dont filter out anything. 

Now go write a hook that makes someone stop scrolling.

deep sangani / flowmatic