Agents and Operators: what the difference is

The unit of work is different

An agent's unit is the task. Summarise this call. Draft this reply. Find the five candidates who look most like this one. It is measured on whether it did that task well, and it is finished the moment it hands back.

An Operator's unit is the job. Every response to yesterday's adverts is screened by nine in the morning, in a consistent order, with the rejections sent and the shortlist on someone's desk. Nobody called it. It knew the work was there.

That sounds like a small distinction and it is the whole distinction. A task can be excellent and still leave the job undone, because most of the job was never the task. It was noticing the work had arrived, deciding the order, chasing the half of it that did not fit the pattern and knowing what to do when something looked wrong.

Why it shows up once you have more than a few

One agent is easy to love. It does a thing that used to take twenty minutes and now takes one, and the person using it is delighted.

Fifteen agents is a different experience. Each one is still good. But somebody has to know which to call and when, somebody has to carry work from the output of one to the input of the next, and when the result is wrong there is no one to ask, because no single agent was responsible for more than its own step. That somebody is usually one of your better people, and the work they are now doing is coordination.

This is the point most firms reach and misdiagnose. It reads like a tooling problem. It is an accountability problem. Capability was added without anyone being made responsible for the outcome, so responsibility fell back to the nearest human by default.

What an Operator has that an agent does not

• A brief. A written description of the job, the standard it is held to and the things it must never do. The same document you would give a new starter, for the same reason.
• A remit. An explicit line between what it may do on its own and what it must bring to a person. Set before it starts, not discovered afterwards.
• A manager. A named person it reports to, who sees its work and answers for it. Every Operator has one, including the senior ones.
• A queue, not a prompt. It picks the work up because the work exists, on the schedule the job demands.
• A record. Every action it took, what it was working from and what it cost. Not a log for engineers. A record a manager can read.
• A review. Its work gets appraised, and the brief gets changed when the appraisal says it should. A role that cannot be corrected is not a role.

None of those are model features. They are the things a business already does to make a job accountable, applied to work that happens to be done by software.

What it does not change

It does not remove people. The honest version of this, and the one we say to clients, is that it removes the need to hire more. The back office of a growing firm absorbs headcount in a very particular way: the work is repeatable, it scales linearly with volume and it is nobody's career. That is the part an Operator takes.

The judgement, the relationships, the negotiation and the exceptions stay exactly where they were, with the people who are good at them and who now have the time to do more of it. If a supplier tells you the same system also does that part, ask them to show you it doing it on a bad week.

Where an agent is still the right answer

Often. If the task is well defined, if the person calling it is already holding the thread of that piece of work, and if the job is finished when the answer comes back, an agent is the cheaper and better choice. Wrapping a role around it buys you governance you do not need and a layer of indirection you will resent.

The test is simple. Ask who is accountable if this runs for a month and the outcome is bad. If the answer is a person who is close to the work and would notice, you want an agent. If the answer is nobody in particular, you either want an Operator or you want to stop doing that work.

What to ask before you buy either

• What is it accountable for, in a sentence a manager would recognise? If the answer describes a feature rather than an outcome, it is a capability being sold as a role.
• What can it do without asking? A supplier who has not thought about this has not thought about the interesting part.
• What happens at the gate? Anything that spends money, sends mail or changes a record of account should stop and wait for a named person. Ask to see that happen.
• Can I read what it did last Tuesday? If the record is only readable by engineers, nobody will read it, and in practice nothing is being supervised.
• Who owns it at the end? A role built inside your business, running on your data, that you keep, is a different asset from a seat you rent and lose when you stop paying.
• What does it cost per unit of work? Not per seat. A role that cannot be costed against the work it did cannot be judged against the person it stood in for.

How to tell which one you need

Three signals, and two of the three is usually enough.

• The work arrives whether or not anyone is ready for it. Inbound mail, responses to adverts, compliance chasers, invoices. Work with its own arrival rate wants a role, because the first part of the job is noticing.
• The next hire you are considering is mostly absorbing volume. If you can describe the job as more of what we already do, an Operator is the direct alternative, and it is the comparison worth pricing.
• Someone senior has become the join between your tools. If a good person spends their week moving work between systems and agents, you have already built the role. It is just being done by the wrong person.

If none of those is true, buy the agents, use them well and spend the money somewhere else. Not every business needs a back office that runs itself, and it is cheaper to find that out before building one.

Where this sits in the work we do

Operators are one strand of what we do, not the whole of it. Most engagements start with an intelligence layer over the systems a firm already runs, because that is where the compounding advantage lives. Operators are what you add when the answer to a capacity problem would otherwise be another hire.

You can see the five we built for recruitment, hear them introduce themselves, and read what each one is accountable for.