My content system produced every draft last week. On time, in my voice, with the images rendered and the comments already written.
Five decisions have been sitting in its queue waiting on me. The oldest is fourteen days old.
I built the thing to remove my bottleneck. It removed the one I was looking at.
So I went back through the last three weeks looking for the things that actually changed a situation for somebody, which is a different list than the things that got produced. Three came up. My system wrote none of them. All three were sentences I said out loud, in conversations, and two of them took under a minute.
What the system actually took off my plate
I want to be precise about this, because “AI does my content” is the kind of claim that sounds like either a boast or a confession depending on who’s reading.
Here is the real division: drafting is handled, and research reads the field and comes back with what people are actually saying this week, sourced. Voice matching is handled well enough that I stopped rewriting openings. Images render. Scheduling holds. The system will not publish anything without me, and that gate has never moved.
That’s a genuine amount of work gone. Ten months ago, most of a Tuesday went into one newsletter, a LinkedIn repurposing, and two Substack notes.
The shape of it, since a few of you asked after last week: every morning a batch gets drafted and lands in a dated folder with a queue file next to it. Each item has an ID, a status, and a line saying what it’s waiting on. Nothing moves out of that folder without me supplying the ID. When something publishes, the system writes back what actually happened, including when it failed, and I read that rather than assume the send worked. The interesting part is that almost all of the engineering went into the refusals: the checks that stop a thing from going out when a gate cannot be verified.
What’s left is smaller and much harder to hand off. Every item in that queue is a judgment call with two defensible answers. Keep pursuing a conversation that’s gone quiet, or let it close. Retire a tool that’s failed repeatedly, or keep trusting it. Approve a post the system has surfaced four separate times, or admit I’m never going to run it.
The system can draft all of those. It can argue both sides better than I can. It cannot decide, because deciding requires knowing which outcome I actually want, and I’m the only one who has that.
Two words, in a conversation I wasn’t managing
Late July. I was talking with someone I’ve met recently about what he was building. He had the experience, he had the track record, and he was describing his offer in a way that took four sentences and still left you unsure what you’d be buying.
I said two words, well, two that mattered: “Fractional CTO.”
That’s it. I didn’t write him anything. I didn’t build him anything. I named the thing he was already doing.
Eight days later he’d rebuilt his entire offer around it, had two people he trusts review the result, and sent the finished structure back to me. Along with a video he thought I should watch, which turned out to reframe how I price my own work.
I’ve thought about that exchange more than anything my system produced that month. Two words, from a twenty-year pattern library I didn’t consciously consult, and it reorganized someone’s business. Then the return came back around without either of us selling anything.
No model in my stack makes that call. The words themselves are easy. Knowing which two matter to this specific person, at this specific moment in his thinking, requires having sat in that conversation.
The call where I gave away the framework
Two weeks ago, a working session with someone trying to figure out where AI actually fits in her QA work at a large company.
She came in with the question most people bring, which is some version of “what should I use.” That question has no good answer, and answering it directly is how people end up with eleven tools and no workflow.
So I gave her a different one. Where do you want this process to be in six months, described as if it already works? Then we worked backwards from her answer.
Out of that came a decision rule she can apply without me. When the thing you want is a repeatable procedure you’ll run the same way every time, build a skill. When it needs to look at a situation and choose, build an agent. Most people build the agent first, then spend a month debugging judgment they never needed.
She left with a specific recommendation for her own workflow and a rule for the next twelve decisions. I left with a sharper version of the rule than I walked in with, because explaining it to someone with a real constraint is what exposes where it’s vague.
My system could have written a thorough article about skills versus agents. It could not have watched her describe her workflow and noticed that the future-state question was the one she needed.
The thing he’d already told me he needed
The third one is barely a sentence, and it’s the one I almost missed.
Someone described a problem to me in detail, as a side note to other things he was telling me about his business and how their business and team leverages AI. His team’s best AI work was stuck on one person’s laptop. Useful things being built, none of it reaching anyone else, and everybody who wasn’t already AI-literate getting more overwhelmed with each new tool.
Then he wished, almost as an aside, that he could get a daily digest of his meetings with risks flagged.
I’d been running exactly that since July. Every recorded meeting, full transcript rather than the vendor’s summary, decisions and commitments pulled out, anything needing a human pushed to a channel where I’ll see it.
Building it was never the valuable part. It already existed. The value was in hearing an aside as the actual request, and recognizing that the thing I run for myself every morning answered the problem he’d spent months trying to solve.
That’s pattern matching across two conversations that a transcript would have flattened into one line of small talk.
What these have in common
Each one took less than a minute of output. Together they produced more value than everything my system generated in the same period, and I say that as someone who genuinely likes what the system produces.
The common thread is that all three required being present while somebody else was thinking. Not retrieving information. Sitting in a live situation with enough context to know which of a hundred true things was the one worth saying right then.
Notice what none of them required. Speed wasn’t the constraint in any of them, and neither was volume or a better model. Two of the three were things I already knew and had already built, waiting for the moment where they applied to someone.
There’s a version of this that turns into a comfortable story about human irreplaceability, and I don’t believe that version. The models are getting better at more of this every quarter, and anyone telling you where the permanent line sits is guessing.
Here’s the narrower claim I’ll defend: right now, today, the constraint in my business is not production. It’s the number of live situations I can be genuinely present in, with enough context loaded to say the useful thing. My system expanded my output roughly fivefold. It expanded that second number by zero.
Which is why the queue keeps growing.
Where this leaves you
If you’ve built something that drafts for you, you already know the feeling. The relief lasts about three weeks and then you notice the work didn’t leave, it concentrated. What’s left is denser and it’s all yours.
None of that argues against building the system. Mine gave me back most of a day a week and I’d build it again tomorrow. It does argue for being honest about what the day is for.
I’ve started treating the queue as the actual job rather than the overhead. Five open decisions is not an embarrassing backlog, it’s the accurate measure of what only I can do. Fourteen days is too long, though, and that one’s on me.
Do this in the next ten minutes. Open whatever holds your undone work. Go through it once and mark every item that is genuinely a decision rather than a task, meaning two defensible answers and no amount of research settles it. Count them. That number is your real workload now. Everything else is production, and production is the part you can hand off.
Then take the oldest one and decide it today. The answer may well turn out wrong. It has been costing you attention every time you look at that list, and a decided-wrong is cheaper than an open-forever.
Mine was fourteen days old. I closed it this morning.
PS. If you’re staring at a list like that and most of it turns out to be production rather than decisions, that’s the gap I help people close. I map how the work actually runs today, build the pieces that should run without you, and stay long enough to see whether your team is still using any of it in month five. Reply to this email and tell me what’s on your list.
Get full access to G8N•AI at www.g8n.ai/subscribe
