How do you write a newsletter subject line that gets opened?
Clear beats clever. Specific beats both.
Why does one subject line get opened and the next one skipped?
A reader scans the inbox and makes a snap decision from three pieces of text: the sender name, the subject line, and the preview text next to it. The sender name earns trust over time. The subject line has to answer one question in a glance: is there something in here for me, today?
Most B2B newsletter subject lines fail that test because they describe the category of the email ("October update", "News from the team") instead of the one thing inside it. The fix is not more cleverness. It is naming the specific thing: the problem the lead article solves, the number it reports, or the situation the reader is in.
How long should a newsletter subject line be?
Short enough that the important words survive the cut. Inboxes truncate subject lines at different points depending on the app, the device and the window width, so there is no single character count where every inbox stops. Mailchimp's help page recommends no more than 9 words and 60 characters, and notes that shorter is often better on phones. Treat 60 as a working ceiling, not a target.
The practical rule is front-loading. Put the specific noun or number in the first four or five words, so that even a phone notification showing a fragment still carries the point. "Renewal stalls in month 10: the three causes" works when it is cut to "Renewal stalls in month 10". "Three causes of something we noticed about renewals" does not.
Should the subject line be clever or clear?
Clear. A pun or a teaser asks the reader to spend attention before they know what they get. For a newsletter they chose to receive, that is backwards: they already want the content, so tell them which content this is. Cleverness also ages badly. A line that reads well on Tuesday morning can read like a sales trick in a crowded Thursday inbox.
Specific beats both. "How procurement teams score vendors" is clear. "The 12-point scorecard one procurement team shared with us" is specific, and the specificity is what makes the reader believe there is something real inside. If you run the newsletter the way we describe in how to run a B2B newsletter, every issue has one lead idea, and the subject line is just that idea stated plainly.
What is the preheader, and what should go in it?
The preheader (also called preview text) is the short line most inboxes show next to or under the subject line. Mailchimp's documentation explains that if you leave it blank, the inbox pulls the first text it finds in the email, which is often a "View in browser" link or raw code. That is a wasted second line.
Write it as the second half of the subject line, not a repeat of it. Subject: "Why your best customers go quiet before they churn". Preheader: "Four signals in the product data, and what to send when you see them". Litmus recommends keeping preview text under 90 characters, and it reports that inboxes show anywhere from five lines of it down to none, so put the useful part first.
Which subject line habits look like spam?
Be careful with lists of "spam words" you see online. Mailbox providers do not publish a banned-word list, and most of those lists are guesses. What Google does publish, in its sender guidelines, is a requirement that the subject, headers and display name accurately represent the sender, and a specific example: do not start a subject with "Re:" or "Fwd:" unless the email really is a reply or a forward. The same guidelines ask bulk senders to keep their reported spam rate below 0.10% and never reach 0.30%, and to support one-click unsubscribe.
Read that together and the pattern is clear: spam placement is driven by how recipients react (complaints, ignores, unsubscribes), and misleading subject lines produce exactly those reactions. On formatting, Mailchimp's guidance is to use no more than 3 punctuation marks, because stacked marks and special characters make an email look like spam. All caps has no published rule behind it; it simply reads as shouting, and B2B readers do not open shouting.
Does personalisation in the subject line work?
A first name on its own is weak personalisation. Everyone has seen "Sara, this is for you" and learned it means nothing. Mailchimp's help page recommends merge tags for name or location and says personalisation tends to lift opens for most users; the part worth keeping is that the line should reflect something true about the reader.
Better personalisation uses what you actually know: role, industry, the lead magnet they downloaded, the stage they are at. "For ops leads: the vendor checklist we use" is personal without a name field. If your list is segmented by role or by what people signed up for, write one subject line per segment and let the content stay the same. That is more work than a merge tag and it is the work that shows.
Ten weak B2B subject lines, rewritten
These are illustrative examples we wrote for this guide, not lines from any client. Each weak line is a pattern we see often. Each rewrite applies one rule from the checklist below.
| Weak line | Rewrite | Why it is better |
|---|---|---|
| October newsletter | Why renewals stall in month 10, and the fix | Names the lead idea instead of the month. |
| Big news from us!!! | New: SSO is live. What changes for admins | One punctuation mark, and it says what the news is. |
| You won't BELIEVE this trick | The onboarding email that lowered our support load | No caps, no teaser. A concrete outcome and a named asset. |
| Quick question | A question about your Q4 renewal process | The vague version hides the topic. The specific version earns the open. |
| Re: your account | Your account review: three settings to check | A fake reply breaks Google's guidelines. The rewrite is honest and useful. |
| Tips for success | Three mistakes on B2B pricing pages, with fixes | A number, a place, and a promise of fixes. |
| Don't miss our webinar | Thursday webinar: how procurement teams evaluate vendors | The day and the topic, front-loaded. |
| {First name}, this is for you | For ops leads: the vendor checklist we use | Personal by role, not by a merge tag. |
| Our new feature is here | Export reports to Google Sheets in one click | Says what the feature does, which is the reason to open. |
| Issue #47 | Issue 47: why your best customers go quiet before they churn | Keeps the issue number for regulars and adds the hook. |
How do you test subject lines with a small list?
Know what a test can tell you first. Most email platforms test by sending each variant to a slice of the list, waiting, and sending the winner to the rest. Kit, for example, sends two subject lines to two 15% segments, runs the test for 30 to 240 minutes, and picks the winner by open rate alone. Mailchimp lets you test up to three variations and pick a winner by opens, clicks or revenue, and tells small audiences to send every combination to the whole list at once.
Two limits follow from that. First, sample size. Kit's own help page recommends at least 500 recipients for a two-way test and says smaller tests are not statistically significant. If your list is 2,000 people, a 15% slice is 300 per variant, and a difference of a few opens is noise. Second, the metric. Open tracking relies on an invisible image loading; Mailchimp documents that it fails when images are off, that Apple Mail Privacy Protection inflates opens, and that security filters click links before a human sees the email. A subject line test measured by opens is measuring a fuzzy number.
So with a small list, test slowly. Change one thing (for example, specific noun versus category) and hold it for four or five issues. Compare clicks and replies, not just opens, as described in newsletter metrics that matter. And compare against your own baseline, not a published average; the open rate benchmarks guide explains why those averages are unreliable for a single list. Over a few months, that record of what worked becomes more useful than any one test.
The subject line checklist
Run every subject line through these seven checks before sending. They are deliberately strict so they can be scored.
- Length. 60 characters or fewer, and the key noun or number in the first five words.
- Clarity. A reader who never opens the email can still say what it was about.
- Specificity. It names a thing: a problem, a number, a situation, a day. Not a category like "tips" or "update".
- No shouting. No all caps. No more than one exclamation mark, and no more than 3 punctuation marks in total.
- Honesty. No fake "Re:" or "Fwd:", no false urgency, nothing the body does not deliver.
- Preheader written. It adds the second half of the thought, under 90 characters, and is not left to default.
- Promise matches content. Open the draft and check the first paragraph pays off the line. If it does not, change the line, not the paragraph.
A good line is easier to write when the issue itself is clear. If you are sending on a schedule you can keep, which we cover in how often to send a B2B newsletter, each issue tends to have one lead idea, and the subject line writes itself from that idea. This is also how we approach newsletters inside Sawa's engage work: the line comes last, after the content earns it.
Where these rules come from
The length, punctuation and preheader figures come from vendor documentation. The honesty rules come from Google's sender guidelines. The rest is judgement from writing and reviewing B2B newsletters, and should be tested against your own list.
About this guide and its sources
This is Sawa's working checklist for B2B newsletter subject lines. The numeric limits (60 characters, 3 punctuation marks, 90 characters of preview text, 500 recipients for a test) are the vendors' own published recommendations, not measured results from Sawa clients. The before-and-after lines are illustrative examples written for this guide.
- Google: Email sender guidelines
Supports the honesty rule (subject must accurately represent the sender, no fake Re: or Fwd:), the 0.10% and 0.30% spam rate thresholds, and the one-click unsubscribe requirement.
- Mailchimp: Best practices for email subject lines
Supports the 9 words and 60 characters guidance, the limit of 3 punctuation marks, the note on emojis, and the merge tag personalisation point.
- Mailchimp: About preview text
Supports the description of preview text and what inboxes show when it is left blank.
- Litmus: The ultimate guide to preview text support
Supports the 90-character preview text recommendation and the range of preview lines different inboxes show. Litmus is an email testing vendor; this is its own guidance.
- Kit: How to A/B test subject lines
Supports the 15% test segments, the 30 to 240 minute test window, winner by open rate, and the 500 recipient minimum for a two-way test.
- Mailchimp: About A/B testing campaigns
Supports the three-variation limit, winner by opens, clicks or revenue, and the advice to small audiences to send all combinations at once.
- Mailchimp: Use open tracking in emails
Supports the explanation of how opens are tracked and why the number is inflated or missed (images off, Apple Mail Privacy Protection, bot clicks).
Frequently asked questions
Plan the issue the subject line has to describe
The newsletter issue template gives each issue one lead idea, which makes the subject line the easy part.
Need help with this? See how Sawa handles newsletters and content, or book an intro call.