Writing guide
How to write a newsletter
A newsletter has one job: earn a standing appointment in someone’s inbox. Not a viral issue, not a click — the habit. A subscriber who opens forty issues a year gives you forty chances to be useful before they ever buy, and the inbox is the only channel where you own delivery: no algorithm sits between you and the reader who asked to hear from you. That ownership is the entire strategic case for the format.
Most company newsletters squander it by being announcement digests nobody requested: five links, three product updates and a webinar invite, sent “when there’s news”. Ask a subscriber what such a newsletter is for and they cannot answer — which is why they stop opening long before they unsubscribe. The other killer is silence: the send schedule collapses around issue six, when whoever writes it gets busy, and the half-built habit dissolves.
The craft is mostly discipline: one promise, a cadence you can hold for a year, one idea per issue, one ask, and formatting built for a thirty-second scan on a phone. This guide walks through each.
What it is
A newsletter is a recurring email sent on a fixed schedule to people who asked for it, delivering one useful idea per issue under a consistent promise. It is a product with a retention curve — not a distribution channel for whatever the company did this month.
When to use it
Start a newsletter when you can name the reader, the promise and the day — “ops managers, one hiring tactic that worked, every Thursday” — and can hold that schedule for a year on honest effort. Do not start one to “stay top of mind” with no promise attached, do not relabel the product-updates email as a newsletter, and do not choose weekly when the calendar says monthly: a cadence you abandon costs more trust than the slower one you keep.
The structure that works
The subject line and preview text
The open decision happens in the inbox, on about two lines of text. Nothing inside the email matters until those two lines work.
- Hold subjects to 30-45 characters and make them specific: “The 9-minute quote” beats “News from Fieldbase”.
- Write the preview text deliberately — it is your second line, not a home for “View in browser”.
- Never repeat the subject in the preview; extend the pitch instead.
The one-idea lead
The first two sentences after the greeting decide read versus archive. An issue about everything is an issue about nothing.
- Open with the idea’s sharpest claim or number, not “hope you’re well”.
- One issue, one idea — surplus material becomes next week’s issue or three short links at the end.
- If you cannot state this issue’s idea in one sentence, it is not ready to send.
A body built for the 30-second scan
Most subscribers scan on a phone between other tasks. The scan itself has to deliver the value, with deep reading as a bonus.
- Keep paragraphs to one-to-three sentences with whitespace between blocks.
- Bold the three or four lines that carry the argument, so the bold alone reads as a summary.
- Repeat the same section pattern every issue — familiarity is a feature; readers learn where to look.
The single CTA
Every additional ask splits attention and trains readers that the email is a menu. One ask concentrates the whole issue’s goodwill on one action.
- One CTA per issue, placed after the idea has paid off.
- Rotate ask types across issues — read, reply, try, share — instead of stacking them in one.
- Make replying itself a periodic CTA; replies improve deliverability and hand you future issues.
The footer and the P.S.
The P.S. is the most-read line after the subject, and the footer quietly does the trust work.
- Use the P.S. for one light ask or a teaser for next issue — not a second CTA stack.
- Keep unsubscribe visible; hiding it converts mild annoyance into spam reports.
- Sign with a person’s name when a person actually writes it.
Step by step
- 01
Write the promise in one sentence
Who plus what plus when: “Every Tuesday, one pricing teardown you can read in five minutes.” That sentence becomes your signup page, your welcome email and your editorial filter — anything that does not fit the promise does not ship, however good it is. A newsletter without this sentence is a mailing list waiting to churn.
Test the promise against the inbox it enters, not against your content plan. Your reader already receives dozens of newsletters; “marketing tips and news” loses to “one teardown, every Tuesday, five minutes” because the second names a job and a cost. Specific promises recruit slower and retain far better — which is the trade a newsletter exists to make.
- 02
Pick the cadence you can hold for a year
The asset you are building is a habit, and habits are predictability multiplied by time. Fifty issues a year is fifty touches with a reader who chose you — no other channel compounds like that. But the compounding runs on the schedule: every missed week teaches subscribers that the schedule is optional, and they learn that faster than they learned to open.
Do the honest math before announcing anything: hours per issue — research, writing, editing, most people underestimate by half — times 52. If the total makes you wince, choose biweekly. A biweekly newsletter held for a year beats a weekly one abandoned in March, and the graveyard of issue-six newsletters exists because founders picked the ambitious number over the true one.
- 03
Build a repeatable issue template
Fix the skeleton once: the lead idea in 150 to 250 words, one worked example or how-to block, three curated links with one-line takes, a P.S. Writing into a fixed template cuts production from about four hours to about ninety minutes, because the structural decisions — what goes where, how long — were made once instead of weekly.
The template is also your bad-week insurance: when time runs short you shrink the sections, never the schedule. A 200-word issue that arrives on Tuesday preserves the habit; a beautiful issue that arrives on Saturday erodes it. Readers subscribe to the appointment as much as to the content.
- 04
Open with the idea, not with warm-up
Delete the weather report. “Hope your week is going well” plus a paragraph of wind-up spends the most valuable screen in email on nothing. Subscribers granted you the inbox at signup; re-introducing yourself every issue spends that permission instead of using it. Start at the sharpest sentence you have — the claim, the number, the mistake.
Micro-technique: draft the issue freely, then find your best sentence — it is usually hiding in the third paragraph — move it to position one, and rewrite the lead around it. Then run the one-idea check: if you cannot state this issue’s idea in a single sentence, you have two issues, and one of them just wrote next week for you.
- 05
Write the subject and preview as a pair
Draft 5 to 10 subject lines after the issue is finished, and keep the one that names the specific payoff in 30 to 45 characters. Nouns and numbers beat adjectives: “The 9-minute quote” beats “Big news inside”. Curiosity is legitimate only when the first screen of the issue pays it off — unpaid curiosity buys one open today and archives forever after.
Treat preview text as the subject’s second line: roughly 40 to 90 visible characters that extend the pitch rather than repeat it. Subject “The 9-minute quote” plus preview “how a five-person ops team cut quoting from 40 minutes” reads as a two-line ad for the issue. Leaving it to default — “View this email in your browser” — wastes a third of the inbox impression.
- 06
Format for a phone screen
Assume a phone and a thumb: single column, paragraphs of one to three sentences, bold on the three or four load-bearing lines, whitespace between blocks. Then run the scan test on your own phone — read only the bold. If the bold lines alone deliver the idea, the thirty-second reader, which is most of your list, got value and will open next week.
Watch the mechanics that silently break issues: keep total email weight under Gmail’s roughly 102KB clipping threshold — heavy images and pasted formatting are the usual culprits — and send yourself a test on mobile before every issue. A clipped issue hides your CTA and your unsubscribe link, the two links that must always work.
- 07
Measure the habit, then prune the list
Judge the newsletter across a quarter, not per send: the open-rate trend (opt-in lists commonly sit around 35 to 50 percent, but direction matters more than level, and privacy proxies inflate the raw number), replies per issue, unsubscribes per issue, and clicks on the single CTA. A drifting open trend usually means promise drift — reread issue one and compare it to the latest.
Prune quarterly: subscribers with no opens in 90 days get one win-back email, then removal. This feels like shrinking and is actually maintenance — mailbox providers score engagement, and a large dead segment drags the whole send toward the spam folder. A 2,000-reader list that opens beats a 10,000-name list that does not.
Before and after: what good looks like
Before
Hi everyone, hope you’re having a great month. It’s been a busy few weeks here at Fieldbase and we have lots of exciting updates to share. We shipped several new features, including improvements to our dashboard and reporting tools. We also attended the LogiCon conference, which was a great experience for the whole team. Further down you’ll find some articles we enjoyed this month, plus details of our upcoming webinar. As always, thanks for reading and don’t hesitate to reach out with any questions.
After
Most freight quotes die in the first hour — and most teams take four to respond. This week’s idea: the one-hour quote window, and how a five-person team at Harlan Freight hit it without hiring. Their trick was not speed; it was triage. Every inbound request gets a 90-second yes, no or refer decision before anyone builds a quote, which cut their real workload 30% and doubled their win rate on the quotes they did send. Below: the three triage questions they use, and where the rule breaks down. One link at the end if you want to go deeper. — Dana
The before is a company diary: 84 words in, the reader has been offered nothing — the updates, the conference recap and the webinar all serve the sender. The after opens with a claim and a number, names the issue’s single idea in sentence two, pays it off with a specific team’s result, and commits to one link. It even promises the failure case (“where the rule breaks down”), which is the difference between an editor and a promoter. A subscriber scanning for five seconds knows exactly what this issue is for.
Mistakes that sink a newsletter
| Mistake | The fix |
|---|---|
| The digest with no idea — five links, three updates, a webinar | One idea per issue, stated in the first two sentences. Surplus material becomes future issues or three short links at the end. |
| Sending “when there’s news” | Fix a day and time and hold them. The schedule is the product — readers build habits around Tuesday, not around your release calendar. |
| Subject lines that label instead of sell — “Fieldbase Newsletter #14” | Name the issue’s payoff in 30-45 characters. The issue number means something to you and nothing to the reader. |
| Three CTAs competing in one issue | One ask per issue, rotated across weeks. When everything is clickable, the reliable choice is archive. |
| Writing to “our audience” | Write to one named reader — a real person who fits the promise. Broadcast tone is why company newsletters all sound alike. |
| Never scrubbing the list | After 90 days of non-opens and one win-back email, remove them. Engagement drives inbox placement; dead weight sinks deliverability for the readers who want you. |
Pre-publish checklist
- The promise — who, what, when — is one sentence, and this issue keeps it.
- The subject line is 30-45 characters and names a specific payoff.
- The preview text extends the subject instead of repeating it.
- The one idea is stated within the first two sentences — no warm-up greeting paragraph.
- Reading only the bold lines on a phone delivers the idea.
- No paragraph runs past three sentences.
- Exactly one CTA, placed after the idea pays off.
- The P.S. carries one light ask or teaser, not a second CTA.
- The send lands on the fixed day and time.
- Every link was click-tested and the email renders unclipped in Gmail.
- A real person signs the issue, and replies go to an inbox someone reads.
Free tools for this work
Check your newsletter before it ships.
Frequently asked questions
- How often should I send a newsletter?
- Weekly if you can hold it for a year; biweekly if the honest hours say so. Monthly is the floor — below that the habit never forms and every send performs like a cold email. The decisive number is hours per issue times 52 measured against your real calendar, not your ambition. Change cadence by announcing it, never by silently missing.
- How long should a newsletter be?
- 300 to 800 words — a two-to-four-minute read. Long enough for one idea with proof, short enough to finish between meetings. If you are consistently over 1,000 words, you are writing essays into email; publish the essay on your site and let the newsletter carry its sharpest 300 words plus the link.
- What’s a good open rate for a newsletter?
- For an opt-in list, 35 to 50 percent is healthy; under 25 percent signals promise drift, deliverability trouble or a stale list. Watch the trend across 8 to 10 issues rather than any single send, and remember privacy proxies inflate raw opens — treat the number as an index. Five real replies tell you more than two points of open rate.
- How do I get my first 1,000 subscribers?
- Put the promise — not the words “subscribe to our newsletter” — on your highest-traffic pages, in your email signature, and on your social profiles, and invite existing customers directly; they are the warmest list you have. Expect slow math: 1,000 typically takes 6 to 12 months of consistent issues. The only reliable accelerant is an issue good enough that readers forward it.
Free download
The Pre-Publish Checklist
This guide covers one format. The checklist covers every article. 47 checks WriteZu runs before an article ships — as a checklist you can run by hand.
No spam. The checklist, then only what's worth knowing.
Or let WriteZu handle the writing for you
It follows this exact structure — researched, drafted, scored against quality gates, and published to your CMS — while you approve from your inbox.
Start free