The obvious way to think about AI automation is to ask what a piece of software costs. The more useful way is to ask what the person currently doing the work costs. Those are very different questions, and the second one is where the actual decision lives.
A custom automation system costs roughly the same to design and build whether it removes routine work from a junior administrator or from a compliance officer earning CHF 200,000 a year. The engineering is the engineering. What changes, enormously, is the value of the time you recover. This is the single most important idea in automation economics, and most businesses get it backwards. They start with the lowest paid, highest volume roles because the headcount looks large, when the highest return is almost always sitting inside their most expensive roles.
This piece is about how to find that return and how to size it. The maths works in any currency, and it works hardest in the economies where skilled labour is most expensive.
What is the fully loaded cost of an employee?
The first mistake is treating gross salary as the cost of a role. It is not close.
The fully loaded cost of an employee adds everything the business actually spends to keep that person productive: employer taxes and social contributions, pension and benefits, equipment, software licences, allocated office and overhead, recruitment and onboarding spread across their tenure, and the management time spent supervising them. Across most high-wage economies the fully loaded figure lands between 1.25 and 1.4 times gross salary, and higher where employer social charges are steep.
So the real numbers look like this:
- A professional on GBP 90,000 in London costs the business around GBP 112,000 to GBP 126,000 a year, all in.
- A senior compliance specialist in Zurich on CHF 180,000 costs the firm well over CHF 225,000 once Swiss employer contributions and overhead are included.
- A fund administration lead in Luxembourg on EUR 110,000 carries a loaded cost north of EUR 140,000.
- A financial analyst in Singapore on SGD 160,000 costs the business closer to SGD 200,000.
These are not edge cases. They are the standard cost of skilled professional staff in the world's wealthiest economies, and the headline salary understates each of them by tens of thousands a year.
Why does automation ROI scale with the cost of the labour?
Here is the part that changes how you should prioritise.
Imagine the same routine task, document intake and validation, performed in two different roles. In the first, a clerk on a loaded cost of GBP 35,000 spends half their week on it. In the second, an analyst on a loaded cost of GBP 125,000 spends half their week on it. The automation that handles that task is, to a first approximation, the same build. Same integrations, same validation logic, same exception handling.
But the capacity you recover is worth GBP 17,500 a year in the first case and GBP 62,500 a year in the second. The build cost barely moved. The return more than tripled.
Now extend that across a team. The work that quietly consumes the most expensive hours in your business, the reconciliations, the data gathering, the first drafts, the status chasing, the compliance assembly, is precisely the work that automation handles well. The reason to start there is not that expensive people are the problem. It is that an hour recovered from an expensive role is worth far more than the same hour recovered from a low-paid one, for the same engineering effort.
This is why the economics of automation are strongest in high-wage markets. A system that pays for itself slowly against UK clerical wages pays for itself quickly against Swiss, Nordic, Luxembourg, or Singapore professional salaries. The cost of the build does not rise with the local wage. The value of the time it returns does. We wrote about the flip side of this, the silent ongoing cost of leaving it undone, in the cost of not automating.
You are not replacing the person. You are recovering the salary you already pay
The framing that fails is "automate the role." The framing that works is "remove the routine load from the role so the salary buys only judgment."
Every expensive professional role is a blend of two kinds of work. There is judgment, the part that genuinely needs an experienced human: the exception that does not fit the rule, the call that carries risk, the relationship, the interpretation. And there is routine, the part that follows a process: gathering the inputs, checking them against rules, assembling the document, moving it to the next stage.
You pay a senior salary for the judgment. You also pay it, at the same hourly rate, for the routine. Automation lets you stop paying a senior rate for routine work without losing any of the judgment. The same compliance officer reviews exceptions instead of assembling them. The same analyst interprets results instead of compiling them. The same paralegal advises instead of collating.
The result is not a smaller team. It is the same team covering far more volume, with response times measured in minutes instead of days, and the next expensive hire deferred or avoided. In our own engagements we have seen a subject access request process compress from twenty two days to under four hours, and a finance back office move most of its routine load onto systems while the senior reviewers stayed in place and took on more. The headcount did not shrink. The output per expensive person rose sharply.
The compute side makes the case stronger, not weaker
There is a reflexive worry that the running cost of AI eats the saving. For the work that matters here, it does not come close.
The economics of running a model in production come down to inference, the cost of producing each output once the model is built. An inference call that handles a task costs a fraction of a penny. The senior professional whose routine work it removes is priced at six figures a year. The ratio between those two numbers is the whole argument. We explain the underlying mechanics in our glossary entry on AI inference, and the broader economics in the cost of not automating.
For regulated firms in high-wage markets there is a second layer. Running inference privately, on infrastructure the client controls, removes both the per-call API cost and the data-residency exposure of sending regulated data to a third party. That is the architecture we build for finance, legal, and healthcare clients, and it is covered in depth in private AI for UK regulated businesses and why on-premise matters for regulated industries. The point for the cost case is simple: at production volume, private inference is both the more defensible and the more economical option, and it makes the return on automating expensive professional work larger, not smaller.
A worked example
Take a mid-sized regulated firm with two senior professionals whose combined fully loaded cost is GBP 250,000 a year. Suppose 60 percent of their working time goes on routine, rule-based work: intake, reconciliation, data assembly, first-draft reporting.
That routine fraction represents roughly GBP 150,000 of annual loaded cost. A custom automation system that handles the bulk of it does not make either person redundant. It returns most of that GBP 150,000 as recovered senior capacity, faster turnaround, and avoided future hiring, while the two professionals concentrate on the 40 percent that needed them all along.
Against a retainer build, a recovery on that scale typically pays for the engagement inside the first year, and often inside the first two quarters when the salaries involved are high. Raise those two salaries to Zurich or Singapore levels and the payback period shortens again, because the value recovered rises while the build cost does not. This is the same decision we frame in build versus buy, viewed through the lens of what your most expensive hours are actually worth.
How to find your own number
You can run this for your own business in three steps.
- List your most expensive roles by fully loaded cost, not headline salary. Apply the 1.25 to 1.4 multiplier.
- For each, estimate the share of the week spent on routine, rule-based work rather than judgment. Be honest. For most professional roles it is between 30 and 60 percent.
- Multiply. The routine share of the loaded cost of your most expensive roles is your automation opportunity, ranked by size. Start at the top.
That ranked list is almost never the same as the one you get by counting heads. It points at your most expensive people, because that is where the recoverable hours are worth the most.
Working with us
Ayoob AI builds custom automation systems for exactly this kind of work. We are based in Newcastle upon Tyne and deliver remotely to clients internationally, with engagements across the UK, Europe, the Middle East, and Asia. We are ISO 27001:2022 and Cyber Essentials certified, hold five pending UK patents on our compute architecture, and build private and on-premise systems for regulated firms where data cannot leave the client's environment.
If you want to know what the routine load inside your most expensive roles is costing you, and what recovering it would return, that is the conversation we have on a discovery call. Bring your two or three most expensive roles and we will work the number with you.
Related reading
- The Cost of Not Automating: What Manual Processes Actually Cost You
- Build vs Buy: Why Custom AI Software Beats Off-the-Shelf Tools
- Private AI for UK Regulated Businesses: A 2026 Decision Framework
- AI Automation for Singapore Financial Services: PDPA, MAS, and the Cost of Senior Talent
- AI Automation for Luxembourg Fund Administration and Financial Compliance
- AI Automation for Switzerland's Finance and Pharma Sector: FADP, FINMA, and the Cost of Swiss Talent
- AI for Finance Teams
- AI Inference (glossary)
