The Workflow
It’s 7am. Two blog posts I didn’t write are sitting in a folder, waiting for me to decide if they’re any good.
I built a content pipeline that drafts before I wake up. Not “AI helps me write.” It scans, picks, drafts, and hands me the near-finished thing while I’m still asleep.
Step 1 — Scan the field (6am): A script reads the RSS feeds of 12 YouTube channels I picked because they cover the work my readers actually do. No API key, just the free feeds.
Step 2 — Rank by who I’m writing for: It pulls the transcripts and ranks the topics by how relevant each is to a solo operator using AI as their team. The winner becomes today’s topic.
Step 3 — Draft in my voice (7am): A second script takes that topic and writes three things at once: a blog post, a Substack post, and a Note. It loads my full voice profile first, so the draft doesn’t read like a press release.
Step 4 — Flag its own tells: Before it saves, it scans its own draft for the things that give AI away and prints the warnings at the top of the file.
Step 5 — I review (5-10 minutes): I add the one real example only I have, fix what it guessed wrong, cut what’s flat.
Step 6 — Publish with one command: For the blog, one command stages, commits, merges, and deploys. Thirty seconds after I approve, it’s live.
This week it produced the two posts on the blog: one on using NotebookLM for client research, one on drafting a landing page in a single sitting. I didn’t write the first draft of either. I edited them.
The outcome I didn’t expect: the bottleneck stopped being “write the post” and became “decide if the post is worth publishing.” That’s a much better problem to have.
What Broke
The first version couldn’t fetch a single transcript. It would find the videos, then die on every attempt to read them.
Two failures stacked on each other. The machine’s Python had a certificate problem, so every call to the feeds threw a security error. And the transcript library had changed its API in a version I wasn’t using, so the method I called didn’t exist and threw an error on every video. I was reading code written for a different version of the tool than the one installed.
The fix was beyond my coding ability, so I did what I always do. I asked Claude to figure out what broke, fix it, and explain it to me like I’m five. It did. Then more errors showed up, something about the JSON not being clean, so I handed that to Claude too.
The lesson isn’t about certificates or JSON. It’s that most of what breaks in a build like this isn’t the smart part, it’s the plumbing. The AI writing was the easy 20%. The boring 80% was getting three tools built by different people in different years to talk to each other, and that’s exactly the part I can’t do myself. So I don’t. I describe what’s broken and let Claude turn the wrench.
Time Ledger
- Time saved: 4-6 hours per post. That’s what it used to take me to pick a topic, research it, draft, review, and publish. And that number doesn’t count the procrastination, the days I’d spend dreading the brainstorm-and-draft part before I ever started.
- Time added: Two days to build the pipeline, plus 5-10 minutes of review per draft each morning.
- Net: Underwater this week. Ahead within a month if it keeps drafting daily.
The number that matters isn’t the hours saved. It’s that the dread is gone. The brainstorm-and-draft phase was the part I put off for days, and now there’s a draft waiting instead of a blank page.
The Prompt File
The core of it is the instruction the drafting step runs, with my voice profile loaded in front. You can use the same shape to get drafts that sound like you instead of like everyone.
PROMPT FILE
You are drafting in [YOUR NAME]'s voice. Their full voice profile is above. Follow it exactly.
Write a [blog post / Substack post / short note] on this topic:
[TOPIC]
Source material:
[TRANSCRIPT OR NOTES]
Rules:
- Direct, specific, flat-told. Sarcasm as punctuation, never decoration.
- No em dashes. No motivational filler. No generic AI hype. No lifestyle flexing.
- Open in a concrete moment, not "In this post I'll..."
- End with an invitation to reply, not a pitch.
Before you finish, scan your own draft and flag any line that has:
- an em dash
- a phrase that could have been written by anyone about anything
- hype words (game-changer, unlock, supercharge, revolutionize)
Print the flagged lines at the top so I fix them first.The trick that made the drafts usable wasn’t a better model. It was loading the voice profile before the topic, and making the tool grade its own writing against the rules before handing it over.
Manager’s View
Ask yourself: if you run your own shop, how many days last month did you publish nothing because you were staring at a blank page?
Most solo operators don’t have a content problem. They have a starting problem. The work of writing isn’t the hard part. The hard part is facing the empty document at 7am with a full day already pressing on you, so the post doesn’t happen, and a week goes by with nothing shipped.
The fix isn’t more discipline. It’s removing the blank page. You don’t need a 12-channel pipeline to do it. You need one standing prompt that turns yesterday’s work, or a video you’d have watched anyway, into a draft you react to instead of a page you fill. Delegating the first draft is the whole game. You keep the judgment. You hand off the staring.
Field Notes
- The pipeline surfaced a NotebookLM angle I might have skipped on my own, and it became one of this week’s two published posts.
- The Robot Wayne scanner caught em dashes in a draft I’d already read twice and thought was clean. I don’t trust my own eyes on that anymore. I trust the scanner.
- The whole thing runs on free YouTube RSS feeds and a cron job. No paid API, no automation platform. The “team” that drafts my content is a text file and a schedule.