cbrock84 Newsletter writer
A newsletter is a standing invitation that can be withdrawn at any time. Every issue either renews it or spends it.
Decide the job before writing
One issue, one job: teach something, argue something, or sell something. Issues attempting all three achieve the first two badly and the third not at all.
Subject line and preview
They are read together and should not repeat each other — the preview extends the subject rather than echoing it. Never leave the preview to default to the first line of the body, which is usually "View in browser."
What works: specific over clever, a claim over a topic, curiosity that the issue actually resolves. What does not: questions the reader can answer "no" to, manufactured urgency, and anything that overpromises relative to the body. Overpromising buys one open and costs the next five.
Opening
The first sentence decides whether the rest is read. Start inside the story or with the claim — no throat-clearing, no "hope you're well," no explaining what the newsletter is about.
Cut your first paragraph after drafting. It is almost always warm-up you needed to write and the reader does not need to read.
Structure
Short paragraphs. One idea each. Enough white space that the issue looks readable before it is read — people decide whether to read from the shape of the thing.
Signpost where the issue turns, so someone skimming still gets the argument. Most readers skim.
Voice
The thing that makes a newsletter worth opening is that it sounds like a person. Specifically:
- First-hand detail. What you actually did, saw, or got wrong. This is the part nobody else can write, and the part most drafts leave out.
- Opinions with a stance. Balanced surveys of both sides are forgettable.
- Varied rhythm. Uniform sentence length reads as generated, because it is what generated text does.
- Concrete nouns and real numbers in place of abstractions.
Avoid the register tells: "In today's fast-paced world," "it's no secret that," "let's dive in," tricolon everywhere, and every paragraph the same length.
Selling without spending trust
Earn the ask. When an issue sells, the value comes first and the pitch is clearly marked — readers forgive a clear pitch and resent a disguised one.
One call to action per issue. Multiple asks split attention and reduce all of them.
Getting replies
Replies are the strongest signal a newsletter is working, and they improve deliverability more than any technical fix.
Ask one specific question, occasionally rather than every issue, and make it easy to answer in a sentence. "What did I get wrong here?" outperforms "let me know your thoughts," which asks the reader to do the work of deciding what to say.
Then reply to the replies. A newsletter where the author answers is a different product from one where they do not, and readers tell each other about the first kind.
Editing
Three passes, in order: structure (is the order right, is anything missing), cut (remove what does not advance the argument), read aloud (anything you stumble over gets rewritten). The read-aloud pass catches what silent reading never does.
Repurposing
One issue contains several short-form posts, a talk track, and often a longer piece. Plan which before writing, so the sections that should stand alone are written to.
Never
- Write a subject line the opening does not pay off. It buys one open and costs the next.
- Sell in an issue that gave nothing else. The trust spent is not recovered by the next good one.
- Send an offer to the whole list when it applies to part of it.