Writing for a Reader Who Is Deciding

Most writing aimed at customers imagines an interested reader working through an argument. The real reader is doing something different and less flattering: scanning for a reason to stop.

They have several tabs open. They are not evaluating you on the merits; they are eliminating options to get the list down to a size they can actually think about. Writing for elimination rather than persuasion changes the priorities completely.

Make disqualifying easy

The most counter-intuitive move is to help people leave.

Being explicit about who something is not for — too small, too large, the wrong industry, the wrong problem — is usually resisted, because it feels like turning away business. In practice the people it turns away were not going to buy, and they were going to consume time discovering that.

More importantly, it is the strongest available signal to the people who are a fit. A page that says plainly what it does not do reads as confident and specific. One that implies it suits everybody reads as a company that has not decided what it is, and the reader has to do the sorting themselves.

Lead with the conclusion

The structure taught in school — context, argument, conclusion — is precisely wrong for a scanning reader, because it withholds the answer until they have already left.

Put the conclusion first, then support it. If the page is about a service, say what it is and what it costs before explaining the philosophy behind it. If an email is asking for something, ask in the first line.

This feels abrupt to the writer and does not feel abrupt to the reader. The reader is grateful, because you have let them decide quickly whether the rest is relevant to them.

Specifics survive skimming; adjectives do not

"Fast", "powerful", "seamless", "intuitive" and "robust" carry no information, because every competitor uses them and none of them can be checked.

Replace them with something a reader could disagree with. "Replies within one working day" is checkable. "Excellent support" is not. "Set up in an afternoon without a developer" makes a claim. "Easy to implement" makes a noise.

The test is simple: could a competitor put the opposite on their site? If nobody would ever claim to be slow, unreliable and hard to use, then claiming the reverse tells the reader nothing at all.

Formatting is comprehension, not decoration

A scanning reader reads headings, first sentences, bold text, and lists. Everything else is available if the first pass earns it.

That means headings should say something rather than label a topic. "Pricing" is a label. "What it costs, and what changes the number" is a sentence that does work even for someone who reads nothing else.

It means the first sentence of each paragraph should carry the point, not build towards it.

And it means restraint with emphasis: if six things are bold, nothing is. Bold is a claim on attention, and a page that makes too many gets none.

The reader's environment is part of the writing

It is easy to treat presentation as somebody else's problem, but the conditions the words arrive in are part of whether they are read.

Web Vitals frames these as "quality signals that are essential to delivering a great user experience on the web" [1], and the writing-specific consequence is direct: text that appears late, or shifts as the page settles, breaks the first pass a scanning reader is making. A well-written paragraph that arrives after the reader has moved on has not been written at all.

Line length, contrast, and font size belong to the same category. They are not aesthetic preferences; they determine whether the second sentence gets read.

Email is the same reader, with less patience

Everything above applies more sharply in an inbox, where the competition is not three other companies but forty other messages.

Two practical points. The subject line and the first line are the whole message for most recipients, so the ask belongs in both. And the way you handle people who want out is part of the writing: unsubscribing should be genuinely one click, which is exactly what the specification for signalling "a one-click function for the List-Unsubscribe email header field" [3] provides for. Making it hard does not retain readers; it converts a quiet departure into a spam complaint, which costs you every future message to everyone else.

Write less, and ask for less

Length is the most common form of self-indulgence in business writing. A page that says one thing clearly outperforms one that says four things adequately, because the reader only had capacity for one.

The same applies to what you ask for. Every field on a form is a small negotiation, and asking for information you will not use is a cost with no return — the writing equivalent of collecting data speculatively "in case it is useful later" [2]. If you cannot name what a field is for and who reads it, removing it will improve your results measurably and immediately.

Write about the objection, not around it

There is one subject almost every business avoids in writing, and it is the one readers most want addressed: the reason not to buy.

Every offering has a genuine drawback. It is expensive relative to alternatives, it requires setup effort, it does not do a thing competitors do, it suits one situation better than another. The people deciding know this, or suspect it, and they are looking for it while they read.

When the writing does not mention it, one of two things happens. The reader assumes you are unaware of it, which is a competence problem. Or they assume you are concealing it, which is a trust problem. Both are worse than the drawback.

Naming it directly does something no amount of persuasion achieves: it makes everything else you wrote more believable. A page that says "this takes an afternoon to set up properly, which is more than some alternatives, and here is why it is worth it" has established that it will tell you inconvenient things — so the favourable claims around it acquire weight they otherwise would not have.

It also filters. The people for whom the drawback is disqualifying leave earlier, which is better for both parties than discovering it after a sales conversation.

The revision that improves almost anything

Write the piece, then delete the first paragraph.

The opening paragraph is usually the writer clearing their throat: context, framing, a preamble that helped them start. The reader does not need it, and the second paragraph is almost always a better beginning.

Do it once and it will feel like something is missing. Show it to someone who has not read the original, and it will not.