pagelint

Benefit-led headlines: the outcome, not the feature

Ogilvy's prescription for benefit-first copy, what CXL's tests show about outcomes vs capabilities, and the rewrite formula.

TL;DR

Your headline should state what changes for the buyer. 'Get answers from real buyers in 24 hours' beats 'AI-powered survey platform with 50+ integrations'. Ogilvy (1983) called the headline the telegram that decides whether the reader reads the copy. Feature copy fits product-aware visitors who are comparing capabilities.

"AI-powered survey platform with 50+ integrations" describes what the product is. "Get answers from real buyers in 24 hours" describes what the buyer experiences. These are not the same statement. One leads with engineering capability; the other leads with buyer outcome. Visitors scan landing pages to answer one question: what changes for me if I use this? Feature-led headlines make them work to find the answer. Benefit-led headlines hand it to them. This is the long version of PageLint check VA-6: Benefit-led, not feature-led headlines.

What Ogilvy actually prescribed

Ogilvy was specific about this in Ogilvy on Advertising (1983): the headline must promise a benefit to the reader.

The headline is the most important element in most advertisements. It is the telegram which decides whether the reader will read the copy. On the average, five times as many people read the headline as read the body copy.

— Ogilvy, David. Ogilvy on Advertising. Crown Publishers, 1983. Ch. 7.

The operative word in Ogilvy's framing is "telegram" — a compressed message that must stand alone. A telegram about features tells the recipient what the product has. A telegram about benefits tells the recipient what they get. The reader's interest is in themselves, not in the product's architecture.

Ogilvy's prescription in the same chapter: "Your headline should telegraph what you want to say — and say it in simple language." The "what you want to say" is always the benefit. Not the mechanism that produces it.

Features vs benefits — the actual distinction

A feature is a property of the product. A benefit is a change in the buyer's world.

Features: 50+ integrations, AI-powered, real-time sync, drag-and-drop editor, SSO support, 99.9% uptime SLA.

Benefits: invoices paid 11 days faster, no more chasing clients for payment, audit results in 30 seconds, find the exact line losing you conversions.

The distinction matters because buyers don't buy features. They buy changes in their situation. A "50+ integrations" headline requires the visitor to infer: integration with what? For what purpose? Saving me how much time? The buyer's brain has to do the translation work that the copywriter failed to do.

Visitors scan to answer one question: what changes for me? Feature headlines make them work for it.

Why features appear in headlines anyway

Three reasons features dominate SaaS landing pages:

1. Engineers write or approve the copy. Features are concrete, verifiable, and defensible. "50+ integrations" is a fact. "Get answers in 24 hours" requires evidence. Features feel honest; benefits feel like marketing.

2. Benefits are harder to write specifically. "Faster" is a benefit but a weak one. "11 days faster invoice payment" is a benefit with enough specificity to be persuasive. The work of finding the specific benefit is harder than listing features.

3. Competitive anxiety. Founders list features because they're worried about objections — "does it have X integration?" — before the visitor has decided they want the product. This answers a later question before answering the first one.

The rewrite formula

The formula: [specific role] [specific action] [specific outcome] [specific timeframe or condition]

Not all four components are always needed. But the more specifics present, the stronger the headline.

AI-powered survey platform with 50+ integrations
Get answers from real buyers in 24 hours — no agency needed
Before: feature list (AI-powered, 50+ integrations). After: buyer outcome (answers from real buyers), timeframe (24 hours), removed barrier (no agency). Same product, different framing.
The intelligent CRM for modern revenue teams
CRM that shows you which deals close this quarter — before you push them
'Intelligent' and 'modern' are adjectives that substitute for a claim. The rewrite names a specific buyer outcome (which deals close) and a specific timing (this quarter, before you push them).
Automated email marketing platform
Send the right email to each subscriber without writing 12 versions
'Automated' is a feature. The rewrite names the problem (writing 12 versions) and the outcome (right email, no manual work). The buyer understands immediately what changes.

A benefit headline assumes the visitor already wants the outcome. If they don't yet feel the problem, start one step earlier: the PAS copywriting formula names the problem first and gets to the outcome after.

The "so what?" test

Every feature headline can be tested with the "so what?" question. "AI-powered survey platform." So what? "You get faster responses." So what? "You make decisions in days instead of weeks." So what? "Your product ships with evidence instead of assumptions."

The last answer is usually the headline. Writers stop too early — at the feature or the immediate benefit — and don't follow the chain to the outcome the buyer actually cares about.

When feature copy is appropriate

Features work in a specific context: the visitor already knows they want the product and is now evaluating capabilities. This is product-aware traffic (Schwartz's fourth state). For these visitors — comparison shoppers, people evaluating specific integrations — feature copy is the right language. Visitors one step further along, who already want the product, need even less: the product name and the offer. That case is covered in Schwartz on headlines for most-aware visitors.

The error is using feature copy for awareness-stage traffic — visitors who are still deciding whether they need this category of product at all. Those visitors need benefit framing to translate the features into outcomes they care about.

On a landing page designed for paid or SEO traffic, the audience is typically problem-aware or solution-aware, not product-aware. Benefit framing is correct for this traffic.

To test a single headline against this check without auditing the whole page, paste it into the free headline analyzer. It runs VA-6 with five other headline checks and suggests a rewrite.

How PageLint detects this

VA-6 is an LLM check. The model reads the H1 and the H2 section headings and asks whether they lead with visitor outcomes or with product features. Two things decide it:

  1. Outcome presence: Does the headline describe a change in the buyer's world? Words like "get", "save", "find", "stop", "close", "ship" signal outcomes. Words that describe product properties (AI-powered, automated, intelligent, next-generation) signal features.

  2. Consistency: Does the pattern hold across the section headings? Headlines that consistently lead with outcomes pass. One or two feature-led headings among benefit-led ones are flagged low. An even split is flagged medium. Headlines that mostly describe features are flagged high.

VA-6 does not grade specificity. A vague benefit ("better results") is a job for VA-1 and CL-4; "11 days faster" and "close 23% more deals" are what those checks reward.

Severity: Critical. This check starts with the H1, which Ogilvy established carries 80% of the advertising value. A feature-led H1 is the most expensive single copy error on a page.

Sources cited

Primary:

  • Ogilvy, David. Ogilvy on Advertising. Crown Publishers, 1983. Ch. 7: "How to write potent copy."
  • Ogilvy, David. Confessions of an Advertising Man. Atheneum, 1963. Ch. VI.

Secondary:

  • CXL Institute. Benefit vs feature headline testing. Peep Laja public writing on clarity > persuasion.
  • Hopkins, Claude. Scientific Advertising. Lord & Thomas, 1923. Ch. 6: "Being Specific." (foundational source Ogilvy cites for specificity prescription)
Put this into practice

Apply it to your own page.

Paste your URL. 16 free checks, a score out of 100, each finding quoted from your copy with its source. About 60 seconds, no signup.

Was this useful?
D

Building PageLint solo. Reading the source material so you don't have to. Writing about what I find.

Related

← PreviousMost-aware headlines: write the offer, not the pitchNext →Specific claims in landing page copy: numbers beat adjectives

Related teardowns

The same checks run on real SaaS landing pages, with the score and what to change.