Guides · ROI calculator

Work out whether automating this process pays.

Four numbers you already know, and four assumptions you can argue with. Nothing is sent anywhere — the arithmetic runs in your browser, and you can take the result to your own finance team or to us.

Step 1

The process as it runs today.

Loaded cost means salary plus employment costs and tooling — usually 1.2–1.4× the headline salary, not the salary itself.

Step 2

The assumptions. Change them until you believe them.

These four are where every ROI model is won or lost. The defaults are what we would use for a first pass on a typical back-office process; they are not promises, and the honest range is wide.

70%

The straight-through rate. Above 85% is rare in the first year and should be treated with suspicion in any proposal, including ours.

50%

Exceptions do not become free. At 50% a case that took 9 minutes takes about 4½ when it lands on a person with the work already done.

400

Model and infrastructure usage, licences the flow needs, and the maintenance it takes to keep working when a supplier changes a format.

25 000

Move this until it matches a real quote. If payback only works at the bottom of the range, the project is marginal — that is useful to know now.

What this model deliberately does not count
·

Hours spread thinly across many people. Twenty minutes saved for forty people is a nicer day, not a line in the P&L. Count it only if a role is not backfilled or a hire is not made.

·

Cycle time, error rates and rework. Often worth more than the labour saving and frequently easier to prove — but they belong in their own units, not converted into money with an invented multiplier.

·

Your internal project time. Realistically a few hours a week from whoever owns the process, and more during the pilot. It is not on our invoice and it is still a cost.

·

Volume growth. A process whose volume is rising is worth more than this shows, because you are also buying the headcount you will not add.

Your numbers
Manual cost today, per year
50 400
1 440 hours a year on this process
Net annual saving
12 840
After exception handling and running costs.
Payback period
23 months
Net in year one: -12 160
Marginal, but plausible.

Payback lands inside two years. That can still be right, particularly if volume is growing, but it leaves little room for the assumptions to be optimistic.

Get this checked, free →

Your numbers travel with the request. The mini-audit either confirms them or tells you where the model is wrong.

Related

What to read once you have a number you believe.

{{ crumbGuides }} · {{ crumbCalc }}

{{ heroTitle }}

{{ heroSub }}

{{ step1 }}

{{ s1Head }}

{{ rateNote }}

{{ step2 }}

{{ s2Head }}

{{ s2Sub }}

{{ autoPct }}%

{{ autoNote }}

{{ excPct }}%

{{ excNote }}

{{ curSym }}{{ runFmt }}

{{ runNote }}

{{ curSym }}{{ buildFmt }}

{{ buildNote }}

{{ honestKicker }}
·

{{ hn }}

{{ resKicker }}
{{ rManual }}
{{ curSym }}{{ manualFmt }}
{{ hoursFmt }} {{ hoursLabel }}
{{ rNet }}
{{ curSym }}{{ netFmt }}
{{ rNetNote }}
{{ rPayback }}
{{ paybackText }}
{{ rFirstYear }} {{ curSym }}{{ firstYearFmt }}
{{ verdictTitle }}

{{ verdictBody }}

{{ ctaBtn }}

{{ ctaNote }}

{{ nextKicker }}

{{ nextHead }}

{{ l.kind }}
{{ l.t }}

{{ l.d }}