How I Write Four Newsletters a Week With Claude
My Creator's MBA newsletter goes out four times a week, and Claude drafts every issue. Each edition has its own Claude skill, my voice rules live in one place, every issue starts from something I already wrote and the finished draft goes straight into Kit. I still pick the topic, bring the stories and the numbers, read every draft and schedule it myself.
My Creator's MBA newsletter goes out four times a week. There's a Wednesday issue about AI, a Friday issue about the Creator Growth Flywheel, a Saturday issue about events and the Sunday issue, which is the big one.
If I wrote all four from a blank page every week, I wouldn't get anything else done. And I know a lot of you are sending one newsletter a week and it's still taking up most of a day.
So I want to show you how I actually do this with Claude. It comes down to setting a few things up once, so every issue starts most of the way there and I'm not explaining my newsletter to AI from scratch every week.
Why one prompt at a time doesn't save much time
Most people start using AI on their newsletter by opening a chat, pasting in some notes and asking for a draft. That works for a little while. Then you spend the next hour fixing it, because it doesn't sound like you, the sections are in the wrong order and the links are missing.
The next week you do it all over again, because the chat doesn't remember any of it.
Meera Kothand is teaching a workshop at the AI Newsletter Summit called Stop Managing Your Newsletter One Prompt at a Time, and that title says it well. You get your time back when you stop explaining your newsletter again every single week.
The four things I set up once
Here's what sits behind every issue I send. None of it is complicated, and you can set up a smaller version of each one for a single weekly newsletter.
A skill for each edition
A Claude skill is a saved set of instructions that Claude reads before it starts a task. Each of my four editions has its own skill with the sections in order, the colors, the fonts and the rules for that edition. So the Saturday issue always has the same sections, and the Sunday issue always ends with my offers and a P.S.
My voice rules
I keep the rules for how I write in one place, and Claude reads them before it writes anything for me. Things like no em dashes, use contractions, write prices like $97, keep paragraphs short and a list of words I'd never say, like "unlock" and "skyrocket."
Something I already wrote
Most of my issues start from a blog post I've already written. This month my Wednesday issue came from my article on plain subject lines, and my Friday issue came from my article about the real person behind a newsletter. Claude turns the article into the newsletter's sections, so the ideas and the numbers are mine.
A connection to Kit
Kit is connected to Claude, so when a draft is ready it goes straight into Kit as a draft, on the right template and set to go to the right list. Before it writes, Claude can also pull one of my recent sends out of Kit and match how my real issues look.
What a normal week looks like
I pick the article and tell Claude which edition it's for. Claude reads that edition's skill and my voice rules, looks at a recent issue and writes the draft.
Then I read it, and this is where most of my time goes now. For this month's issues, I cut a paragraph that didn't need to be there, swapped out the image in one issue and asked for a shorter box at the top of another one.
I also ask for 10 or more subject lines with preview text for every issue. I pick two that are different from each other and test them, so I learn a little more about my readers every week.
When it looks right, Claude puts the final version in Kit and I schedule it myself. Nothing goes out without me reading it first.
Where I still catch mistakes
AI gets things wrong, and the mistakes are usually small enough that you'd miss them if you were skimming.
Recently one of my subject lines described a speaker's summit workshop too narrowly. Her workshop covers calls, workshops and voice notes, and the subject line only talked about voice notes. I caught it, we checked her real title on the registration page and fixed it before it ever got near Kit.
So I have one rule for myself. Anything with a name, a number, a date or a price gets checked against where it came from before it goes out.
I pick the topic every week. I bring the stories, the numbers and my opinion. I read every draft, I check anything with a name, number, date or price, and I'm the one who schedules it. Claude does the drafting, the formatting and the subject line options.
What's next for my setup
The next thing I'm working on is having these drafts start on their own, on a schedule. I already track my newsletter sponsors in Airtable, so the plan is for a scheduled task to check whether an issue has a sponsor and build the draft with the sponsor already in place, ready for me to read.
Brittany Long is showing something close to this at the summit. Her workshop is called How I Used a Scheduled Task to Write My Money-Making Newsletter Each Week.
Robin Simmons runs three newsletters as one person, and that workshop is One Operator, Three Newsletters: The AI Engine That Drafts, Verifies, and Schedules Every Weekly Send, so if you've ever thought about adding a second newsletter, that's a good one to watch.
How to start if you send one newsletter a week
You don't need four editions or a connected email platform to start. Here's how I'd set it up for one weekly newsletter.
- Write down your sections in order and what each one is for. If your newsletter changes shape every week, pick the three or four sections you want to keep.
- Pull up your last three issues and make a list of what you'd change in each one. That's your first set of voice rules.
- Pick one thing you already made, like a blog post, a podcast episode or a voice note, to be the starting point for next week's issue.
- Save steps one and two where Claude reads them every time. That can be a skill, or a Claude Project if you're not ready to build a skill yet.
Then read every draft like it's going out under your name, because it is. The time you used to spend writing from scratch goes into reading and fixing, and that's a much shorter job.
The Write It workshops at the summit
The AI Newsletter Summit runs October 27 to 29 and it's free. The whole Write It part of the summit is about this, and every workshop shows the real setup behind someone's newsletter with the prompts and the workflow on screen. Here are a few of them:
- Adrienne Farrow, How I Use a Claude Skill to Write My Weekly Newsletter in Half the Time
- Emily Grace, 5 Hours to 30 Minutes: The Newsletter System That Sounds Like Me
- Faith Mariah, Talk Once, Email Weekly: Turn Calls, Workshops, and Voice Notes Into Better Emails With Claude
- Bianca Soler, Prompting Your Point of View
- Meera Kothand, Stop Managing Your Newsletter One Prompt at a Time
I'm opening the summit live on Tuesday, October 27 at noon ET with Write It, Grow It, Get Paid: Where Does Your Newsletter Need AI First? Right after that, at 1pm ET, I'm doing Destini's AI Email Playbook with Kit.
Watch how other people set this up
27 free workshops on using AI to write your newsletter, grow your list and get paid, with the prompts and the workflow on screen. October 27 to 29.
Save your free seat →Frequently asked.
Can Claude write my newsletter in my voice?
It can get close when it has your rules to work from. Give it a list of how you write, the words you never use and a few of your real issues, and save them in a skill or a Claude Project so it reads them every time. You'll still want to read every draft before it goes out.
What is a Claude skill?
A skill is a saved set of instructions that Claude reads before it starts a task. For a newsletter, it has your sections in order, your layout and your rules, so you don't have to explain them again every week.
Can Claude put my newsletter draft into Kit?
Yes. Kit can connect to Claude, so Claude can create the broadcast as a draft on your template and set it to go to the right list. You still review it and schedule it in Kit yourself.
Should I let AI send my newsletter without reading it?
No. AI makes small mistakes with names, numbers, dates and titles that are easy to miss. Read every draft and check anything with a name, number, date or price against where it came from.
What should I still write myself if AI drafts my newsletter?
The topic, your stories, your numbers and your opinion. Those are the parts readers come to you for, and AI can't make them up for you.
Dr. Destini Copp helps digital product creators build sustainable, systems-based businesses through the Creator Growth Flywheel framework. She's the founder of Creator's MBA and HobbyScool, and has been teaching online business strategy for over a decade. Learn more →
