Automation isn't about replacing people

Whenever we start a new project, at least one person in the room is quietly worried that automating a workflow means eliminating a job. It's the most common concern we hear, and it's the one we spend the most time addressing — because it's rarely true, and when it is, it's worth being honest about it.

What actually happens to the hours

The reality of automation, in almost every case we've worked on, is that it doesn't remove roles. It removes tasks. Specifically, it removes the parts of a role that nobody particularly wanted in the first place:

• Copying data from one system to another.
• Retyping information that already exists somewhere.
• Waiting for a response before the next step can happen.
• Recreating the same report every Monday morning.
• Chasing approval emails through three inboxes.

These aren't the reasons people joined your company. They're the tax on doing the actual job.

A real example

One of our clients — a professional services firm with about 30 staff — had a finance team of three people. A significant chunk of their week went to invoice processing, bank reconciliation, and month-end reporting. When we asked the team what they'd rather be doing, the answers were interesting:

• "Actually understanding what's happening in our cash flow."
• "Having proper conversations with clients before invoices get disputed."
• "Getting ahead of the numbers so we can plan properly, instead of reporting on the past."
• "Not working late on the last two days of the month."

After automating the routine work, no one was made redundant. The team got their evenings back. The firm hired an additional analyst eight months later — because the finance function had become valuable enough to justify the investment, and the people there now had time to be strategic.

The question isn't "will automation remove jobs?" It's "what will your team do with the time it gives them?" That's a leadership decision, not a technology one.

When it does replace work

Let's be honest: sometimes it does. If a role consists entirely of the kind of work that automation handles well — and only that — then the role can disappear. We've seen this happen. What we haven't seen is a good employer using it as a reason to make people redundant without exploring alternatives first.

The more common pattern is:

• Some people take on new responsibilities that are more valuable.
• Some people move into roles that only exist because the company can now take on more work.
• Some people leave over time through normal attrition, and the role isn't replaced — the company grows without hiring more admin.

All three of these are outcomes that benefit the business without destroying anyone's career.

Why this matters beyond ethics

Even if you set aside the moral argument — which you shouldn't — there's a practical reason to handle automation carefully. The team that feels threatened by a new system is the team that will quietly make it fail.

We've seen projects die because the people expected to use them kept "forgetting" to log in, or kept running their own shadow processes "just to be safe". Not out of malice — out of fear that proving the system works means proving they aren't needed.

The fix is straightforward, if uncomfortable: explain what's happening, be honest about the future, and involve the team in the design of the automation itself. The people closest to a process usually have the best ideas about how to improve it.

The role that gets created

Another thing we notice: automation tends to create a new kind of role, even in small businesses. Someone needs to own the workflows, decide what to automate next, and keep an eye on how things are running. Sometimes that's the operations lead, sometimes it's a new junior role, sometimes it's a hybrid admin/automation position.

In every case we've seen, the person who takes on that role ends up more valuable to the business — and better paid — than they were before. Because the work is more interesting, more strategic, and harder to replace.

What we tell clients

Three things, in every kickoff:

1. Tell your team before we start. Nothing good comes from surprises. Explain what's being automated, why, and what it means for them.
2. Show them the boring parts you're removing. Nobody will miss retyping invoices. Frame it as a gift, because it is one.
3. Have a plan for the freed-up time. If you don't, the time gets absorbed by the same problems you were trying to solve. If you do, this is where the growth actually comes from.

The bigger picture

Over the next decade, most administrative roles will change significantly. The question for every business isn't whether to automate — it's whether to do it thoughtfully, in a way that respects the people involved, or to do it reactively and badly.

The businesses we admire most are the ones who treat automation as an opportunity to upgrade their team's work, not replace their team. Those are also, not coincidentally, the ones that get the most out of it.