https://lnkd.in/p/gTnTXdY9

I started the newsletter build on 5 June, and as of today I have 762 sub. I made my first ad revenue - $80 - two days ago. I think people are hungry for local information hubs that pull 50 facebook groups together without the facebook bs that goes with them, all into one place. I'll talk more about this build and what I did, but it started with a tweet that I copy and pasted into claude code. __________________________ Can you build this project out in a folder? I'd use substack. Call it the Barrhaven Bugle. Confirm spelling. Task second brain, researching the idea to flesh it out and save findings. If I had to start one AI side hustle in 2026, this would be it: a local newsletter that pulls in 2k a month and runs entirely by a team of four AI agents. The founder (Lucas Walter) has never written a single edition. This is a copy-pasteable system that could be applied to any city in the world. Here's the agent setup: 1. A growth engineer agent scrapes every local news site, subReddit, and event calendar at 6:00 a.m. daily. 2. A content director reads the database and writes the weekly newsletter in his voice every week. 3. A sales director handles every inbound advertiser email back-and-forth, pitching AI-generated ad creative. 4. A CEO agent orchestrates all three and reports back to him. Results from Lucas's newsletter: Spokane Pulse, 7,400 subscribers, 47.5% open rate (industry average 20% to 30%), 11% click-through rate, 2k a month in ad revenue, and growing under 4 hours a week of human in the loop. Now imagine running the same system in your city. I link to the Spokane Pulse in the comments so you can check it out for yourself. ___________________________ From that tweet I just started building it out. Now I ultimately ended up with a different system than this. That looks much like a news aggregator. I do have seven Hermes agents doing it. I am pushing out five-question interviews to people by email and building features. I've added a cartoon daily, a crossword, and a swipe deck pulse.

@Kari Davis quick one I thought the group might find useful. Now that Fable 5 is staying on as my assistant, I had it map out something I'd only ever kept in my head: how Claude in Chrome and headless Playwright actually divide the work in my setup, and how the system decides which one to reach for on any given job. The short version is that it stopped being a "which tool is better" question. They're two engines for two kinds of work. Anything hands-on — verifying a deploy, checking a page behind my own logins, a client walkthrough — runs through Claude in Chrome. Anything unattended and repeating — my scheduled monitoring, research pulls, bulk work — runs on Playwright, because Chrome can't sit in that seat at all. Build on one, ship on the other. The attached brief lays it out against my real workflows, plus a section on how the same split turns into client offerings. Thought it might be of interest.

https://youtu.be/5teG6ou8mWU