How to Write a Newsletter Call to Action: One Ask Only
How to write a newsletter call to action: pick the single next step that matters most, ask for it once and plainly after the value, and rotate its type.
To write a newsletter call to action, choose the single next step that matters most in this issue and ask for it once, plainly, after the value has been delivered. An issue that asks for five things gets none of them.
The call to action is where a newsletter stops being content and starts being business. It is also where founders most often go wrong, in one of two directions: they never ask for anything, so the list produces no conversations, or they ask for everything, so the issue reads as a sales page. The playbook's answer is neither silence nor a menu. It is one ask per issue.
How to write a newsletter call to action with only one ask
A single clear ask outperforms a list of options because it removes the decision. A reader presented with four possible next steps has to choose, and the easiest choice is to do nothing. A reader presented with one has only to say yes or no.
The rule has two halves. First, pick the single next step that matters most this issue. Second, ask for it clearly, once, after the value. Both halves need discipline. The first means leaving good options out of the issue. The second means resisting the urge to repeat the ask three times at different points in case you were missed.
It does not have to be a sale
This is the point that frees most founders. The call to action is the next step, and the next step can be small. The playbook lists several kinds, and they sit on a scale of commitment.
| Kind of ask | What the reader does | When it fits |
|---|---|---|
| Reply | Tell you how they handle the problem | When you want conversations and research |
| Read | Open a case study | When the reader needs proof before talking |
| Book | Book a call if this is their problem right now | When the issue touches an urgent need |
| Join | Join a workshop | When you have an event or a group to offer |
Rotate the type over time so the newsletter does not become a sales sequence. A newsletter that asks for a purchase every issue teaches readers to expect a pitch. One that mixes replies, reading and occasional offers keeps the tone of a letter from a person.
Place it after the value
Position matters. The ask comes after the reader has received the one idea of the issue. This is the order in the five part shape described in how to structure a newsletter issue: subject line, opening, one idea, one call to action, then the sign-off with a question.
An ask placed first spends permission before earning anything. An ask placed after the value feels like a natural continuation. The reader has just been helped, and you are offering a way to go further.
The ask and the closing question are different things
It helps to separate two lines that are easy to confuse. The call to action is the one step you want an interested reader to take. The sign-off is a direct, easy question that invites a reply. They can be the same when the ask is "reply and tell me", but they do different jobs.
| Element | Purpose | Rule |
|---|---|---|
| Call to action | Move interested readers to the next step | Exactly one, after the value |
| Closing question | Invite a private reply | Direct and easy to answer |
If your call to action is a booking and your closing question invites a reply, a reader who is not ready to book still has a low pressure way to respond. That is deliberate: the question catches the people the ask is too big for. How those replies become a measurable result is in how to measure a newsletter by replies.
Connect the ask to the business next step
Before the first issue, the playbook asks you to name the business next step the newsletter is meant to produce: a reply that becomes a call, a booked diagnostic, a trial, a purchase of a specific offer or an introduction. Not awareness. That named step is the source of your calls to action.
It gives you a test. Is this issue's ask a move towards the named step, or a detour? A call to action that has no connection to the business step may be pleasant, but it will not produce what the newsletter is for. Over a run of issues, the asks should add up to a path, with some small and some larger steps, all pointing to the same destination.
Product news and offers: one ask, inside the promise
Announcements are the commonest cause of a crowded call to action. The playbook's rule is that product news and offers can appear as the one call to action inside an issue that still keeps the promise. They cannot replace it.
In practice, that means the issue is still built on its one idea, and the offer is the ask at the end. If the issue exists mainly to serve you, it spends permission you will have to earn back. A useful check from the pre-send list: nothing in the issue exists only to serve me.
Make it real before you send
The pre-send checklist contains a line that is easy to underrate: every link works, and the call to action goes somewhere real that I have tested. A broken link on the one ask of an issue wastes the whole send. Click through as a reader would, on a phone, and make sure that the destination matches what the ask promised.
It also helps to know where the click lands. If the call to action leads to a page with several competing offers, you have reintroduced the choice you removed in the email. Keep the destination as focused as the ask.
What to do when someone says yes
The call to action is only half the loop. When a reader responds, answer personally and promptly. Many replies are thanks; some are questions; a few describe a problem from someone who is, without saying so, looking for help. Those are the conversations the newsletter exists to produce.
Respond to the substance, ask a follow-up question and, when it is genuinely appropriate, suggest a call as a natural continuation rather than a handoff to a sales process. Then record the conversation where your pipeline lives, with the newsletter noted as where it started. Without that record, the value of the ask is invisible.
A checklist for the ask
- I have chosen one next step for this issue and left the others out.
- It is placed after the value, not before.
- It is stated plainly, with no list of alternatives.
- It differs in type from the last few issues, so the newsletter does not read as a sales sequence.
- It moves the reader towards the business step I named before launch.
- The destination works, and I have tested it on a phone.
- The issue still ends with a direct, easy question.
An ask that fails this list is usually one that tries to do too much. The first fix is to cut. For other patterns that turn a newsletter into an obligation, see newsletter mistakes founders make.
Choosing which ask to make this issue
With four kinds of ask available, the question each time is which one the issue has earned. A simple way to decide is to look at what the one idea of the issue has just done for the reader.
| If the issue has just | The natural ask is |
|---|---|
| Raised a question the reader will have views on | Reply and say how they handle it |
| Made a claim that needs evidence | Read the case study |
| Described a problem that is urgent for some readers | Book a call if it is their problem right now |
| Introduced something with a date attached | Join the workshop |
Matching the ask to the idea keeps the issue honest. The ask grows out of the value instead of being bolted on, and the reader can feel the difference.
The risk of asking for nothing
The opposite mistake is just as costly. A newsletter that never asks for anything produces warm feelings and no business. The whole argument of the playbook is that the newsletter exists to start conversations with people who already trust you, and conversations start when somebody is invited into one.
So the discipline is not to ask less. It is to ask once, clearly, and to ask for something real. A founder who does that every issue, with the type rotated, builds a list that knows how to respond.
Frequently asked questions
Can I include a secondary link just in case?
The playbook's rule is never two asks in the same issue. A second link competes with the first and brings back the decision you removed. Keep it for another issue.
How often should the ask be a sale?
Rotate the type over time so the newsletter does not become a sales sequence. There is no required ratio in the playbook; the principle is variety, with the promise intact.
Does the ask have to be in every issue?
The checklist for each issue has exactly one call to action, so yes, but it can be as light as a request to reply.
What if nobody responds to the ask?
A reader who ignores it for months is not lost. They may not be in the market yet. When they are, they think first of whoever has been quietly useful in their inbox.
The full method, with the checklists, is in The Founder's Newsletter Playbook, a free 32-page playbook.