Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Frameworks

Features, Advantages, Benefits (FAB)

The FAB framework explained: turning features into advantages and benefits buyers care about, the so-what test, using it on pages, ads and in sales, and limits.
Frameworkbeginner8 min readUpdated

What FAB is

FAB is a chain of three statements about one feature. The feature is what the product is or has: a specification, a component, a material, a capability. The advantage is what that feature does or makes possible, usually against an alternative such as the old way, a competitor or doing nothing. The benefit is the result the buyer cares about: time, money, comfort, safety, confidence or a problem that no longer exists.

The middle step is what distinguishes FAB from the simpler advice to "sell benefits, not features". Jumping straight from a feature to a benefit produces claims that feel unconnected: a technical specification followed by a promise of a better life, with nothing to explain how one leads to the other. The advantage supplies the mechanism. It tells the reader how the feature produces the result, which is what makes the benefit believable rather than decorative.

The chain is used in copywriting, in sales conversations and in training anyone who has to explain a product. The guide to the anatomy of a landing page describes translating features into benefits in the benefits section of a page. This page is the full chain, including the middle step, and works at the level of a single feature. Which few benefits a product leads with across all its messaging is a separate decision, covered by the guide to messaging hierarchy and proof points.

The three layers

LayerQuestion it answersExample phrasingTest
FeatureWhat is it, or what does it have?"Taped seams and a sealed zip"Is it a verifiable fact about the product?
AdvantageWhat does that let it do, compared with the alternative?"Keeps the contents dry in a downpour, where an ordinary backpack leaks at the seams"Does it explain how the feature makes a difference?
BenefitWhat does the buyer gain, in their terms?"Your laptop and papers arrive dry, however wet the walk to work"Would the buyer say they want this, in roughly these words?

One feature can lead to several advantages, and one advantage to several benefits, depending on who is buying. The same waterproof backpack offers a commuter a dry laptop and a hiker a dry change of clothes at the summit. A FAB chain is therefore written for a segment, and a product sold to more than one segment needs more than one version of its strongest chains.

Writing FAB chains

Start with the features that matter to the buying decision, not the full specification. A product may have dozens of features; most buyers decide on a few. Customer interviews, reviews, sales notes and support questions show which ones come up when people choose.

For each of those features, ask what it lets the product do, and state the comparison. "Dishwasher-safe parts" is a feature; "goes in the dishwasher instead of being scrubbed by hand" is an advantage, because it says what changes and against what. Then ask "so what?" again, and keep asking until the answer is something the buyer would recognise as a want rather than a property of the product. The buyer's own words are the best source for this last step: phrases from reviews and interviews are usually plainer and more specific than anything written in a meeting.

Check every chain backwards. Read the benefit, then the advantage, then the feature, and ask whether each step follows from the one before without a leap. If the benefit only works with some squinting, it is a guess, and a reader will feel the gap even if they cannot name it.

Then attach proof. A chain explains how a benefit arises; it does not show that it does. Test results, a demonstration, a measurement, a guarantee or Social Proof such as reviews and customer stories make the benefit credible, and the proof works best placed next to the chain it supports.

Finally, choose the order for the reader. Most copy leads with the benefit and uses the advantage and the feature as support. For expert buyers the order often reverses. Bridging phrases such as "which means" and "so you can" help in drafts, but repeated in finished copy they turn into a tic. The messaging house template lists the features that support each pillar; FAB is how each of those features is turned into copy that serves its pillar.

Where FAB fits

Landing pages. On a Landing Page, each item in the benefits section can be one chain: the benefit as the heading, the advantage as the sentence beneath, the feature in the detail or a specification block. The page then moves from what the visitor gains to how, which is the order most visitors read in.

Product pages. The guide to product page optimisation gives each layer of product copy its own job: the short description gives the reason to want the product, and the specification table answers exact questions. FAB maps onto those layers, with the benefit in the short description, the features in the specification table and the advantages in the longer description that connects them.

Ads. An ad has room for one chain at most, and usually for its benefit plus a single feature as evidence. The CTA follows from the benefit, so an ad promising a dry laptop after a wet commute might invite the reader to watch the bag tested in the rain, rather than simply to "learn more".

