Claude Prompts to Write a Newsletter (8 Prompts)

It's Sunday evening. Your newsletter goes out Tuesday morning. You promised yourself last week you wouldn't write it at the last minute again. Here we are. You open the doc, stare at the blinking cursor, and three minutes later you're back on Twitter "researching."

Newsletter writers — solo creators, founders, consultants who build authority through email — universally describe the same problem: the structure is the easy part. The hard part is generating the idea fresh every week and converting it into 600-1,000 words that actually deserve someone's inbox. That weekly grind is where the right Claude prompts to write a newsletter give you a foundation you can build on instead of a blank page.

This post gives you eight Claude prompts I use across the whole newsletter workflow: idea generation, outlining, drafting, editing, subject lines, and the dreaded P.S. line.

Why Most Newsletters Stall at Issue 12

I've watched dozens of creators launch newsletters and quit by issue 12. The pattern is identical every time.

Issue 1-3 is the "I've been saving this up" period

You ship the three ideas you've been mentally hoarding for months. Easy. Energizing. Subscribers reply.

Issue 4-11 is "what am I going to write about this week?"

The hoard runs out. You start writing on Sunday night, scrambling for an angle. Quality drops. Open rates flatten. Replies dry up.

Issue 12 is "I'll skip this week"

Skipping breaks the habit. Two weeks later you've quietly stopped.

The thing that breaks this cycle isn't more discipline — it's a system that surfaces three viable ideas every Monday morning so Sunday night is editing, not creating. That's what AI does well.

The 8 Newsletter Prompts (In Order of Workflow)

1. The weekly idea generator

Run this every Monday before you do anything else.

You're my newsletter strategist. My niche is {niche}. My audience is
{persona — be specific: "freelance designers earning $80K-$200K"}.
The angle they trust me for is {your angle}.

Generate 5 newsletter ideas for this week. For each:
(a) working title (under 60 chars),
(b) the one thing the reader will be able to do after reading,
(c) the hook line that opens the issue,
(d) why this is timely for THIS week (recent news, season, trend).

Reject any idea that's generic enough you could have published it 2 years
ago. I want this-week-specific only.

2. The angle pressure-tester

Once you've picked one of the five, pressure-test it.

The newsletter idea I'm running with: {paste idea}.

Steelman the case AGAINST publishing this. What's been written on this
topic already? What's the obvious take I should avoid? What's the
counter-intuitive angle that would make this issue actually stand out?

Then suggest 3 sharper angles. Pick the strongest and tell me why.

This single prompt is responsible for most of the upgrade in my newsletter quality. It turns a 6/10 idea into an 8/10 angle.

3. The outline builder

Outline a 700-word newsletter on {sharpened angle from prompt 2}. Use
this structure:

- Hook (50w) — a specific scene the reader recognizes
- The pattern (200w) — what most people get wrong and why
- The fix (350w) — 2-3 specific tactics with examples
- The application (80w) — one thing to try this week
- The P.S. (20w) — one related resource or aside

For each section, bullet the 2-3 key beats I should hit. Don't write
the prose yet — just the beats.

4. The hook generator

The opening 50 words decide if anyone reads the rest.

Write 5 different hooks for a newsletter on {topic}. Each hook should:
(a) be 35-50 words,
(b) open with a specific scene, not an abstraction,
(c) name a tension the reader is already feeling,
(d) end on a question or stake that pulls them into the next paragraph.

Variation: one funny, one urgent, one observational, one contrarian,
one personal-anecdote-based.

5. The first draft

Draft the full 700-word newsletter using the outline I'll paste below
and hook #{number} from the previous prompt.

Voice: conversational, direct, no MBA filler words. One specific example
per major claim. Cut every adverb. Use "you" not "we." Short paragraphs
(2-3 lines max).

Outline + hook:
{paste}

6. The subject line tester

Five candidates, then pick.

Generate 8 subject line candidates for this newsletter. Mix of styles:

- 2 curiosity-driven
- 2 outcome-driven
- 2 numbered/specific
- 1 contrarian
- 1 one-word

All under 50 characters. No clickbait. No emoji. Then rank them 1-8
and explain which is most likely to be opened by a {persona} who already
subscribes to me.

Newsletter content: {paste draft}

7. The P.S. line

The single most-read line in any newsletter, after the subject. Almost everyone wastes it.

Write 5 P.S. line options for this newsletter. Each under 30 words. They
should either:
(a) tee up next week's topic in one teasing sentence,
(b) point to a relevant product/resource with a soft CTA,
(c) ask one short question that invites a reply.

The newsletter ends on: {paste closing paragraph}.

8. The "send-or-don't" editor

The last pass before you hit send.

Read this newsletter as if you were the persona: {persona}. Score it
1-10 on these dimensions:

- Hook strength (did you keep reading after sentence 2?)
- Concreteness (could you act on this this week?)
- Differentiation (is this saying something you haven't read elsewhere?)
- Voice (does this sound like a person, not a brand?)
- Brevity (any paragraph that should be cut?)

For any score below 7, give me the specific edit.

Newsletter: {paste full draft}

The Voice Calibration Trick

The biggest reason AI-drafted newsletters underperform: they don't sound like the writer. Fix this once and you never have to fix it again.

Paste 3 of your best previous newsletters (or any 2,000 words of your writing) into Claude and run:

Analyze the voice in the writing below. Identify: (1) sentence length
patterns, (2) signature phrases or sentence-openers I use repeatedly,
(3) tone (formal/casual/contrarian/warm), (4) the kinds of metaphors
and references I lean on, (5) what I deliberately don't do (e.g.
exclamation points, em-dashes, business jargon).

Output as a "voice profile" I can paste into future prompts.

Save the output. Paste it as a system note at the top of every newsletter prompt going forward. Quality jumps immediately.

This is the same calibration approach I cover in Claude prompts for content creators — pairs well with this newsletter workflow if you publish in more than one format.

A Quick Note on Cadence

The data on newsletter frequency in 2026 is consistent: weekly outperforms daily for solo creators, and bi-weekly outperforms monthly. The reason is replies. Replies decide deliverability; deliverability decides whether you even show up in inboxes six months from now. Weekly is the cadence that produces enough replies to keep your sender reputation strong without burning you out by month four.

If you want more on building a creator-side content stack, see Claude prompts for solopreneurs.

Skip the Prompt Library — Buy It Pre-Built

The eight prompts above will get you a clean newsletter every week. If you'd rather skip the iteration cycle, 50 Claude AI Prompts for Business Owners includes the entire newsletter workflow — ideation, hooks, drafting, subject lines, P.S. lines — plus the supporting prompts for social repurposing, lead magnets, and the cold-email follow-ups that turn newsletter subscribers into customers.

It's $17 and saves you the 4-6 hours of prompt iteration it took me to dial mine in.

The Honest Test

Try this: write next week's newsletter the old way, then re-write it using prompts 1-8 above. Send both to three friends. Ask which one they'd be more likely to read all the way through.

If the prompt-driven version wins, you've just bought back 2-3 hours of your Sunday evening — every week, indefinitely. Stack that across a year and it's 100+ hours.

Grab the Claude Prompts for Business Owners pack if you want the whole library pre-tuned, or build your own from the templates above.

What's the part of newsletter-writing you dread most — the idea, the draft, or the subject line? Reply and tell me; I'll send back the exact prompt I'd use.