The slide says the agent saved the planning team hours. A director who has read a few capital requests asks one question: hours against what? You have a vendor dashboard and a usage count. You have no figure your finance team booked before launch. The room nods, the minute-taker writes "revisit next quarter," and the AI line goes into the budget round with a question mark on it.
Manufacturing Happy Hour episode 307 (20 October 2026) lists as a discussion topic "why manufacturers stay cautious on AI until the ROI is clear." The panel includes Rockwell Automation staff, so read that as commentary, not data. The caution is rational when the proof on offer is a number nobody outside the vendor can check.
An AI ROI board report is the evidence page a CEO or CFO takes to the board to justify AI spend. It states the baseline finance booked before launch, the interval measured, the deployment type, the named owner, and the cost line that moved, net of AI spend and rework. Decision counts appear as supporting volume, never as the return.
From the work
Written from 5+ manufacturing and distribution engagements, 2025-2026. This is analysis, not a case study: it names no customer and publishes no client figure.
Why a board rejects an AI ROI claim before it reads the number
The AI business cases we review assume a faster return reads as a stronger one. So the deck leads with the 30-day result, the quick win, the first-month dashboard. A board runs a different test. It asks whether the number could have come from somewhere else: seasonality, a price change, a headcount move, a supplier that happened to ship on time. A shorter window gives the number fewer ways to rule those out.
A 30-day result against a baseline rebuilt from invoices after launch loses to a 90-day result against a figure finance booked before go-live. The first has a flattering window and no anchor. The second has an anchor, and a director can check it without calling anyone.
McKinsey's The state of AI in 2026: On the road to ROI (August 2026) surveyed 1,719 respondents between 4 May and 8 June 2026. It counts AI high performers, those with at least 5% of EBIT from AI and significant impact, at about 6% of respondents (92 of 1,719), and reports them about twice as likely as others to have defined processes to measure the impact of AI initiatives. The survey is global and does not list what those processes record, so read it as direction, not as a benchmark for your plant. We read a defined process as the page in your board pack: baseline source, interval, owner.
The cost is a quarter. The next decision on the AI budget waits for the next board cycle, and the spend keeps running while it waits. You can tell you are exposed without opening a dashboard: the result lives only in a vendor portal, or your finance lead first saw the figure the week the deck was built. The fifth root cause in Your AI Pilot Succeeded. Your Operations Didn't., success never defined in operational terms, is the same gap seen from the pilot side.
The AI ROI board report spec: six fields a CFO can check
Six fields turn an AI result into something a finance reviewer can accept or reject on its merits. They follow the checks in our AI ROI calculator, which is IntelliConnectQ's own scoring rule, not an external standard. They also double as the methodology note a CEO needs under any AI figure on a slide: deployment type, measurement interval, baseline source.
| Field | What the page states | What fails the board |
|---|---|---|
| Baseline source | The cost line finance booked before launch, the ledger or invoice set it came from, the period, and the date it was recorded. | A baseline reconstructed from invoices after launch, or estimated. In the calculator either one caps the claim at Partly defensible. |
| Measurement interval | At least one full business cycle after go-live, such as a quarter-end, with start and end dates. | A single month, a pilot window, or any span that skips a close. |
| Deployment type | What the AI does and where: reads and answers, proposes a decision, or writes to the ERP after a named approval. Which system and environment, live or pilot. | "AI-enabled" with no scope. A board cannot price a capability it cannot locate. |
| Named owner | One person who approves or overrides each AI decision, and one who signs the saving. | "The team" or "operations." A saving nobody signed belongs to nobody. |
| Decision count and dollar outcome | The cost line that moved, in dollars, with decision count beside it as supporting volume. | Decision count presented as the return. |
| Net position | The saving after AI spend (for Business Central agents, Copilot Credit consumption plus licence and partner fees) and after the cost of undoing AI decisions that were overridden or reversed. | Gross saving. |
The first row carries the most weight. In the calculator a claim grades Defensible only with at least 6 of its 7 checks passed and a baseline recorded before launch. A reconstructed or estimated baseline caps the grade at Partly defensible however many other checks pass. A CFO may weight the fields differently. Copy the fields, not the weights.
Decision count earns its place as volume. A count says the system is used. The dollar line says the use paid. Report the dollars first and put the count beside it. The line under the figure on the slide comes straight from the other five fields:
Saving = [cost line] booked in [period] before launch, less [cost line] in [period] after go-live. Site: [site]. Deployment type: [what the AI does, system, live or pilot]. Net of [AI spend] and [rework cost]. Interval: [start date] to [end date]. Baseline recorded [date] by [finance owner]. Approver of AI decisions: [name]. Saving signed by: [name].
Every bracket is something a director can ask about. A bracket you cannot fill means the slide is not ready.
Six AI return claims a board should reject
Each claim below fails a finance reviewer on sight. Each fix is a field from the table.
- Usage as the return. Queries answered, agent actions taken, active users. Each counts activity. A board cannot price a query, and usage climbs when people are told to use the tool. Replace it with the cost line that moved.
- Hours saved with no baseline. The vendor's tool estimates minutes per task. Finance books overtime, contractor spend and headcount. If none of those moved, the board sees spare capacity, which is worth money only once you say who redeploys it and to what.
- Vendor-reported figures. A vendor dashboard sets the metric, the denominator and the period. Ask for the figure from your own ledger. If the two differ, the ledger wins and the vendor figure moves to the appendix.
- A baseline rebuilt after launch. The person rebuilding it already knows the result. Use the figure finance booked before go-live, or say the baseline was reconstructed and let the board discount the claim.
- A window shorter than one business cycle. A single month holds one close. Seasonality, a price change or a late supplier can produce the same movement, and a 30-day result cannot rule them out.
- Gross savings. Credits consumed, partner fees and the time spent undoing overridden AI decisions all offset the saving. On Business Central, agents bill by consumption, covered in Business Central Copilot Credits billing: a default limit is not a budget. The calculator nets that spend against the saving.
A claim that survives all six has already answered most of what a director will ask. The slide that follows can be short.
AI ROI measurement window: report on a business cycle, not a countdown
A 30-day AI return can be true. A board that knows what month-end does to the numbers cannot confirm it in 30 days. Choose the window from your own calendar: the first full close or quarter-end after go-live, with start and end dates on the page.
Set the window before launch, together with the review date and the stop threshold. Write the AI Pilot Stop Criteria Before the Pilot Starts covers who signs that decision at the review date: a sponsor and a finance controller together. The board report is the document that review produces. If you built the case with the four-variable framework in AI agent ROI in manufacturing, the board report is that case settled against booked figures.
A vendor guarantee window sits beside the reporting period and does not replace it. The guarantee settles who carries the risk. The reporting period settles whether the number holds.
Frequently asked questions
What should an AI ROI board report include?
Six fields: the baseline source (a cost line finance booked before launch), the measurement interval (at least one full business cycle), the deployment type, a named owner for the AI decisions and for the saving, the dollar outcome with decision count as supporting volume, and the net position after AI spend and rework. The six fields follow the checks in IntelliConnectQ's AI ROI calculator, which is our own scoring rule and not an external standard.
How long should you measure AI ROI before reporting to the board?
Measure for at least one full business cycle after go-live, such as the first quarter-end, and state the start and end dates. No external standard sets a number of days. The calculator's seven-check rule asks whether the result was measured over a full business cycle, because a single month holds one close and the movement in it has other possible causes. A vendor guarantee window is a separate commitment about who carries the risk.
Is the number of AI decisions a valid ROI metric?
No. A decision count shows the system is used. It does not show the use paid. Report the cost line that moved, in dollars, first, and put the decision count beside it as supporting volume. Take the count from a decision log that records each decision and its approver.
What baseline will a CFO accept for AI savings?
A figure finance booked before launch, with the ledger or invoice set it came from, the period, and the date it was recorded. A baseline reconstructed from invoices after launch, or estimated, weakens the claim: in the calculator it caps the grade at Partly defensible. If you have not launched yet, record the baseline now. If you launched without one, say so on the page and grade the claim down yourself before a director does.
What to get in writing before you sign an AI ROI guarantee
A guarantee moves risk. It creates no evidence. OpsGrid, IntelliConnectQ's decision infrastructure for Dynamics 365 Business Central, is in active beta with a 3-week implementation, and the offer reads "Guaranteed ROI on one agreed use case in 60 days or 50% refund." The OpsGrid page states the terms as "Measurable ROI within 60 days of go-live on one use case we agree with you after the discovery phase, or we refund 50% of the implementation cost." Business Central is required. The guarantee covers one use case, agreed with you in a discovery analysis meeting before kickoff, not every workflow OpsGrid supports. Most companies don't carry every problem on that list, so the use case is picked from the ones you have.
A refund clause answers what happens if the number misses. It leaves open which number, measured against what, and signed by whom. Get three things in writing before kickoff, from any vendor: the baseline source, the interval, and the person who signs the measurement. OpsGrid is in beta and has no standard ROI definition yet, so we set those three for each engagement in the discovery meeting, against the one use case the guarantee covers. With them, the guarantee and your board report describe the same number. Without them, the vendor and your finance lead each measure something different and each can be right.
OpsGrid logs every decision, override and outcome to an audit trail, which gives the decision-volume line of your report a source. The dollar line still comes from your ledger, and the baseline still comes from finance. Run your own claim through the seven checks in the AI ROI calculator first, then apply for OpsGrid beta access with the baseline already in hand.