It’s Thursday morning. Your newsletter goes out tomorrow. You don’t have a topic, much less a draft. This tutorial replaces the “stare at the blank doc until 11pm” cycle with a 60-minute Thursday-morning routine: 10 minutes of AI-assisted ideation, 25 minutes of drafting, 10 minutes of subject-line A/B prep, 15 minutes of editing and send. Aimed at creator newsletters, brand newsletters, and indie product newsletters where the bottleneck is consistency, not voice.
What this covers
A complete weekly newsletter workflow — topic ideation, draft, subject lines, send — plus a one-week feedback loop that feeds learnings back into next week’s topic selection. AI does the heavy lifting on candidate generation and first draft; you keep the voice, the personal note, and the CTA. The system is designed to ship 50 issues a year without burning out the writer.
Who this is for
Creator newsletters (writer’s personal list, indie expert), brand newsletters (SaaS company weekly, ecommerce news), indie product newsletters (changelog plus tips). Best when you have a defined audience and three themes you cover. Worst when you do not know your audience yet — AI cannot manufacture a voice for an audience you have not met.
When to reach for it
Weekly publication days. Newsletter is one stage of a bigger funnel — see the AI content marketing stack guide for the 7-tool set covering ideation, drafting, scheduling, analytics, and repurposing that the workflow below plugs into. Also useful for relaunching a dormant newsletter; the workflow’s discipline restarts the habit.
When this is NOT the right tool
The first issue of a newsletter that has no clear voice yet — write it by hand, twice, before bringing in AI. Newsletters where every issue is highly personal (a writer’s life updates) — AI flattens voice. One-off announcements that go in your newsletter occasionally — overhead exceeds value.
Before you start
- Document your audience in one sentence (“indie SaaS founders running 10-50 person teams, mostly technical, US/EU”). AI mirrors what you tell it — vague audience, vague newsletter.
- List your three themes (“scaling without funding, AI tooling, founder mental health”). Every issue should be visibly one of these themes.
- Confirm your ESP (Substack, Beehiiv, ConvertKit, Mailchimp) supports A/B subject testing. Substack does; some others require a paid tier.
- Have a “swipe file” of three past issues you were proud of. Paste these into the AI as voice references — it learns the voice faster from examples than from descriptions.
Step by step
- Topic ideation. Prompt: “Audience: [paste]. Themes: [paste]. Last 3 issues covered [list]. Generate 8 topic candidates for this week’s issue — each as a one-line title plus a one-line “why now.” Avoid topics close to what I just covered.” Pick one; if none are good, the prompt or theme list is too thin.
- Outline the issue. Standard structure: 1-line hook, 3 takeaways (numbered), 1 personal note (your voice, your story), 1 CTA. Draft the outline yourself in 5 minutes — this is the part AI cannot do well because the personal note carries the voice.
- Draft the body. Prompt: “Write a 350-word newsletter issue from this outline. Tone: [reference your past issue]. No corporate-speak. No filler adjectives.” Expect to rewrite the personal note paragraph entirely; AI flattens voice on that part every time.
- Subject lines. Prompt: “Generate 10 subject line variants for this issue. Mix of: curiosity gap, specific outcome, question, contrarian, personal. Under 50 characters. No emoji unless I ask.” Pick the top 2 for A/B testing.
- Send. Most ESPs A/B test subject on a 10-20% sample then send the winner to the rest. Set a 4-hour test window; longer tests waste open windows.
- After one week, log: open rate, click rate, replies, unsubscribes. Note which sections drove clicks (use UTM tags). Use this as input for next week’s topic prompt — “Last week ‘X topic’ got 38% open rate; readers replied about subtopic Y; explore Y this week.”
First-run exercise
- Run the full workflow once for next week’s actual issue. Real stakes; do not rehearse on a fake issue.
- Time each step. If ideation took 25 minutes instead of 10, your audience and themes are not specific enough.
- Save the prompts that worked. The ideation prompt is the most reused; tune it for a month before declaring it done.
- For the second issue, change only one variable: tighter theme list, longer voice reference, or a different model.
Quality check
- The issue solves something the reader cares about today. Not “interesting” — useful. Re-read the takeaways and ask: would the reader thank me for this on Monday?
- The personal note sounds like you, not AI. Read it aloud; if it sounds smooth and corporate, rewrite by hand.
- The CTA is one specific ask, not three vague invitations. “Reply with your hardest hiring decision this quarter” beats “let me know what you think.”
- Subject line under 50 characters, no emoji unless your audience expects them, no clickbait that the body cannot deliver.
- All links work and have UTM tags. Broken links destroy the trust you spent the issue building.
How to reuse this workflow
- Save the ideation prompt, the draft prompt, and the subject-line prompt as a Notion or text snippet. New week, swap the audience and theme details — keep the structure.
- Maintain a “winning topics” doc — issues with open rates above your baseline. Patterns emerge; future ideation is faster.
- Quarterly, audit unsubscribes by topic. Topics that consistently drive unsubscribes have leaked into the wrong audience.
Recommended workflow
Topic candidates → outline → draft → subject A/B → send → log learnings → next week. Sending the issue in a second language? Run it through our AI translation self-critique workflow — the region-aware critique catches tone slips that flat translation would silently ship.
Common mistakes
- Spending 90 minutes on the body and 10 seconds on the subject line. Subject line drives open rate, body drives reply rate — both matter, neither should be an afterthought.
- No CTA — readers do not know what next. A clear ask earns the relationship.
- Not logging what worked. The same writer rediscovers the same insight every six months without a log.
- Letting AI write the personal note. AI smooths it into a stranger’s voice and unsubs follow.
- Stuffing every issue with 5 links. Subscribers leave when an issue feels like a digest. One link is enough.
- Ignoring unsub feedback. Unsub reasons are the cheapest research a newsletter can get.
FAQ
- Which ESP is best for AI workflows?: Substack, Beehiiv, and ConvertKit all integrate well. Substack has the cleanest A/B subject testing. Beehiiv has better analytics. ConvertKit has better automation.
- How long should an issue be?: 300-500 words for most niches. Tech industry newsletters tolerate up to 800. Friction is at the open, not the read.
- What about images?: One header image, maybe one inline. AI-generated header images are fine; AI-generated stock photos of people are not.
- Should I use the AI to translate to other languages?: Use AI to draft, then have a native speaker (or our AI translation self-critique workflow) review tone. Flat machine translation reads as flat machine translation.
- How often is too often?: Weekly is the sweet spot for most niches. Daily requires a different format (short, single-link). Monthly loses momentum.
- What if I miss a week?: Skip it. A wobbly schedule beats a forced bad issue. Resume next week, no apology paragraph needed.