Skip to content
Writing Style Library

Marketer

A voice that speaks for a product to someone deciding whether to buy, opening on their problem in their own words before naming what the product does.

Marketer

Section titled “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 is also comfortable being brief in a way most professional voices are not. This voice writes for a reader who is scanning, who decides in seconds whether to keep reading, and who owes the writer nothing. It cuts qualifiers that a careful internal document would keep, because a hedge in a headline reads as a lack of conviction rather than as intellectual honesty.

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

Section titled “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

Section titled “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

Section titled “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

Section titled “Pairs well with”

confident, problem-solution, landing-page

Often confused with

Section titled “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 state their claims without hedging. The columnist argues a position they personally hold, in the first person, 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, speaks to the reader as “you”, and the piece succeeds if the reader acts. A column that ends in a purchase has changed genre.

Tells

Section titled “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

Section titled “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

Section titled “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

Section titled “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.
Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Confident, Problem-Solution, Landing Page

Avoid with

Section titled “Avoid with”

Reverent, Researcher

Often confused with

Section titled “Often confused with”

Executive, Product Thinker, Columnist

Examples

Section titled “Examples”

You’ve sat through the 9am Pacific standup when it was 9:30 at night where you live, said your three sentences, and logged off wondering why that couldn’t have been a message. If you’re on the India side of this team, you already know the number: you made it to 3.2 of 5 standups last quarter, against 4.6 for engineers on Pacific or Eastern time. That’s not a discipline problem. That’s a meeting that only works for people who aren’t you.

Here’s the part that holds even if you’re on the convenient side of the clock: the standup runs 14 minutes and produces about 4 of signal - a blocker raised, a dependency flagged, something that changed what someone did next. The other 10 minutes is status nobody needed to hear live. And none of it sticks. One blocker that a previous standup had already resolved still cost the team 45 minutes before anyone realized it had been answered, because nothing from that call was searchable five minutes after it ended.

#team-standup replaces the call with one Slack post, due by 10am your local time: what shipped, what’s in progress, what’s blocked and who can unblock it. No call, no 9:30pm login, no waiting for your turn to talk. Post it, and it’s there - searchable, @mentionable, read by the on-call engineer between 10 and 11am Pacific and answered within 30 minutes if you’re blocked.

You get back roughly 70 minutes a week that used to go to standup. You don’t get all of it back for free: the daily call is replaced by one 60-minute Thursday working session, not five short ones, and you’ll see your team live less often than you do now. That’s a real trade, not a hidden one. What you get instead is a channel that doesn’t forget what you told it and doesn’t make you choose between sleep and attendance.

This is a 30-day trial, not a permanent switch. The team reviews attendance, blocker resolution time, and how it actually felt at day 30, and reverts if it doesn’t hold up.

Post your first update to #team-standup by 10am tomorrow, your time.