Sell the Outcome, Not the Product: Nobody Wants a Drill — They Want the Picture on the Wall
Topic: Sell the Outcome, Not the Product·4 principles
What the customer pays for is never your product — it's the better situation they're in once they've used it. The more you rattle on about the product, the further you drift from that.
Take one step on from last time. Last topic: "people hire a product to get a job done." Today: once the job is done, the result the customer walks away with is the actual reason they paid. Yet the moment most people start selling, all they describe is what the thing is — specs, materials, feature counts. Meanwhile the buyer's head is stuck on a different question: "So what does that do for me?" If you don't translate "what it is" into "how my days get better," they have to translate it themselves — and most people won't bother, so they leave. This topic teaches one move: push every feature up the ladder — feature → benefit → outcome — all the way to a concrete result in the customer's world that they can see, count, and want to pay for. You'll notice the most expensive things are often described the "lightest" — because they're selling a change, not a part.
PRINCIPLE 01
Feature → Benefit → Outcome: They Only Pay for the Top Rung
Features tell, outcomes sell — climb the ladder
FAB ladderso whattranslate
The principle, in one line
Every feature has to answer a "so what does that do for me?" — and keep answering it until it lands on a concrete result in the customer's life. Features are nouns; outcomes are verbs — people only ever pay for the verb.
From the masters
"Don't sell the steak — sell the sizzle."— Elmer Wheeler, Tested Sentences That Sell (1937)
How one feature climbs to the "outcome" rung
Scene
You're selling a robot vacuum. The customer is at the counter.
✗ Reciting features (they're not translating)
"It's 5000Pa suction, lidar navigation, app-based zone cleaning, a 280ml bin, 180-minute runtime." A wall of specs. The customer nods while privately thinking, "how's this different from the 4000Pa one next door, and why is it $50 more?" — so the conversation slides straight to price.
✓ Climb to the outcome (translate all the way)
Feature → benefit: "It maps and cleans by zone on its own (feature), which means you never have to move furniture or babysit it (benefit)."
Benefit → outcome: "So you come home from work and the floor is already clean — that's 40 minutes a day back, for your kids, or just for lying down. What it really sells isn't suction; it's the time you get back every day."
Same machine — you turned a spec sheet into "40 minutes a day," and now the customer isn't comparing "cheap vs pricey," they're comparing "is 40 minutes worth it?"
Why it works · mechanism & evidence
Why it works
Mechanism: the curse of knowledge + translation cost. You know your product so well you unconsciously assume the other person does too — so you recite specs, forgetting the customer has no "5000Pa = no moving furniture" wire in their head. That translation from feature to their benefit is your job; skip it and you dump the cognitive load onto the customer — and a tired brain walks. Climb the ladder for them and the decision becomes effortless.
The curse of knowledge · the "tapping" study (Elizabeth Newton, 1990, Stanford PhD; popularized in the Heaths' Made to Stick) — tappers drummed out a song everyone knows and predicted 50% of listeners would guess it; only 2.5% did. The "spec = benefit" tune is crystal-clear in your head; the customer just hears noise. This is the psychological root of "experts only recite features."
The FAB (Feature–Advantage–Benefit) rule — translating spec → advantage → benefit step by step is one of the oldest frames in sales training. Honest strength: this one is mostly craft wisdom / industry method, not a controlled experiment; but it points the same way as the curse-of-knowledge finding above, so it's well-grounded in practice.
The "sizzle" principle (Elmer Wheeler, 1937) — over eighty years ago, ad testing already found that what triggers the order is the imagined sensation and result, not the ingredient list.
Boundary: with a genuine expert (someone who translates specs into outcomes themselves — an engineer sourcing components), over-"translating" just sounds like padding. Then getting the specs accurate and complete matters more. See this topic's last principle.
Run each selling point through the "so what?" triple (checklist)
Write down the feature you most want to mention (one line — what it is).
Ask "so what?" once → you get the benefit (what it does for the user).
Ask "so what?" again → it lands on the outcome (how their life / work / situation concretely improves).
Can you ask once more? Then climb another rung, until the sentence contains "time saved / money made / pain avoided / the kind of person they become."
Then lead with only the top rung or two — attach the feature behind it as evidence, not as the star.
Common mistakes
Stopping at the "benefit" and calling it the outcome. "More convenient" is still a benefit; "you get home to a clean floor and 40 extra minutes with your kids" is the outcome. The more concrete, the more valuable.
Reciting features fluently and mistaking it for expertise. The better you know the specs, the deeper you fall into the curse of knowledge — you think you're showing mastery; the customer hears noise.
Serving all ten features at once. Nobody remembers ten; they remember one outcome that's about them. Less is more.
Key references
Chip & Dan Heath, Made to Stick — source of "the curse of knowledge" and Newton's tapping study. Elmer Wheeler, Tested Sentences That Sell (1937) — "sell the sizzle, not the steak," a classic of early ad testing.
Scripts to steal
Ready-to-use lines
"So what?" — ask yourself these two words after every feature, until you can't ask anymore.
"Which means you…" — the cleanest bridge from feature to benefit: "it has X, which means you get to…"
"Sell the sizzle, not the steak." — sell the aroma, not the raw meat.
PRINCIPLE 02
Sell the World They're In Afterward — the After-State
Sell the after — the picture on the wall
before/afterreward previewvivid picture
The principle, in one line
The customer doesn't want the drill, or even the hole — they want the picture hanging on the wall, and the satisfied version of themselves who hung it. Your job is to make them see that better world before they pay.
From the masters
"People don't buy products; they buy better versions of themselves."— common in copy & branding (often traced to Samuel Hulick / the Ogilvy lineage)
Scene
You sell online personal-training programs. The customer asks, "how many sessions, and how big is your exercise library?"
✗ Selling the product (stuck in "now")
"48 sessions, 200 exercise videos, an app to track it, plus a meal plan." All "what you'll receive" — the customer still has no idea "who I'll be in three months," so all they can do is compare session counts against another provider's price.
✓ Selling the after-state (show the better them first)
"Picture three months from now: you wake up without the lower-back ache, climb four flights without gasping, those jeans from last year fit again, and coworkers ask what you've been doing because you look so on it." Light up the picture first, then land it: "To get to that version of you, what you actually need is someone to lay out what you train each day and keep you from slacking — these 48 sessions and the meal plan are the path there, not the destination."
Why it works · mechanism & evidence
Why it works
Mechanism: the buying decision is ignited by imagining the reward of ownership. When people decide whether to buy, the brain doesn't coolly tally specs — it first previews "what will it feel like to have this?" The more concretely you paint that better picture, the more the customer's reward circuitry lights up — and that anticipated pleasure is the force pushing them to pay. Reciting specs alone leaves that circuit cold.
Neuroscience · the brain "previews" the reward before you pay: Knutson, Rick, Wimmer, Prelec & Loewenstein (2007, Neuron), "Neural Predictors of Purchases" — using fMRI to watch buying decisions: seeing a desirable product activated the nucleus accumbens (NAcc, the reward-anticipation hub), which predicted "will buy"; seeing a price that felt too high activated the insula (which processes pain) and dropped medial prefrontal cortex (mPFC) activity, predicting "won't buy." Selling the outcome = enlarging the NAcc side of that imagination. (cross-ref neuroscience on the reward system, psychology on persuasion.)
Psychology · a concrete picture persuades more and sticks better — consistent with the "concreteness / imageability" effect: the more vividly information can be pictured, the more persuasive it is (same root as the Heaths' "concrete" principle in Made to Stick).
Honest strength: Knutson's study is a well-designed, heavily-cited fMRI result — fairly hard evidence; but "describe it more vividly and they buy more" is a reasonable extrapolation, not a causal claim the same experiment directly proved. Don't treat it as a switch you flip.
"Before → after" script
Before → After, three steps
· Now (the pain): "Right now, aren't you…? (name today's situation and its friction)"
· After (the relief): "Once you've got this, you'll… (one concrete, picture-able scene with sensory detail)"
· The bridge (the product): "To get from here to there, all you need is… (only now do you present the product as that bridge)"
Common mistakes
A hollow picture. "It'll make you more successful and confident" — too abstract to picture. Get concrete: "you speak up first in Monday's meeting and your boss nods."
Exaggerating past the truth. The after-state must be one the product can actually deliver; invent an impossible picture and delivery day is a trust cliff. Vivid ≠ overblown.
Giving the "after" without the "bridge." Light up the picture but never land on "so here's your next step," and the moved customer, unsure what to do, cools right off.
Key references
Knutson et al., 2007, "Neural Predictors of Purchases" (Neuron) — the "reward anticipation vs price pain" neural model of buying. Donald Miller, Building a StoryBrand — a practical frame for casting the customer as the hero and selling the transformed version of them.
Scripts to steal
Ready-to-use lines
"Imagine waking up three months from now…" — the opener for any after-state.
"the after state" — the better situation once they've used it.
"We sell the transformation, not the tool." — sell the change, not the object.
PRINCIPLE 03
Translate the Outcome Into Money and Time — Make Value Computable
Quantify the outcome — put a number on it
quantify valueROIcost of inaction
The principle, in one line
Once the outcome is counted in concrete money or time, "is it expensive?" becomes "is it worth it?" Price is a fixed number; if value stays an adjective, the scale always tips toward price — your job is to put a number on the value too.
From the masters
"Price is what you pay. Value is what you get."— Warren Buffett
Price is one point; value has to be stacked into a mountain
Scene
You sell bookkeeping / inventory software for small shops, $6,000/year. The owner frowns: "that's a bit steep."
✗ Fighting a number with adjectives
"It's not expensive, it's really good, saves you tons of hassle, everyone in your industry uses it." "Tons" and "everyone" are adjectives — they can't hold down the hard number "6,000," so it ends in a discount.
✓ Put a number on the value too
"Let's run the numbers: how many hours a week do you spend reconciling by hand right now? …Four? That's about 200 hours a year. The software cuts it to half an hour a week — roughly 180 hours saved a year. At your own hourly worth, what's that? On top of that, last month you over-ordered two batches because inventory was logged wrong — this flags that early, and that one mistake alone covers most of the annual fee. $6,000 buys back 180 hours plus no more dead stock — is that spending money, or saving it?"
Why it works · mechanism & evidence
Why it works
Mechanism: comparability + lower uncertainty. Price is inherently a precise number; if value stays an adjective like "really good," the two aren't on the same axis, so the brain can't compare them and just fixates on the one number it has (the price). Count the outcome in money / time and you give value a scale — for the first time the customer can put "get" and "pay" on the same balance. And a concrete number lowers the "is it actually worth it?" uncertainty, so decision resistance drops.
Value selling / the business case — quantifying ROI and spelling out "the cost of not changing" is a mature B2B playbook (covered in depth later, in Phase F). Honest strength: this one is mostly industry consensus, short on clean controlled trials, but its logic aligns with the two points below.
Concrete, vivid numbers persuade more — consistent with the concreteness effect: a claim that lands on "180 hours" or "two batches of dead stock" is more memorable and credible than "saves a lot of hassle."
Losses hurt more (prospect theory): Kahneman & Tversky (1979) — for an equal amount, a "loss" hits roughly twice as hard psychologically as a "gain." So framing value as "the 180 hours you're losing / that dead stock" often moves the decision more than "what you could earn." (This is hard evidence — but don't let it slide into manufacturing fear: quantify the real cost, not an invented one.)
Boundary: the numbers must be true and checkable. Compute with the customer's own figures ("you said four hours a week"); don't hand them a fake ROI they don't buy — get caught once and every number you cite after is dead.
Three questions to quantify value (script)
Turn the "outcome" into money / time
· "How much time a week / month do you spend on this right now?" — convert time into money.
· "Last time this went wrong, how much did it cost (money / customers / rework)?" — put the cost of not changing on the table.
· "If it were solved, how much would you save / earn extra over a year?" — let them say the number; it carries more weight than yours.
Common mistakes
Fighting a price war with adjectives. "Great value," "high bang-for-buck" are empty words that lose to a concrete price every time.
Inventing an ROI and forcing it on them. A number the customer doesn't accept is no number at all; compute it together, with their figures, and they believe it.
Counting only the gain, never the cost of inaction. Often "how much quietly leaks away each year if this continues" stings more than "how much you'd earn" — don't miss that half.
Key references
Kahneman & Tversky, 1979, "Prospect Theory" — the origin of loss aversion (the pain of a loss is roughly twice the pleasure of a gain). Value selling / business-case methods — the consultative practice of quantifying ROI and the cost of inaction (detailed later in this site's value-selling piece).
Scripts to steal
Ready-to-use lines
"What's the cost of doing nothing?" — the sharpest single question for quantifying value.
"Let's run the numbers together." — compute it jointly, with their figures.
"It pays for itself in three months." — it earns back its cost in a quarter.
PRINCIPLE 04
More Features ≠ More Value — and When Outcome-Selling Fails
More features ≠ more value — and when outcome-selling fails
feature fatigueboundarieshonesty
The principle, in one line
Before buying, more features look like "more worth it"; after buying, more features often turn into "more of a headache." Value isn't the length of the feature list — it's the actual outcome the customer walks away with. Extra features may be dragging your value down.
Scene
You sell a note-taking app and habitually pitch "more features" as the selling point.
✗ Piling on features (longer = better?)
"We've got 30 templates, backlinks, AI summaries, kanban, Gantt charts, formulas, a whiteboard, 24 themes…" The customer thinks "wow, so complete" on the spot — then opens it at home, gets overwhelmed, has no idea where to start, and abandons it in three days. You won the demo and lost the retention.
✓ Aim at one outcome (less is more)
"If all you want is 'nothing in my head gets lost,' then you only need three steps: jot it down, it auto-organizes, you can find it anytime. The rest can wait until you've settled in." You collapsed thirty features into the one outcome they actually want — easy to start, easy to keep.
Why it works · mechanism & evidence
Why it works
Mechanism: feature fatigue + choice overload. Before buying, people imagine value through capability — more features, more powerful; after buying, they experience value through usability — more features, harder to use. The mismatch between the two views produces "thrilled at purchase, regretful in use." Piling on features also creates choice overload: more options spike cognitive load, which actually lowers action and satisfaction.
Feature fatigue · Thompson, Hamilton & Rust (2005, Journal of Marketing Research) — before purchase consumers lean toward more features, but after use, complexity drives satisfaction down and buyers regret "getting too much." Piling on features builds short-term closes on long-term dissatisfaction. (Peer-reviewed, fairly hard.)
Choice overload · the "jam study," Iyengar & Lepper (2000, JPSP) — a display of 24 jams drew more people to stop and look, but the eventual purchase rate was far below a display of just 6 (about 3% vs 30%). More options ≠ more sales. (Note: later replications are contested and the effect size depends on context, so treat it as directional, not iron law.)
This also marks the failure boundary of outcome-selling: when the buyer is an expert purchasing a standardized commodity (they already know the outcome and are only comparing specs and price — buying screws or RAM in bulk), your "imagine this…" is just filler. Then accurate, complete specs at the right price is the respectful move. Selling the outcome is the default play, not the only play.
Collapse it to one outcome (checklist)
If you could keep one selling point, what's the one outcome the customer wants most? Lead with it.
Of the features I list, how many will the customer actually use — and how many just make the list look long?
Is this person "an ordinary user who wants the outcome" or "an expert comparing specs"? Sell the outcome to the first, accurate specs to the second.
Does my demo leave them thinking "I could actually use this," or "too complicated, never mind"?
Common mistakes
Making "more features" the core pitch. It wins the demo but often loses on onboarding and retention.
Forcing "imagine this…" on an expert. They want a spec sheet and a quote; your vivid picture only makes you look unprofessional.
Serving everything for fear of missing a selling point. Ten selling points dilute into zero memorable ones; one that hits the outcome is the one that sticks.
Key references
Thompson, Hamilton & Rust, 2005, "Feature Fatigue" (JMR) — evidence that more features means lower post-use satisfaction. Iyengar & Lepper, 2000, "When Choice is Demotivating" (JPSP) — the jam study, a classic of choice overload (replication contested; treat as directional).
Scripts to steal
Ready-to-use lines
"Feature fatigue" — wanting more before buying, drowning in it after.
"Less is more."
"What's the one thing you need it to do?"
Your Day 5 Action
Take anything you have to "sell" — a product, your résumé, a proposal you want someone to accept:
Pick the 1 feature you most want to mention, and push it up the ladder with Principle 01's "so what?" triple: feature → (so what) → benefit → (so what) → outcome, until the sentence contains "time saved / money made / pain avoided / the kind of person they become."
Then, using Principle 03, try to put a number on that outcome (hours saved a year / extra earned / the cost of not changing).
Write the before and after sentence side by side and read them out loud — the first describes your thing; the second describes their future. Notice which one even you would rather buy.
Think It Through
1. My product genuinely has strong specs and hard features — shouldn't I lay them out properly?
You should — but in a different position. Specs aren't skipped; they're just not the star, they're the evidence. The order is: lead with the outcome ("a full day of battery, no hunting for outlets"), and once the customer is drawn in and starting to believe, back it up with the spec ("because it's 5000mAh plus a 10-minute fast charge"). Specs first means the customer has to translate them and most won't — they leave; specs after gives an already-interested person the ledge to tell themselves "I'm not being impulsive, I'm being rational." The one exception is the last principle here: if they're an expert comparing specs on a standardized commodity, give accurate, complete specs and don't dance around — selling the outcome is the default play, not the only one.
2. What's the actual difference between selling the "outcome / after-state" and last topic's "Jobs-to-be-Done"? They sound alike.
They're close cousins, but they look at different things. JTBD looks forward: what situation is the customer in, what progress do they want, so they "hire" a solution — it helps you figure out "what job they're really trying to get done and who the real rivals are." It's the discovery lens. Selling the outcome looks backward: after the job is done, the result they hold, the better situation they're in — it helps you say the right thing. It's the expression lens. In one line: JTBD tells you "which outcome to aim at," selling the outcome tells you "how to describe that outcome so they want it." Use the first to find the bullseye, the second to make the arrow sing.
3. If I make the outcome sound that appealing, won't I slip into exaggeration and hype?
There's exactly one dividing line: can the product actually deliver that outcome? If yes — making it vivid and concrete helps the customer see what they'll really get; that's your job. If no — a picture puffed to the sky becomes a trust cliff on delivery day, and one fall is fatal. The test is simple: the after-state you describe — would you dare repeat it to the customer's face after the sale? If yes, you're illuminating value; if you flinch, you're hyping. Same with quantifying: compute with numbers the customer accepts, don't slip in a fake ROI. Vivid means stating a real benefit clearly, not stating a benefit that doesn't exist.