You Don’t Need a Tech Team to Build an AI Workforce
Somewhere along the way, “AI workforce” started sounding like something only a startup with a Series A round could afford to build. Engineers. Infrastructure. A roadmap nobody outside the company understands.
That’s not what it took for me, and I don’t have a tech team. I have a marketing job at a staffing company. What I have is one workflow I got sick of doing by hand, a willingness to explain it in painful detail, and about a year of doing that same thing again with the next task, and the next.
You don’t need to build an AI workforce in one fell swoop. You need to build it one workflow at a time, starting with whichever one is costing you the most right now.
The first workflow
The one I started with was our podcast’s social media content. It had a lot of small, mechanical tasks in it and just a few moments that actually needed my judgment. Mostly repurposing existing content: pulling clips, writing captions, scheduling posts. Ninety-five percent of it didn’t need me specifically.
I talked to Claude about it. Sometimes I showed it screenshots of what I actually did. I explained the process the way you’d train a new hire on their first day: don’t assume it knows anything, spell out every step. From that, Claude built three skills. One pulled ten 1 to 3 minute clips from a full episode. One wrote social captions across four platforms, pulling from the transcript and what we know about our audience. One pushed everything out to our scheduler.
Doing all of that by hand used to take about 12 hours spread across three and a half days. Now I step in at three checkpoints: approving the clips, tweaking the copy, reviewing the queue before it goes live. That’s about 35 minutes of my time, while the rest of my week goes to work that actually needs me.
I built a few more agents the same way, one workflow at a time. Eventually I had Claude build an orchestrator, a kind of chief of staff, that I named Zoe. I don’t manage each agent individually anymore. I tell Zoe what needs to happen, and Zoe calls up the right agent and reports back when something needs my judgment or when it’s done.
There’s an important distinction buried in that process. When you’re first explaining a workflow, building the instructions an agent will follow, you have to treat AI like a junior intern. Don’t assume it knows where to look or what you mean. Spell it out. That detail is what makes the skill repeatable.
Once those skills are in place, that’s when those AI agents become a competent team.
A first workflow anyone can build today
You don’t have to start with something as involved as a podcast pipeline. One of my favorite beginner routines takes ten minutes to set up and it’s just about your inbox.
So many of us are getting pulled out of real work constantly by email notifications. Here’s the fix. Set up two routines, in Claude, Gmail with Gemini, or Copilot in Outlook, whichever you already use.
The first checks your inbox twice a day and summarizes what actually matters:
Summarize unarchived emails from the primary inbox, organize them into action-oriented categories, and exclude promotional and non-essential content, and send it to me via chat.
I run mine at 10 a.m. and 3 p.m.
The second flags anything genuinely urgent the moment it lands, so you can turn your notifications off entirely and trust it to interrupt you only when something actually needs you right now.
Then I turned my notifications off. Now I check email on my own schedule, twice a day, plus whatever the urgent-flag routine surfaces. That’s it.
The fear that stops most people, and why it didn’t hold up
Before I turned notifications off, I ran what I’d call a catastrophization check. What’s the actual worst case? I miss something urgent for a few hours. Unlikely, and if it’s genuinely urgent, someone’s calling or messaging me directly, not waiting on email. Could I survive that? Yes, easily.
It wasn’t perfect out of the gate. A few things slipped through the first couple of days, mostly important-but-not-urgent items that didn’t get flagged. I just went back in and adjusted the instructions. Within a few days it was running smoothly.
No one has even asked about an email I might have missed, much less fussed at me about it.
The version of this you can do this week
Here’s the version of this you can actually do this week, no matter what your job looks like.
Step one: Open Claude and tell it who you are and what you do. Give it five things you love about your job and five things you hate.
Step two: Ask it to interview you, at least 20 questions, one at a time, until it’s 99% confident it understands your situation. Then let it explain exactly how it could take over the tasks eating your time without needing your expertise.
Step three: Pick the one workflow costing you the most, and either build it out with Claude directly or download The Wizard and let it walk you through the whole process.
You don’t need a tech team. You need one honest conversation about what’s actually draining you, and the willingness to hand the first piece of it off.