How to Run a One-Person Newsletter With AI Agents: What Three Real Operators Documented
A weekly newsletter eats a day or more of research, drafting, promotion and inbox work. Three solo operators documented how they cut that with Claude and OpenClaw, including one agent that wiped a database. Here is a setup you can copy and what it costs.
The newsletter that quietly takes your week
You publish one email a week. The writing is two hours. The other nine hours go to reading sources, picking a topic, building the social posts that drive signups, sorting reader replies and checking what worked. That is why so many solo newsletters stop at issue 14.
Three operators in the site's directory attacked that second pile with AI, and their results differ enough to be instructive. John Brewton reports going from a 2,200 dollar annual run rate in January 2026 to a roughly 200,000 dollar annualized pace in five months, with 5,861 subscribers and 266 paying, using Claude Cowork, Claude Code, Perplexity, Notion, Substack and Canva. Claudia Faith reports cutting her weekly Substack Notes planning from about 90 minutes to roughly 20 with a Claude Code agent that reads her own engagement data. Jenny Ouyang ran two OpenClaw agents on 12 scheduled jobs for six weeks at close to zero hosting cost. All of these are self-reported and unverified, and the revenue figures are the exception rather than the baseline for a solo newsletter. The workflow patterns are the useful part.
What each operator automated
Brewton's setup splits the work by tool. Perplexity does the raw research. Claude turns research into drafts and design assets, with Cowork for broad workflow help and Claude Code for structured tasks. Notion holds the operating notes and Substack publishes. He also watches which individual posts convert paid members, because one post reportedly converted 85 paying community members in a single day, so results are lumpy.
Faith's agent is narrower and easier to copy. It starts from a prompt she already liked, then adds what the prompt could not do: it scrapes her own Substack engagement data with Puppeteer, feeds it to Claude Code through MCP, picks topics from what resonated and drafts 21 Notes for the week. It surfaced a useful surprise: a Note with 34 likes brought in more subscribers than one with 266. Likes are not signups.
Ouyang's agents handle inbox processing, article indexing, research digests and social posting on a schedule, with Telegram as the control panel. Her most useful contribution is the failure story: while debugging, one agent dropped every table in her database. She documented it anyway. Treat that as the cost of giving an agent write access.
A worked example: a weekly newsletter for local contractors
Say you write a Thursday newsletter for 2,000 readers who own small contracting businesses. Before AI, the week looks like this: three hours reading industry news and permit updates, two hours writing, two hours making five social posts, an hour on replies and stats. Eight hours.
After: a Monday research digest arrives by 7 a.m. (30 minutes to read and choose the angle), Tuesday you dictate three real stories from your own week (20 minutes), the agent produces a first draft, you rewrite the opening and cut the filler (60 to 75 minutes), Wednesday the agent drafts the week's short posts and you approve them (20 minutes), Friday it summarizes replies and last week's stats (20 minutes). You land near three hours. Do not expect more than that; the stories and the opinions are the product, and they stay yours.
Step by step: set it up in a weekend
Step 1: Write a voice document before you automate anything
Open a Claude project (Pro is enough) and paste in five of your best past issues. Ask it to write a one-page style guide: sentence length, what you never say, how you open, how you close, three phrases you overuse. Edit it by hand until it sounds like you. Save it as a project file. Every later step reads this file, and a vague one gives you vague drafts.
Step 2: Build a Monday research digest
Choose a research tool and give it a fixed source list: six to ten sites, three competitor newsletters, two subreddits. Ask for a digest of ten items, each with a link, two sentences on why it matters to your readers and a rating of how surprising it is. Run it by hand for two weeks. Only schedule it once the digest is consistently worth reading. If you use Claude's scheduled tasks or an OpenClaw cron job, send the result to your inbox or to Telegram so you see it without opening anything.
Step 3: Dictate raw material, then draft
Talk to your phone for ten minutes about what happened this week: a customer call, a mistake, a number you were surprised by. Paste the transcript and the chosen digest items into Claude with the voice document and ask for a first draft with a specific structure: hook, one story, three practical points, one opinion. Your job is to rewrite the first two sentences and the ending, replace anything generic with something that happened to you, and delete anything you would not say out loud.
Step 4: Turn the issue into short posts
Ask for seven posts from the finished issue, each with a different angle and none longer than 80 words. This is where Faith's pattern pays off: before drafting, export last month's engagement and signup numbers and tell the model which posts actually brought subscribers, not just likes. If you cannot export the data, copy the top ten posts by hand into the prompt. Post the drafts yourself or schedule them in your platform.
Step 5: Sort the inbox with read-only access
Reader replies are gold and also a chore. Connect Claude to Gmail and ask for a Friday summary: questions that deserve a personal answer, complaints, testimonials, story ideas. As of November 2026 Anthropic's Gmail connector is read-only, so Claude can search and summarize but cannot send, which is exactly the safety margin you want here. You write the replies.
Step 6: Add one guardrail before any agent can write
If you move to a scheduled agent that edits files or databases, give it a copy, not the original. Keep a nightly backup of your subscriber export and your drafts folder. Ouyang's dropped tables are the reason. And keep publishing a manual step.
What this costs
Claude Pro is 20 dollars a month, or 17 dollars a month on annual billing (200 dollars up front), as of November 2026. Substack is free to start and takes 10% of paid subscription revenue plus card processing fees. beehiiv has a free plan up to 2,500 subscribers; its paid Lite plan is 59 dollars a month on monthly billing or 49 dollars annually at up to 1,000 subscribers, rising to 79 dollars a month at up to 2,500 on monthly billing, and it takes 0% of paid subscription revenue, though Stripe's 2.9% plus 30 cents still applies. If you add OpenClaw, the software is open source and you pay for model usage and hosting; Ouyang reports close to zero hosting on a free cloud tier. A sensible starting stack is 20 dollars a month for Claude, a free newsletter plan and a research tool you already pay for.
When this is a bad idea
If your newsletter is a personal essay, automating the drafting will make it worse and your readers will notice. Use AI for research, social posts and inbox work, and keep writing yourself. If you do not yet have a clear audience and angle, no workflow will rescue you. And be careful with the numbers in these stories. Brewton's pace came from advisory, coaching and community revenue alongside the newsletter, not from the AI writing posts. The tools saved him time. The business was already there.
Frequently Asked Questions
Can AI write my newsletter for me?▾
It can write a competent first draft, and that is usually the part that saves the least time. The best use is research, repurposing and inbox sorting, with you writing the opening, the stories and the opinions.
What is the cheapest setup to run a newsletter with AI?▾
Claude Pro at 20 dollars a month as of November 2026, a free Substack or beehiiv plan, and a written voice document. That covers research, drafting help and social posts without running any server.
Is Substack or beehiiv better when you use AI tools?▾
Neither is better at AI. Substack is simpler and takes 10% of paid revenue; beehiiv charges a monthly fee from 59 dollars on monthly billing for paid plans, takes 0% of paid subscriptions and has a free plan to 2,500 subscribers. Pick on your revenue and list size.
Will readers know the newsletter is AI-assisted?▾
They will if every issue reads generic. Specific stories, real numbers from your week and strong opinions are what readers pay for, and AI cannot supply those for you.
Is it safe to let an AI agent publish my newsletter automatically?▾
Not yet for most people. Ouyang documented an agent that dropped every database table while debugging, which shows how far a small mistake can travel. Keep publishing manual and keep backups.