The AI Newsroom.

Writing one good Substack note is easy. Writing 35 a week, every week, forever, is the thing that quietly kills your newsletter.

So I stopped writing them.

I built a tiny newsroom of 8 AI agents to do it instead. Last Wednesday it drafted a full week of notes before I woke up. It runs on its own every Wednesday at 6pm, the night before I publish my article. Eight agents, one job each. It costs about $8 a month.

And nothing goes out without me. I read and edit every note before it publishes. The system does the heavy lifting. I keep the voice.

One honest thing before we start. People hear "agent" and picture Hermes or OpenClaw - a bot that wakes up, decides what to do, and runs off on its own. This is not that. Mine is a workflow: eight specialized prompts, run in order by a script, with me approving in the middle. I call them agents because each has a single job and does it well. But it does not pick its own goals. It follows mine.

Why does posting 35 Substack notes a week break creators?

The bottleneck was never ideas, and it was never writing one note. It was volume, rhythm, and timing. Five notes a day, seven days a week. That is 35 notes, on top of the actual newsletter, client work, and a life.

Every growth guide says the same thing: "Post Substack notes consistently." True. And useless. Because consistency is the entire problem.

I did the obvious thing first. I solved the scheduling. Substack already has a scheduler, but you feed it one note at a time: paste the text, save a draft, pick a time, then do it all again. For 35 notes a week, that is soul-destroying. So I built a small tool that bulk-schedules from a CSV. One upload, and it creates all 35 drafts and their posting times at once, using Substack's own scheduler underneath.

That solved the busywork. It did nothing about what to write, or whether what I wrote was any good. Scheduling an empty calendar is still an empty calendar. The scheduler is the hands. The engine is the brain.

What are the 8 AI agents in the growth engine?

If I had hired humans to run my Substack notes, I would have needed a small team: researchers, a strategist, a writer, a coach. I did not hire people. I wrote eight prompts instead, gave each one a single job, and called the whole thing the growth engine. It works in three phases.

The growth engine: eight agents across three phases.

Phase 1: Parallel research (five agents at once)

Five agents act like a newsroom, all working at the same time, each pulling intelligence from a different place.

• The Past-Performance Analyst reads last week's actual numbers - likes, restacks, replies - and says what worked and what flopped, with real figures, not vibes.
• The Article Analyst reads my new article for the week and pulls out 10 to 14 angles worth turning into notes.
• The Evergreen Analyst mines everything I have ever published for timeless ideas, so the week is not all reactions to current news.
• The Competitor Analyst studies the top creators in my niche and spots patterns worth adapting. Adapt, never copy.
• The Audience Analyst reads my engagement heatmaps to find the best times to post.

Phase 2: Strategy and writing (two agents, in order)

• The Synthesizer (the strategist) turns all those notes into one weekly game plan, built on a fixed content mix: 40% from the new article, 30% evergreen, 20% competitor-inspired, 10% pure brand voice.
• The Writer takes that plan and drafts all 35 notes in my voice, each one scheduled for the right date.

Phase 3: Continuous improvement (one agent, on a loop)

• The Retro Analyst (the coach) runs after the week is over. It reviews how every note performed and writes the instructions for next week's team: fix the misses, double down on the wins.

That last one is the difference between a tool and a system. The first seven do the work. The eighth makes next week's work better.

You do not need eight agents to start. You need one good one (the writer) and a clear file describing how you sound. The other seven are how it gets better than you on a tired Tuesday.

How does the Writer agent draft a note in your voice?

The Writer is the agent people assume is the whole system. It is not. But it is the one that turns a plan into 35 finished notes, so here is exactly how it does that.

What it reads before it writes a single word

The Writer does not start from a blank page. Before it writes, it is handed a stack of context: the week's brief from the Synthesizer, the exact posting times from the Audience Analyst, the angles pulled from this week's article, the evergreen angles from my archive, the competitor patterns to adapt, my full voice file, and my "about me" with my real stories in it.