Sales material and conversations. Battlecards, demo scripts and retail staff training often use FAB to present each capability. In a conversation it works best after the buyer has described their situation, so that the salesperson picks the chains relevant to that buyer rather than reciting every one. In a product demo script, the chain becomes the closing line of each moment, said after the buyer has seen the screen.

Worked example (illustrative)

Illustrative example — not a real result

A thermostat maker rewrites a product page

Kindlethorn Smart Thermostats, an invented maker of home heating controls, opens its product page with a list of 9 features, starting with "learns your schedule". The team rewrites the top of the page as 3 FAB chains. The first reads: the thermostat learns your schedule (feature), so it adjusts the heating to when you are actually home rather than to a fixed timer (advantage), so the rooms are warm when you arrive without heating an empty house all day (benefit). The benefit becomes the headline, the advantage the subheading, and the feature moves to the specification table with the other 6 features. Proof sits beside the chain: an in-house test in 12 homes over 6 winter weeks, published with its method, in which heating hours fell by an average of 18% against each home's previous timer, and rooms reached the set temperature within 10 minutes of arrival on 94% of occasions. Two customer reviews that mention coming home to a warm house sit below. In a 4-week split test, the new page lifts add-to-basket rate from 3.1% to 3.6%.

Limits and criticisms

FAB starts from the product rather than the customer. The chain begins with what the product has and works outwards, so the benefit at the end is often the team's guess about what buyers value. Where that guess is wrong, the copy is fluent and irrelevant. Research into what buyers are trying to do, what gets in their way and what they would value should decide which benefits are worth writing, and FAB then connects those benefits to the features that deliver them.

It tends to produce generic benefit claims. "Saves time", "peace of mind" and "works smarter" could close almost any chain for almost any product, and readers have learned to skip them. A benefit becomes specific when it names the situation and the result: whose time, saved on what, compared with what.

Expert and technical buyers often want the feature first. Engineers, IT buyers, trade buyers and enthusiasts filter options by specification, and copy that leads with benefits can slow them down or read as evasive. For them, put the specification where they expect it and let the advantage carry the explanation.

Every benefit still needs proof. A well-built chain is an argument, not evidence, and a claim about performance, savings or results needs substantiation that would satisfy a sceptical buyer or a regulator. The messaging hierarchy guide covers how claims are substantiated.

Finally, the chain can become a formula. A page made of identical feature-advantage-benefit blocks reads like a template, and chaining every feature buries the few that decide the purchase.

The value proposition canvas is the customer-side counterpart: it maps the jobs, pains and gains of a segment against what the product offers, which is the research that tells you which FAB chains are worth writing. The AIDA framework describes the sequence a message moves a reader through, and FAB chains supply much of the material for its interest and desire stages.

Common mistakes

  • Leaping from feature to benefit. Without the advantage, the benefit has no visible connection to the product.
  • Benefits nobody asked for. A benefit chosen in a meeting rather than from customer research is a guess.
  • Generic benefits. Phrases that fit any product tell the reader nothing about this one.
  • One chain for every buyer. The same feature leads to different benefits for different segments.
  • Hiding the specification from experts. Technical buyers need the facts first and can find benefit-only copy evasive.
  • Benefits without proof. A claimed result needs evidence beside it, not just a plausible chain.
  • Chaining every feature. A few strong chains carry a page; the rest belong in the specification table.

Frequently asked questions

What is the difference between an advantage and a benefit?

An advantage describes what the feature lets the product do, usually compared with the alternative: it is still about the product. A benefit describes what the buyer gains as a result, in their own terms: time saved, a risk avoided, a problem gone. If the sentence would make sense on the product's specification sheet, it is an advantage; if it would make sense in a customer review, it is a benefit.

Should copy always lead with the benefit?

Not always. Most consumer and general business copy reads best benefit first, because the reader wants to know what is in it for them before the detail. Technical and expert buyers often filter options by specification, so for them a page that hides the features behind benefit statements is slower to use and can look evasive; lead with the feature and its advantage, and keep the benefit close by.

How many FAB chains should a product page or ad carry?

As few as carry the decision. A page usually works best with a handful of chains for the features that matter most to the target buyer, with the remaining features in a specification table. An ad has room for one chain at most, and often only its benefit with a single feature as proof.

Terms used on this page

Where this page is used

Also related

Related