A newsletter gets four things decided before it gets read: the subject line, the first sentence, the shape of the body, and the one action it asks for. Most newsletter AI prompts generate an entire issue at once, which means all four get an average answer. Generate each part separately, with its own constraints, and the quality changes immediately because each part has its own job.
The prompts below follow the order you would actually write in, with a filled example and a review pass for the draft before you schedule it.
The four parts that decide whether a newsletter is read
Treat a newsletter as four short problems rather than one long one.
- Subject line: earns the open, or nothing else matters.
- Opening line: decides whether the reader stays past the second line.
- Body: carries one idea, because a newsletter is not a place to cover a quarter.
- Call to action: asks for one thing, because two asks produce one response at best.
Once you split them, each prompt gets narrower and the model stops producing the smooth, undifferentiated prose it defaults to. The split also makes revision cheap, because a weak subject line is a two-minute fix instead of a rewrite.
The subject line prompt that writes twenty and keeps three
Write [twenty] subject lines for an issue of [newsletter name] about [the one idea], sent to [specific subscriber]. Constraints for all twenty: under [character limit] characters, visible on a phone with the sender name included, no emoji, no false urgency, no open loop the issue does not pay off, and no word that would appear in [three competing newsletters you want to be distinguishable from]. No more than five words of capitalisation. Write them in four shapes: a plain statement of the idea, a specific number or detail, a question my subscriber actually asked me, and a sentence describing what they will be able to do after reading. Do not use inflated words such as ultimate or essential. Do not promise a result the issue does not deliver. Do not write a line you would be uncomfortable seeing quoted back at you. Then pick the three strongest, explain in one sentence each why, and say which one you would send if your last six subject lines all performed the same.
The four shapes are what stop a list of twenty collapsing into one idea worded five ways. Pick the shapes deliberately and the options diverge.
The opening line prompt, because the first sentence does the work
Write [five] opening lines for a newsletter issue about [the one idea], aimed at [reader]. The reader opens the email, sees the subject line "[subject line]", and has [number] seconds before deciding to keep reading. Each line must do one of these: state a situation the reader is in now, name a specific number I supplied, admit something the reader will not expect me to admit, or give a concrete example from my own work. Under [word count] words each. No greetings. No "I hope you had a good week". No rhetorical question. No summary of the issue. Two of the five must be plain and calm, two must carry some tension, one must be self-deprecating about a mistake I actually made. Do not invent a mistake. Do not use the phrase in this email.
Fill in these details
- One idea: if you cannot name it in a sentence, the opening line has nothing to point at.
- Reader and their week: context decides whether an opening line sounds relevant or just clever.
- Number or detail: the supplied fact that only you have. Without one, the model reaches for a platitude.
- Word count: openings that run long get cut, and the point is lost with them.
The body prompt that holds one idea
Draft the body of a newsletter issue about [the one idea]. Structure: [your standard sections, for example what happened, what I tried, what I learned, what I am doing next]. Total length: [word count]. Voice: [three adjectives and one anti-adjective]. Use these materials only: [paste your notes, links, examples]. Rules: one idea per issue. Every section must advance that idea or be cut. Write in first person where it is about your own experience, and in second person only where you are describing something the reader does. Do not open with a recap of the previous issue. Do not summarise what you are about to say. Do not use bulleted lists unless the information is genuinely a list. Do not invent a statistic, a customer, or a result. If a section has no material, tell me to cut it rather than filling it. End the body two paragraphs before the call to action, so the action is not buried.
That last instruction is not stylistic. A call to action that arrives straight after the last paragraph of argument reads as a summary of the issue rather than a next step.
One call to action, decided before you write
My newsletter issue argues [the one idea]. The single action I want a reader to take is [one action, in one verb]. It should take them to [destination], where the next step is [what they will do there]. Write three versions of the call to action: a plain sentence, a sentence that connects the action to the idea of the issue, and a sentence with a reason to act now that is true. Under [word count] words each. No urgency the issue does not support. No fake scarcity, no countdown, no implication that they will miss out. Do not add a second ask, even a small one, such as a reply or a share. If the action I chose does not follow from the idea of the issue, tell me which idea it does follow from.
Three versions of one action beats one version of three actions. If you need a second ask, put it in the next issue.
Worked example: the same issue, two subject lines and two opens
A newsletter about a client's delayed launch. The issue explains what went wrong and what changed in the process.
| Part | First attempt | Second attempt |
|---|---|---|
| Subject | "What we learned from a delayed launch" | "The launch slipped six weeks. Here is the one thing we fixed." |
| Opening | "I hope you had a great week. I wanted to share some thoughts." | "The launch slipped six weeks, and the first three weeks we spent waiting on an answer we never chased." |
| Body | a summary of the project timeline | the three decisions that caused the delay and the one that fixed it |
| Action | "Read the full case study and share your thoughts" | "Here is the checklist we now run before every launch" |
The second column has one action and one idea. The first has three, which is why it reads as a newsletter about a newsletter.
Check the draft before you schedule it
1. Read the subject line without the body
If it makes no promise the body does not keep, rewrite it. Unpaid promises are why people mark a sender as spam.
2. Count the asks
One action per issue. If you find a second one buried in a paragraph, move it to the next issue.
3. Check every number and name against your notes
Readers of a small newsletter often reply. A wrong number is found quickly and costs more than the issue earned.
4. Read only the opening two lines
That is the portion most readers see before deciding. If the second line does not follow from the first, the structure is wrong.
Common newsletter prompt mistakes
- Generating the whole issue in one prompt: subject, open, body, and action get averaged into one register instead of four.
- Describing the tone instead of naming the reader: "friendly and professional" produces the neutral average of two unrelated registers.
- Letting the model choose the ask: it adds a reply request or a share request to fill space.
- Writing the call to action last with no destination: an action without a stated destination turns into vague encouragement.
- Using urgency you cannot back: check your own platform rules on what claims are acceptable for your list, since they change.
Frequently asked questions
How long should a newsletter be?
Long enough for one idea to be fully argued. A short issue that finishes its argument beats a long one that introduces a second idea halfway through and abandons both.
Should I use AI for the whole issue?
Most readers of a small newsletter will notice if an issue has no owner. The prompts are stronger on structure, subject lines, and drafts you then rewrite than on anything you would send untouched.
How many subject lines should I test?
Enough to be a real choice rather than a first idea. Twenty options across four shapes gives you candidates, and you should pick the one that sounds like your newsletter rather than the cleverest one.
Write next issue's subject line first
Before you draft the next issue, run the subject line prompt and settle on the three candidates you would actually send. If none of them is one you would send, the idea is not specific enough yet. For more prompts covering the sending side, browse the email marketing topic collection.