How to Write a Newsletter Subject Line That Gets Opened
How to write a newsletter subject line: name the specific thing inside for the one reader who should open it, and avoid the habits of a promotion email.
To write a newsletter subject line, name the specific thing inside the issue so the right person knows in a second what they will get. Specific beats clever, and a line that looks like a promotion costs you trust and reach.
A subject line is the smallest piece of writing in a newsletter and the one that decides whether the rest is read. It has to work for a reader who is deciding in a second, usually on a phone, among many other messages. That reader is not browsing for entertainment. They are asking whether this is for them.
How to write a newsletter subject line that names the thing inside
The playbook gives the job of the subject line in one sentence: to tell the right person what they will get. Everything else follows from that. It is not there to tease, to provoke curiosity for its own sake or to trick anyone into opening. The aim is to be opened by exactly the people who should open it.
The guide contrasts two lines to show the difference. "How we priced our first retainer, and what we would change" will be opened by exactly the people who should open it. "Lessons learned" will be opened by nobody in particular. The first names a subject, a point of view and a payoff. The second names nothing.
| Quality | What the reader sees | Who opens it |
|---|---|---|
| Specific | A named subject and a clear payoff | The people the issue is meant for |
| Vague | A general label such as "lessons learned" | Nobody in particular |
| Teaser | A hint with the subject withheld | The curious, who may not be your reader |
Specific beats clever
Clever lines are tempting because they feel like writing. But a reader scanning an inbox does not give you time to decode a joke. If the line makes them work to find out what it is about, many will not bother. A specific line is a kind of respect: it tells people exactly what they would be spending their attention on and lets them decide.
This also protects the relationship over time. If your subject lines reliably describe what is inside, readers learn to trust them. A line that overpromises is opened once. A line that describes accurately is opened for years.
A simple way to find the specific thing is to write the one idea of the issue in plain words and then trim it. If you have followed the five part shape in how to structure a newsletter issue, the idea is already clear, and the subject line is its shortest honest description.
The habits that make an email look like a promotion
The playbook names the habits to avoid: capital letters, manufactured urgency and misleading prefixes. They have a double cost. With readers, they cost trust, because the reader recognises the pattern of a promotion and discounts it. With the systems that decide whether you reach the inbox at all, they cost reputation.
| Habit | Why it hurts | Do this instead |
|---|---|---|
| Capital letters for emphasis | Reads as shouting and as a promotion | Write in plain sentence case |
| Manufactured urgency | Costs trust when nothing is actually urgent | State the subject; urgency only if it is real |
| Misleading prefixes | Pretends to be a reply or a forward, and readers feel tricked | Say what the issue actually is |
The pre-send checklist makes the same point in one line: the subject line names the specific thing inside, with no manufactured urgency. Treat it as a standing rule, not a style preference.
Match the line to the promise
A subject line is the promise delivered one issue at a time. If your promise says one pricing decision per issue, each line should name the decision. This is why the promise comes first. A newsletter with a clear promise almost writes its own subject lines, because the structure of the content is fixed and only the subject changes.
If you find yourself reaching for a clever line because the content is vague, the problem is upstream. Go back to how to write a newsletter promise and check that every issue is meant to deliver one nameable thing.
Write the line last, then test it on the reader
Many founders write the subject first and then bend the issue to fit. It usually works better the other way round: finish the issue, then name what is in it. You will know by then what the one idea is, and the line becomes a matter of description rather than invention.
Then run three checks.
- Would the named reader of this newsletter know, from the line alone, whether it is for them?
- Does it describe what is actually inside, with nothing exaggerated?
- Does it avoid capitals, false urgency and borrowed prefixes?
If the answer to all three is yes, send it. If a line passes only by being vague, it has failed the first check.
What a subject line cannot do
A good line gets the right person to open. It cannot rescue an issue that does not keep the promise, and it cannot make a list want to hear from you. It is also not the place to measure your success. The opening rate depends on many things, and the number itself is unreliable, because modern mail clients and privacy features can register an open no human performed, or hide one that did.
That is why the playbook treats opens as hygiene and not as the result. A sudden drop in opens is an early warning worth a closer look, but the question that matters is whether readers reply. For what to track instead, see how to measure a newsletter by replies.
Keep the sender clear too
The subject line is read next to the sender name, and the two work together. A newsletter from a named founder reads as a letter; one from "The Team" or a no-reply address reads as marketing before anyone opens it. A specific line from a recognisable person is a much stronger combination than a clever line from an anonymous sender.
It is worth deciding who the newsletter is from before you write any lines, since the sender name becomes part of how the line is read. The same person should also be the one who reads the replies.
A quick routine for each issue
- Write the one idea of the issue in plain words.
- Trim it to the shortest line that still names the subject and the payoff.
- Remove capitals, urgency and prefixes.
- Check it against the promise and against the named reader.
- Send yourself a test and read the line on a phone.
The final step is easy to skip and worth keeping. A line that looks sensible on a desktop can read differently in a narrow preview, where only the first words show.
Putting the rules to work on a draft
Rules are easier to use when you can watch them change a line. The two lines from the guide make a good pair to practise with. "Lessons learned" says nothing about what is inside, so it will be opened by nobody in particular. "How we priced our first retainer, and what we would change" names a subject, a point of view and a payoff.
| Question to ask of a draft line | If the answer is no |
|---|---|
| Does it name the subject? | Add the noun the issue is about |
| Does it hint at the payoff? | Say what the reader will take away |
| Would only the right person open it? | Narrow it until it speaks to your named reader |
| Is anything shouted or rushed? | Remove the capitals and the false urgency |
Run a weak line through these four questions and it usually repairs itself in a minute. The result will not always be elegant, but it will be accurate, and accuracy is what keeps the right readers opening.
Why accuracy builds the list over time
Each subject line is a small promise about what is inside. When the issue delivers it, trust grows a little. When it does not, trust drops, and permission is withdrawn quietly: readers stop opening long before they unsubscribe. That is the real cost of a misleading line. It may win one open and lose the next ten.
An accurate line also helps the reader later. A person searching their inbox for the issue about pricing finds it, because the line said so. Specific lines age well, and clever ones do not.
Frequently asked questions
Should I use a question as a subject line?
Only if it names the specific thing inside. A question that hides the subject is a teaser. A question that makes clear what the issue answers can work, as long as it is honest.
Should subject lines be short?
Short enough to be read on a phone and long enough to name the subject. The guide sets no length; its rule is specificity.
Can I use the same format every issue?
You can, and a consistent shape helps readers recognise your issues. Keep the content of each line specific to that issue.
What if a vague line gets more opens?
Be careful with that signal. Opens are the least reliable number on the dashboard, and a line that wins opens by hiding the subject may lose the trust that produces replies.
The full method, with the checklists, is in The Founder's Newsletter Playbook, a free 32-page playbook.