Work it out yourself
This is the same arithmetic we do in a scoping session, run in your browser. Nothing is sent anywhere, there is no form, and we do not know you were here. If the number is not big enough to be worth a meeting, you have saved yourself the meeting.
Defaults are the midpoint of what we see in each vertical. Overwrite them with yours — the result updates as you type.
Year one, at your numbers
net annual benefit after what you pay us
Runs entirely in your browser. No values leave this page — check your network tab.
A calculator that hides its arithmetic is a brochure with a slider on it. Here is all of it.
| Assumption | Value used | Why, and how it could be wrong |
|---|---|---|
| Productive hours per reviewer per year | 1,600 | 2,080 gross less leave, training, meetings and administration. If your team is heavily part-time this overstates the hourly cost and therefore the saving. |
| Supervision time on a completed file | 8% of the original handling time | Someone still reviews exceptions and samples the rest. In the first quarter of a deployment this is realistically 15–20% while thresholds are tuned, so year one is worse than steady state. |
| Files not completed by agents | Cost unchanged | They still take the full manual time. We do not claim partial credit on files the agent could not finish — that is the assumption most vendor calculators quietly break. |
| Rework reduction | 60% of your rework cost | The evidence layer catches its own errors before they leave the process; it does not catch errors that were in the source document. This is the softest number on the page. |
| Price per completed file | Illustrative planning rate by complexity | Demo placeholder. Real pricing depends on document type, integration surface and volume commitment. Replace this with the live rate card before the page ships. |
| On-premise platform fee | US$180,000 per year, illustrative | Appliance, support and model updates. Also a demo placeholder. |
| Implementation cost | Excluded | Deliberately. Payback below is on run-rate only; a first-year view should carry the implementation fee against it. |
This calculator is a planning tool, not a quote, and nothing on this page is a contractual commitment. If the number matters to a decision, bring twenty real files to a scoping session and we will rebuild it against measured handling times rather than your estimate of them.
What the number does not tell you
88% of agent pilots never reach production. Almost none of them fail on arithmetic — they fail because risk and audit cannot see how an individual decision was reached. That cost does not appear above, and it is the one that kills projects.
The number above is annual. The change your operations lead will actually feel is that a backlog becomes a configuration change rather than a recruitment cycle — which matters most exactly when volume spikes.
Every correction a reviewer makes feeds back into your ontology, so the automated share rises on your own documents over time. The calculator holds it flat for year one, which makes it conservative by design.
A number you calculated yourself is still a number about money. The question your risk committee will actually ask is how a decision was reached. Open a real file in the audit-trail explorer →
The next step
A scoping session is not a demo. Bring twenty real files, redacted if you need to. We take three numbers off you — annual volume, fully loaded cost per file today, and what happens when the output is wrong — and hand back a one-page value case in your own KPIs.
If the arithmetic says we are not a fit, we will tell you in the room rather than six weeks later.
If your data can go anywhere and your documents are already clean and digital, you do not need us. Use a hyperscaler document API and spend the money on something harder.
Densery