Digital workers, AI agents, and compounding digital labour

Three terms that get used as if they mean the same thing. They do not, and the difference decides what you should buy, what it will cost you to run, and whether it is worth anything to you in year two.

Vocabulary in this space is a mess, mostly because vendors pick whichever word sounds biggest. It matters more than it sounds like it should: the word you use decides what you compare the thing to, and what you compare it to decides whether you think it is expensive.

An AI agent

A system that can take an action, not just produce text. It calls a tool, writes to a record, sends a message, queries a database. The defining feature is that it can do something rather than only describe something.

An agent is a capability. It is bounded, it is usually single-purpose, and on its own it has no memory of your business beyond what you hand it each time. Most of what is sold as "an AI agent" is exactly this, and there is nothing wrong with it. It is just smaller than the word suggests.

What an agent is compared to

A feature. Which is why agents are priced like features, per seat or per call, and why buying five of them from five vendors produces five bills and no coherence.

A digital worker

A named role inside your operation with a defined scope, its own knowledge of how your business works, and continuity between one interaction and the next. It may use several agents underneath, the same way a person uses several tools.

The test is whether you can describe it the way you would describe a job. If the honest answer is "it answers the phone", that is an agent doing one task. If the answer is "it handles enquiries end to end, knows our prices, knows who is available, escalates the ones that need a person, and follows up the ones that go quiet", that is a role.

What a digital worker is compared to

A hire. Not because it replaces a person cleanly, it rarely does, but because the hire is the alternative you were actually going to choose. That comparison also changes what counts as expensive.

Compounding digital labour

The part almost nobody sells, because it does not demo.

A person who has worked somewhere for three years is more valuable than the same person on day one, and none of that value is in their CV. It is in knowing which customer is difficult, which supplier lies about lead times, which question is really a complaint. It is also the value you lose entirely when they resign.

Compounding digital labour is that accumulation, held by the business instead of the person. Every conversation, every correction, every escalation that turned out to be unnecessary makes the next one better, and the accumulation stays when a staff member leaves.

Why this is the only part that matters in year two

In month one, an agent and a digital worker look similar. By month twelve one of them knows how your business actually runs and the other is exactly where it started. That gap is the entire argument for building on something that keeps state rather than assembling tools that do not.

It also has an uncomfortable implication. If the accumulation is the value, then losing it matters, so ask the awkward question before signing: if we stop working together, what do we keep? The honest answer is that you keep your data, your content and whatever the system learned about your operation. What you do not keep is the engine. Any vendor unwilling to say which is which is telling you something.

How to use the three words

• Agent when you mean a capability that performs one task. Compare it to a feature and price it like one.
• Digital worker when you mean a role with continuity. Compare it to a hire.
• Compounding digital labour when you mean the accumulated operational knowledge. Compare it to tenure, and notice that it is the only one that gets more valuable while you sleep.

Most disappointment in this market comes from buying the first and expecting the third.

Related: What it costs compared with hiring · Who is accountable for the decision