Reviewed and updated October 8, 2026.
Use this guide to estimate the full cost of an AI workflow before choosing a pilot, buying a platform or commissioning a build. A quote for software or development is only part of that decision. Data preparation, review time, integration, training and ongoing operation also need an owner and an estimate.
Evidence scope: This page is a planning guide. Its previous numerical study findings are not used as evidence here. The worksheet below does not establish typical costs, savings or a return timeline.
Define the decision before estimating cost
Name one workflow, its users and the output they need. Describe the current process and the proposed change. Include an option that keeps the current process or improves it without AI. Compare those options over the same period, with the same workload and acceptance requirements.
For example, a knowledge assistant might reduce searching but add time spent checking answers and maintaining source documents. Count both activities. Time released from a task is not automatically cash saved or revenue earned; explain how the organization would use that capacity.
Full-cost worksheet
Copy this table into your planning document. For each row, record the estimate or range, its source, the responsible person, whether it recurs and what remains unknown. Use supplier quotes, current invoices, workload records and staff estimates that can be checked.
| Cost area | What to include | Evidence to request |
|---|---|---|
| Discovery and evaluation | Workflow mapping, test cases, baseline measurement and human review | Scope, evaluator time and acceptance criteria |
| Data and access | Document preparation, permissions, source cleanup and refresh work | Sample data review, access design and maintenance owner |
| Build or purchase | Development, licensing, model usage, hosting and integration | Itemized quote, usage assumptions and change terms |
| Rollout | User training, parallel operation, support and process changes | Rollout plan, staff time and support responsibilities |
| Operation | Monitoring, evaluation, incidents, backups, upgrades and source updates | Operating plan, recurring charges and response expectations |
| Change or exit | Data export, supplier transition, credential rotation and replacement work | Export format, ownership terms and handoff requirements |
Separate an estimate from a demonstrated benefit
Record each proposed benefit alongside its baseline, measurement method and dependency. Distinguish an observed change from a forecast. A reduction in handling time needs comparable tasks and a record of any added review or rework. A revenue claim needs a defensible link between the change and the revenue, rather than attributing all growth to AI.
Keep a separate list of consequences that are important but not reliably priced, such as a change in access risk or a better audit trail. Do not turn them into monetary savings without a stated method and evidence.
Compare return and break-even consistently
State the period and included costs before calculating a return. For a simple planning comparison, net benefit means the attributed benefit minus the included costs; the return ratio is that net benefit divided by those costs. Break-even is the point when cumulative attributed benefits cover cumulative included costs. Include ongoing costs in both calculations and avoid counting the same saving twice.
A positive monthly operating contribution does not by itself mean the initial investment has been recovered. A forecast return also does not establish when break-even will occur. Show the assumptions, test less favorable cases and update the estimate with actual records.
Choose the next evidence step
If the main uncertainty is answer quality, evaluate representative questions before expanding the build. If it is integration or data access, test that dependency first. If no owner can maintain the workflow, resolve the operating responsibility before rollout.
The production-gap field report explains why an AI-generated business case was checked against verbatim transcripts. It is a firsthand delivery account with status and limitations, not a cost benchmark. The platform ownership report offers a practical view of operating and handoff responsibilities.
For help building a scoped comparison, see AI business-case and ROI modeling and the AI roadmap offer. Request a project review with the workflow, current cost records, proposed options and the assumptions you need to test.
