The task
Your newsletter is due in 3 hours. You have a theme, three links, and a few raw thoughts. The risk is shipping a curated link list that reads like a feed: no take, no voice, no reason to open next week. The job is to turn the links into a piece of writing with your reaction at the centre, not the links.
When AI helps — and when it does not
AI is good at structuring an issue, varying section lengths, and tightening rambling first drafts. It is bad at having a take. That part is yours. Feed it your raw reactions, not just the links; otherwise you get a competent summary that nobody re-opens.
What to feed the AI
- The theme of this issue (one sentence)
- 3-5 links with title + URL + your one-sentence take on each
- Audience (segment, why they subscribed, what they expect)
- Brand voice: paste a previous issue you are proud of
- The CTA (drive to a paid tier, share, reply, click out, or none)
- Banned phrases — your AI tells (“dive in,” “let’s get into it”)
Copy-ready prompt
Write a newsletter issue.
Theme (one sentence): <line>
Audience: <segment, why they subscribed, what they expect>
Brand voice (previous issue I am proud of): "<paste 200-300 words>"
CTA: <paid / share / reply / click / none>
Banned phrases: <list>
Links + my take:
1. Title — URL — my take: <sentence>
2. ...
3. ...
Return a 600-800 word issue with:
- Hook (75-100 words) that sets up the theme
- Three sections, each: one-line link reference + 100-130 word essay using my take as the spine. The link is the prompt, not the body.
- A "what to do with this" callout — one practical action for the reader
- A 50-word closer with the CTA
Constraints:
- No "let's dive in," no "🎯", no engagement bait
- Vary sentence length — alternating short and long
- Do not summarise the linked article in detail; assume the reader trusts me to pick
- Keep my take recognisable as mine — flag any paragraph that drifted into "AI summary" voice
For paid newsletter: “Add a 100-word teaser of next issue’s topic, positioned to make a free reader curious.”
Recommended output structure
Hook → 3 sections → action callout → closer with CTA. Subject + preview line at the top. Total 600-800 words. Sections separated by a single line break, not heading hierarchy (newsletter clients render headings inconsistently).
How to check the output is usable
- Each section reads as a take, not a summary
- Your voice from the reference is recognisable
- Sentence length varies (no “AI cadence”)
- The CTA is one ask, not three
- A reader could skip a link and still get value from your take
Common mistakes
- Long link list + thin take. Readers can get a link list from Reddit
- Stacking CTAs (subscribe + share + reply + click). Pick one
- Letting AI summarise the linked article. That defeats the link
- Same-rhythm sentences. The giveaway of AI prose
- Forgetting the subject line. That decides whether the work matters
Practical depth notes
For How to Use AI to Write a Newsletter Issue: Theme, Three Links, Your Take, One CTA, the difference between a usable AI result and a generic one is the input packet. Give the model the audience, the current draft or raw material, the desired format, the decision you need to make, and two examples of what good and bad output look like. Ask it to preserve facts first, then improve structure or wording second.
After the first response, do a separate review pass. Look for missing constraints, invented details, weak calls to action, and language that sounds plausible but does not match the real situation. The best final output should be easy to use immediately: clear owner, clear next step, and no hidden assumption that someone else has to untangle. A stronger version of this workflow also defines the handoff. Decide who will use the output, what they should do next, and what information would make them reject it. If the deliverable is copy, test whether it has a single clear action. If it is analysis, test whether it separates observation from recommendation. If it is planning, test whether dates, owners, and tradeoffs are explicit enough for someone else to execute. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.
FAQ
- How long is too long? 1,200 words is the upper bound for most newsletters. Longer needs a paid tier.
- Should I include images? One hero image, optionally. Inline images in newsletters often break.
- Schedule consistency? Same day, same time, weekly. Open rates degrade fast on irregular schedules.
Related
- Newsletter prompts — alternative phrasing
- AI newsletter tutorial — end-to-end workflow
- Cross-platform repurpose — repurpose the newsletter
- Email marketing copy — promo emails, not newsletter
- Email subject line prompts — subject lines for the issue
- Storytelling outline — newsletter intro as a story
Tags: #AI writing #Content creation