An AI chief of staff is an AI role, built on a platform like Claude, that knows your whole business - your priorities, your customers, your voice, your files - and turns that knowledge into briefings, drafts and plans for you to review. You build one by teaching it your world through a guided interview, spread over about a fortnight of real sessions, then testing it before you trust it. It's the first role in any well-built AI team, and for many people it's the only one they need for a while.
Here's what that means in practice, why it comes first and how the build actually goes.
Think about what a human chief of staff does for a busy executive: holds the whole picture, filters the noise, preps the decisions and makes sure nothing important slips. An AI chief of staff does the paperwork end of that job for a one-person business.
A normal week looks something like this:
Notice what's missing: nothing posts, sends or spends on its own. Everything arrives as a draft, a briefing or a list. The chief of staff does the legwork; the judgement stays yours. That's not a limitation, it's the design.
Because every other role leans on it. If you later add a content writer, it needs your voice. A marketing assistant needs to know your offer and your customers. A finance admin needs your prices and history. All of that lives with the chief of staff.
Build specialists first and you end up teaching each one the same facts separately, then maintaining five slightly different versions of the truth. Build the chief of staff first and there's one home for every fact that the rest of the team inherits. If you're planning a bigger build, our complete beginner's guide to building an AI team covers the full sequence.
The honest version takes about a fortnight. Here's the shape of it.
You need a computer you can install software on and a Claude account on a paid plan. Pro, from $17/month, is the starting point - it's a separate subscription billed in US dollars by Anthropic, and the free plan won't run what a team needs. We've broken down what Claude costs a small business separately.
This is the heart of the build, and it's a conversation, not a prompt. Over a handful of sessions the role interviews you: what do you do, for whom, at what prices? How do you write? What does a good week look like? What always slips?
Your answers become short, structured files the role keeps between sessions. This is the bit prompt lists never gave you: memory with a structure. It's also why the build takes real sessions at the keyboard. You're not configuring software, you're briefing a new hire, and new hires take a fortnight to be useful in any business.
Give it your real writing - emails you were pleased with, a proposal that won, posts that sounded like you. From that it builds a personal style guide, so drafts come back sounding like you on a good day rather than like a press release.
Before the role goes live, give it real work and score the results. Ask it to draft the kind of email you send weekly. Ask it what you'd charge for a familiar job and check it against your records. Ask for a week plan and see whether it flags the right things.
If it passes, it goes live. If it fails, you fix its brief and test again. No role goes live until it passes its checks - that rule applies to the chief of staff first and to every hire after it.
A couple of minutes at the end of each session to file what changed: a new client, a price change, a decision made. Skip this and the role's picture of your business slowly goes stale. Keep it and the chief of staff gets more useful every week, which is more than can be said for most software.
It won't make your decisions, and you shouldn't want it to. Judgement, relationships and anything going out under your name stay with you. It won't send emails, post to social media or move money on its own. And it won't work while your laptop is shut - you still press the buttons.
It also isn't instant. The first fortnight is genuine effort, front-loaded. If someone offers you a chief of staff in five minutes, you're getting a chat window with a job title, and the difference shows by week three. That difference - structure and memory against a burst of first-day value - is the whole story of prompt packs versus a persistent team.
Two costs, plainly. The Claude subscription: Pro from $17/month, billed in US dollars by Anthropic. And your time: about an hour for setup, then the fortnight of build sessions, then a few minutes of close ritual per session. After that, the running cost is the subscription and the payback is measured in evenings you get back.
You can build an AI chief of staff from scratch by trial and error. The trial is fine; the error is what costs people months. Build My AI Team is a guided method that walks a non-technical person through the whole thing - day zero setup, the interview, the voice work, the checks and the filing structure that keeps it working at month six - then on to a full team if you want one.
One-time purchase, £119, 12 months of updates included, no subscription to us. Built on Claude, not affiliated with or endorsed by Anthropic. If a fortnight of honest effort for a working chief of staff sounds like a fair trade, it's there when you're ready.