---
title: "Hero Subhead Swipe File"
summary: "The subhead's only job is to buy the next 6 seconds of attention by adding the specifics the headline implied. It elaborates on the cohort, the outcome, or the mechanism – never all three. Treating it as a second headline is the most common waste of the hero block."
canonical: https://unlocksaas.com/swipe-file/hero-subhead
updated: 2026-05-21
publisher: "Unlock SaaS"
author: "Maryan"
license: All rights reserved. Quotation with attribution permitted.
---

# Hero Subhead Swipe File

> The subhead's only job is to buy the next 6 seconds of attention by adding the specifics the headline implied. It elaborates on the cohort, the outcome, or the mechanism – never all three. Treating it as a second headline is the most common waste of the hero block.

## Brunson lens

Hook

## When this is the right thing to rewrite

When the headline tested well but scroll depth still craters in the first 200px. When session recordings show visitors reading the headline, pausing, and bouncing without scrolling past the fold.

## When the hero subhead is NOT the constraint

When the subhead is doing the headline's job because the headline is broken. Fix the headline first; the subhead is a multiplier, not a replacement.

## Pattern library

### 1. Cohort Elaboration

**Formula.** Specifically: <2-3 cohort qualifiers>. <2-3 cohorts who shouldn't read further>.

**Example.** Specifically: founders post-launch, pre-product-market-fit, with a Stripe account that's blinked once. Not for pre-launch dreamers or post-PMF operators.

**Why it works.** Self-disqualification builds trust. Naming who shouldn't read makes the cohort word in the headline mean more.

### 2. Mechanism Reveal

**Formula.** Using <named framework> to <specific job> in <specific time>.

**Example.** Using Russell Brunson's Hook / Story / Offer to label your live page's broken step in 90 seconds.

**Why it works.** Names the method without explaining it. The visitor either recognizes the framework (credibility) or doesn't (curiosity).

### 3. Constraint Statement

**Formula.** <Concrete constraint>. <Implied trade-off>.

**Example.** No ads, no agency, no rewriting the whole page. Just the one step that's actually broken.

**Why it works.** Constraints earn belief because they're specific in a way puffery cannot be.

### 4. Outcome Cascade

**Formula.** First <small outcome>, then <medium outcome>, then <big outcome>.

**Example.** First: a labeled diagnosis. Then: the rewrite that fixes it. Then: 10 paying customers in 30 days.

**Why it works.** Resolves the 'too good to be true' problem by showing the sequence of wins instead of one fat promise.

### 5. Proof Anchor

**Formula.** Based on <named proof>: <one-line proof description>.

**Example.** Based on Russell Brunson's Hook / Story / Offer framework, applied to 1,000+ indie SaaS landing pages.

**Why it works.** Borrowed credibility from a named source. Avoids the 'trust us' problem.

### 6. Time-Bounded Process

**Formula.** <Action verb> in <time>. <Action verb> in <time>. <Outcome>.

**Example.** Diagnose in 90 seconds. Rewrite in one sitting. Recover the first 10 paying customers in 30 days.

**Why it works.** Verbs + times. Reads as a process, not a promise. Founders trust processes more than promises.

### 7. Cost Reframe

**Formula.** For the price of <comparable expense>.

**Example.** For the price of one of your already-failed Facebook ad tests.

**Why it works.** Anchors against a cost the audience has already paid without thinking. Pricing then feels small.

### 8. Negative Promise

**Formula.** Without <unwanted thing the audience expects>.

**Example.** Without rewriting the whole page, without a 6-week brand sprint, without firing your designer.

**Why it works.** Three negations together compress the objection list into one line. Use the audience's exact objection words.

### 9. Quantified Outcome

**Formula.** <Number> <unit> in <time>, from <starting state>.

**Example.** 10 paying customers in 30 days, from a flat post-launch Stripe line.

**Why it works.** Numbers + units beat adjectives. Naming the starting state makes the destination credible.

### 10. Single-Question Reframe

**Formula.** The one question: <specific question the headline implies>.

