Enterprise automation, designed, built and operated in the United States.

What is the manual work costing you?

Seven calculators, arithmetic you can check, and no sales email required. Everything runs in your browser and nothing is sent to us.

Your process

Answer for one process or one team. Estimates are fine; the assessment is where they become measurements.

Everyone who touches the process, including part of a role.
Copying, checking, chasing, rekeying, routing. Not judgment work.
Salary plus employer costs, tooling and supervision, divided by productive hours.
Rule-driven, document-heavy work usually lands between 50% and 85%. The rest stays with people as exceptions.
Model usage, infrastructure, monitoring and the team that keeps it working.

The estimate

Net recovery, first full year $0
Manual hours on this work per year0
Hours a system would take over0
Gross annual cost of those hours$0
Less: running the automation$0
Capacity returned to the business0 people
Build investment that still pays back in 12 months$0

An estimate from your own inputs, not a quote and not a promise. It assumes 46 working weeks and 1,800 productive hours per person per year.

Send these numbers with an assessment request

Opens the contact form with the figures filled in. You can edit them before sending.

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.

Interactive · your numbers, in your browser

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?

Copying, checking, chasing, rekeying, routing. Not the judgment part of the job.
Salary plus employer costs, tooling and supervision, divided by productive hours.
Rule-driven, document-heavy work usually lands between 50% and 85%. The rest stays with people as exceptions.
Cost removed, per person, per year —
Hours they spend on it per year—
What those hours cost today—
Hours a system would take over—
Working days returned to that person—
The same figure across a team of ten—

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 request
Interactive · your numbers, in your browser

What one process costs you a year

Pick a single repetitive process — invoices, orders, applications, claims, tickets — and price it end to end.

Whatever one unit of the process is: an invoice, an order, a case, a ticket.
Everything a person touches, including the checking and the chasing, not just the keying.
Salary plus employer costs, tooling and supervision, divided by productive hours.
The rest comes back to a person as an exception, which is how it should work.
Cost removed from this process per year —
Transactions per year—
Hours the process consumes per year—
What the process costs today—
Hours a system would take over—
Capacity returned to the business—
Cost per transaction today—
Cost per transaction after—

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 request
Interactive · your numbers, in your browser

What reading and keying documents costs

Contracts, invoices, forms, statements, emails. Someone opens each one, reads it, and types what it says into another system.

Anything that arrives as a file or an email and has to become data.
Opening, reading, keying, and the second pair of eyes if there is one.
Manual keying runs at roughly 1% to 4% per field, so a multi-field document is worse than people expect.
Usually far longer than the original keying, because someone has to work out what went wrong.
Salary plus employer costs, tooling and supervision.
Structured and semi-structured documents sit at the top of this range; handwriting and bad scans sit lower.
Cost removed per year —
Documents per year—
Hours spent on them per year—
Of which, fixing keying errors—
What that costs today—
Hours a system would take over—
Capacity returned—

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 request
Interactive · your numbers, in your browser

What your contact volume costs

Calls, chats, emails and forms. Most of them ask a question your systems already know the answer to.

Every inbound channel added together.
Talk or type time plus the wrap-up afterwards.
Status, balances, bookings, documents, simple changes. Anything needing judgment or empathy is not in here.
Including supervision, QA, tooling and shrinkage.
Today these wait until morning. A system answers them as they arrive.
Cost removed per year —
Contacts per year—
Agent hours they consume—
What handling them costs today—
Contacts resolved without a person—
Agent hours returned—
Contacts answered outside business hours—

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 request
Interactive · your numbers, in your browser

How 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.

What the team gets through now, at full stretch.
Capped at 90%: the exceptions never go to zero.
Transactions a month the same team could handle —
Volume multiple, same headcount—
Additional transactions per month—
Additional transactions per year—
Total transactions per year—

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 request
Interactive · your numbers, in your browser

When does it pay for itself?

Put the saving from any calculator above against what a build would cost, and see when the line crosses.

Take an annual figure from another tool on this site and divide by twelve.
Assessment, design, build and integration. Use your own budget figure.
Model usage, infrastructure, monitoring and the team that keeps it working.
Nothing saves anything while it is being built.
Payback from the day you start —
Net saving per month once live—
Net saving per full year—
Cumulative position after 12 months—
Cumulative position after 36 months—

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 request

Why 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.

How an engagement runs, and what each stage costs

Turn the estimate into measurements

A fixed-fee assessment replaces every assumption above with a measured number from your own systems.