Quick Answer
The median newsletter dies at issue 7 because the writer runs out of time, not ideas. This workflow cuts issue production from 6 hours to under 90 minutes so the cadence survives.
What you get
- Ship a weekly issue in 75-90 minutes instead of 4-6 hours
- Survive past issue 7, where most solo newsletters stall on time cost
- Hold a 40-50% open rate by writing subject lines against your own send data
- Run the platform, drafting, and research stack for $63/mo
- Convert 2-4% of free subscribers to paid within 90 days once you turn on a paid tier
Step-by-Step Workflow
7 steps · 3 hours to set up · 90 min per issue ongoing
Workflow at a glance
7 steps · 3 hours setup
Pick the promise
Set up platform
Build template
ClaudeCurate + pick
PerplexityDraft with AI
ClaudeHuman pass
Send + repurpose
ClaudePick the promise
Set up platform
Build template
Curate + pick
Draft with AI
Human pass
Send + repurpose
- 1
Choose one job the newsletter does for one reader
Before touching a tool, write the one-line promise: '[audience] reads this every [cadence] to [outcome].' Example: 'Freelance designers read this every Tuesday to find one new client-getting tactic they can use that week.'
The promise decides everything downstream: the subject line pattern, the section structure, the send day. A newsletter without a specific job reads as a personal blog and does not compound. If you cannot name the reader and the outcome in one sentence, you are not ready to send.
20 minOutput: One-line promise plus a named target reader - 2
Set up beehiiv: publication, signup form, and welcome automation
Create the publication on beehiiv Scale. Set up: (1) a signup landing page with the one-line promise as the headline, (2) a subscribe form you can embed anywhere, (3) a 2-email welcome automation that fires on signup.
The welcome automation is the single highest-leverage setup step. Email 1 (instant): deliver on the promise immediately with your single best past issue or a quick win, and set the expectation for cadence and day. Email 2 (day 3): ask one question and invite a reply - replies train the inbox provider that you are wanted mail and lift future deliverability.
Turn on beehiiv's Recommendations network so other newsletters can recommend yours and vice versa; it is the cheapest organic growth lever in the platform.
60 minOutput: Live signup page, embeddable form, 2-email welcome sequence, recommendations onTools: beehiivTip: Set the send day and time once and never move it. A predictable slot ('every Tuesday at 8am') outperforms a better-written issue sent at random times, because opens are a habit before they are a decision.
- 3
Build a reusable issue template and a subject-line bank
Create a beehiiv template with fixed sections so you never design from scratch. A durable structure for most newsletters: (1) a 60-90 word personal intro you always write yourself, (2) the main piece (one idea, 400-700 words), (3) 3-5 curated links with one line of your take each, (4) a single clear CTA.
Separately, keep a running subject-line bank. Ask Claude once: 'Here is my newsletter promise and three past issues. Generate 20 subject-line patterns that fit this voice - curiosity-driven, specific, under 45 characters, no clickbait.' Save the winners and reuse the patterns.
40 minOutput: Locked issue template plus a bank of 20 subject-line patternsTools: beehiiv, Claude - 4
Curate the week with Perplexity, then pick the one idea
Open Perplexity Pro and run: 'Surface the 8-10 most significant developments in [your beat] from the last 7 days. For each, give the source link, one-sentence summary, and why it matters to [target reader]. Prioritize primary sources over aggregators.'
From that list, pick ONE idea to be the main piece and 3-5 links for the curated section. The discipline is one idea per issue - newsletters that try to cover everything read as a firehose and get skimmed then unsubscribed.
Perplexity - the interface you'll work in for this step. Screenshot of the tool's own UI, not our results. 15 minOutput: One main-piece idea plus 3-5 curated links with sourcesTools: PerplexityTip: Always constrain Perplexity to 'last 7 days' and 'primary sources.' Without the recency and source-type constraints it drifts to older, general-knowledge answers that make your newsletter feel behind.
- 5
Draft the main piece and the link blurbs with Claude
Paste the curated research into Claude. Prompt: 'Using only the sources below, write the main piece for my newsletter. 500 words max. Voice: [describe or paste a past issue]. One clear point of view. Include one specific number or example from the sources. Do not use the words revolutionary, seamless, or game-changing. End on a single actionable takeaway.'
Then: 'Write one-line takes for these 4 links in the same voice - what it is, why it matters, in under 20 words each.'
Read as it generates and fix the voice inline. This produces the connective tissue; it does not produce your intro or your take.
Claude - the interface you'll work in for this step. Screenshot of the tool's own UI, not our results. 20 minOutput: Draft main piece plus curated link blurbsTools: ClaudeTip: If a paragraph sounds like AI, paste it back with: 'Rewrite in a more conversational voice, cut transition words like however and therefore, and add one concrete detail.' Two passes usually clears the tells.
- 6
Write the intro and subject line yourself, then edit
Write the first 60-90 words by hand every single time. The intro is the most-read part of any issue and the fastest AI tell to spot; owning it is what separates a newsletter people forward from one they filter.
Pick a subject line from your bank, adapt it to this issue, and write one preview text line. Do a final editing pass: cut filler, add your take where the AI stayed neutral, verify every stat against the source link.
20 minOutput: Final issue: hand-written intro, chosen subject line, verified body - 7
Schedule, then repurpose the issue into 3-4 social posts
Schedule the issue in beehiiv for your fixed slot. Then reclaim distribution: paste the final issue into Claude with 'Turn this into 3 short posts for X and 1 for LinkedIn. Keep my voice. Each post stands alone and ends with a soft nudge to subscribe.' Drop a header or quote graphic from Canva if the platform rewards visuals.
This repurposing loop is how the newsletter grows without a separate content calendar - every issue becomes a week of social that points back to the signup page.
15 minOutput: Scheduled issue plus 3-4 social posts driving signupsTools: beehiiv, Claude, Canva
Most newsletter advice stops at 'pick a niche and be consistent.' The problem is never the niche. It is that a solo writer spends 5-6 hours per issue, burns out by week 7, and the newsletter quietly dies. This workflow is the end-to-end system that keeps the cadence alive: it sets up the platform and welcome automation once, then compresses each weekly issue into a 90-minute research-draft-edit-schedule loop. AI does the heavy lifting on research aggregation and first drafts; you keep control of the subject line, the intro, and the point of view, which are the three things that actually drive opens and replies. The stack costs $63/mo required, $83/mo with the optional research and design tools.
What running a newsletter with AI actually looks like in 2026
Two things changed the economics of newsletters. First, platforms like beehiiv folded growth tooling (referral programs, recommendation networks, boosts, ad network) into the base product, so a solo operator no longer stitches together five tools. Second, LLMs got good enough to turn a pile of sources into a coherent draft in one pass, which moves the bottleneck from writing to curation and voice. The failure mode also changed: fully AI-written newsletters get unsubscribes fast because they read generic and add no signal a reader could not get from a search. The winning pattern is AI-assisted, human-owned - AI drafts the connective tissue and the summaries, you own the take, the subject line, and the first 80 words. This workflow is built around that split.
Stack cost breakdown
Public list prices as of July 2026. Optional tools are marked in the notes.
| Tool | Plan | Monthly cost | Notes |
|---|---|---|---|
| beehiiv | Scale | $43/mo | Required. Hosting, automations, segmentation, referral program. |
| Claude | Pro | $20/mo | Required. Drafting, subject lines, repurposing. |
| Perplexity | Pro | $20/mo | Optional. Sourced curation and fact-checking pass. |
| Canva | Free | $0 | Optional. Header graphics and social snippets. |
| Total | $63 - $83/mo($63 required, $83 with optional tools) | ||
Email me this stack as a checklist
Every tool, the plan to pick, and the monthly cost - in your inbox.
Real usage
What people actually run
No usage reports yet - be the first to share what you run. Tell us your real stack, your actual monthly cost, and any tools you swapped.
Sample prompts and a welcome email that earns replies
These are the exact prompts and the welcome email pattern behind the workflow. Swap the bracketed variables for your beat and voice.
Welcome email 2 (day 3) - the reply-getter
Subject: quick question, [first_name] You signed up for [newsletter] a couple days ago - thanks for that. So I write the right things: what are you hoping this helps you with? One line back is plenty. I read every reply. Meanwhile, the most-shared issue this year is here: [link]. Talk Tuesday, [your name]
Note: Under 60 words. The single question is the point - replies in the first week are the strongest deliverability signal you can send an inbox provider.
The weekly research prompt (Perplexity)
Surface the 8-10 most significant developments in [beat] from the last 7 days. For each: source link, one-sentence summary, and one line on why it matters to [target reader]. Prioritize primary sources (company posts, filings, original reporting) over aggregators. Flag anything that contradicts last week.
Note: The 'flag anything that contradicts last week' line is what surfaces the contrarian angle that makes an issue worth opening.
The repurposing prompt (Claude)
Here is today's issue. Turn it into 3 standalone posts for X (under 280 chars each) and 1 for LinkedIn (under 120 words). Keep my voice - direct, specific, no hashtags. Each post makes one point from the issue and ends with a soft line inviting a subscribe. Do not summarize the whole issue; pull the sharpest single idea for each post.
Note: Standalone is the key constraint - a post that requires the reader to 'read the full issue' converts far worse than one that delivers value on its own and lets the subscribe be optional.
Adjust for Your Situation
If you plan to monetize with a paid tier
Stay on beehiiv (it takes 0% of paid subscription revenue, unlike Substack's 10%). Structure free vs paid as: free gets the main piece, paid gets the main piece plus a deeper how-to section, archive access, and a monthly subscriber thread. Turn on paid only after ~1,000 engaged free subscribers - converting a tiny list wastes the launch moment. Expect 2-4% free-to-paid within 90 days.
If you are starting from zero subscribers
Start on beehiiv's free Launch plan (up to 2,500 subs) and drop the required cost to $20/mo (Claude only) until growth justifies Scale. Lean hard on the Recommendations network and the social repurposing loop for the first 500 subscribers, since paid acquisition rarely pays back on an unproven newsletter.
If your beat is fast-moving news
Move to twice-weekly and run the Perplexity curation step daily into a running note, so issue assembly is just selection, not research. Add a one-line 'what changed since last issue' at the top - recency is your whole value proposition on a news beat.
Swap options
Drop-in substitutions if a tool does not fit your budget or stack. These trade cost or effort for the recommended setup.
| Swap out | Use instead | When |
|---|---|---|
| beehiiv | Kit (ConvertKit) Creator ($39/mo) or Substack (free, 10% of paid revenue) | You want Kit's automation depth, or Substack's built-in discovery and zero fixed cost while under ~$500/mo in paid revenue |
| beehiiv Scale | beehiiv Launch (free, up to 2,500 subs) | You are pre-launch or under 2,500 subscribers and do not yet need automations or branding removal |
| Claude | ChatGPT | You already pay for it; re-prompt the voice constraint on each section |
| Perplexity | Manual Google research plus saved sources | Your beat is one you already read daily and you have the links on hand |
Common Pitfalls
- Letting AI write the intro. It is the most-read and most-recognized-as-AI section. Write the first 80 words yourself every issue.
- Publishing everything you found. One idea per issue. A firehose gets skimmed, then filtered, then unsubscribed.
- Moving the send day. Opens are a habit. A predictable slot beats a better issue sent at a random time.
- Skipping the welcome automation. Without the day-3 reply prompt, you lose the strongest early deliverability signal and half your would-be engaged readers go cold.
- Turning on paid too early. Converting a 200-person list burns the launch moment for a few dollars. Build to ~1,000 engaged free subscribers first.
- Not fact-checking AI summaries against the source link. LLMs paraphrase confidently and occasionally invert a stat; one wrong number in a curation newsletter costs trust you cannot rebuy.
Frequently Asked Questions
Can I skip beehiiv and just use a free platform?
How is this different from just using ChatGPT to write my newsletter?
Will AI-written content hurt my open or deliverability rates?
What open rate should I expect?
How long until this is worth the time?
Do I need Perplexity, or can I research manually?
How we built this workflow
Prices verified July 2026 from each vendor's pricing page: beehiiv Scale $43/mo, Claude Pro $20/mo, Perplexity Pro $20/mo, Canva Free. The 'dies at issue 7' failure point and the 40-50% open-rate range reflect common patterns across solo newsletter operators; your niche, list quality, and send consistency drive more variance than any tool choice.
Last updated July 7, 2026; prices verified at publication.