**Example.** The one question: which of your three real funnel steps is actually broken?

**Why it works.** Compresses the page's value into a single question the visitor can't stop asking themselves.

### 11. Outcome + Audience Filter

**Formula.** If you're <specific audience>, this is <outcome>. If you're not, here's where to go.

**Example.** If you're post-launch, pre-revenue, here's your 90-second diagnostic. If you're not, /alternatives-to walks you somewhere honest.

**Why it works.** Self-disqualification + helpful redirect = trust signal. Most founders won't do it; you should.

### 12. Negation Stack

**Formula.** Not <thing 1>. Not <thing 2>. Just <real thing>.

**Example.** Not a course. Not an agency. Just the 90-second diagnostic on the page you already shipped.

**Why it works.** Negations land harder than affirmations because they cost the seller something.

## Common implementation mistakes

- Repeating the headline in different words. The subhead must add a new specific, not restate the existing one.
- Three adjectives stacked together. 'Simple, fast, effective' adds zero new information.
- Subhead longer than the headline. The subhead should be 1.2 to 1.5x the headline length, not 3x.
- Subhead written for the founder's mom. The cohort word in the headline disappears in the subhead, breaking the qualifier chain.

## Real examples from indie SaaS teardowns

### [Beehiiv](https://unlocksaas.com/funnel-teardown/beehiiv) – Future-identity positioning

_Beehiiv positions against Substack on creator monetization, not features. The funnel sells the upgrade path._

**Why this is a reference for hero subhead.** Subhead carries the future-identity claim the headline only gestures at ('the creator who scales').

**From the hook lens analysis.** The hero appeals to who the reader wants to BE (a creator running a real newsletter business) rather than what the platform does. The reader who lands the identity does not comparison-shop on features.

### [Cal.com](https://unlocksaas.com/funnel-teardown/cal-com) – Open-source as differentiator

_Cal.com sells the open-source alternative to Calendly. The repo IS the trust signal._

**Why this is a reference for hero subhead.** Subhead names the structural differentiator (open-source, self-host) so the headline's promise lands.

**From the hook lens analysis.** The hero frames the product as the open-source version of a SaaS the reader already knows. This compresses two messages into one: what we do (scheduling, like Calendly) and why we are different (open, extensible, self-hostable).

### [Senja](https://unlocksaas.com/funnel-teardown/senja) – Universal-pain naming

_Senja sells a problem most SaaS know they have but never name. The funnel uses its own product as the demo._

**Why this is a reference for hero subhead.** Subhead names the universal pain (collecting testimonials) the headline's promise resolves.

**From the hook lens analysis.** The hero names a pain (collecting and displaying testimonials) that nearly every SaaS founder has felt. The reader does not need a category education; they need the solution. This compresses the entire awareness-stage funnel into the hero.

### [Loops](https://unlocksaas.com/funnel-teardown/loops) – Buyer-by-job-title naming

_Loops sells the SaaS-specific email job. The funnel ignores marketers and talks to founders._

**Why this is a reference for hero subhead.** Subhead specifies the buyer-by-job-title (founders, marketers, devs) so the cohort word is unambiguous.

**From the hook lens analysis.** The hero names the buyer (SaaS founder, SaaS company) explicitly and refuses to position to anyone else. A SaaS founder reading the page feels addressed; a generic marketer reading the page self-selects out, which is the correct funnel behavior.

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

### Should the subhead be longer or shorter than the headline?

Slightly longer. The headline is the visual unit (10-16 words); the subhead adds 1.2 to 1.5x that to land the specifics. Going 3x longer breaks the hero rhythm.

### Can I skip the subhead?

Only if your headline is doing two jobs (cohort + outcome + time). Most aren't, so the subhead is doing the load-bearing work of qualifying the cohort or naming the mechanism.

### Should the subhead repeat the cohort word from the headline?

Yes, at least once. The cohort word is the qualifier the visitor uses to self-select. Dropping it in the subhead breaks the qualification chain and forces the visitor to re-scan upward.

---

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