Newsletter

newsletter

Run the newsletter as a product you ship on a cadence, not a one-off send. The job is the system around the recurring issue: the subject + preview that earns the open, the issue body that earns the click, the welcome sequence that activates a new subscriber, the cadence and segmentation that keep the list healthy, the growth loops that compound it, and a scorecard that still tells the truth after Apple broke open rates. Every send is one episode of an ongoing show — design the show, not the episode.

When NOT to use — route instead

You own the recurring opted-in publication and its open/click/growth system. The plumbing under every send and the page that captures the signup are someone else's.

The metric truth after Apple MPP

Apple Mail Privacy Protection pre-fetches the tracking pixel, firing an "open" even when nobody read the email. It accounts for ~49% of all tracked opens and inflates reported open rate by ~15–35% on iOS-heavy lists — one beehiiv newsletter jumped from a 28% to a 55% open rate with zero behavior change. So stop steering on open rate. MPP does not touch link tracking, which is why the click is now the honest signal.

Rule: make click rate and non-Apple CTOR the north star, because the click is the one event MPP cannot fake. Leading 2025 programs removed open rate from decision-making entirely and anchor on clicks.

Calibration benchmarks (2025, cross-industry): average open rate ~42–43% (MPP-inflated, treat as noise), average click rate ~2.1% (range 0.83%–4.90%), click-to-open ~6.8%, conversion ~0.08% (top decile ~0.44%). Use the click figures to calibrate; ignore the open figure as a target.

The scorecard — track these, in this order:

Issue anatomy — one job per issue

Each issue gets exactly one job and exactly one primary CTA. A second CTA halves the first. Put the hook on the first screen (subject's promise paid off before any scroll), keep the body scannable (short paragraphs, one idea per block, links that read as links), and end at a single button-grade action.

Bad (rambling, no single job, CTA buried):
  Hey everyone! Lots going on this week — we shipped some updates, there's a
  webinar coming, I read a great book, and oh also our pricing changed, plus
  here are five links I liked. Anyway, check it all out when you get a chance!

Good (one promise, one payoff, one CTA):
  This week: the 3-line config change that cut our cold-start by 40%.
  • What it was   • Why the default is wrong   • The exact diff
  → Read the 4-minute breakdown   [single primary link]

Everything secondary becomes a one-line P.S. or a small "also" block, never a competing button.

Subject + preview as a pair

The subject and the preview (preheader) ship together and are tested together — they share the inbox row.

• Payload in the first ~33 characters; keep the whole subject ~30–50 chars (≈7–9 words) so it survives mobile truncation.
• The preview extends the subject, it never repeats it. Its first ~35–50 chars are prime real estate; waste them on a duplicate and you've burned the line.
• ≤2 emojis, at the end, never an all-emoji subject — an all-emoji subject is the one case that actually trips filters.
• The "spam trigger words" list is a myth. "Free", "guarantee", a normal emoji — these do not sink you; authentication and sender reputation dominate deliverability. Police reputation, not vocabulary; the reputation/auth layer lives in ../email-deliverability/SKILL.md.

Bad (payload past char 33, preview repeats subject):
  Subject:  We are very excited to finally share our big new feature today!!!
  Preview:  We are very excited to share our big new feature

Good (payload first, preview extends):
  Subject:  Cut cold-start 40% with 3 lines
  Preview:  The default config is wrong — here's the exact diff and why

Cadence & segmentation

Cadence is not one number for the whole list — it branches on how engaged the reader is. This is the decision table:

Sunset dormant addresses on purpose — complaint rate, not list size, gates the inbox. Mailing a decaying list harder is how a sender torches its reputation.

Send-time default: Tuesday/Thursday mid-morning (~10am) or early afternoon (1–3pm) is the cross-industry baseline — but treat it as a hypothesis to test against your own list's click data, not a law. Segmented sends earn roughly 100% higher click rates than blast-to-everyone, so segment before you optimize send time. Tier definitions and the full sunset/re-permission flow live in references/growth-loops.md.

The welcome sequence

A confirmed subscriber gets a 3–5 email sequence, not silence until the next issue — this window is the highest engagement they'll ever have. One job per email:

1. Deliver the promise (immediate) — the thing they signed up for, instantly. Sets the expectation that you ship value.
2. Set expectations + best-of (day 1–2) — what arrives, how often, plus your best past issue so they see the ceiling.
3. The referral ask (day 4–5) — once they've gotten value, ask them to share (the theSkimm pattern: referral ask inside the welcome, not bolted on later). 4–5. Optional: segmentation/preference capture and a feedback prompt.

Full skeleton with timing, subject+preview per email, and the one-job rule: references/welcome-sequence.md.