Writing a newsletter every week without burning out

What it is good at

• Turns scattered weekly notes into a structured first draft quickly.
• Good at suggesting a subject line and preview text once the draft exists.
• Can maintain a consistent section structure week to week for reader familiarity.
• Helps trim a rambling draft down to something people will actually finish reading.

Where it falls short

• It can't generate genuine weekly insight from nothing, the raw material still has to come from you.
• Left unedited, its default tone drifts toward generic newsletter voice.
• It doesn't know your audience's specific inside jokes or ongoing threads unless you remind it.

How to use it for creative work

1. 01

   Keep a running notes file all week

   Every time something newsletter-worthy happens or occurs to you, drop one line into a running notes document. By writing day you have raw material instead of a blank page.

2. 02

   Turn notes into a structured draft

   Paste the week's notes and ask for a draft in your usual section structure, for example: one main story, two shorter items, one recommendation, rather than a single flowing essay.

3. 03

   Add the personal detail back in

   Check that the draft includes your actual voice and a specific personal detail per section; generic AI drafts read flat without this pass.

4. 04

   Generate subject line options

   Once the draft is set, ask for five subject line options, tell it which style performs for your list historically, and pick based on that pattern rather than novelty alone.

5. 05

   Trim before sending

   Ask the model to flag any section that could be cut without losing the core point. Shorter, focused issues tend to get read more fully than long ones.

Ready-to-use prompts

Here are my raw notes from this week: [paste]. Turn them into a newsletter draft in this structure: one main story (150 words), two shorter items (60 words each), one recommendation (40 words). Flag any section where you had to guess at meaning.

Compare this draft to my past three newsletters: [paste all]. Does the new draft sound like me? List anywhere it sounds generic or unlike my usual voice, and suggest a fix.

Give me five subject line options for this issue: [paste summary]. My past subject lines that performed well were: [paste examples]. Match that pattern where sensible, but don't just repeat it.

Read this draft and flag any sentence or section that could be cut without losing the core point of that section. List them, don't rewrite yet: [paste draft]

Here's a newsletter I wrote six months ago: [paste]. Is there an angle on this topic that's newly relevant given [recent development]? Suggest a fresh take, not a repeat.

Questions people ask

Won't readers notice if AI helps write it?

Not if the ideas, details and voice are genuinely yours, the model is doing structuring and drafting, and the personal-detail pass is what keeps it recognisably you.

How do I keep a consistent voice over many issues?

Paste two or three past issues into the session each time and explicitly ask for a voice comparison before sending, this catches drift early.

What if I have no notes some weeks?

Ask the model to suggest three topic angles based on your past issues and current events in your niche, then pick one and build the notes from there in a short session.