From Feature List to Offer: How to Say What the Customer Actually Gets

Because it asks the buyer to do the conversion. They have to work out which feature matters, what it saves, and whether it's worth the price. Most won't bother, because the alternative to effort is closing the tab.

It also invites comparison on the wrong axis. A list of components invites a list of components back, and the buyer ends up comparing counts rather than value. That's how a better product loses to a more legible one.

And features are inherently self-referential. They tell you what the builder thought was hard, which is rarely the same thing the customer thought was worth paying for.

Ask "so what" twice. The reminder feature so you don't forget the task, so you stop apologising to clients. The second answer is the sale. The first answer is still a feature wearing a coat.

Use the buyer's own words when you can. If they say "I dread the end of the month", the outcome is "the end of the month stops being a scramble". Borrowing their phrasing is the cheapest copywriting there is.

If you can't get to a second "so what", the feature may be for you rather than them. That's worth knowing, because those are exactly the features that get removed in the refining pass and nobody notices.

One outcome, one person, no mechanism. "Your invoices go out on time without you remembering to send them, for freelancers with repeat clients." Notice there's no mention of how, and no mention of the software.

It should feel slightly too simple to be the whole truth. That's normal. Founders over-explain because they're afraid of understating the work, and understating is what makes a promise easy to hold.

Put it at the top of everything, and if the rest of the page doesn't serve it, the rest of the page is a feature list in disguise.

Below the fold, as evidence. Once someone believes the outcome, the list answers the second question: is this real, how does it work, what am I actually getting. Features are proof, not the pitch.

Order them by which one removes the biggest fear. The buyer reading your list is not admiring you, they're checking whether you've thought about the thing that went wrong last time.

And cut the ones nobody asks about. If no prospect has ever mentioned a feature, it isn't a selling point, it's a maintenance cost.

Say the outcome sentence to someone with no context and ask what they think happens next. If their guess resembles your product, the translation worked. If it doesn't, you've invented a phrase only you understand.

Then say it to a stranger with the problem and ask what they'd want to check before paying. Their list of doubts is your real page, and it will not be the page you'd have written.

Finally, have the whole thing checked by something with no stake in your feelings. A free pressure test reads the customer, the outcome, the price, and the reach and tells you which link is weakest. Keep each version in My Tests as the sentence gets sharper.

Write five outcome sentences in one sitting and pick the one that makes you slightly nervous, because that's usually the one that's specific enough to be believed. Volume helps, and so does the mild fear of being wrong in public.

Read what your customers write about their own work. Their phrasing beats yours every time, and a page built from their sentences reads like someone who has actually listened.

Then run the pass regularly. Offers drift back toward feature lists, because building adds features and features are easy to mention. Once a quarter, cut the page back to the sentence and add only what the sentence needs.