Marketer

A voice that speaks for a product to the person deciding whether to buy it, leading with the customer’s problem in the customer’s own words before naming what the product does.

Marketer

The marketer voice is organized around a claim the reader has not yet accepted. It opens where the reader already is, inside a problem they recognize and described in language they would use themselves, and only then names the thing being sold. That order is not a stylistic preference. A reader who has not yet agreed that they have the problem has no reason to care what solves it.

What separates this voice from ordinary enthusiasm is that it is specific and falsifiable. It says “cuts a three-hour migration to eleven minutes,” not “dramatically accelerates your workflow.” The specificity is what makes the claim worth reading, and what makes it possible to be wrong. A marketer voice that cannot be wrong has stopped saying anything.

It addresses someone outside the organization, which is the constraint that shapes everything else. The executive announces a decision to people who must act on it. The product thinker aligns colleagues on which problem is worth solving. The marketer has no authority over the reader at all, and so everything it gets, it gets by being useful or interesting first.

Language patterns

Opens on the reader’s problem, in the reader’s vocabulary, before naming the product
Concrete and falsifiable claims: “eleven minutes” rather than “dramatically faster”
Second person throughout; the subject of most sentences is “you”, not “we”
Benefit stated before mechanism, with the mechanism kept only where it is the proof
Short sentences and short paragraphs, built for a reader who is scanning
Names the specific alternative the reader is living with today, not a strawman
One call to action, stated plainly, rather than several competing invitations

When to use

Use for landing pages and hero copy, product launches written for customers rather than for the team, ad copy under real character limits, and outbound email to someone with no prior relationship to the writer. Reach for this voice whenever the reader is deciding whether to buy, sign up, or try something.

When not to use

Avoid for internal decision records, where persuasion is the wrong job entirely; for technical documentation, where the reader has already bought and now needs to succeed; for anything addressed to people the writer has authority over; and for bad news, incidents, or apologies, where selling reads as evasion. Avoid it also for regulated claims about health, finance, or safety, which must be hedged to remain accurate.

Pairs well with

confident, problem-solution, landing-page

Often confused with

executive: Both are brief, both lead with a claim, and both are comfortable being unhedged. The difference is standing. The executive is announcing a decision to people inside the organization who will act on it, and can assume the reader’s attention as a matter of role. The marketer is addressing someone outside it who owes them nothing and may leave at any sentence. That is why the executive’s subject is usually “we” and the marketer’s is usually “you”.

product-thinker: Both start from a problem rather than a solution, which is what makes them confusable. The product thinker is establishing agreement among colleagues about which problem is worth solving, and the audience is internal and collaborative. The marketer is establishing that a specific reader has the problem already and can stop having it, and the audience is external and deciding. One is aligning a team; the other is converting a stranger.

columnist: Both write to persuade a reader who has not agreed yet, and both use a confident first-person claim. The columnist argues a position they personally hold and stands behind it as their own view; the piece succeeds if the reader thinks differently afterward. The marketer advocates for a product rather than a personal position, and the piece succeeds if the reader acts. A column that ends in a purchase has changed genre.

Tells

Opens on the reader’s problem in the reader’s words, before the product is named
Claims are specific enough to be checked: a number, a duration, a named alternative
Second person dominates; “you” is the subject far more often than “we”
Benefit leads and mechanism follows, appearing only where it serves as proof
Sentences and paragraphs run short, built for scanning rather than reading
Ends on exactly one action, stated plainly
Names the status quo the reader lives with today rather than a strawman

Anti-patterns

Superlatives with nothing behind them: revolutionary, seamless, best-in-class - The voice earns attention with specificity; an unfalsifiable claim gives the reader nothing to evaluate and signals that no real number was available.
Leading with the product and its feature list before the reader’s problem - A reader who has not yet agreed they have the problem has no reason to care what solves it, so a feature-first opening argues to someone who has already left.
Stacking three calls to action so the reader can pick one - Every added choice lowers the chance of any being taken; the voice exists to make one next step obvious, and offering several returns the decision to the reader unmade.

Failure modes

Enthusiasm outruns the evidence until every sentence is a superlative and none is checkable - Hold each claim to a number, a duration, or a named comparison; if none exists, the honest move is a smaller claim rather than a louder one.
Compression goes so far that a real limitation is not merely unstated but actively obscured - Brevity may leave things out; it may not imply the opposite of what is true. If a caveat changes whether the reader should buy, it belongs on the page.
The reader’s problem is described so aggressively that the writing manufactures anxiety rather than naming a real friction - Describe the problem at the intensity the reader would use themselves; if they would not call it painful, the copy should not either.

Instruction

Write in a marketer voice. You are speaking for a product to someone who is deciding
whether it is worth their time, and who owes you nothing. Open on the reader's problem, in
the words they would use for it, before you name the product. Address them as "you". Make
every claim specific enough to be checked - a number, a duration, a named alternative -
and if you cannot be specific, make a smaller claim rather than a louder one. Never use
superlatives you cannot substantiate. Lead with the benefit and give the mechanism only
where it is the proof. Keep sentences and paragraphs short, because this reader is
scanning. End on exactly one action.

Marketer

Marketer

Language patterns

When to use

When not to use

Pairs well with

Often confused with

Tells

Anti-patterns

Failure modes

Instruction

Related

Pairs well with

Avoid with

Often confused with