Nobody Warned Me How Boring AI Agents Actually Are

Everyone's talking about multi-agent AI workflows like they're some kind of digital dream team — agents talking to agents, handing off tasks, running your business while you sleep.
I want to tell you what it actually looks like from the inside, because I built one, and it is nowhere near as dramatic as the LinkedIn posts make it sound.

Where this started

A few months into my pivot, I was drowning in one specific problem: every blog post I wrote needed to become five other things. A newsletter edition. A LinkedIn post. A carousel. CMS metadata. An excerpt that didn't sound like it was written by a robot.
I was doing all of it manually, in order, every single time. Draft the post. Open a new chat. Re-explain my voice. Draft the newsletter version. Open another chat. Re-explain my voice again. You get the idea.

That's when I stopped thinking about "using AI" and started thinking about building a role, not just sending a prompt.

The insight: agents are just roles with memory

Here's the part nobody tells you plainly — a "multi-agent workflow" isn't some complex piece of engineering. It's closer to hiring, except the hire is a Claude Project with a very specific job description and a lot of context already loaded in.
My first one is what I call the Writer Agent. It's not a separate piece of software. It's a Claude Project that already knows:

• My voice across three different content types
• My offer ladder and how CTAs should land
• My formatting rules down to hashtag limits
• What "sounds like Sri" versus what sounds like generic AI output

When I hand it a blog brief, it doesn't just write a post. It writes the post, then hands me the CMS package, then hands me the repurposing angles for the newsletter and LinkedIn. One brief in, five deliverables out, all in voice, without me re-explaining myself every time.
That's the whole trick. Not magic. Just a role that remembers what it's for.

Where it's still messy — because it is

I'll be honest with you, because that's the deal I've made with myself about this blog: I am not running a slick three-agent pipeline where agents pass work to each other automatically. I'm not there yet.
I have the Writer Agent working well. I'm still building out an Intelligence Agent — one whose job is research and pattern-spotting before the Writer even starts — and a Conversion Agent, whose job would be tightening CTAs and offer language. Right now those two are half-built ideas in a Claude Project, not finished systems doing real work.
If I told you I had a fully autonomous multi-agent operation running my content calendar, I'd be lying to you, and I promised myself I wouldn't do that on this blog. What I actually have is one agent doing its job well, and two more in progress. That's the honest state of it.

Why this still matters for you

If you're a coach, consultant, or solopreneur reading this and thinking multi-agent workflows are out of reach — they're not, but they're also not what the hype suggests.
You don't need five agents. You need one role, clearly defined, with enough context that it stops asking you to repeat yourself. That's it. That's the whole unlock.
Before you build anything with "agent" in the name, ask yourself: what's the one task I redo, from scratch, every single time — and what would it take for something to remember how I want it done?
That question is the actual starting point. Everything after that is just building out the role, one piece at a time, the way I'm still doing with mine.

Where to start if this is you

If you're staring at your own repetitive tasks and can't see the workflow underneath them, that's exactly what a Workflow Audit is for — mapping what you're doing before you try to automate any of it. And if you want to go deeper on the "how" behind building a system like this yourself, that's what I walk through inside the Connect Framework Course at sklearningonline.com.

Start with one role. Let it get good at one thing. The rest can wait.