Skip to content
AvlokAI

What is that process costing you?

Four numbers you already know. It shows its working, asks for no email, and runs entirely in your browser.

Salary plus employer costs, divided by hours worked, not the take-home rate.

The part with one clear right answer each time. Judgement calls are not automatable and should not be counted here.

Annual cost of this process

 

Of which is rule-driven

 

Hours a year returned to the team

 

The arithmetic

 

Nothing here is sent anywhere. The whole calculation runs in your browser, and you can check every step of it above.

Scope this workflow

What this tells you

The cost of doing something by hand, annualised, and the portion of it that is rule-driven enough to be a candidate for automation. That is a genuinely useful number, because most teams have never put one on the work: it sits inside salaries and looks free.

What it does not

It is not a return, and we are not claiming one. Automating a process has a build cost, leaves an exception path a person still works, and takes time to pay back. Anyone showing you a return without knowing your systems is guessing. This estimates the size of the problem, which is the honest thing a calculator can do.

Assumptions

  • 48 working weeks

    Allowing for leave and public holidays. Adjust the weekly hours if your year looks different.

  • Loaded hourly cost

    Salary plus employer costs divided by hours worked, not take-home pay. Using take-home understates it by a wide margin.

  • Rule-driven means one right answer

    The part with one clear right answer each time. Judgement calls should not be counted; they are the part a person keeps.