That last part matters. The Writer is not allowed to invent my life. If it writes a personal story, it has to pull from real details I have written down - real numbers, real places, real moments.

The Writer's quality is capped by the files behind it. Good voice file, good notes. Thin voice file, generic notes. The agent is a mirror, not a magician.

The seven shapes a note can take

A note is not just "a short post." For months I have tracked the notes that actually land for creators in my niche, and the winners almost always fall into one of seven shapes. The Writer works from these seven fixed formats, and every note has to be one of them.

• Imperative Command. Do this. A direct instruction.
• Bold Claim plus Reality Check. A strong statement, then the twist.
• Definitional Framework. Name a thing, define it in a fresh way.
• The Confession. A vulnerable admission that earns trust.
• Quick Tip. One small, usable thing.
• Ultra-Short Truth. Under 50 words. A single clean observation.
• Data Truth. A number that changes how you see something.

The point of fixed formats is rhythm. A feed of 35 notes that are all "bold claims" reads like a robot shouting. A mix reads like a person.

The house rules it cannot break

Here is the part I like most. The Writer is forced to live by the same rules I do:

• No two notes in a row use the same format.
• No two notes open with the same first line.
• The first sentence is always the hook. No warm-up.
• Specific numbers always. "884 subscribers," never "almost 900."
• No emojis. No em dashes. No closing call to action.
• A set mix of lengths every week - at least a few under 50 words, a stack of short ones, a handful of longer ones.

These are not suggestions in the prompt. They are hard constraints. If the Writer drifts, the rules pull it back. Steal this even if you never build the system: write your own rules down once - the things you would never publish - and you can hand them to any AI and get something that sounds like you instead of like everyone.

Watch one note get built

Say the week's plan calls for a personal story note tied to courage. The Writer opens my "about me," finds a real moment, and builds the note in four beats: the setup, the moment, what it taught me, then the line that hands the lesson to the reader.

So it might pull the time I landed in Costa Rica at 19, alone, unable to count to three in Spanish. The setup. The moment I realized no one was coming to translate for me. The lesson, that being lost in public is the price of learning anything fast. Then the turn to the reader: if you are four months into something new and crying, that is the part where it works.

It writes that as one tight note, around 150 words, in the Confession format, and stamps it with a posting time. Then it does that 34 more times, in different shapes, on different angles, never repeating an opener. What it cannot do is know whether any of it actually worked. That is the next agent's job.

How does the system learn to sound like me?

This is the agent I did not expect to love. The Retro Analyst, the coach, is what turns a clever drafting tool into a system that gets better every week. It runs after the week is over, once the notes have collected real engagement, and it reads three things most people never think to feed back in.

One: the numbers, scored the right way

The coach pulls the actual likes, restacks, and replies for every note. But it does not just add them up. It scores each kind of note on the thing that note was trying to do. A story note is judged on likes and replies, because its job is to make people feel something. An identity note is judged on restacks, because its job is to be amplified. A question note is judged on replies, because its job is to start a conversation.

Most dashboards average everything into one number, and that hides the truth. A note with 2 replies and 40 restacks did not fail. It did exactly its job. You just have to score it on the right scale.

Two: my edits, which are the real gold

Here is the part that surprised me. The coach reads the edits I made by hand - not the notes I approved as-is, the ones I rewrote before publishing. It treats every edit as a correction. It compares what the Writer drafted to what I actually published, and looks for the pattern: "She cut the throat-clearing opener from three notes." "She removed the closing call to action every time." "She shortened a two-line hook to one line."

Those patterns get written into a running voice file - a flat list of rules. Next week, the Writer reads that file before it drafts anything. The system does not get better because I tune it. It gets better because it watches me. My edits are the training data.

The voice file is capped on purpose. It holds the strongest rules, not every passing whim. If a new correction contradicts an old one, my latest behavior wins and the old rule is dropped. It is a living style guide, written by my own red pen.

Three: a plan for next week

