Write an email newsletter for [AUDIENCE] about [TOPIC OR NEWS HOOK]. The single reader takeaway is [TAKEAWAY]. Use only these approved facts, links, observations, and quotes: [SOURCE MATERIAL]. The desired voice is [VOICE], and the intended action after reading is [CTA OR NO CTA]. Ask up to 3 clarifying questions only if a required input is missing. Then produce: 1. Five subject lines of 45 characters or fewer and five preheaders of 90 characters or fewer. Label the best pairing and explain its specific promise in one sentence. 2. A newsletter of [LENGTH] words with: a sharp opening, context the reader needs, the central insight, 2-4 supporting points or examples, a practical implication, and a closing CTA or sign-off.
3. A plain-text version with no tables or formatting-dependent meaning. 4. A link and claims checklist showing every external claim, quote, number, date, or recommendation that requires source confirmation. Write for an inbox: use short paragraphs, specific verbs, and descriptive links. Make the subject line match the body; do not use false urgency, clickbait, fabricated personal anecdotes, unsupported trend claims, or vague praise. If this is a roundup, explain why each item matters to this audience rather than merely listing links. If a CTA is provided, make it proportional to the issue and place it after useful content. Before answering, check that the opening earns the subject line and that every paragraph supports the single takeaway. Flag anything in the supplied material that is ambiguous, outdated, or unverified instead of filling the gap.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [AUDIENCE] | Describe the subscribers and what they care about. | Independent consultants who sell operations work to small businesses |
| [TOPIC OR NEWS HOOK] | Enter the issue topic, announcement, or timely hook. | Why a discovery call should end with a written problem statement |
| [TAKEAWAY] | State the one useful conclusion readers should leave with. | A shared problem statement prevents scope confusion before a proposal is written |
| [SOURCE MATERIAL] | Paste approved facts, links, notes, quotes, and examples. | Workshop notes: ask for the current process, cost of delay, decision-maker, and evidence of success; send a three-sentence problem statement within 24 hours; do not promise a solution during the call. |
| [VOICE] | Describe the editorial voice in a few concrete traits. | Practical, calm, lightly opinionated, no hype |
| [CTA OR NO CTA] | Enter the desired reader action or say no CTA. | Invite readers to reply with the question they use to uncover cost of delay |
| [LENGTH] | Enter the approximate body length in words. | 650-800 words |
How to use
- Paste approved source material rather than asking the model to report current news from memory.
- Choose one takeaway; split unrelated announcements into separate sections or issues.
- Check subject-line promises, links, names, numbers, and quoted language against the source material.
- Send this follow-up: “Give me three alternate openings: one contrarian, one story-led, and one data-led, using no new facts.”
Variations
Weekly roundup
Use this to explain a set of links or updates.
Create a weekly newsletter roundup for [AUDIENCE] from these items: [LINKS AND NOTES]. The issue theme is [THEME]. Produce a subject line, preheader, 100-word opening, and 3-5 item sections. For each item, state what happened, why it matters to this audience, and one concrete action or question. End with [CTA]. Use only supplied facts and flag items with weak sourcing. Do not write a link dump or imply that any source says more than it does.
Product update
Use this for an announcement to existing users.
Write a product-update email for [USER SEGMENT] announcing [CHANGE]. Use these release notes and constraints: [APPROVED DETAILS]. Explain the user problem, what changed, who gets access, exact steps to try it, limitations, and support path. Produce three subject lines, a 250-400 word email, and a plain-text version. Do not claim the change saves time or improves results unless the notes support it. Flag unclear eligibility or rollout details.
Welcome issue
Use this for a new-subscriber email.
Write a welcome newsletter email for [NEW SUBSCRIBER TYPE]. The publication helps readers with [READER BENEFIT] and publishes [CADENCE AND FORMAT]. Include these approved links: [STARTER LINKS]. Produce a subject line, preheader, 350-word email, and a three-item “start here” list. Set expectations about frequency and content. Do not promise individualized advice, access, or outcomes not stated in the inputs. Check that every link has a reason to click.
Tips
- Give each issue one job: teach a decision, interpret a development, or ask for a reply; combining all three usually weakens the email.
- Write the subject after the draft so its promise reflects what readers actually receive.
- For a news-based issue, preserve dates and source links in your notes; an email can be accurate when drafted and stale when sent.
- Use a CTA that matches the reader's commitment level: reply prompts work well after a lesson, while a product link needs enough context to stand on its own.
FAQ
Should I ask AI for newsletter ideas or a finished email?
Use it for both, but select the issue angle before drafting. A clear audience need and one takeaway produce a stronger email than a broad topic.
How long should an email newsletter be?
Match length to the promise. A product update may need 250 words; a researched analysis may need 800, provided the structure stays easy to scan.
Can AI write subject lines safely?
Yes, if you check that the subject accurately represents the email. Avoid urgency or curiosity gaps that the body does not resolve.