A different question
Other articles in this series cover what the features do. This one is about the part that gets skipped: what it means for your team.
Automation changes jobs. Handled badly, it produces anxiety, quiet resistance, and people who work around the system. Handled well, it removes the work nobody valued and leaves the work people were hired for.
The difference is mostly in how it is introduced.
What actually goes
Be specific, because vague statements about “efficiency” frighten people.
Typing supplier invoices. The system reads the document; a person checks the draft.
Matching obvious bank transactions. Two hundred clear matches proposed; a person handles the twelve that are not clear.
Reading long threads before a call. Summarised in a minute.
Writing routine follow-up emails. Drafted; a person edits and sends.
Building repetitive documents. Product descriptions, standard quotes, knowledge base articles.
Chasing invoices in date order. Replaced by chasing in likelihood order.
Notice the pattern. Every one is repetitive, low-judgement work that nobody describes as the interesting part of their job.
FIGURE 1: WHAT GOES AND WHAT STAYS
Work that goes
- Typing what is printed on a document
- Matching the obvious bank lines
- Reading long threads before a call
- Writing the same email again
Work that stays
- Deciding whether the draft is right
- Investigating the items that do not match
- Judging what the history actually means
- Deciding what to say to this customer
What stays
The work that needs a person, and it is more than people expect.
Checking. Every AI output in a business system needs review. Extraction is good, not perfect. Predictions are estimates. Generated text is fluent, not necessarily true.
Exceptions. The twelve unmatched bank items. The invoice that does not match the receipt. The customer whose situation does not fit any pattern.
Judgement. Whether to extend credit. Whether a provision is adequate. Whether this deal is real.
Relationships. Difficult conversations, negotiations, a customer who is upset. None of this is a task.
Understanding why. A number tells you margin fell. Knowing it fell because you deliberately took a large low-margin order is understanding, and it is not in the data.
The honest conversation about jobs
People will wonder. Not saying anything is worse than saying something imperfect.
What is usually true in a small or medium business:
Roles change more than they disappear. The accounts person spends less time typing and more time investigating. The support agent handles more tickets with better preparation. The salesperson spends more of the week in conversations.
What is sometimes true:
If a role was mostly data entry, it changes substantially. That is worth being straight about, and worth planning for — retraining into the checking and exception work is usually both possible and cheaper than replacement.
What is rarely true:
That a team gets cut in half. Most SMEs are not overstaffed on admin. They are behind on it. The capacity released usually goes into work that was not getting done.
Say which of these applies in your case, early. People fill silence with the worst version.
Introducing it well
Six things, and they are mostly about sequence and honesty.
1. Start where nobody loses
Agent summaries. Reading supplier invoices. Work everyone already dislikes.
Beginning with something that visibly helps the person doing it makes the next step easier.
2. Let the team see the errors
Do not present it as flawless. Show where extraction gets tax codes wrong. This does two things: it builds appropriate trust rather than blind trust, and it makes clear why the checking role matters.
3. Keep the review visible
If people believe review is a formality before it gets removed, they will stop doing it properly. Say plainly that the review is permanent where money moves.
4. Measure and share the result
Hours saved on bill entry. Days off the collection cycle. Share the numbers with the team, not just with management.
5. Name what the freed time is for
“Efficiency” is not a plan. “You will have four hours a week back, and we want it going into supplier negotiation” is.
Without this, released capacity quietly fills with more of the same.
6. Do not announce it as transformation
The change is real and incremental. Overselling it internally creates expectations that make ordinary results feel like failure.
FIGURE 2: HOW TO INTRODUCE IT
Start where nobody loses
- Work people already dislike. Reading invoices, summarising threads.
Show the errors
- Appropriate trust, not blind trust. It also shows why checking matters.
Say the review is permanent
- Otherwise people stop doing it properly, expecting it to be removed.
Name what the time is for
- Otherwise released capacity quietly fills with more of the same.
What goes wrong
Five patterns.
Announcing efficiency without a plan. People hear “we need fewer of you” whether or not you meant it.
Removing review too early. Because accuracy looked good in a demo. The one bad month costs more than the year of saved seconds.
Automating a broken process. It runs faster in the same wrong direction.
Ignoring the people who work around it. If someone keeps a private spreadsheet, that is information. Find out what the system is not giving them.
Measuring nothing. Without a baseline you cannot tell whether it helped, and you will keep paying for things that did not.
A realistic picture
For a company of thirty people, adopting the well-established uses:
Accounts. Several hours a week back from bill entry and reconciliation. The role shifts towards investigation and analysis.
Sales. Less time on notes and follow-up drafting. More conversations per week, better prepared.
Support. Faster first responses, better context. Watch reopened tickets — if they rise, speed came at the cost of correctness.
Management. Faster answers to routine questions, less waiting for reports.
Nobody’s job disappears. Several jobs get less tedious. That is the realistic outcome, and it is worth having without being oversold.
FIGURE 3: WHAT TO MEASURE
Hours on data entry
- The headline number. Should drop clearly and visibly.
Errors reaching the ledger
- Should be flat or lower. If it rises, review is being rushed.
Where the time went
- Named in advance, or it quietly refills with more of the same.
The rule that protects everything
A person checks anything financial and anything a customer sees.
Not as a temporary measure. Permanently.
The review costs seconds. Removing it saves those seconds and eventually costs a duplicate payment, a wrong price sent to a thousand people, or an entry nobody can explain to an auditor.
The short version
AI removes repetitive, low-judgement work. Typing, matching, drafting, summarising.
It leaves checking, exceptions, judgement and relationships — which is most of what the people were actually hired for.
Introduce it where nobody loses, be honest about what changes, keep the review permanent, and name what the freed time is for.
Done that way it is a straightforward improvement. Done as an announcement about efficiency, it produces resistance that costs more than the automation saves.
Wondering what this would actually mean for your team?
Get in touch. We will look at where the hours go now and give you a realistic picture — including which roles change and which do not.
