KyperX AI  /  Tools  /  AI business case builder

Free tool · Plan an AI opportunity

Estimate the annual benefit and payback of one AI use case.

Hours released is not the same claim as money saved.

Most automation calculators multiply a volume by a rate and call the answer a saving. This one keeps the four things a finance reviewer will separate anyway on four separate lines, subtracts what it costs to run, and prints a one-page case with every assumption attached.

For
Whoever has to put a number in front of a finance reviewer
Time
About 10 minutes
You need
Process volume, handling time, a loaded hourly rate, and what it would cost to build and run
You get
A one-page business case: hours released, benefit, first-year net, payback, and every assumption beside it

The tool

Your figures.

Name a currency and use it throughout; nothing is converted. Press Generate when the required fields are filled.

Enter every money figure in the currency you name below. Nothing is converted and no currency is assumed.

The input controls on this page need JavaScript. Everything else works without it: the worked example below is computed when the page is built, and the method, tables, limits and questions are plain text.

The case

One line. It appears as the heading of the printed business case.

The role that owns the outcome, not the project manager.

A code or symbol of your choosing. It is printed beside every money figure and carried into the export. Nothing is converted.

Baseline, as the work runs today

How many times the process runs in a typical month.

Hands-on time now, including the checking that is already done.

Salary plus on-costs, divided by productive hours. Your figure, in your currency.

Cash the errors in this process already cost: credits, penalties, reprocessing, write-offs.

Licences, contractors or outsourced processing that exist only because of this process.

What changes, in your own judgement

Share of instances the system would handle at all. The rest stay untouched.

Review, correction and handling that remains after the system runs. Not zero in any design that keeps a human check.

How much of the released time converts into something the organisation can actually use or stop paying for. Your assumption, not ours.

Of the baseline cash costs above, the part you could stop spending. Name it or leave it at zero.

Only where there is a stated mechanism: more throughput sold, a queue cleared, a deadline met. Zero is the honest default.

Cost to build and run

Build, integration, data work, testing and your own people's time.

Inference or licence charges, hosting, monitoring.

Changes, retraining, re-evaluation and the support arrangement.

How long before there is enough evidence to continue, change or stop.

Dependencies and consequence

What has to be true for this to be buildable. One per line is easiest to read back.

This drives how much review the design has to keep, which is why residual time is rarely zero.

What you enter stays in this browser. Nothing is sent to KyperX, nothing is written to browser storage, and the copy, CSV and print are assembled from what is already on screen. Reloading clears it.

Method and limits

How it works, and what it does not do.

Open what you need. None of it is required to use the tool.

A worked example, computed when this page was built

Neutral synthetic figures for an invoice-coding process. They are not drawn from any engagement, client or benchmark, and they are not a prediction about your own process.

  • Use-case name — Supplier invoice coding and exception routing
  • Accountable owner — Finance operations manager
  • Currency — AUD
  • Process volume — 900 instances a month
  • Time per instance — 14 minutes
  • Loaded hourly rate — 62 per hour
  • Annual rework or error cost — 48000 a year
  • Other annual baseline cash cost — 22000 a year
  • Proportion in scope — 70 %
  • Residual human time per in-scope instance — 4 minutes
  • Realisation you are willing to state — 40 %
  • Avoidable cash cost you can name — 30000 a year
  • Revenue or capacity value, if any — 0 a year
  • Implementation cost — 85000 one-off
  • Running cost — 1400 a month
  • Maintenance — 18000 a year
  • Pilot duration — 8 weeks
  • Key dependencies — Read access to the accounting ledger; a labelled sample of 400 historical invoices; one finance reviewer for two hours a week during the pilot.
  • Consequence if the output is wrong — Material: affects a payment, a customer or a regulatory record
Hours released
1,260.0
hours a year
Realised capacity value
AUD 31,248
a year
Avoidable cash cost
AUD 30,000
a year
Revenue or capacity assumption
AUD 0
a year
Annual modelled benefit
AUD 26,448
a year
First-year net
AUD -58,552
annual modelled benefit − implementation cost
Simple payback
38.6 months
shown only when the annual modelled benefit is positive
Every line of the worked example, with what each one means
FigureValueWhat it is
Annual instances10,800 a yearmonthly volume × 12
Baseline labour hours2,520.0 hours a yearthe whole process as it runs today
Baseline labour capacity valueAUD 156,240 a yearthose hours at the loaded rate — a measure of size, not a saving
Baseline cash costAUD 70,000 a yearannual rework or error cost plus other baseline cash cost — the ceiling on what can be avoided
Hours released1,260.0 hours a yearin-scope instances only, current time less residual time
Equivalent capacity valueAUD 78,120 a yearreleased hours at the loaded rate — not cash unless you remove the cost
Realised capacity valueAUD 31,248 a yearcapacity value × the realisation you stated
Avoidable cash costAUD 30,000 a yearas you named it
Revenue or capacity assumptionAUD 0 a yearas you named it
Running and maintenance costAUD 34,800 a yearmonthly running × 12, plus maintenance
Annual modelled benefitAUD 26,448 a yearrealised capacity + avoidable cash + revenue assumption − running and maintenance
First-year netAUD -58,552annual modelled benefit − implementation cost
Simple payback38.6 monthsshown only when the annual modelled benefit is positive

