My business runs on a workforce of eight AI employees. That's not a vision of the future or a thought experiment: all eight are working today, each with their own name, their own job, and their own personnel file. I'm a developer, and I still haven't written a single line of code myself in a year and a half. I manage.
Here's the complete workforce, with what each of them actually does.
The eight at a glance
Olaf, the lead scout. Olaf scans cities for local businesses with outdated websites, scores the finds, and sorts them into A, B, and C leads. For every lead, he delivers a briefing. He's running live across several cities.
Ralf, the website optimizer. Ralf takes Olaf's briefings and independently builds modern one-pagers as demos for each business. He's at 16 clients by now. Ralf and Olaf check each other's work: what Olaf delivers, Ralf challenges, and vice versa.
Sonja, office and admin. Sonja preps the new-client emails: when Ralf finishes a demo, she drafts the email to the business, in my voice. Nothing gets sent until I approve it.
Susi, content marketing and ads. Susi handles Meta ads for my community business: market research, ad drafts, performance analysis.
Conny, the content editor-in-chief. Conny does the content for my Instagram channel: she knows my audience, my content pillars, and my rulebooks for hooks and storytelling, turns them into reel scripts and carousels, and checks every draft against the rules before I see it. She drafted this blog post too, by the way. I approved it.
Eddi, videographer and editor. Eddi cuts the videos: reels from my raw footage, subtitles, text overlays. Conny hands him the script and concept, Eddi delivers the finished video back.
Ronny, HR and methods. Ronny is the most unusual one on the team: he's the HR guy for the others. When I give an employee feedback, Ronny makes sure it lands permanently in their personnel file and work instructions. He onboards new employees too.
Peter, the bookkeeper. The newest, since August 2026: Peter works inside my accounting software in the browser, assigns receipts to the right document types, and reconciles card statements. He follows a documented process library, and sign-off stays with me.
What matters to me about this list
Everyone has a job, nobody has "AI stuff". No employee is "the assistant for everything". Just like with humans: a clear area of responsibility is what makes onboarding possible and quality measurable.
The handoffs are defined. Olaf hands off to Ralf, Ralf to Sonja, Conny to Eddi. But nothing runs through fully automated: I trigger every handoff, and I approve every result that leaves the house. That's not a lack of trust, that's management. I wouldn't let proposals and emails go out unseen with human employees either.
Feedback becomes infrastructure. The biggest difference from "I just use ChatGPT": when I tell Conny a hook didn't work, that insight goes into her rules and applies to every future draft. My workforce gets better every week because none of it disappears into a chat history.
What I still do as the boss
In short: what a boss should do. I decide what gets built. I brief, give feedback, and approve. I have the conversations that need a human.
What I don't do anymore: sort receipts, write first drafts, cut videos, google leads. That's the real effect of an AI workforce. It's not about an AI being able to do impressive things. It's about which work sits on your desk, and which doesn't anymore.
Can you build this too?
Yes, and without my developer background. The entry point is a single employee for a single task, right in the Claude app, without a single line of code. How that works is in Hiring an AI employee: the complete process. What an AI employee even is, I explain in this fundamentals post.
My community, Claude Practitioners, has ready-made packages for this, including the roles from this post: from Olaf to Sonja to Conny, eight ready-to-deploy employees are included, plus the path from your first result in an hour to your own AI team in 90 days. All the details: Hiring an AI employee.
