How to Write a Newsletter Promise in One Sentence
How to write a newsletter promise: one specific sentence saying what arrives, how often and why it is worth opening, written before the first issue is drafted.
To write a newsletter promise, finish one sentence that says what arrives, how often it arrives and why it is worth opening, and make it specific enough to be slightly uncomfortable. The promise is what someone gets in exchange for their address and their attention.
It is the most underrated piece of a newsletter, because it does three jobs at once. It does the work of the signup form, the welcome email and the subject line before you have written any of them. And it is the standard you will be held to, because permission is granted for a specific promise and withdrawn the moment you break it.
How to write a newsletter promise that a reader can picture
Start with the reader, not with yourself. A promise written for "founders," "marketers" or "people interested in growth" describes a category, and a newsletter written for a category feels written for nobody. Narrow the reader until a specific person appears. The guide gives three examples of the level of detail to aim for: the operations lead at a twenty person agency who has just been told to sort out reporting; the solo consultant who has more referrals than capacity and no idea how to price; and a third reader, the second time founder, described in the same specific way.
Narrowing feels like shrinking your market. In practice it is the only way a small list grows by recommendation, because the right person forwards an issue to someone exactly like them. If you do not yet know how narrow to go, the sibling post on what a founder newsletter is sets out the five facts to settle first, and the reader is the first of them.
The three questions a good promise answers
A promise is a single sentence, but it has to carry three separate answers. If one is missing, the sentence is a slogan.
| Question | What it covers | What goes wrong without it |
|---|---|---|
| What arrives? | The specific content, named plainly | The reader cannot tell what they are agreeing to |
| How often? | The cadence, stated as a day or a rhythm | Nothing tells the reader when to expect you, so no habit forms |
| Why open it? | The benefit to this particular reader | The issue competes with everything else in the inbox and loses |
The guide offers one model sentence: every other Tuesday, one pricing decision a services business got wrong, and what it should have done instead. Notice what it contains. The rhythm is fixed. The content is one thing, not a mix. The value is stated: you will see the mistake and the better decision. It is specific enough that some people will decide it is not for them, which is exactly what you want.
The finishing test
If you are stuck, use this test from the playbook: after reading this for six months, my reader will be able to do something specific. Fill in the blank with a skill, a decision or a capability. If you cannot complete it, you do not have a newsletter. You have an intention to send emails.
The test works because it forces you to think about the reader's outcome rather than your topic. A topic is a subject area. An outcome is a change in what a person can do. Readers sign up for outcomes, even when they do not say so.
Weak promises and stronger ones
Most weak promises fail in one of three ways: they name no reader, they name no rhythm, or they name no benefit. The comparison below shows the pattern, using only wording in the style of the guide's own model.
| Weak version | What is missing | Stronger shape |
|---|---|---|
| A newsletter about what we are up to | No benefit for the reader at all | A named kind of reader and one useful thing per issue |
| Thoughts on business, whenever I write | No rhythm, no specific content | A fixed day and one clearly named subject |
| Updates for founders | A category rather than a person | One role, in one situation, trying to do one thing |
The first row is the pattern the playbook calls out directly: a newsletter about what we are up to gives no reader a reason to open it. If you cannot state the promise in one sentence, readers cannot either.
Where the promise gets used
Once written, the promise is not a private note. It appears in several places, and they should all say the same thing.
- The signup form. It should state the specific promise rather than "subscribe to our newsletter," which describes an obligation instead of a value. See how to grow a newsletter list from your own site for where those forms belong.
- The welcome email. It restates the promise so the reader knows what to expect and when.
- The subject lines. Each one should name the specific thing inside, which is the promise delivered one issue at a time.
- Your own editing. Before every send, the question is whether the issue keeps the promise and whether anything in it exists only to serve you.
That last use is the quiet one. A promise is a discipline as much as a description. When a launch or an announcement tempts you to bend an issue, the promise is what tells you to put the announcement in as the one ask rather than letting it replace the content.
Promises that you cannot keep
A promise is only valuable if you can keep it in your worst month. The commonest way to break one is to make the rhythm too ambitious. A founder announces a weekly newsletter, meets a launch or a hiring crunch in month two, skips an issue and never recovers. The fix is to choose the slowest rhythm you can defend before you write the sentence, not after. The reasoning is laid out in how to set a newsletter cadence.
The other way to break a promise is to drift in content. If the sentence says one pricing decision per issue and you send a roundup of links, the reader notices. They may not unsubscribe, but they stop opening, and permission is withdrawn quietly.
Say who it is not for
A narrow promise has an edge, and the edge has a flip side. The pre-launch checklist in the guide asks you to know who the newsletter is not for. That is not unfriendliness. It is what lets the right reader recognise themselves quickly, and it protects you from writing a diluted issue that tries to please everyone.
A practical way to do it: write the promise, then write a second sentence beginning "This is not for" followed by the reader who would be disappointed. If that second sentence is hard to write, the first is probably still too broad.
A short routine for writing yours
- Name the reader as a role in a situation trying to do one thing.
- Choose the format and the rhythm you can hold in your worst month.
- Write the sentence with what arrives, how often and why it is worth opening.
- Run the six month test and rewrite until the blank is filled with something concrete.
- Write the "not for" sentence and check the promise against it.
- Read it aloud to someone in the target audience, if you can, and see whether they can say back what they would get.
The format step matters because the promise names a shape. An essay, a teardown and a set of field notes make different promises, and how to choose a newsletter format covers that choice.
Taking the model sentence apart
It helps to see how the guide's own example is built, because the structure can be copied even when the subject is different. The sentence is: every other Tuesday, one pricing decision a services business got wrong, and what it should have done instead.
| Piece of the sentence | The part it plays |
|---|---|
| Every other Tuesday | The rhythm, stated as a day the reader can expect |
| One pricing decision | A single named subject, not a mix |
| A services business got wrong | A recognisable situation, and a reason to feel it is meant for them |
| What it should have done instead | The payoff: a better decision the reader can use |
Copy the shape, not the words. Your rhythm, your subject and your payoff will differ, but each of the four pieces needs an answer. If one is hard to write, that is the gap in your thinking, and it is far cheaper to find it now than after twenty issues.
Why a narrow promise travels further
A precise promise does something a broad one cannot: it gives a reader a sentence to pass on. When someone forwards an issue to a colleague, they are in effect repeating your promise in their own words. If the promise is a category, there is nothing to repeat. If it names a particular kind of person with a particular problem, the right recipient recognises themselves immediately.
This is the practical meaning of the playbook's claim that narrowing is the only way a small list grows by recommendation. The promise is the unit of recommendation. A founder who spends an hour on one sentence is spending it on the thing most likely to be repeated.
Frequently asked questions
Can the promise change later?
It can, but treat a change as a new agreement. People joined for the old sentence. If you narrow or shift it, say so plainly to existing readers rather than letting the content drift.
Should the promise mention the business next step?
Not necessarily. The promise is about what the reader gets. The business step, such as a reply that becomes a call, is what you decide privately and then deliver through one call to action per issue.
Is one sentence really enough?
Yes, and the limit is the useful part. If it takes a paragraph to explain, readers will not be able to repeat it, and a promise nobody can repeat does not help anyone decide to join.
What if my audience is genuinely broad?
Pick the narrowest slice you are able to serve well and start there. A small list that feels personal grows by recommendation, which a broad one rarely does.
The full method, with the checklists, is in The Founder's Newsletter Playbook, a free 32-page playbook.