Most owners want to know: "How does it actually work?"
This page contains the answer. None of it is a secret, and none of it requires you to understand the technology.
It is an employee, not a chatbot
An AI Employee is not something you ask questions. It is something you give duties. It has a name, a job description, an employee file, a first ninety days, and performance reviews. It does not improvise. Every duty it runs is written down in advance, with a definition of done, and every run produces a report a human can read in five minutes.
It is the delegate in the Four Moves. You decide which loops to leave, the work gets documented, the employee takes it, and you manage by report.
That distinction matters because it is the difference between a tool your team has to remember to use and an employee who shows up on Monday whether or not anyone reminds it.
Duties, three kinds
Everything the employee does is a duty, and a duty starts one of three ways.
On its calendar.
The week-close audit runs Friday afternoon. The Monday operating brief runs Monday at six. The month-end package runs on the first. Scheduled duties are the backbone, because most of the loops an owner is stuck in have a calendar attached.
When an email arrives.
The employee has its own inbox. When a message arrives that meets the criteria in its playbook, a timesheet approval, a client's purchase order, a bounced invoice, it acts on it. It reads, sorts, files, replies, or escalates, according to the duty.
When something happens in an application.
An invoice goes overdue. A deal closes. A new client is created. The employee sees it and does the next step, the same way every time.
The playbook
Each duty is written down in plain English: what triggers it, the steps, the checkpoints, the known-correct answer at each one, what to do when something doesn't match, and who to tell. Together those documents are the playbook. It is the operations manual every business book told you to write, with one difference: something actually runs it, every week, so it has to stay current, and it does.
The playbook is yours. It lives in your accounts, it is written for people to read, and it describes how your business actually operates.
Friday at four, the employee pulls the week's time entries, checks them against the project rules in its playbook, flags the three that don't match, drafts the two client-facing invoices that are ready, and sends you a report: what it checked, what it found, what it did, and what needs you. You read it Monday morning in the time it used to take to open the timesheet.
The Playbook stays alive because something actually runs it.
The first ninety days
- Shadow. The employee drafts the work and a person does it. You see what it would have done and correct it.
- Draft. The employee does the work and a person approves it before anything goes out. Corrections get written into the playbook.
- Unattended. The employee does the work and a person reads the run report. It escalates what it is not sure about.
Most duties are unattended well before day ninety. The ones that touch clients or money get the longest shadow period, on purpose.
What it needs from you
An AI Employee is set up the way you would set up a new hire, minus the desk.
- An email address and a calendar of its own, on your domain.
- A Claude license on your company's account. That is the AI it runs on, and it is billed to you directly, like any seat.
- Its own login to each business application it works in, scoped to what its duties require and nothing more. Its actions are attributable to it, not to you or your team.
- A person it reports to. Usually you.
What it does not need
New software. A rebuild of your systems. A data warehouse. Your team changing how they work. The employee works inside what is already in place, the way a new hire would, and if a tool changes, the playbook changes with it.
Guards
The employee runs inside limits that are written down before it runs anything. Which duties it can complete on its own and which need a person. What it does when the numbers don't match. How it says "I'm not sure" instead of guessing. Every action it takes is logged under its own name, so you can see what it did and why, and so can an auditor or a buyer. We go deeper on this in the blog for the people who want it; for everyone else, the short version is that it does not get to improvise.
Whose is it?
The playbook is yours. The records are yours. The employee works for you, and we keep it trained: as the AI models improve and your applications change, the employee changes with them, and that is what the monthly management covers. If we ever part ways, you keep the playbook and every run report, and you can hire anyone to run it.
Want to talk it through?
Your first move is a thirty-minute conversation about your business and what you want from it. No preparation, no charge, and nothing to decide until you have a job description in your hands. The Moves walks through the rest.
No Pitch. Just Possibilities.
How delegation works
What an AI Employee is, the three kinds of duties it runs, and what it needs from you.