---
title: "Hero Headline Swipe File"
summary: "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."
canonical: https://unlocksaas.com/swipe-file/hero-headline
updated: 2026-05-21
publisher: "Unlock SaaS"
author: "Maryan"
license: All rights reserved. Quotation with attribution permitted.
---

# 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.

## Brunson lens

Hook

## When this is the right thing to rewrite

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 the hero headline is NOT the constraint

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.

## Pattern library

### 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.

### 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.

### 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.

### 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.

### 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.

### 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'.

### 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.

### 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.

### 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.

### 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.

### 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.

### 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

### [Tally](https://unlocksaas.com/funnel-teardown/tally) – Structural promise as hero

_Tally turns the freemium ceiling into the headline. The funnel is the price line._

**Why this is a reference for hero headline.** The freemium ceiling IS the headline. One structural promise (free forever, unlimited) replaces a feature list.

**From the hook lens analysis.** 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.

### [Plausible Analytics](https://unlocksaas.com/funnel-teardown/plausible) – Named villain plus principle

_Plausible sells transparency as the product. Open revenue dashboards do the conversion work._

**Why this is a reference for hero headline.** Named villain (Google Analytics) plus principle (privacy). The cohort-match happens in the named villain alone.

**From the hook lens analysis.** 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.

### [Lemon Squeezy](https://unlocksaas.com/funnel-teardown/lemonsqueezy) – Category reframe

_Lemon Squeezy sold a category swap (MoR), not a feature. The funnel reframes payments into compliance relief._

**Why this is a reference for hero headline.** Category reframe ('merchant of record') turns a feature into the whole positioning.

**From the hook lens analysis.** 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.

### [Resend](https://unlocksaas.com/funnel-teardown/resend) – Code as hero

_Resend sells developer experience as the differentiator in a commodity category. The funnel reads like documentation._

**Why this is a reference for hero headline.** Code snippet as the hero block. The audience self-qualifies on whether the code is legible to them.

**From the hook lens analysis.** 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.

### [Polar](https://unlocksaas.com/funnel-teardown/polar) – Named-segment bundle hook

_Polar bundled MoR plus creator monetization into a single sell. The funnel targets the open-source maintainer specifically._

**Why this is a reference for hero headline.** Named-segment bundle hook ('for open-source maintainers'). Cohort word does the qualification.

**From the hook lens analysis.** 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.

## Related terms

- [Hook](https://unlocksaas.com/glossary/hook) – The promise plus polarity move a page makes in the first three seconds, before the visitor decides whether to keep reading.

## FAQ

### 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.

---

Canonical URL: https://unlocksaas.com/swipe-file/hero-headline
Publisher: Unlock SaaS (https://unlocksaas.com)
Contact: maryan@unlocksaas.com