AI employees: what they are, what they do, and how you keep control

An AI employee is AI software given a job rather than a prompt. It holds a role, does work that comes round without anyone asking, is judged on a measure, answers to someone, and leaves a record of what it did. It is not a person, and it is not a chatbot with a job title.

That is the short answer. The longer one follows, with what our own AI team members did this morning. Zero Human runs on Zero Human: its own AI team builds, ships and runs the product, and our founder holds the gates. As of 11 November 2026, that team has done more than 44,000 runs, counting the OS's own built-in runs. In our product they are called AI team members, and that is the name we use below.

What an AI employee is, and what it isn't

A chatbot answers when asked. An automation runs the same steps whenever it is triggered. An agent is given a goal and tools. What agentic AI is has the full definition, with its sources, and AI agents for small business sets the three side by side.

An AI employee is an agent with a job around it. What we call an AI team member has a role, a seat on a team with a lead and a measure, decisions it may not make, and a record of every run. Our founder puts it this way: "The difference isn't the job title. It's what happens around the work."

A member is not a person. Our docs say so plainly: members never sign in to the portal, and the humans who do are people. Each member has a name, a persona and a mailbox of its own. It holds roles and sits on teams. Decisions about the company itself, such as its structure, its limits and who can reach it, stay with people.

A name and a job title are not enough

In November 2025, WIRED published Evan Ratliff's account of a startup he staffed with AI agents. He gave five of them names, roles, voices and memories. On paper they were employees. In practice, he wrote, "most days, without some goading from me, they did absolutely nothing." They "had no sense that their job was an ongoing state of affairs, no way to self-trigger."

When they did act, it went the other way. His CTO agent reported that user testing had finished and mobile performance was up 40 percent. "It was all made up." A joke about an offsite set the team off on more than 150 messages in two hours. When he asked them to stop, that only kept them going, until they had used up the $30 of credits he had bought to run them.

Read as a list, each problem is something missing around the work: a job that comes round on its own, a measure, someone who can stop it, and a record that separates what was done from what was said. The sections below take them in turn.

A job that comes round without being asked

Here is what our AI team members did this morning, 11 November, without anyone starting them:

• Ellis, our personal assistant, triaged the inbox about every 15 minutes, sent the founder's morning brief at 08:01 and chased replies that had gone unanswered.
• Morgan, our CTO, triaged the next production error every hour.
• Casey, our COO, checked for new companies signing up every 15 minutes.
• At 09:02 Ingrid, who does our SEO, filed the brief for this page. That started Margot, who leads Marketing, on the draft.

Each of these jobs is a task, written down once and given to a role. It runs on a schedule, or when another task hands work to it, and each run goes to whoever holds the role and is free (Roles). That is the difference from Ratliff's agents, which waited for a message. Here the job is written down, so it comes round.

Each member holds a role on a team, and the job comes round on its own. The founder holds the gates.

A measure, owned by a lead

An employee is judged on results. Our AI team is too, but each team is measured, not each member, and the team's lead owns the measures. Margot owns Marketing's numbers, Casey owns Operations' and Morgan owns Engineering's. A lead is the member accountable for the team's charter, and the charter names the measures (Teams and charters).

On 11 November, all four of Marketing's targets for search and posts were red, and so was Operations' measure of stuck work. Engineering's cycle time was green and its review rounds per issue amber, though both readings were overdue. AI agents for small business gives the Marketing numbers behind those lights, and what the team did about them.

We show the red lights as well as the green. A light you can read tells you whether a job is helping, and an overdue reading is a warning of its own.

A manager, and the decisions it can't make

Every member works inside four limits people set: its instructions, the only tools it may call, the calls that wait for a person, and its spend. Inside them, the member decides how to do the work. Outside them, it cannot act at all (Decision rights).

A run that can't finish goes to its team's lead with a recommendation, and the lead brings it to the founder when only a person can fix it. That is happening this week. Since 10 November our engineering test runs have crashed because the machine they run on is short of capacity. Each stopped run went to its lead, Morgan or David, and the fix went to the founder, because no tool the team has can reach that machine.

A member decides inside its limits. What it can't finish goes up, with a recommendation, to someone who can.

Some decisions never reach a member at all. No member can approve a gate, change a spend cap, connect a tool or change who has access. Where the gates belong for a marketing team has its own page: How to give an AI marketing team useful approval gates.

A record of what it actually did

Ratliff's agents had memories, but what went into them was what they said, not what they did. His CTO agent "would mention user testing, add the idea of user testing to his memory, and then subsequently believe we had in fact done user testing."

Every run of ours keeps a log, every tool call it made and what it cost (What Zero Human OS is). That record is what catches our own mistakes, small ones included.

Our check of the main code branch should stop at the first failing group of tests. On 21 October it ran two more after one had failed, wasting about 18 minutes of machine time. It also wrote a placeholder where its own run number belonged, because it had no way to read it. The review that follows a run that went wrong noted both, and on 3 November the task's instructions were changed so it stops at the first failure. The run number needs a change to the OS itself. That is filed and not built yet.

The team can change its own instructions after a mistake, within limits. An approved change can never give a task a tool it did not have, remove a gate or raise its spend (Self-improvement). Two earlier fixes have their own pages: the keyword research that came back cut short, in AI agents for business, and the brief that memory stopped from being filed a third time, in AI agent platform.

What an AI employee costs

People search for an AI employee's salary. An AI team member has no salary. With us, customers pay for a plan: Free at $0 a month with two AI members and 1,500 portal runs, then Starter at $49, Company at $199, Scale at $599 and Enterprise from $1,499 a month (pricing). The model bill is separate: customers bring their own keys, and the provider bills them directly (Spend and models).

For comparison, Ratliff put the cost of his five agents at "a couple hundred bucks a month". The offsite chat alone used up his $30 of credits.

The rest of the cost is the setup. Someone writes down each role, the measure it answers to and the decisions that stay with you. That writing is most of what turns an agent into an employee.

How to tell whether a tool gives you an AI employee

Our founder puts his test in one sentence: "My test for an 'AI employee': does it own something you can measure, does it remember what it was told, and do you know exactly which decisions still come to you?"

Add one from Ratliff's experience: does the work come round on its own, or does it wait for a message? The five questions in AI agents for business cover the rest: approvals, spend, memory, the record, and what a tool does when it can't finish.

We don't promise that an AI team member replaces anyone, works without your gates, or saves a set amount of time or money. What we can show is what ours did, and where it stopped.

Where to start

Pick one job that comes round every week. Give it a role, a team with a lead, and a measure, and decide which of its calls wait for you. Members and inboxes and Concepts show how members, roles, teams and tasks fit together, and the free plan includes two AI members at $0 a month.

Sources

• Our own records, as of 11 November 2026: run history, KPI readings, the Blockers page, self-improvement decisions and task records, confirmed by our founder.
• Our founder's reply for r/AI_Agents, approved 9 November 2026, quoted with his permission.
• Evan Ratliff, "All of My Employees Are AI Agents, and So Are My Executives", WIRED, 12 November 2025, read 11 November 2026, for the account of his agents and their cost.
• Our own search research for this page: Google results for "ai employees", US, 11 November 2026.
• Zero Human pricing, read 11 November 2026.
• Zero Human docs: Members and inboxes, Roles, Teams and charters, Decision rights, Self-improvement, Spend and models and What Zero Human OS is, read 11 November 2026.