Automation is easy to oversell and easy to under-use. The interesting question is not whether a tool is clever — it is whether the task has a structure a machine can follow and a consequence a person should own.
Where agents earn their place
Repetition with a pattern. Enriching a record, formatting an export, routing a ticket, drafting a first version of a reply, checking that yesterday's numbers landed inside expected ranges. The work is bounded, the correct answer is recognisable, and the volume is high enough that speed matters more than judgement.
Work that happens while the office is closed. Overnight reconciliation. Monitoring a queue. Watching a competitor's pricing page. Alerts that arrive before the workday starts are worth more than alerts that arrive during it.
Retrieval instead of memory. Finding the clause in the contract, the ticket in the archive, the invoice behind the discrepancy. Machines do not get bored of searching, and they do not misremember which of four documents was final.
Where people must stay
Anything where being wrong is expensive or public: the message that goes to a customer, the number that goes to a board, the decision about whether to hire, the judgement about whether a situation is unusual.
Not because a machine cannot draft these things — it can draft them well. But "well enough to publish" is a judgement, and judgement is exactly what you are paying a person for.
The line that makes it work: review, not rework
The difference between automation that compounds and automation that erodes trust is where the human sits.
If the person reviews by rebuilding the work from scratch, the agent has saved nothing — it has created a second job. If the person reviews a complete draft against a checklist they wrote once, review takes minutes and the volume that can be handled rises sharply.
So every automated workflow we run has three parts: the machine does the pass, a named person reads the output against a fixed standard, and anything the reviewer corrects becomes an instruction for the next pass. The system gets better in the direction your standards point, and nothing leaves the building unreviewed.
A simple test before you automate anything
Write down what a correct output looks like, in plain language, without using the word "quality". If you cannot write it, you do not understand the task well enough to delegate it — to a machine or a person. If you can write it, you have the beginning of a standard, and the standard is the asset.
Tools change every year. The standard does not, and it is the thing worth owning.