Monday morning our readers got an email about AEO.
Before lunch that same day, over 12,000 words were live on FranchiseFinePrint.com. Researched, written, fact-checked, cited, and published. No writer typed them. No human pasted them into the website.
The AI newsroom did it. Here's what that means.
Quick Scoreboard update first, because Mondays we talk and Thursdays we build, but the numbers don't take days off.
SUBSCRIBERS: 6. SPENT: $33.59 plus the domain. MADE: $0. HUMAN MINUTES: ~90.
Six subscribers and zero dollars might not impress your golf buddies. Keep reading anyway, because what happened this week is the part of this whole experiment I would tattoo on my forearm.
What an AI Newsroom Actually Is
An AI newsroom is a system where AI does the jobs a publishing team used to do. The researcher who digs up sources. The writer who drafts the story. The fact-checker who verifies every claim. The copy editor who enforces the style guide. The web person who loads it into the site and hits publish.
In our newsroom, all of those jobs are done by Claude. One human remains, and that human is me. I do two things. I make decisions and I approve or reject work. That's the whole job description. Editor-in-chief, not writer.
Here's what our newsroom did on its first day:
- Researched six different franchise topics using six parallel research agents, with orders to verify every source by actually loading the page it came from
- Pulled 545,751 loan records from the U.S. government's own small business loan database and computed franchise default rates itself, instead of trusting somebody's blog post
- Wrote six articles totaling about 12,000 words, each with the answer in the first 100 words, FAQ sections, and definitions for every piece of jargon
- Added 77 inline citations, meaning every factual claim links to the document it came from
- Ran every article through the website's built-in editorial checker, which scans for missing sources, hype language, and buried answers, and passed clean on the first try
- Sent me the drafts, took my edits (I made it rewrite all six intros and tighten the citation format), and then published all six articles to the live website in three seconds
I reviewed. I redlined. I said "go." That was my whole contribution, and the site went from six placeholder pages to a real publication before lunch.
One of those articles, by the way, reveals which famous barbecue franchise had 20% of its government-backed loans written off. The newsroom found it in the government's own files. That's the caliber of content this thing produces on a Monday.
Why We Hired Claude (And Not the Shiny New Thing)
The newsroom needed an engine, and I had three candidates.
I'll be honest. I thought hard about using Grokbot for this, because I know people want to hear about it. It's the new toy. It would have made a great subject line.
But I've already said publicly on Twitter that I don't recommend it, and I'm not going to run my company on something I wouldn't recommend to you. Here's the simple truth. There is nothing Grokbot can do for this build that Claude or Hermes can't do. And they do more, and they do it better. Choosing tools by novelty instead of capability is how you end up rebuilding everything in six months.
Hermes was the serious contender. It runs on my own server around the clock, and I've spent months training a profile named Nikki that writes in my voice. But that's exactly why Hermes lost this job. FranchiseFinePrint isn't supposed to sound like Justin Brooke. It's a publication with its own voice, its own style rules, its own editorial standards. The newsroom needed to write in the publication's voice, not mine. Hermes will get its own spotlight later in this series, because an always-on server doing scheduled work is a superpower we'll want eventually.
Claude won for four reasons. It already runs my CMO HQ, the file-based marketing headquarters my whole company operates from, so the newsroom got its own department folder inside a system that already existed. It supports scheduled tasks, so the newsroom can run on a calendar instead of waiting for me. It was already connected to Kit, my email platform. And it already had the AEO Writer skill loaded, the writing playbook I broke down on Monday.
One more thing about that skill, because this matters. A skill is just a plain-text instruction file. It's an open format. The AEO Writer works in Claude, but you could hand the same file to ChatGPT, Hermes, or yes, even Grokbot, and it would follow the same playbook. The engine is swappable. The system is the asset.
Continue with Build Notes+
This is the free preview. The complete step-by-step guide and supporting files are available to Build Notes+ members.
