0.3Features vs benefits
The essentials in 30 seconds
- Customers buy the payoff: the feature says what it is, the benefit says what it brings them.
- Two bridges: “which means that…” and “so what?” — up to the emotional benefit.
- Benefit first: open with the gain, keep the feature as proof right after.
Running mini-case — Mehdi and the mattress nobody wants
An SME client of Mehdi’s sells mattresses in Algiers: his page lists “25 cm foam, 7 comfort zones” and triggers nothing. Mehdi applies “so what?": 25 cm means a supported back, so mornings without pain and serene days. He rewrites the page opening with waking up without back pain, features as proof.
Sequel to cases 0.1-0.2 — Mehdi turns technique into desire.
1. Customers don’t buy what it is, but what it does for them
Founding distinction of copywriting: the feature describes what the product is or has (size, material, function); the benefit describes what it concretely brings to the customer (result, gain, emotion, problem avoided).
The famous line: “people don’t buy a drill, they buy a hole in the wall” — and really, the mounted shelf and the pride that comes with it. You sell the result, not the tool.
2. Two bridges from one to the other
To turn a feature into a benefit, two reflexes. The bridge phrase “which means that…”: “20h battery which means that you only charge once a week.” And the question “so what?” repeated until the real customer gain.
Push to the emotional benefit: what the product makes them feel (pride, peace of mind, confidence). It’s often more powerful than the functional benefit. “Charge only once a week” → “finally forget the anxiety of a dead battery.”
3. Keep the feature as proof
Careful: you don’t remove features, you put them in service of the benefit. The feature remains the proof that makes the benefit credible. “You save 2h a week (benefit) thanks to automated follow-ups (feature).”
The winning structure: benefit first, feature after as justification. The reader wants to know “what’s in it for me” before “how it works.”
🔎 Concrete example — Rewriting a product page
A mattress described only by its features. Let’s transform it.
Features: "25 cm memory foam, 7 comfort zones."
Benefits: "Wake up without back pain: the foam molds to your body (25 cm memory foam) and supports every zone (7 comfort zones)."Result: the benefit (sleeping pain-free) opens, the feature proves it.
Test: for each technical line, ask “so what, for the customer?”
Section vocabulary
- Feature
- What the product is or has: a technical fact, an attribute (size, material, contents, function).
Simple example: “25 cm foam, 7 comfort zones” on the mattress page.
What it is not: presenting that raw fact as if it sold alone.
Reflex: list the facts, then run them through “so what?”.
- Benefit
- What the feature concretely brings the customer: result, gain, emotion, problem avoided.
Simple example: “Wake up without back pain” thanks to that foam.
What it is not: a vague slogan with no link to a real feature.
Reflex: each benefit must be able to cite its technical proof.
- “Which means that…”
- A bridge phrase to turn a feature into a customer-oriented benefit.
Simple example: “20h battery, which means you only charge once a week.”
What it is not: piling up numbers without ever translating them for the customer.
Reflex: stick the phrase after each listed feature.
- Emotional benefit
- What the product makes you feel (pride, peace of mind, confidence); often more powerful than the functional one.
Simple example: “Finally forget dead-battery anxiety” after the functional benefit.
What it is not: believing emotion replaces proof and the functional benefit.
Reflex: push each benefit one notch with “so what?”.
- “So what?”
- The question to ask of each feature to extract the real benefit for the customer.
Simple example: “7 comfort zones… so what? Support adapted to each body part.”
What it is not: stopping at the first functional benefit without reaching the emotion.
Reflex: repeat the question until the customer’s feeling.
In practice — The features → benefits table
- Take an offer and list its 5 main features in a column.
- Next to each, apply “which means that…” to write the functional benefit.
- Push each benefit one notch with “so what?” up to the emotional benefit.
- Rewrite 3 selling sentences opening with the benefit, feature as proof.
Ready-to-use script — turn technique into benefit (30s)
"This mattress is 25 cm of memory foam, which means your back is supported all night. So what? You wake up without back pain, serene for your day."
Say facing a customer comparing spec sheets: fact, translation, feeling.
Copy-paste template — feature → benefit table
FEATURE 1: _______________
→ WHICH MEANS THAT: _______________
→ SO WHAT (emotion): _______________
SALES SENTENCE (benefit + proof): _______________
FEATURE 2: _______________
→ WHICH MEANS THAT: _______________Small business / tight budget
With no full redesign: rewrite only the first 3 lines of each page (the opening benefit) and leave the rest as is.
Algerian SME
Buyers comparing price and durability at the market: translate each feature into concrete savings or peace of mind (“repairs less, sleeps better”).
Service / freelance
“10 years of experience” doesn’t sell alone: translate into “your texts delivered with no back-and-forth, so your shop online faster”.
Technical product
Keep a “spec sheet” box for rational buyers, but always after the benefits paragraph.
✓ Best practices
- Open with the benefit, keep the feature as proof right after.
- Push to emotion: how it feels often sells harder than how it works.
- Run each feature through the “so what?” test before keeping it as is.
✗ Common pitfalls
- Lining up technical features without saying what they bring.
- Removing features: they remain the proof of the benefit.
- Stopping at the functional benefit when an emotional one would be stronger.
Key takeaways
- Customers buy the result (benefit), not the tool (feature).
- Two bridges: “which means that…” and “so what?”
- Push to the emotional benefit, often the most powerful.
- Winning structure: benefit first, feature as proof.
48h Challenge — apply tomorrow
Take 1 real product page, list 3 features and rewrite them as benefit + proof (template above). Publish at least the first.
- I can turn any feature into a benefit.
- I can push to the emotional benefit.
- I’ve rewritten 1 page benefit-first, proof-second.
Frequently asked questions
Should I banish all features from the text?
No. Features make the benefit credible and answer rational buyers. The mistake isn’t citing them, but stopping at them without saying what they bring.
How to find the emotional benefit?
Ask what the customer will feel once the problem is solved: relief, pride, peace of mind, confidence. The functional benefit says “what it does”; the emotional one says “how it makes you feel.”
“25 cm foam, 7 comfort zones” triggers no purchase. What does Mehdi do first?