Run a weekly local newsletter with a six-Bot team
The Arlington Bagel, reported at about 6,000 weekly readers, runs research, compilation, editing and email on six Grok Bots that replaced an intern.
Explain it simply
A weekly newsletter for one town is put together by six AI assistants, each with one job: research, collecting stories, editing and answering email. A lead assistant coordinates them and reports to the owner. Together they took over work an intern used to do.
What was done
Billy Howell started with one Chief of Staff Bot and gave it access to Notion, Slack and Gmail. Its first job was an audit: define the newsletter’s mission and name the two or three roles that matter most for revenue.
The write-up's 'earn your agent' rule: run a workflow with the Chief of Staff until it works, and only then give it a dedicated Bot.
It also recommends routines for the daily and weekly work, and a five-line daily report from each specialist to the Chief: what shipped, what's stuck and what needs a human.
How it went
Per the write-up, six Bots now cover research, content compilation, editing and email correspondence, replacing a human intern.
- No revenue, open-rate or time-saved figures were given for the newsletter.
- This is a secondhand write-up by Stork.ai, not Billy's own account.
- Greg Isenberg, quoted in the write-up, advises keeping Grok Bot on one project; running several businesses at once lets context bleed and burns through usage.
Prompt
You are Chief of Staff for [newsletter], a weekly newsletter about [topic or town] for [audience].
Read our Notion, Slack and Gmail. Write a one-page audit: what we publish, each step and how long it takes, and where revenue comes from.
Recommend the two or three Bots that would save the most time or earn the most first, with a one-paragraph job description for each.
Don't create Bots, send email or change anything until I approve.Setup notes
- Start with the Chief of Staff only, with read access to Notion, Slack and Gmail.
- Run each workflow with the Chief until it is reliable, then hand it to a dedicated Bot.
- Add daily and weekly routines, and have every Bot send the Chief five lines a day.
- Keep the send of each issue behind your approval.
Business fit
Who this helps, and how:
- CreatorsNewsletter writers hand off sourcing, first drafts and reader email while keeping the final edit.
- Local & serviceA local business can run a neighborhood newsletter as a marketing channel with the same team.
- AgenciesNewsletter agencies can template this per client; one account per client avoids context bleed.
Related
- Start a local newsletter run by a small team of BotsIncome automation
- Evidence grade BCurate newsletter sources and first drafts with a writer BotGrok Bot
- Evidence grade CLet Claude Code hand X research to Grok Bot mid-taskClaude Code + Grok Bot
- Evidence grade BMake launch and product animations with Claude in code, and budget for follow-upsClaude
Similar tools
Other tools for this job, and how they differ. Chosen by our editors, never paid for.
- Claude
A writing assistant; one newsletter agency keeps its projects in Claude but found Grok Bot's curation stronger at scale.
Source: Moodboard
- Make
A visual builder for fixed-step content pipelines; reliable when the steps don't need judgment calls.
Stack: Grok Bot + n8n or Make: fixed workflows hand the judgment to a Bot
Evidence grade C means: A tool maker's case study, a promotional demo, or someone else's write-up. How we grade. Spotted a mistake? Suggest a correction.