Swipe file
Hero Headline Swipe File
The hero headline carries the entire Hook job: in one sentence it tells a specific cohort what specific outcome they get. Indie SaaS founders lose more conversions on this single line than on the rest of the page combined, because a vague hero forces the visitor to do the cohort-matching work.
Verified · editorial policy
TL;DR
As of , the short version is: The hero headline carries the entire Hook job: in one sentence it tells a specific cohort what specific outcome they get. Indie SaaS founders lose more conversions on this single line than on the rest of the page combined, because a vague hero forces the visitor to do the cohort-matching work.
Hero Headline Swipe File TL;DR
- Element
- Hero headlines
- TL;DR
- The hero headline carries the entire Hook job: in one sentence it tells a specific cohort what specific outcome they get. Indie SaaS founders lose more conversions on this single line than on the rest of the page combined, because a vague hero forces the visitor to do the cohort-matching work.
- When to use
- When time-on-page is under 15 seconds and bounce rate is over 75 percent. When the live headline could plausibly describe three different products. When founders read it out loud and can't finish the sentence 'this is for ___'.
- When NOT to use
- When the bottleneck is checkout (price shock, payment friction). When traffic is already converting but volume is too low – fix the channel first. When the founder is rewriting weekly without testing – the headline is fine, the operator is the problem.
- Brunson lens
- Hook
- Patterns
- 12 named patterns with formula + example + structural notes
- Last verified
- May 21, 2026
When to use
Rewrite this when
When time-on-page is under 15 seconds and bounce rate is over 75 percent. When the live headline could plausibly describe three different products. When founders read it out loud and can't finish the sentence 'this is for ___'.
Do NOT touch when
When the bottleneck is checkout (price shock, payment friction). When traffic is already converting but volume is too low – fix the channel first. When the founder is rewriting weekly without testing – the headline is fine, the operator is the problem.
12 named patterns
Pattern 1
Specificity + Outcome
Formula
<Specific cohort> get <specific outcome> in <specific time> without <objection>.
Example
Post-launch SaaS founders get their first 10 paying customers in 30 days without paid ads.
Why it works
Names cohort, outcome, time, and the objection in one breath. The visitor self-qualifies on the cohort word.
Pattern 2
Contrarian
Formula
Stop <thing the audience is doing>. <Better thing> instead.
Example
Stop rewriting your landing page. Fix the 90-second diagnostic underneath it.
Why it works
Pattern-interrupt: the audience expects validation, gets contradiction. Earns the next 6 seconds of attention.
Pattern 3
Two-Step (Pain + Promise)
Formula
<Pain statement>. <Specific promise that resolves it>.
Example
Your traffic isn't the problem. The diagnostic that tells you what is – in 90 seconds.
Why it works
Names the pain in the language the audience uses for themselves, then offers the resolution.
Pattern 4
Outcome + Mechanism
Formula
<Outcome> using <named mechanism>.
Example
Find your funnel's broken step using Russell Brunson's Hook / Story / Offer.
Why it works
Pairs the outcome with a credibility-borrowed mechanism, so the promise sounds like a method, not a wish.
Pattern 5
Question Headline
Formula
Why is <observed effect> happening?
Example
Why does your launch traffic spike and then go flat for 6 weeks?
Why it works
Earns the click by naming the observed effect the founder is privately searching for an explanation to.
Pattern 6
Number + Cohort + Outcome
Formula
The <N>-step <category> for <cohort> who want <outcome>.
Example
The 4-step launch playbook for indie SaaS founders who want repeat revenue.
Why it works
Numbers shrink perceived effort. Cohort word does the qualifying. Category word avoids 'magic'.
Pattern 7
Before / After
Formula
Go from <starting state> to <ending state> in <time>.
Example
Go from launch-day spike to compounding monthly revenue in 90 days.
Why it works
Movement framing. Names the current state without insulting it, names the destination concretely.
Pattern 8
Job-To-Be-Done
Formula
<Tool / system> for <specific job> when you <constraint>.
Example
A 90-second launch diagnostic for founders who can't afford a 6-week brand sprint.
Why it works
The job is the unit of search intent. Naming it back to the founder is the cheapest match.
Pattern 9
Negative Promise
Formula
Never <unwanted state> again.
Example
Never ship another launch you can't explain the post-launch flatline of.
Why it works
Loss-aversion variant. Heavier than the positive version, but burns out fast – use sparingly.
Pattern 10
Stack Reveal
Formula
The <stack item 1>, <stack item 2>, and <stack item 3> that get you <outcome>.
Example
The diagnostic, the offer, and the email sequence that get post-launch founders their first 10 buyers.
Why it works
Replaces a feature list with a curated stack. The reader infers completeness without reading further.
Pattern 11
Time-Boxed Mini-Outcome
Formula
In <short time> you'll <concrete one-step outcome>.
Example
In 90 seconds you'll know if your page has a Wrong Person, Weak Offer, or Weak Belief problem.
Why it works
Promises a single deliverable in a single sitting. Lowers the activation friction visibly.
Pattern 12
Anti-Vague
Formula
Not <vague thing the category usually promises>. <Concrete unit of value>.
Example
Not another generic launch course. A 90-second diagnostic on the page you already shipped.
Why it works
Frames against the category's default and substitutes a measurable unit. Reads as honest, which is rare in this category.
Common implementation mistakes
- Writing the headline for the founder, not the visitor. The founder knows the cohort word; the visitor only knows their own job-to-be-done.
- Naming the product before naming the outcome. Visitors don't care what the thing is until they know what it does.
- Using three adjectives where one specific number would do. 'Faster, simpler, smarter' loses to '90 seconds'.
- Burying the cohort word in a sub-bullet. The cohort word belongs in the H1, not the H3.
- Testing headlines without keeping the rest of the hero fixed. A/B noise becomes signal only when the rest of the page is identical.
Real examples from indie SaaS teardowns
Pattern names above are illustrative. These are real, named, dated funnels from the Unlock SaaS teardown set where the hero headline demonstrates the pattern in a shipping product. Funnel-hack the real ones.
hook lens
Tally – Structural promise as hero
Tally turns the freemium ceiling into the headline. The funnel is the price line.
The freemium ceiling IS the headline. One structural promise (free forever, unlimited) replaces a feature list.
From the teardown: The hero communicates one structural difference from the dominant incumbent (Typeform) and lets that difference do the heavy lifting. There is no metaphor and no founder narrative on the first scroll. The implicit argument is: if you already know the category, you know what 'unlimited' is worth, and you do not need more copy.
hook lens
Plausible Analytics – Named villain plus principle
Plausible sells transparency as the product. Open revenue dashboards do the conversion work.
Named villain (Google Analytics) plus principle (privacy). The cohort-match happens in the named villain alone.
From the teardown: The hero names Google Analytics as the thing being replaced and frames the replacement on a principle (privacy) rather than a feature. This converts an undecided reader into a decided one within the first paragraph by giving them a side to be on.
hook lens
Lemon Squeezy – Category reframe
Lemon Squeezy sold a category swap (MoR), not a feature. The funnel reframes payments into compliance relief.
Category reframe ('merchant of record') turns a feature into the whole positioning.
From the teardown: The hero does not say 'cheaper than Stripe' or 'easier than Paddle'. It says 'we sell on your behalf', which moves the buying decision from payment-processor evaluation to compliance evaluation. The reader who lands the reframe never compares the per-transaction fee directly.
hook lens
Resend – Code as hero
Resend sells developer experience as the differentiator in a commodity category. The funnel reads like documentation.
Code snippet as the hero block. The audience self-qualifies on whether the code is legible to them.
From the teardown: The homepage shows code, not testimonials. A developer who can read the snippet has effectively completed a demo before scrolling. This is the equivalent of a SaaS landing page where the hero IS the product window.
hook lens
Polar – Named-segment bundle hook
Polar bundled MoR plus creator monetization into a single sell. The funnel targets the open-source maintainer specifically.
Named-segment bundle hook ('for open-source maintainers'). Cohort word does the qualification.
From the teardown: The hero names open-source maintainers as the buyer and bundles payment, subscription, and sponsorship features at that named segment. A maintainer reading the page sees a tool built for them rather than for generic creators.
Which Brunson job does this element do?
This element sits in the Hooklens. Knowing the lens tells you what the element is supposed to accomplish, not just what shape it takes – so you don’t rewrite a Story element using Hook tactics or vice versa.
People also ask
What is a hero headline swipe file?
The hero headline carries the entire Hook job: in one sentence it tells a specific cohort what specific outcome they get. Indie SaaS founders lose more conversions on this single line than on the rest of the page combined, because a vague hero forces the visitor to do the cohort-matching work.
When should I rewrite my hero headline?
When time-on-page is under 15 seconds and bounce rate is over 75 percent. When the live headline could plausibly describe three different products. When founders read it out loud and can't finish the sentence 'this is for ___'.
When is the hero headline not the right thing to fix?
When the bottleneck is checkout (price shock, payment friction). When traffic is already converting but volume is too low – fix the channel first. When the founder is rewriting weekly without testing – the headline is fine, the operator is the problem.
Questions founders ask about hero headline copy
How many words should a SaaS hero headline be?
10 to 16 words is the workable range. Under 8 forces vagueness; over 18 stops scanning. The constraint is one breath, one cohort word, one outcome word.
Should I A/B test hero headlines on low traffic?
No. Under 1,000 weekly visits, you don't have enough resolution. Rewrite based on diagnostic feedback (which cohort word is the visitor actually searching) and re-publish – treat the live page as a single read each week.
What's the difference between a hero headline and a hook?
The headline is the visual unit. The hook is the conceptual job that headline + subhead + image together perform: stopping the qualified visitor's scroll long enough to start the story.
Related Brunson terms
Apply these patterns to your live page
The free 90-second Launch Diagnostic checks whether the hero headline is actually the broken step on your page, or whether the bottleneck is upstream.