The coach does not just grade the past. It writes hypotheses for the future, and states them like bets. "If we run two identity notes next week instead of one, expect weekly restacks to grow about 80 percent, based on this week's numbers." Then it hands the next Synthesizer a short list of changes to make.

This is the difference between posting and learning. Most people post, glance at the likes, and move on. A simple weekly retro - even one you write by hand - compounds harder than any single viral note. And because I asked it to be a truth machine, not a hype machine, the coach is blunt. If a format flopped, it says so in numbers.

What should you automate, and what stays yours?

I stole my golden rule from a creator I read, Daria from AI Blew My Mind: automate the work you dread, not the work that is you.

Automated: the research, the timing, the first draft of all 35 notes, and the weekly retro. The heavy, repetitive, soul-draining volume.

Stays mine: the final edit, the approve button, and the voice. Nothing publishes without me reading it. The newsletter article itself is never touched by this system. That is the part I love, so I keep it.

And because I am a truth machine, not a hype machine, here is where it still fails:

• It over-rates its own work. The coach's grades are a starting list, not a verdict. I still decide what was actually good.
• It drifts toward generic when the week's article is thin. Garbage in, garbage out is not solved by AI.
• The timing is a guess. Substack does not tell you when your readers are online, so the Audience Analyst uses my own past engagement as a proxy. Useful, but not the same as truth.

None of these are dealbreakers. They are just the honest shape of the thing. Anyone who tells you their AI system runs itself perfectly is selling you something.

What does an 8-agent Substack engine cost to run?

The whole thing runs in the cloud on a schedule. It fires itself every Wednesday at 6pm, drafts the week, and emails me when the drafts are ready. My laptop can be closed. I can be asleep, or out, or on a train.

It is built on tools that are free or nearly free: a small web app on Vercel for the dashboard, a Supabase database to remember everything, and Claude doing all the thinking. Add it up and it costs about $8 a month - roughly $2 a run, once a week.

When I open the dashboard, I read the brief, edit the notes I want to change, and click one button: approve and push to scheduler. The engine hands the finished list to my bulk-scheduler as a CSV, and the tool creates all 35 drafts in Substack at their scheduled times in one go. This is not enterprise software. It is a folder of plain-text prompts and one small app. You could read the whole thing in an afternoon.

How do you build your own Substack notes engine?

Here is the honest path, in the order I would do it again.

1. Start with the scheduler. It is the simplest piece and it solves the most annoying problem first - the timing. Get comfortable handing it a list of notes and watching them go out on their own.
2. Add a writer. One prompt, one good voice file, and you have a first draft instead of a blank page. That alone changes your week.
3. Layer the rest of the team as you learn what you actually want. The analyst, the scout, the coach. You do not build all eight on day one. I did not either.

The three files that do 80 percent of the work are not code. They are your voice profile, your "about me," and your list of writing habits to avoid. The agents are only ever as good as those three files. Spend your time there. Do this tonight: write one file describing how you actually sound, then feed it to a single note-writing prompt. That is day one of your own newsroom.

The deal. I am giving the scheduler template away. Recommend the brisk. newsletter, and the scheduler repo is yours - the code, the setup steps, all of it. I am keeping the full engine private, because it is wired so tightly to my voice and my data that it would not help you as-is. But if you want to build your own version of the eight-agent engine, reply to the brisk. newsletter and tell me. If enough of you are interested, I will write up exactly how I set mine up.

Sources and further reading

• The Last Time You'll Write a Workflow - why systems beat one-off prompts
• Workflows. - the prompt to skill to scheduled workflow spectrum
• How to train Claude to write like you - the voice file is the whole system
• Claude Code documentation - Anthropic
• Supabase and Vercel - free-tier tooling behind the dashboard

A year ago, the notes were the part I dreaded most. Now they are the part I think about least. You can keep writing 35 a week by hand, or you can spend one weekend teaching a system to draft them, and get your Wednesdays back.

Recommend brisk., grab the scheduler, and go build your newsroom.