| name | newsletter-publisher |
| description | - You run a paid or free newsletter (Substack, Beehiiv, ConvertKit/Kit, Ghost, Mailchimp) and want to systematize the operational work around each ... |
Newsletter Publisher
When to activate
- You run a paid or free newsletter (Substack, Beehiiv, ConvertKit/Kit, Ghost, Mailchimp) and want to systematize the operational work around each issue
- Your newsletter is shipping inconsistently because writing it takes too long
- You're growing the list and want a structured plan for growth tactics (referral, cross-posts, paid acquisition)
- A specific issue has performed unusually well or poorly and you want to understand why
- You're considering monetizing — paid tier, sponsors, products — and need help structuring the offer
When NOT to use
- You have a dedicated newsletter editor or VA who runs the operational layer for you — they should keep ownership
- Your newsletter is purely a hobby and adding workflow scaffolding to it kills the fun
- You're shipping daily — at that cadence, the operational overhead is so tight that ad-hoc writing is faster than structured workflows
Instructions
Step 1: Set up your newsletter context
Spend 30 focused minutes on this. The business context document is the difference between Claude outputs that read like you wrote them and outputs that read generic.
Say:
"I run a [free / paid] newsletter called [name] on [platform]. My audience is [persona — their role, what they think they want, what they actually need]. My subscriber count is [N]. My open rate is [X%], my click rate is [Y%]. My point of view in three sentences: [your POV]. My signature voice rules: [things you always do, things you never do]. My monetization is [list current and planned: paid tier, sponsors, products, services]."
Step 2: Pre-flight an issue draft
After you've written a draft, run it through Claude for structure and distribution prep.
Say:
"Here's my draft for this week's issue. Generate: (1) three subject line variants, ranked by likely open rate, with the reason each might or might not work, (2) a preview text (the snippet under the subject line), (3) a one-paragraph summary suitable for a tweet thread or LinkedIn post, (4) three pull quotes I could highlight on social, (5) a 2-line teaser for next week to put at the bottom."
The subject line generation alone justifies the workflow — most newsletter writers reuse subject line patterns out of habit, and Claude's variants surface options you'd never have written yourself.
Step 3: Repurpose across channels
Most newsletter writers underdistribute their work. Each issue is a 1,500-word piece that could feed 5-8 social posts, a podcast/YouTube companion, and a blog post.
Say:
"Repurpose this issue into: (1) a 5-tweet Twitter/X thread, (2) a LinkedIn long-form post, (3) an Instagram carousel script (slide-by-slide), (4) a YouTube short script if I were to record one, (5) a podcast intro if I were to record a companion episode."
Pick the channels that fit your distribution. The point isn't to ship everything — it's to have the option without the writing cost.
Step 4: Growth tactics
Newsletter growth compounds slowly. Most writers do too few growth experiments because each one feels small. Claude lowers the activation cost of growth experiments.
Say:
"Suggest 5 growth experiments for the next 30 days, given my niche and audience size. For each: (1) what the experiment is, (2) the rough effort, (3) the expected gain, (4) the metric to track, (5) the disqualifying condition that would tell us to stop."
Pick 2-3 experiments. Run them. Discard the ones that don't move the metric.
Step 5: Performance autopsy
For an issue that performed unusually well or poorly:
Say:
"Issue [title] from [date] had a [X%] open rate vs my baseline of [Y%]. The subject line was [headline]. The hook was [opening]. The topic was [topic]. What patterns explain this performance? What's the testable hypothesis for my next 3 issues?"
Claude will surface patterns that are obvious in retrospect but hard to see in the moment. Most newsletter writers don't do performance autopsies because the work is unstructured; Claude structures it.
Step 6: Monetization design
When you're considering monetizing:
Say:
"I want to add [paid tier / sponsors / a product]. My current audience is [size and engagement metrics]. My niche is [niche]. Draft: (1) the case for monetization at this stage and the case against, (2) the proposed offer structure with pricing rationale, (3) the launch sequence (3-5 emails), (4) the messaging for existing readers to address concerns about whether the free tier will degrade."
Edit hard. Monetization decisions are strategic, not just operational. Use Claude's drafts as a starting point, not as the decision.
Example
You run a paid newsletter on B2B SaaS strategy. 14,000 free subscribers, 850 paid at $12/month — about $122K ARR. You ship every Tuesday. Each issue takes you 6-8 hours: 4 hours writing, 1 hour editing, 1 hour for subject lines and preview, 1-2 hours for social distribution.
You set up the business context, write your draft on a Sunday afternoon, and run the pre-flight workflow.
Claude produces:
Three subject line variants:
- "Why your activation rate is lying to you" — strong but possibly too aggressive for your warm-but-direct voice
- "The activation metric problem" — too understated, will under-perform
- "Your activation rate is measuring the wrong thing" — best fit; declarative, curiosity gap, voice match
Preview text: "Three signs your activation metric is hiding churn, plus the cleaner alternative most ops teams haven't tried."
Tweet thread: 5 tweets, each one a punchy summary of a section of the issue.
LinkedIn post: 220 words, opens with the strongest pull quote, three short paragraphs of context, a CTA.
Carousel script: 8 slides for Instagram.
Two pull quotes for graphic treatment.
You spend 30 minutes editing all of this for voice. You schedule the social posts for Tuesday-Friday distribution. The issue ships Tuesday morning.
Total time: writing 4 hours, editing 1 hour, distribution prep with Claude 30 minutes. Down from 7-8 hours total to 5.5 hours total — and the distribution is actually shipped instead of being on the to-do list.
Over 50 issues per year, that's 100+ hours saved annually. More importantly: the distribution actually happens, which compounds growth over the next 12 months in a way that previously didn't fit into the week.
