How I Built an AI Team in Claude (Skill + Routine + Workflow)

I used to think AI agents were something other people built. People who could code. I'm a strategist, not a developer, and "build an autonomous agent" sounded like something I'd pay someone for.

Then I worked out that an AI employee isn't one clever thing. It's three ordinary things, put together.

This post is the whole picture. Not a prompt - I've written the prompts up separately and I'll link them - but how the pieces fit, what the team looks like, and the five I built first.

An employee is three things

Every AI employee I've built, from the one that sorts my inbox to the one that runs the others, is made of the same three parts:

Part	What it is	What it does
A skill	A file. The job description - who they are, what they know, how they do the job, what they never do.	Holds the how. Loaded into any chat by name, or by a routine on a timer.
A routine	A timer. Wakes the skill up at 6am, or every half hour, or when a task lands.	Makes them turn up without you asking.
A workflow	Your task manager. A field that says who owns a task, a status that says whose turn it is, one view for you.	Tells them what to work on, where to put it, and when to stop and ask.

Take any one of those away and it stops being an employee. A skill without a routine is a well-briefed contractor you have to phone. A routine without a skill turns up and doesn't know the job. Both without a workflow do the job and have nowhere to put it, or do it twice, or do it to the wrong thing.

I wrote each of the three up on its own:

• Part 1 - Skills - the three types, and the template
• Part 2 - Routines - the three types, and the templates
• Part 3 - The Workflow - the ClickUp setup, and how a task moves

This post is what happens when you put them together.

All of it sits on your AI brain.

Every employee reads your business from your files, every run, because they start with no memory. If your business isn't written down somewhere Claude can read it, none of this works. Not set up yet: The Co-Founder Setup.

The team, from the top

Once you've got one employee working, the question becomes: what's the org chart?

I did what you'd do for a real company. I sat down and mapped every job my businesses need done - not the ones I do now, the ones that should be done - and put them in departments with someone in charge of each.

Me (CEO)
├── Chief of Staff        - my attention, my accountability, the morning message
├── COO                   - builds and runs the machine: ClickUp, the vault, the employees
├── Editor-in-Chief       - reviews every output before it reaches me
├── Client Services       - one account manager per retainer client
├── Marketing             - content, blog, LinkedIn, email
├── Sales                 - leads, applications, scoping, follow-up
├── Product               - the things I build
├── Education             - the academy
├── Web & Technology      - the websites, integrations, security
└── Personal              - health, life admin, travel, money

I settled on ten directors. Under them, managers who each own one thing. Under the managers, employees who each own one job - one task moving from one status to the next.

What the chart gives you is that when you need a new employee, you already know where it sits, who it reports to, who checks its work and what it hands on to. Building one takes about fifteen minutes once the template exists, because all the thinking's been done.

How a task moves

The bit that makes it a team rather than a pile of bots is that they hand work to each other.

Every task in my ClickUp has a field called AI Employee and a status. Two statuses matter: W/ AGENT (an employee is on it) and W/ SAMANTHA (needs me). Each employee's routine wakes up and runs one filter - AI Employee = me AND status = W/ AGENT - and works whatever it finds, oldest first.

So a blog post goes: I write the brief on a task, set AI Employee = Blog Writer, status = W/ AGENT. The Writer's routine picks it up, writes the draft, saves it to the vault, comments a link, and sets AI Employee = Editor-in-Chief. The Editor's routine picks it up, checks it against the brief and the brand, and either sends it back with a list or sets status = W/ SAMANTHA. It lands in the one view I look at. I say yes or "not like that."

Every handoff is three things, every time: change the status, leave a comment, link the output. That's how nothing gets done twice, nothing gets lost, and I can always see where something is without asking.

Three loops that come out of it:

• The nightly truth loop. Every night the Knowledge Base Updater reads every chat, every closed task and every file from the day and writes it into each client's log and status page. Every morning the Morning Brief reads what it wrote and tells me what today is. I never write a status update. I never reconstruct yesterday.
• The content loop. Analyst → Strategist → Scriptwriter → Blog Pairer → Keyword Builder → Scheduler → Analyst. My gates: I edit the script, I film, I approve the caption. Everything else moves on its own.
• The lead loop. Form → Lead Triage → prep pack → call → notes → plan draft → me → delivered → follow-up. I'm on the call and I finalise the plan. The rest is employees.

