Free calculator

What is that manual process actually costing you?

Five questions, one minute. Your own numbers, our arithmetic, and every constant we use written out on this page.

A team reviewing the hours spent on a repetitive back-office process
Run the numbersCheck your AI readiness

Anyone who touches it regularly. Between 1 and 500.

A typical week, not the worst one. Between 0.5 and 40.

03Currency

Each currency has its own salary bands. Nothing is converted.

04What does that group earn, roughly?

Gross annual salary for a typical person on the process. We load it for employer costs.

05How much judgment does the work need?

This sets the share a system realistically takes over.

One step left

Send me the full breakdown

Enter your work email. We will send the annual cost, the hours reclaimed, the saving and what the process still costs once a system runs.

How the numbers work

No black box. Two constants, one formula.

We multiply your people, hours and salary band into an annual cost, then hand back the share of it an agentic system realistically removes.

  1. 01

    Annual hours

    People on the process, times hours each per week, times 46 working weeks. We use 46 rather than 52 because of holiday, public holidays and sick leave, which makes the figure smaller, not larger.

  2. 02

    Cost of an hour

    The midpoint of your salary band taken as a fully loaded cost of employment, divided across a full time year of 1840 hours. Loaded means what the role actually costs you: gross pay plus employer social contributions, workspace, equipment, software, IT and the management time every role carries.

  3. 03

    What the system takes over

    A share set by how much judgment the work needs, never a number you pick for yourself. None of the three reaches everything, because review, exceptions and the decision itself stay with a person.

  4. 04

    What is left

    Annual cost minus the saving. That residual is the honest half of the picture, and it is why we ask about judgment before anything else.

  5. 05

    Over three years

    The same annual figure across the horizon a business case is actually built on. Nothing new is assumed: a process nobody changes keeps costing what it costs, and three years is how long the decision to leave it alone really runs.

The share we apply

How much a system takes over, and why never all of it.

Mostly rules (70% taken over)The steps are the same every time.

Data moves between systems, documents get classified, the same checks run on every case. A system handles the run and a person handles the exceptions and the sign off, which is the part that does not go away.

Routine with exceptions (50% taken over)Predictable most of the time, judgment on the edges.

The common path is mechanical and the exceptions are where the expertise sits. The system clears the volume so your people spend their time on the cases that actually need them.

Judgment heavy (25% taken over)Every case needs a person to decide.

The saving here is in preparation, not decision: gathering context, drafting the answer, surfacing what matters. That is a real quarter of the time, and claiming more would be a number you could not defend to your own team.

FAQ

Fair questions, straight answers.

Does this tell me what a system would cost to build?

No, and that is deliberate. We price a defined outcome after we understand the process, so any number a web page gave you would be a range we would then have to correct. This calculator prices what the manual process costs you today, which is the half you can work out without us.

Why 46 working weeks and not 52?

Holiday, public holidays and sick leave. Using 46 makes the annual cost smaller than a 52 week figure would, which is the direction an honest estimate should err in.

What do you do with my numbers?

Your answers and email go to our team so we can send the breakdown and follow up with related insights, with your consent. We do not sell or share them, and you can ask us to delete them at any time. Details are in our privacy policy.