Free tools

Work out whether it is
worth building.

Two calculators we use in discovery, published rather than kept behind a sales call. They run entirely in your browser — nothing you type is sent anywhere, stored, or seen by us. No email required, no result gated.

Tool one

What is this process costing you?

The arithmetic behind every automation decision. Put in what the manual work costs today and what a build would cost, and it tells you the payback period — including when the answer is that you should not spend the money.

Automation payback calculator

Pick one process, not your whole business. It works best on something specific: order entry, invoice matching, weekly reporting, quote preparation.

Labels only. Nothing is converted — put every figure in one currency.
Salary plus everything else that comes with the seat. A rough rule is annual cost to the business divided by about 1,900 hours.
Rework, chasing, corrections. Across everyone, not each.
Be honest here. Almost nothing removes 100%: somebody still handles exceptions. Most real projects land between 60 and 80 per cent.
Costing you now, every year
Saved each year, after the buildTime recovered, less what the system costs to run.
Payback
Net position after three yearsTotal saved less the build and three years of running cost.

This is the same calculation we run in discovery, and it is deliberately conservative: it counts only time, not the errors you avoid, the customers you keep or the reporting you gain. Those are real but harder to defend in a number, so we leave them out.

Tool two

Is this process ready to automate?

Payback is only half the question. A process that nobody agrees on will fight any system you point at it. Ten questions, answered honestly, and a score that tells you whether to build now or fix something first.

Readiness audit

Answer for one specific process. There are no wrong answers and nothing is sent anywhere — a low score is genuinely useful information.

0out of 10
Answer the questions and a reading appears here.

Scores are a prompt for a conversation, not a verdict. We have built successfully for businesses scoring five, because the two failing answers were fixable in a week.

A workshop group seated with laptops, working through a process together
The same arithmetic we run in discoveryThese two calculators are the ones we use before recommending a build.

Got a number you do not believe?

Send us the inputs and we will tell you where the estimate is wrong. We have been on the other side of enough of these to know which assumptions usually break.