The five I built first

1. The Inbox Assistant

Every 30 minutes, 7am to 9pm, it opens my inboxes and files every email that isn't from a human into the folder that sender already lives in. Receipts to receipts, tools to tools, newsletters to newsletters. New senders get sorted by the same rules. Anything from a person, or anything it's not sure about, stays where it is. It never deletes, never sends, never touches anything else, and reports in three lines: moved N, stayed N.

I built this one first because it's the simplest possible employee - one fixed job, no judgement, a two-line receipt - and it gave me my inbox back on day one. My inbox is now only people.

2. The Morning Brief

Every morning at 6 it reads my Google Calendar, every ClickUp list, and the status page for each client, and writes me one page: today's schedule with clashes flagged, to-dos split into mine and overdue, new leads since yesterday, one line per client, where my product build is, what's ready to post, and what's waiting on me. It changes nothing. Read-only, always.

This is the employee that tells me whether the others are working. If a client's status page is stale, I see it. If a task's been stuck at W/ AGENT for two days, I see it. Everything else reports into this.

3. The Knowledge Base Updater

The other half of the brief. Every night it reads the day - what was done, decided, blocked, produced - and writes it into the right client's daily log, then rewrites their status page. Anything it can't place with confidence goes to a "for review" file rather than being guessed into the wrong client.

This is the company ledger. Without it the Morning Brief is reading my memory, and my memory is the thing I was trying to stop relying on.

4. The Chief of Staff

This is the one that runs the others. It reads the dashboard the brief produces, sends me my morning message, turns my brain-dumps into ClickUp tasks through the routing rules, chases anything stuck, and keeps the managers accountable - what's with an employee, what's with me, what I owe people.

In a real company the Chief of Staff manages the CEO's calendar and everyone else's accountability. Same here. Directors hold the goals, managers own one thing each, employees own one job each, and the Chief of Staff makes sure the whole thing keeps moving so I don't have to.

5. The Keyword Builder

Every post I publish has a keyword - comment SKILLS101, comment ROUTINES101 - that sends a DM with the blog post. Setting that up meant duplicating a ManyChat flow, renaming it, setting the keyword, creating a Mailchimp tag, duplicating a Zap, and testing it. Fifteen clicks across three tools, every single post, and it was the single biggest reason I'd have a post ready and not publish it.

So it's an employee. A task in my content list with the keyword, the link and the message text on it, set to W/ AGENT. The Keyword Builder picks it up, builds the flow, creates the tag, screenshots each step into the task, and sets W/ SAMANTHA. I do one test from my phone.

If you're wondering which employee to build first, build the one that sits between you and the thing you keep not doing.

The rules

I'll keep this short.

1. One employee, one job. If it needs "and" twice to describe, it's two employees.
2. Nothing public without me. No employee posts, sends, publishes or deploys. Everything stops at W/ SAMANTHA and I press the button.
3. Every handoff is status + comment + link. All three.
4. Employees write to the vault, never only to chat. A chat is gone by morning.
5. The Editor never edits. It comments. Three loops, then it comes to me with a summary.
6. Every routine reports. One line, even if it's "queue empty."
7. The routine says where the password is, never what it is.
8. New employee = copy the template skill, fill it in, create its routine, add its dropdown option. Fifteen minutes.

What it actually feels like

Not like having a team of robots. More like having a very good operations person who never sleeps and never has an opinion about how I run things.

I open the laptop. There's one page telling me what today is. There's one view with the three things that need me. The inbox has only people in it. The client status pages are true as of last night, and I didn't write them.

That's the whole thing. A skill, a routine, a workflow. Three ordinary parts, and writing the job down instead of carrying it in your head.

Start with one

Don't start with the org chart. I did the chart after I had a few employees running, because by then I understood what one was.

Build the Inbox Assistant or the Morning Brief - read-only, low stakes, done in an afternoon. Let it run for a week. Then build the one that sits between you and the thing you keep not doing.

The three posts that show you how:

Part 1 - Skills · Part 2 - Routines · Part 3 - The Workflow

If you haven't got your AI brain set up, that's the foundation for all of it: start here.

And if what you want is the whole system - the pricing, the positioning, and the tech and AI that lets you run a business on three days a week - that's what I teach.

Watch the free training →