Twelve calculators, all free, none of them gated
Six run further down this page, five sit on the capability page they belong to, and the team calculator is directly below. Every one runs in your browser.
Pick the question you actually have
- What does this cost across a team? Team calculator
- What does one person’s manual work cost? Per employee
- What does one process cost a year? Per process
- What does reading and keying documents cost? Documents
- What does our contact volume cost? Customer operations
- How much more could the same team handle? Capacity
- When does a programme pay for itself? Payback
- What does the payables queue cost? Accounts payable
- What does slow lead handling cost? Lead handling
- What does manual planning cost? Planning & expediting
- What do the gaps between systems cost? Integration
- What does covering nights and weekends cost? Out-of-hours
What this calculator leaves out
Every one of these makes the real case stronger except the last, which we included deliberately.
Errors and rework
Manual processes generate corrections, credit notes, re-submissions and complaints. That cost is real and usually larger than people estimate, and none of it is counted above.
Cycle time
An approval that takes three days instead of three minutes has a cost in working capital, lost orders and customer patience. Not counted.
Coverage
Systems work nights, weekends and December. Adding that coverage with people costs a premium that is not in these numbers.
Attrition and hiring
Repetitive work is the work people leave over. Recruitment and ramp-up costs are not counted.
Risk and evidence
Consistent policy application and a complete audit trail have a value that shows up only when something goes wrong. Not counted.
What is counted against you
The ongoing cost of running and supporting the automation is subtracted, and the automatable share is applied to the whole workload rather than assumed to be everything.
Price it a different way
The calculator above prices a team. These price a person, a process, a document queue, your contact volume, the capacity you would get back, and the point where a programme pays for itself.
What one person's manual work costs you
Take one person on your team. How much of their year goes to work a system could do, and what does that cost?
One person, your numbers. It counts only the labour hours, so it ignores the errors, the delays and the overtime that manual work also produces. Runs on 46 working weeks and 1,800 productive hours per person per year. It is an estimate from your own figures, not a quote.
Send these numbers with an assessment requestWhat one process costs you a year
Pick a single repetitive process — invoices, orders, applications, claims, tickets — and price it end to end.
Labour only. It does not count the rework, the late payments or the customers who left while the queue moved. Runs on 46 working weeks and 1,800 productive hours per person per year. It is an estimate from your own figures, not a quote.
Send these numbers with an assessment requestWhat reading and keying documents costs
Contracts, invoices, forms, statements, emails. Someone opens each one, reads it, and types what it says into another system.
Rework is counted because it is the part nobody budgets for. Downstream costs of a wrong number reaching a ledger are not. Runs on 46 working weeks and 1,800 productive hours per person per year. It is an estimate from your own figures, not a quote.
Send these numbers with an assessment requestWhat your contact volume costs
Calls, chats, emails and forms. Most of them ask a question your systems already know the answer to.
The saving assumes the freed hours are either removed or moved to work that needs a person. Deflection above 60% is achievable but takes longer to reach. Runs on 46 working weeks and 1,800 productive hours per person per year. It is an estimate from your own figures, not a quote.
Send these numbers with an assessment requestHow much more could the same team handle?
The other way to read a saving: not fewer people, but more volume through the team you already have.
Assumes the freed time goes back into the same process and that exceptions still reach a person. It is an upper bound on throughput, not a promise about demand. Runs on 46 working weeks and 1,800 productive hours per person per year. It is an estimate from your own figures, not a quote.
Send these numbers with an assessment requestWhen does it pay for itself?
Put the saving from any calculator above against what a build would cost, and see when the line crosses.
A negative first-year position is normal and not an argument against the programme; look at where month 36 lands. If the monthly saving does not clear the running cost, no payback exists and the tool will say so. Runs on 46 working weeks and 1,800 productive hours per person per year. It is an estimate from your own figures, not a quote.
Send these numbers with an assessment requestWhy we publish this
Most automation proposals arrive with a savings number the buyer cannot reproduce. The number is built on assumptions nobody shows, and the first thing a finance director does with it is discount it by half.
We would rather you do the arithmetic yourself, on your own inputs, before you talk to us. If the number is small, automation is probably not your priority and we have saved you a meeting. If it is large, the assessment turns those estimates into measurements and the roadmap tells you which part to take first.
Turn the estimate into measurements
A fixed-fee assessment replaces every assumption above with a measured number from your own systems.
