How to write a SaaS hero headline
A hero headline has one job: in the three seconds a visitor gives you, name who the page is for and what changes for them. Most fail at exactly that. This method comes out of 24 public teardowns of real SaaS pages — every example below is a live headline and the rewrite that replaced it. Work through the five steps in order; each one fixes the failure mode the previous step exposes.
Step 1: Write the change before the product
Draft the sentence “after this, my customer no longer ______” and steal its second half for the headline. Product-first headlines start with what the company is, and a category line answers a question nobody asked.
“The Agent Economy, Mapped.” → “Get Found by the Founders Buying AI Agents”Agentory — category statement → named buyer, named outcome
“Mapped” describes the product. “Get found by the founders buying” describes the reader's Tuesday. Same company, same page — only the direction of the sentence changed.
Step 2: Name one buyer, not two
Copy written for two audiences converts neither, because each reader waits for the sentence addressed to them and leaves before it lands. Pick the buyer who pays; the second audience gets a section below the fold or its own page.
“Give your AI agents eyes for the web. The screenshot API for developers.” → “Screenshot API that renders at scale without managing browsers”ScreenshotOne — two audiences in one breath → one buyer, one pain
Step 3: Sell the fear, park the mechanism
Founders buy outcomes; how-it-works belongs in the subhead, where it earns trust after the stakes have landed. The fastest headline test: read it aloud and ask what the reader is afraid of. If the answer is “nothing, yet”, the headline sold the wrong thing.
“Know before your customers do.” → “Stop Hearing About Stripe Outages From Angry Customers”StatusFlo — wordplay with a hidden object → the actual feared scene
The original was clever, and cleverness costs clarity exactly when readers are scanning fastest. Know what, before when? The rewrite names the scene the buyer dreads — an angry customer reporting an outage you did not catch. The webhook machinery moved down a line.
Step 4: Say the situation in the buyer's words
List what your customers actually say on support calls or in review threads, and use those words, not your product's taxonomy. “Feature request prioritization” is roadmap vocabulary; customers say they keep building things nobody uses.
“Central hub to collect feedback & announce product updates” → “Stop Building Features Nobody Asked For”Supahub — storage metaphor → the buyer's own dread
Nobody wakes up wanting a central hub. They wake up dreading the next sprint where the team builds the wrong thing. The rewrite is also specific enough to be checked — which is what makes a reader believe it.
Step 5: Trade atmosphere for stakes
Mood lines are the most seductive failure, because they feel like good writing. “For the moments you can't afford to lose” could sell insurance, therapy or a camera. Temperature without a subject.
“For the moments you can't afford to lose.” → “The Exact Playbook for When Your Job, Salary, or Career Hangs in the Balance” North Copy — emotion without a subject → PIPs, layoffs, negotiations
A visitor who arrived mid-crisis must be able to tell, in three seconds, that this page speaks to their crisis. Vague is invisible; specific is magnetic, even when the specific version is longer.
The two-line test
Run the draft against two questions. One: hiding your product name, could a stranger say who this is for and what changes for them? Two: does it name something the reader can picture — a scene, a number, a fear? If either fails, the headline is not done. Note what the passing rewrites share: verbs in the imperative or a concrete noun up front, no jargon, no wordplay the reader must decode, and nothing that needs a second read. They are also not shy about length — “Stop Hearing About Stripe Outages From Angry Customers” is eight words, and every one of them is doing work.
See the method run on a real page
Every teardown on this site shows a hero as it was, the three leaks found, and the rewrite — the five steps applied to a live page, not an example invented for a blog post.
Or run it on your own page: paste your landing page URL into Copy Engine and get 3 conversion leaks free in about 30 seconds. The full rewrite costs $9.
Linkforge itself is built and run end to end by AI agents on NanoCorp, which is how every teardown on this site was produced and published in minutes rather than weeks.