How do we measure the ROI of enterprise AI?
Compare the benefit the project can reasonably take credit for with everything it cost over the same period. Net ROI is (benefit minus cost) divided by cost. Include software, setup, human review and ongoing support. Hours freed count as cash savings only when they reduce an actual expense.
Imagine a team using AI to reduce rework in one process. Before launch, finance records the current cost and the period it will measure. After launch, it counts software, setup, model use, human review, correction and support, then asks which benefit the change can reasonably claim. Completed tasks are evidence of activity, not a dollar return.
Calculate a result over one period
Illustrative example: Over one year, a workflow has $150,000 in benefits that a credible evaluation can attribute to it and $100,000 in all-in software, model, infrastructure, integration, review, and maintenance costs. Net ROI is ($150,000 minus $100,000) divided by $100,000, or 50%. If the $150,000 is only a forecast, the 50% is projected ROI. If a later improvement is observed but the contribution of the workflow is uncertain, report observed change and attributable benefit separately.
Hours freed are capacity. Count them as cash savings only when an actual expense falls; report other valuable uses of that time separately. A rejected AI proposal is not automatically a comparison group: reviewers may reject harder or riskier cases. Agree the baseline, relevant cases, time window and comparison method before calling a change incremental value. The CFO buyer guide gives a wider diligence checklist.
| Record | What it shows | What it does not show by itself |
|---|---|---|
| Proposal and estimated value | Why a change was considered | That the benefit will occur |
| Approved action and confirmed write | What the system was authorized to do and what happened | That the business problem was solved |
| Later business result | What changed for the customer or operation | That AI alone caused the change |
| Evaluated lesson | Whether a proposed rule passed a relevant test | That it applies to every future workflow |
Link decisions to results without claiming proof of cause
A Decision Trace can preserve sources, assumptions, alternatives, a person's judgment, current authority, action confirmation and later observation. A log of API calls has a different job: it shows system events. Keep both when they matter. The trace makes a finance question inspectable; it cannot tell us what would have happened under the path not chosen.
For example, a support workflow may close more tickets while customers still cannot use the service. The owner should check reopens, customer effort and the real outcome. Market conditions, staffing and case mix may also change during the test. Record those possible explanations beside the claimed benefit. The company-intelligence guide separates storing an outcome from testing a lesson for reuse.
At one Fortune 500 insurance carrier, Nodes reports $1.58M in Q1 2025 net savings attributed to the historical candidate-evaluation application and validated by the customer's CFO. This scoped customer evidence has not been independently audited and does not predict a return from a different workflow. The evidence register sets out its scope.
Check the operating cost and authority
Ask which systems and people supply the evidence, who reviews exceptions and who pays for maintenance. Routine steps may run under permission already given for that work. Consequential or newly scoped actions can require review of the actual plan; approval does not guarantee a good decision. If a destination write is uncertain, reconcile it before retrying or calling the task complete.
Deployment matters to the cost and control case. Nodes supports Nodes Cloud, a customer VPC and on-premises options. The selected model, connector, log, support and backup routes determine the actual data boundary and operating responsibility. Private hosting alone does not prove zero external flow. Customers retain their context graph, Decision Traces and outcome history under the applicable agreement; a replacement model still needs testing.
A study discussed by Salesforce in August 2026 surveyed more than 2,000 leaders and emphasized preparation, data scoped to the job and human handoffs. Those are vendor-reported survey findings, not proof that any particular ledger causes ROI. Use them as questions when testing one defined job.
The useful result of an ROI review may be to proceed, narrow the job, gather more evidence or stop. State projected, observed and attributable value separately, and leave a number unpriced when the evidence does not support it.
Sources
Saad Bin Shafiq is the founder of Nodes, serving data-sensitive enterprises. Methodology: Decision Traces.