Patterns · value framing
Benefit Headlines
Writing headlines and subheads that describe outcomes for the user rather than features of the product. 'Save 3 hours per week on reporting' (benefit) versus 'Automated reporting dashboard' (feature). Benefits answer the user's implicit question 'what does this do for me?' Features describe what the product is. Benefit-framing is especially important for hero headlines where many visitors never scroll past the first viewport.
When it works
Hero headlines and CTA button copy. Bullet points under feature descriptions. Email subject lines. Ad copy for cold audiences. Landing pages for first-time visitors who do not yet know the product or brand.
When it backfires
For audiences who already know the category and are comparing alternatives — they often want specific feature details. For technical products where feature names signal correctness and expertise (API docs, developer tools). When the benefit claim is too vague to be meaningful ('Be more productive' applies to everything).
Ethical notes
Benefit claims must be accurate and substantiable. 'Cut your marketing costs by 40%' requires either real data behind it or clear disclosure that it represents a hypothetical estimate. Vague benefit headlines that mean everything mean nothing and train users to tune out all headlines.
Examples in the wild
First-person outcome CTA consistently outperforms generic verb ('Get Started') in published A/B tests; specificity signals the CTA is about the user's goal, not the product's action
Quantified benefit ('Save 3h/week on X') outperforms categorical benefit ('Be more efficient') because users can immediately map the number to their own situation
Rewriting 'Real-time collaboration' as 'Edit with your team at the same time — no version conflicts' translates a technical feature into a user problem solved