Field note · Customer education
How to measure AI ROI before expanding a pilot
Measure AI ROI using completed work, review time, adoption and full operating costs. Includes a worked example and an expansion checklist.
- Source
- Editorial guidance with 1 retrieved source documents for context. Recommendations are our judgement.
- Evidence
- none on this page — it links to the pages that hold it
By Is There an AI for This? · Editorial guidance · Reviewed · How we use evidence
01Decide which benefit finance is being asked to approve
Choose one primary benefit: less paid overtime, more completed work with the same team, faster turnaround or fewer costly corrections. Give it a unit and an owner. Avoid adding several versions of the same benefit together. Time saved and additional output produced in that time may describe the same capacity.
Use a completed task as the unit of comparison. For invoice capture, the endpoint might be an approved record ready for posting. For proposals, it might be a reviewed section accepted by the bid manager. A generated draft is an intermediate output. The measurement must continue through checking, correction and any later rework.
02Collect a fair baseline
- Record a representative sample of ordinary and difficult tasks before the pilot. Keep task category, worker, active handling minutes, waiting time, corrections and final quality.
- Run assisted and unassisted work over comparable categories. Avoid comparing a quiet week of easy enquiries with a peak week of complaints.
- Count rejected drafts and abandoned attempts. If a task falls back to the old method, include both the failed attempt and the fallback effort.
- Measure adoption using eligible tasks completed with the approved workflow. Login counts and enthusiastic demonstrations do not tell you how much useful work passed through it.
Ask a reviewer who did not produce the output to check a sample from both processes using the same rubric. Hide which process produced it where practical. Keep the rubric short enough to apply consistently: correctness, required information, unsupported additions and readiness for the next person.
03Work through the arithmetic without calling capacity cash
For a cash-only business case, replace the planning value with an expense that will actually disappear, such as approved overtime or an avoided temporary contract. If no expense changes, describe the result as capacity. The organisation can still choose to buy capacity, but finance should know what decision it is making.
The simple first-year return on the initial setup investment in this example is (12 × HK$1,400 − HK$14,000) ÷ HK$14,000 = 20%. Its denominator is the initial setup investment, so label it explicitly when comparing other ROI definitions. It excludes discounting and tax. It is a screening calculation, not a valuation model, and it is only useful if the assumptions remain visible.
04Test the assumptions that can reverse the decision
Repeat the calculation at lower adoption and longer review time. At 50% adoption, the same example produces about 13.3 hours, worth HK$2,400 under the assumed rate. Net monthly value falls to HK$200 before setup recovery. If review grows enough to remove the two-minute saving, the time-based business case disappears.
List costs that change with volume separately from fixed costs. Include licences, model usage, document storage, integration support, access reviews, training, source updates and someone monitoring failed tasks. Ask the supplier which line items increase if staff repeatedly regenerate an answer or process an unusually long document.
05Use a decision table with an owner and a review date
- RECOMMENDATION
For a finance-led expansion decision, we recommend requiring a positive conservative case, a quality result at least as good as the baseline, and an owner for every recurring cost.
BasisThe basis is the sensitivity calculation and completed-task measurement above. Document-processing implementation details are provided in the linked source; they do not establish any return on investment.
An illustrative gate is positive net value at 50% adoption, no increase in material correction errors and a payback period within the company’s own purchasing limit. Use the limit finance already applies to similar projects rather than inventing a special rule for AI. Keep high-consequence failures as separate stop conditions even if their average cost appears small.
Stop or redesign if the result depends on excluding review time, if the team cannot reproduce the baseline, or if the benefit is counted twice. Schedule a review after a full operating cycle. A successful pilot earns the next measured step; it does not establish permanent savings across every department.
06Related
Use cases
Stacks
Deployment reports
More field notes
07Evidence
- 01Tier 2official vendor legal documentationVendor legal and technical documentation
GitHub - docling-project/docling: Get your documents ready for gen AI · GitHub
https://github.com/docling-project/docling
FreshRetrieved 19 Sep 2026sha256:5a9468de25771 record
08Primary-source reading
Consult these primary documents when checking a proposed product. Reading links remain available when evidence has not been verified; they do not establish that your planned use is approved or that a recommendation has been proven.