All plays › Coaches and creators

Coaches and creatorsClaude Code

Newsletter ops that ate 12-plus hours a week now take about 10 minutes a day

Picked and checked by Olga Pearson, host of The Practical AI Show · Published

Result

self-reported

With a second newsletter live, hand-built ops (templates, polls, ad slots, A/B tests, link checks) would eat 12+ hours a week. After connecting Claude Code to beehiiv's MCP, the same ops take about 10 minutes a day. Team stays at 4 with 0 new hires while shipping 6 new issues a week.

Tom Alder (@tomaldertweets) runs Strategy Breakdowns and just launched a second daily newsletter, Strategy Screenshots. Rather than hire for the button-pushing, his team connected Claude Code to beehiiv's MCP the day it launched in March. Claude now builds editions, pulls subject-line test history, and sends sponsor proofs on a schedule. A human still writes every word and hits send. Post is marked #ad #beehiivPartner.

Who did it

Tom Alder (@tomaldertweets)Strategy Breakdowns newsletter (~$50.9k/mo stated in profile)Tom Alder (@tomaldertweets) on X · Nov 4, 2026

Try it now

  1. Connect Claude Code (or another coding agent) to your newsletter platform's MCP or API.
  2. Write one plain-English ask that builds tomorrow's edition: template, poll, ads, subject-line tests.
  3. Add a second ask that pulls past subject-line tests and summarizes what won.
  4. Schedule sponsor proof emails and day-7 / day-14 stats without typing them by hand.
  5. Keep a human writing the copy and clicking send. Time one week of ops before and after.
Copy-paste prompt
Build tomorrow's newsletter edition in beehiiv: use our usual template, add the poll, place the booked ads, and set up a 4-way subject line test. Then pull every subject line test we have ever run and tell me what wins. Do not hit send until I approve.

Make it run every week

A play works once. Turn it into a routine in three small steps:

  1. Run it once and check the result yourself.
  2. Give your AI a schedule. Tell it when to run this play (every week, or every month) and to message you with what it found before you act.
  3. Keep a log. One line per run: what was checked, anything flagged, what you did.

See how owners turn plays into systems →

What to watch out for

Self-reported; the X post is a paid beehiiv partner #ad. MCP access can change live campaigns, so keep send and sponsor emails as approve-first. Build it with Page: an archive page for each issue so new readers catch up without you pasting links by hand.

Did it work?

PageMotor keeps this site free.