Assumptions register

Every figure below is one the reader supplied, not one this page chose. They travel with the result so a reviewer can argue with them.

  • Proportion in scope — 70 %
  • Residual human time per in-scope instance — 4 minutes
  • Realisation you are willing to state — 40 %
  • Avoidable cash cost you can name — 30000 a year
  • Revenue or capacity value, if any — 0 a year
  • Pilot duration — 8 weeks
  • Consequence if the output is wrong — Material: affects a payment, a customer or a regulatory record
  • Key dependencies — Read access to the accounting ledger; a labelled sample of 400 historical invoices; one finance reviewer for two hours a week during the pilot.

Information gaps

Nothing in this example is missing or self-contradictory.

How every figure is calculated

Every figure this tool produces, and how it is produced
FigureHow it is calculated
Annual instancesmonthly instances × 12
Baseline labour hoursannual instances × minutes per instance ÷ 60
Baseline labour capacity valuebaseline labour hours × loaded hourly rate
Baseline cash costannual rework or error cost + other annual baseline cash cost
Hours releasedannual instances × proportion in scope × max(current minutes − residual minutes, 0) ÷ 60
Equivalent capacity valuehours released × loaded hourly rate
Realised capacity valueequivalent capacity value × realisation percentage
Running and maintenancemonthly running cost × 12 + annual maintenance
Annual modelled benefitrealised capacity value + avoidable cash cost + revenue assumption − running and maintenance
First-year netannual modelled benefit − implementation cost
Simple payback, monthsimplementation cost ÷ (annual modelled benefit ÷ 12), only where the annual modelled benefit is above zero
Avoidable cash cost, checkedmust not exceed the baseline cash cost above; a case that avoids more cash than it spends is rejected rather than calculated

Why the benefit lines stay apart

Hours released is a count of time, and the most defensible number here. It says nothing about money.

Equivalent capacity value converts those hours at your loaded rate. This is where most calculators stop and where most business cases are successfully attacked, because an hour released only becomes money if somebody stops paying for it or the time is redeployed onto work with a value. Realised capacity value applies the percentage you state to it. Setting that to zero produces a case resting entirely on cash and revenue, which is easier to defend.

Avoidable cash cost is the part of the baseline spend you could actually stop: an invoice you would not receive, a contractor you would not book. It is the only benefit line that reduces a bank balance directly, so it is capped at the baseline cash cost you recorded — a case that avoids more cash than it spends is rejected rather than calculated.

Revenue or capacity value is for the case where more throughput has a stated commercial mechanism. If you cannot name the mechanism in a sentence, the honest entry is zero.

Running and maintenance cost is subtracted before the headline rather than mentioned underneath it. Payback is reported only where the annual benefit is above zero, because a payback period computed from a negative benefit is meaningless rather than long.

Every input, and what a reviewer will ask

Every input this tool takes, with its unit
InputUnitWhat it means
Use-case name—One line. It appears as the heading of the printed business case.
Accountable owner—The role that owns the outcome, not the project manager.
Currency—A code or symbol of your choosing. It is printed beside every money figure and carried into the export. Nothing is converted.
Process volumeinstances a monthHow many times the process runs in a typical month.
Time per instanceminutesHands-on time now, including the checking that is already done.
Loaded hourly rateper hourSalary plus on-costs, divided by productive hours. Your figure, in your currency.
Annual rework or error costa yearCash the errors in this process already cost: credits, penalties, reprocessing, write-offs.
Other annual baseline cash costa yearLicences, contractors or outsourced processing that exist only because of this process.
Proportion in scope%Share of instances the system would handle at all. The rest stay untouched.
Residual human time per in-scope instanceminutesReview, correction and handling that remains after the system runs. Not zero in any design that keeps a human check.
Realisation you are willing to state%How much of the released time converts into something the organisation can actually use or stop paying for. Your assumption, not ours.
Avoidable cash cost you can namea yearOf the baseline cash costs above, the part you could stop spending. Name it or leave it at zero.
Revenue or capacity value, if anya yearOnly where there is a stated mechanism: more throughput sold, a queue cleared, a deadline met. Zero is the honest default.
Implementation costone-offBuild, integration, data work, testing and your own people's time.
Running costa monthInference or licence charges, hosting, monitoring.
Maintenancea yearChanges, retraining, re-evaluation and the support arrangement.
Pilot durationweeksHow long before there is enough evidence to continue, change or stop.
Key dependencies—What has to be true for this to be buildable. One per line is easiest to read back.
Consequence if the output is wrong—This drives how much review the design has to keep, which is why residual time is rarely zero.

