Count the logins. Not the ones you use — all of them. The accounting system, the scheduler, the inbox, the CRM, the file drive, the chat app, the payroll portal, the thing you bought last year that one person still swears by.
Now answer the harder question. Does your team have more time than they had five years ago, or less?
Almost nobody says more. And the strange part is that every single one of those tools was bought for a good reason, by someone sensible, to solve a problem that was real at the time.
So where did the time go?
The five stops hiding in an ordinary week
The time did not vanish. It got spent, in small pieces, on five specific things. None of them appear on any invoice, which is exactly why they are hard to see.
- Somebody exports from one system and imports into another. A spreadsheet download on Friday, a tidy-up, an upload Monday.
- Somebody checks whether the thing that was supposed to happen happened. Did the confirmation send? Did the file land? Did the job get logged?
- Somebody re-types what is already written down somewhere else. The address is in the email, the quote, and the job sheet. It gets typed three times.
- Somebody builds the report by hand because the software holds the data but does not hold the answer.
- Somebody remembers. The chase, the follow-up, the renewal — held in one person’s head, and only in theirs.
Read that list again with your own team’s names attached to it. That is not five inefficiencies. That is a job, and somebody in your business is doing it full time without it ever being written on a job description.
None of that is your team being slow
This is the part worth being clear about, because it is where most owners quietly blame the wrong thing.
Your staff are not carrying work between screens because they are disorganised. They are carrying it because nothing else will. The software you bought has no way to hand anything to the software next to it. So a person becomes the connection — the courier between two systems that were never introduced.
Every hour of that is your team doing the work your software cannot.
A tool is a place a person has to go
Here is the mechanical reason, and it is simpler than the sales conversations around it ever suggest.
A tool sits there. It does nothing at all until a person opens it, looks at it, and works inside it. It has no opinion about whether today’s work got done. It cannot start anything, chase anything, or notice anything is missing. It waits.
Which means every tool you have ever bought did not take work off your team. It gave them another place to be.
Twelve tools, twelve places to be. That is the whole arithmetic, and it explains a five-year trend that no amount of training or discipline ever fixed.
You didn’t buy the wrong tools
The instinct at this point is to conclude you picked badly. You did not. Most of those tools are good at the specific thing they do, and swapping any one of them for a competitor changes nothing about the five stops above.
You didn’t buy the wrong tools. Tools are the wrong shape.
The shape you want is something that picks work up when it arrives, carries it the whole way, handles what it can handle, and stops only when it reaches something a person should genuinely decide. Then it comes to you — with the answer already drafted. One decision, and it keeps going.
That is a different object, not a better tool. Tools wait. Engines run.
What four years of a support queue taught me about this
I ran a technical support team for four years at Pantheon, and before that I spent five years on service desks answering whatever arrived. That is thousands of hours of watching work stop and wait for a person, so here is the part that saves you the slow version of the lesson.
The tickets that hurt were almost never the hard ones. They were the ones that sat. Something arrived, nothing picked it up, and it aged quietly until it turned into a bigger problem than it started as. Not one of those was caused by somebody being bad at their job. They were caused by the handoff being a human, and humans go to lunch.
I have not built an engine for a client — Anito is new, and I am not going to pretend otherwise. What I have done is spend seventeen years watching where work stops in other people’s systems, which is why the five stops above are specific rather than a general complaint about inefficiency.
How to check this yourself, this week
You do not need us, or any consultant, to find out whether this is happening in your business. You need one week and a piece of paper.
- Pick one thing that flows through your business end to end — a quote, a job, an invoice, a new customer. One.
- Follow it from arrival to finished, and write down every point where it sits still waiting for a person to move it.
- At each stop, write the name of the person the work is waiting for. Not the role. The name.
- Write how long it usually waits — your honest estimate is good enough here.
- Count the stops. That number is the one nobody in your business has ever counted.
Then run the arithmetic with your own figures, not mine. If a job stops six times and each stop costs four minutes of someone’s attention, that is twenty-four minutes per job. Twenty jobs a day makes eight hours. One person, every day, being a courier.
If your numbers come out small, that is a genuinely useful answer and it means you should not spend money on this. Most people who actually do the count are surprised by the size of it, and the surprise is the point — the cost was invisible precisely because it was spread across everybody a few minutes at a time.
What to do next
Do the count. One flow, one week, a piece of paper. Whatever the number turns out to be, it is yours and it is the first honest measurement most businesses have ever had of where their week actually goes.
If you want the mechanics of what replaces those stops, read the six parts every engine is made of. If the flow you counted runs on paper in the field, the field team version has the numbers worked through.
If you want the whole picture instead of one workflow: tell us what’s still manual. You get a map of every point where your business stops and waits for a person, what that costs you in hours, and which of those an engine would take over first. Free, yours to keep, and useful even if you never hire us — including on the days the honest answer is that you should not build anything yet.
Common questions
Isn’t this just an argument for buying fewer tools?
No, and consolidating for its own sake often makes things worse. The number of tools is not what costs you — the number of points where a person has to carry work between them is. You can run twelve systems with almost no stops if the work moves between them on its own, and you can run three with a dozen stops if it doesn’t. Count stops, not logins.
Our team says they’re fine and the process works. Should I leave it alone?
Ask them a narrower question. Not ‘is the process working’ — people will defend a process they keep alive by hand — but ‘what would break next week if you were off sick and nobody covered your inbox?’ The answer names the stops. If nothing breaks, your work genuinely does move on its own and you have nothing to fix here.
We already pay for an automation tool. Doesn’t that cover this?
It covers part of it, and it is worth checking which part. A workflow builder can move data between two systems on a trigger. What it does not do is own the whole path from arrival to finished, notice when something never arrived, or hold a decision until you approve it. If somebody on your team maintains the flows and watches them, that tool is one more place a person has to go.
Where would you start if the count comes back high?
Start with the flow that touches money soonest, because that is where a stop costs the most and where the improvement is easiest to see. For most businesses that is quotes or invoices. Do not start with the most annoying process — annoying and expensive are different problems, and only one of them pays for the work.