The hero headline does 80% of the conversion work on a SaaS landing page. The visitor decides whether to keep reading or bounce within 2–5 seconds — almost entirely based on the first line of text. Here are 8 hero-headline patterns that consistently convert, 30 real examples grouped by mechanic, and the audit checklist we use on every customer engagement.
What the hero headline actually does
A hero headline has one job: answer the unspoken question “is this for me?” in under 5 seconds. If it answers yes, the visitor scrolls. If it answers no — or worse, doesn't answer — they bounce. Every other element on the page depends on the headline doing this job.
Most hero headlines fail by trying to describe the product instead of naming the outcome. “AI-powered customer support platform” describes the product. “Cut your support ticket volume by 40%” names the outcome. The first is forgettable. The second pulls qualified buyers into the page.
8 patterns that consistently convert
1. Outcome-first
Lead with what the reader gets, not what the product does.
- “Ship your SaaS site in 60 seconds”
- “Get paid faster — chase invoices on autopilot”
- “Close more deals with the inbox you already use”
2. Number-led
Anchor a concrete number in the first 3 words. The eye locks on digits.
- “12,000 founders ship with InBuild”
- “94% of audits pass on the first try”
- “60-second site generation, every time”
3. Pain → relief
Name the pain, promise relief in the next breath. Powerful for products that solve a recurring frustration.
- “Tired of paying for analytics no one opens?”
- “Stop quoting clients two weeks for a basic site”
- “Your changelog shouldn't take 4 hours every Friday”
4. Question hook
Open a loop in the reader's head — they read on to close it.
- “What if your site shipped in 60 seconds?”
- “Why is your changelog still on Notion?”
- “How much time would you save if standups wrote themselves?”
5. X but for Y
Borrow the schema of a known thing, swap the audience or use case.
- “Stripe for podcasting”
- “Linear for indie hackers”
- “Figma for technical writers”
6. Specificity-driven
Name real things the reader recognizes, not abstractions.
- “Production Next.js sites. Code export. SEO baked in. $49/mo.”
- “Schema.org markup, sitemap.xml, robots.txt — done.”
- “Lighthouse 98 / 98 / 100. Out of the box.”
7. Audience-named
Say who it's for in the headline. Readers self-select.
- “AI website builder for technical founders”
- “The CRM for solo sales”
- “The deployment platform for indie hackers”
8. Imperative / action
Tell the reader to do the thing. Short. Direct.
- “Ship something today.”
- “Type a prompt. Watch it build.”
- “Open your laptop. Have a website.”
The hero audit checklist
When we audit a SaaS hero on a customer engagement, we run through this:
- Length: 30–65 chars. Below that lacks concreteness. Above gets truncated when used as a page title.
- Specificity: contains a number or a named audience. “Smarter analytics” fails this. “Analytics for engineering teams” passes.
- Power verb early. Ship, build, get, close, launch, save, replace, stop. Not “is,” “are,” “helps you.”
- No filler. Innovative, robust, leverage, seamless, world-class — all signal “I had nothing specific to say.”
- Mobile-readable. Test on a 375px-wide viewport. If it wraps to 4 lines, compress.
- Differentiated. Could a competitor swap their logo onto this page? If yes, the headline is generic.
Run your hero through our headline scorer — the same 8 checks, automated, 0-100 score with rationale.
The subhead does the other 20%
The hero headline names the outcome. The subhead answers “okay, but how does it do that?” in one sentence. Together they should let a skeptical visitor decide in 5 seconds whether to keep reading.
Bad subhead: “The leading AI-powered solution for modern teams.” Good subhead: “Describe what you want, get a complete React site in 30 seconds. Yours to export and own.”
Specific > clever. Concrete > aspirational. Always.