Generate a Newsletter from Your Weekly Notes

You'll end up with: A polished newsletter draft assembled from your raw notes and ideas

Overview
15-25 min
Beginner
Free to start
2 tools
Cost breakdown
Claude (writing and editing)Free tier
Google Docs (paste and format)Free
TotalFree to start
Common mistake

Weekly notes almost always contain more ideas than one issue. If you skip a one-sentence spine and a hard section cap, the model mirrors the sprawl and the email feels like a brain dump. Fix: one thesis, at most three body sections, and move leftover ideas to a parking lot for next time.

Before you start
  • 5-7 days of notes in one paste (bullets OK)
  • One line on who reads this list (role and what they want from you)
  • One primary CTA for this issue (reply, click, buy, or book)
  • Claude open; optional Google Doc or blank draft in Substack, Beehiiv, or ConvertKit for paste
1

Choose one spine and paste your week's notes

Collapse messy notes into one thesis and decide what this issue is not about.

Exact action

1. Go to claude.ai and sign in. 2. Start a new conversation. 3. Paste your last 5–7 days of notes in one block (bullets, fragments, and half-sentences are fine). Add one line: who reads this list and what they want from you this week. 4. Use a prompt like: "From my notes below, propose (a) one sentence spine for this week's newsletter — the single point readers should leave with, (b) three working titles, (c) a short 'not this week' list of tangents to explicitly exclude. Use only my notes; do not invent stories or data." 5. Pick one title and one spine. If two themes still feel tied, ask: "Force a choice: which thesis best serves [reader] this week? Merge or delete the other."

You can read the spine aloud in one breath; your "not this week" list removes at least one tempting tangent; you have a chosen working title.
If you still have two competing themes, ask Claude to pick the higher-leverage thesis for this audience and move the other ideas to a "parking lot" note for a future issue.
2

Build a newsletter outline (hook to body to CTA)

Turn the spine into a scannable structure: hook, up to three sections, one CTA, optional P.S.

Exact action

1. In the same Claude conversation, say: "Using only my pasted notes and the spine/title we chose, draft a newsletter outline only — no full sentences in the body yet." 2. Ask for: a one-line hook intent (curiosity, contrast, or story tease), exactly three sections with 2–4 bullets each (each bullet should map to something in my notes), one clear CTA line that matches the CTA I stated earlier, and an optional P.S. tied to a real personal detail from the notes. 3. If a section feels thin, ask: "Swap bullets using different details from my notes" instead of inventing new facts. 4. Reorder sections until the story arc feels obvious in under a minute of reading the outline.

The outline fits on one screen; every bullet traces to something you actually pasted; the CTA is singular and concrete.
If bullets read generic, say: "Rewrite bullets using only details from my notes; where information is missing, write TODO instead of inventing."
3

Generate the full draft and subject lines

Produce a short, email-native draft plus two or three subject lines with different angles.

Exact action

1. In the same conversation, say: "Write the full newsletter from this outline. Target 500–900 words, short paragraphs, conversational tone, one primary CTA repeated once near the end. Ground every claim in my notes; add no new statistics or case studies." 2. Ask for two or three subject lines that are meaningfully different angles (not synonyms) plus one line of preview text (preheader) under 90 characters. 3. If you do not have URLs yet, ask Claude to use placeholders like [LINK: book a call] and list a tiny "links to fill" checklist at the bottom. 4. Read once for flow; if anything feels like an essay, ask: "Cut 25%, merge sections, keep at most one mini-story per section."

You have a single copy block with the draft, subject line options, and preview text; length feels like an email, not a blog post.
If the draft exceeds ~900 words or adds new "research," ask Claude to remove invented material, tighten to three sections, and keep the CTA to a single action.
4

Sound like you and move to Docs or your ESP

Strip AI tells, add one unmistakably personal line, then paste where you send from.

Google DocsOpen Google Docs
Exact action

1. In Claude (same chat), paste the latest draft and say: "Flag phrases that sound like generic AI or consultant-speak. Suggest tighter replacements that keep my meaning." 2. Read the draft aloud. Delete fillers like "In today's world" or "It's important to note." Replace the opening with one specific line pulled from your week (a moment, quote, or observation). 3. Confirm there is still only one primary CTA; demote extras to "maybe later" in your notes. 4. Open a blank Google Doc titled with your working issue title. Paste the final body, subject line pick, and preview text. Add H2 headings for each of the three sections if it helps you scan. 5. Paste into Substack, Beehiiv, ConvertKit, or your ESP draft; open mobile preview and fix awkward line breaks or link placeholders.

The draft lives where you send from; you would be comfortable shipping after a five-minute pass for typos, placeholders, and links.
If it still sounds generic, rewrite only the first three sentences and the CTA yourself using the outline as rails — keep Claude's structure, inject your voice.

All done!

You now have: A polished newsletter draft assembled from your raw notes and ideas

Explore more guides

Want this workflow built for your business?

Book a free audit