Client operations is everything between winning the work and being paid for it that is not the work. Acknowledging an enquiry. Confirming a start date. Telling somebody the cut is ready. Asking for the assets again. Sending the invoice. Chasing it. None of it is skilled, all of it is required, and in a studio under about fifteen people it is almost always being done by the person whose hour is worth the most.
So it is the obvious thing to automate, and it is also where most agencies get automation wrong — usually by starting with the part that felt most annoying rather than the part with the least judgement in it.
The rule: automate the step with no decision in it
Every step of client ops is one of three things. Some are pure mechanics: the information is already known, the recipient is already known, and a person is acting as a courier. Some are judgement wearing mechanical clothes: an apology for a slipped deadline looks like a status update and is not one. And some are relationship work that only reads as admin because it is short.
Only the first kind should ever run unattended. The second kind should be prepared for you — drafted, addressed, ready — and then wait. The third kind should not be touched at all, and an agency that automates it can usually feel the temperature change within a month.
If you would be embarrassed for the client to know a machine sent it, do not let a machine send it. Let the machine write it and hand it to you.
The order that pays back fastest
Ranked by hours recovered against risk taken, for a studio running twenty to fifty jobs a year:
- Enquiry acknowledgement. Pure mechanics, and the one with a revenue number attached: a reply inside an hour changes whether you are in the conversation at all.
- Project status on a fixed rhythm. The client stops asking, which removes two emails per project per week — nearly all of them yours.
- Invoice on delivery approval. The approval is an event, the amounts were agreed in the proposal, and the recipient signed off. There is no decision left in it.
- Payment chasing on a schedule. Day seven, day fourteen, day thirty, in three different registers. Almost nobody does this consistently by hand, because doing it by hand means being the person who chases.
- Testimonial requests after payment clears. Timed well, they arrive at the one moment the client is unambiguously happy.
Notice what is not on the list. Anything that reacts to bad news — a slipped date, a scope problem, a complaint — belongs to a person, and belongs to a person the same day.
Three ways this goes wrong
The first is the tool that needs feeding. An automation that only fires when somebody moves a card is not an automation; it is a second job with a nicer interface. If the trigger is not an event that happens anyway — an email arriving, an approval being pressed, a payment clearing — the sequence will be accurate for six weeks and then quietly wrong.
The second is the anniversary email: a message that fires on a date and knows nothing about the state of the relationship. The client who cancelled last week gets a cheerful check-in, and every automated message you send afterwards is read as machinery.
The third is automating the send before you have automated the draft. Drafting is where the time actually goes. Sending is where the risk actually is. Most studios could take three quarters of the hours out of client ops without ever letting anything leave the building unread.
How to start, in a fortnight
- Pick one step. Enquiry acknowledgement, if you have never done this before.
- Write down the trigger as an event, not as a time. "An enquiry arrives", not "every morning".
- Write the message once, properly, in your own voice. This is the part worth an afternoon.
- Run it in draft mode for two weeks: the machine prepares it, you press send. You are checking the judgement, not the typing.
- Then let that one run unattended, and only then pick the next step.
Two weeks per step feels slow and is not: the failure mode of doing five at once is that when one of them sends something odd you cannot tell which rule did it, and the whole lot gets switched off.
Where we sit in this
We build one of these tools, so take the recommendation with the appropriate amount of salt: what Neoflow does is watch the events that happen anyway and prepare the action, with anything involving money or a client’s inbox asking first until you deliberately say otherwise. That default is not modesty. It is the only version of this we would leave running against our own clients.