The questions a reviewer asks, in the order they arrive

  1. Is the baseline measured or estimated? An estimated baseline is acceptable if it is labelled. Presented as measured, it is the fastest way to lose the case.
  2. What happens to the released hours? Redeployed onto what, or removed from what. A case that cannot answer should set realisation low and lean on cash.
  3. Why is residual time not zero? If it is, no person checks an in-scope instance. Compare that with the consequence you selected.
  4. Who handles the out-of-scope work? Exceptions rarely get cheaper, and often get more expensive per instance once the easy work leaves.
  5. Is the running cost complete? Inference or licence charges, hosting, monitoring, and the review time the workflow still needs.
  6. What would make you stop? If there is no answer, the pilot has no stop condition — which is the pilot measurement plan.

What this does not do

  1. It is a single-period model. Twelve months at a constant volume, rate and running cost. No discounting, no ramp, no benefit arriving in month nine.
  2. It does not know whether the use case is technically feasible. Feasibility usually turns on where the data lives, what condition it is in and who may see it — none of which appear above.
  3. It does not validate your realisation percentage. That figure is the single largest lever in the model and it is entirely yours. A case that is only positive at a high realisation is a case about redeployment.
  4. It is not a quotation. The implementation and running figures are yours. KyperX publishes engagement starting prices separately.
  5. Payback is simple, not discounted. No cost of capital and no tax effect.
General information

This page is general information and a starting point for your own analysis. It is not financial, accounting, tax or investment advice, and it does not take account of your organisation's circumstances. Every figure is arithmetic on values you entered; none is a forecast, a guarantee or a result attributable to KyperX. Where a figure would inform a material decision, have it reviewed by someone accountable for the numbers.

Terms used here

  • Loaded hourly rate — salary plus on-costs divided by productive hours, rather than the headline salary divided by 1,800.
  • Equivalent capacity value — released hours priced at that rate. A measure of size. It becomes money only when a cost is removed or the time is redeployed onto something valuable.
  • Realisation — the proportion of capacity value you are prepared to claim as a benefit. Yours, not ours.
  • Avoidable cash cost — spend that stops. The only benefit line that changes a bank balance on its own.
  • Residual human time — minutes still spent per in-scope instance after the change, including review and correction.

Common questions

How do I calculate the ROI of an AI project?

Start from what the process costs today, measured the same way before and after: volume, handling time and a loaded hourly rate. Then separate the benefit into hours released, the cash cost you can actually stop paying, and any revenue with a stated mechanism. Subtract the annual running and maintenance cost before the headline, then subtract implementation to get a first-year position. A single percentage without those components is not a return, it is a claim.

Why does this tool refuse to call released hours a saving?

Because an hour released is only a saving if the organisation stops paying for it. Most do not: the people stay and do other work, which may be more valuable but is a different claim. Calling capacity a saving is the most common defect in AI business cases and the easiest for a finance reviewer to reject.

What realisation percentage should I use?

The tool deliberately suggests none, because any default would be invented. Pick a figure you can defend by naming what happens to the time, and be aware that a case which only works above about 70% is really a case about redeployment.

Why can't I claim more avoidable cash than my baseline cash cost?

Because it is arithmetically contradictory: you cannot stop paying more than you are paying. The two baseline cash fields set the ceiling, and the tool refuses to generate a result that breaches it rather than producing a number you would have to defend later.

What is a reasonable payback period for an AI project?

There is no defensible general answer, and any figure quoted as an industry norm is invented. What you get here is your own payback under your own assumptions, printed beside them so the number can be argued with rather than believed.

Does anything I enter get sent to KyperX?

No. The calculation runs in your browser, nothing is written to browser storage, and the copy, CSV and print outputs are built from what is already rendered.