Efficiency isn't a headcount problem
Cutting people is the laziest version of efficiency, and usually the most expensive one. The real work is fixing what you're doing twice and three times over.
Somewhere along the way, “efficiency” became a polite word for layoffs. A firm shows up, benchmarks your headcount against a spreadsheet, and recommends you run leaner. Everyone nods. A few months later the work is still there, the people who understood it are gone, and the ones who stayed are quietly rebuilding what got cut.
That’s not efficiency. That’s stupidity with a slide deck.
The work is the problem, not the people
Walk any growing service company and you’ll find the same thing: work being done two and three times over, feeding a structure that made sense five years ago and hasn’t been questioned since. An order gets entered in one system, re-entered in another, then emailed to a third person who keys it in a fourth time so the numbers reconcile. Nobody designed that. It accreted.
Real efficiency is finding that duplicated work and cutting it, so the hours go back to the people who were doing it by hand. You don’t have fewer people. You have the same people, no longer spending their afternoons being a human copy-paste function.
The tell is simple. Ask where the day actually goes:
- How many times does one piece of information get typed?
- Which reports exist only because someone once asked for them and nobody stopped?
- What gets checked twice because the first system can’t be trusted?
The answers are rarely about capability. They’re about plumbing.
Where AI actually earns its place
This is the part where most people either roll their eyes or lose their minds, so let’s be plain about it.
AI is very good at the copy-paste function. It’s good at moving structured information from one place to another, watching for the exception, and handing the exception to a person. That is genuinely useful, and it’s exactly the busywork that’s eating your team’s hours right now.
What it does not do is replace the judgment that made your company worth calling in the first place. Knowing which exception matters, which customer needs a phone call, which corner can be cut and which absolutely cannot: that’s competency, and it doesn’t come out of a model.
The tool is useful. Knowing where to point it is the expertise.
Efficiency and competency are two different things, and the whole job is knowing the difference. Automate the first. Protect the second. Most people get this backwards, automate the judgment, and keep the busywork, then wonder why it got worse.
Start by counting the double-work
If you want a first move that costs nothing, it’s this: for one week, have your team flag every time they enter the same information twice. Don’t fix anything yet. Just count.
The list will be longer than you expect, and it will point straight at the work worth automating. That’s where we usually start, because it’s where the hours are hiding. It’s also the opposite of cutting people. It’s giving them their afternoons back.
If that sounds like your operation, let’s have a conversation. We’ll find the double-work, cut it, and leave you with a team that spends its time on the part only they can do.