How Boards Actually Evaluate AI Strategy Proposals
What directors read, what they skip, and how to write an AI plan that survives a board meeting instead of getting parked.
Most AI strategy proposals die quietly. Not rejected, just "let's revisit next quarter." The pattern is almost always the same: too many slides, too little math, and no honest answer to the five questions every director asks. This post is about what boards actually read, and how to write an AI plan that clears the room.
The five questions boards actually ask
You can predict a board meeting on AI strategy by the questions asked. In practice they're the same five, in the same order, every time.
- What does this cost us — total, all in?
- What's the expected return, and how confident is that number?
- What are we not doing so that we can do this?
- Who's accountable if it goes wrong?
- Where do the risks concentrate?
Everything else — market context, technology comparison, vendor selection — is background. Boards give you 20 minutes to answer these five questions. The plan that answers them clearly clears; the one that buries them under context stalls.
Question 1 — what does this cost us, total, all in
Boards want the fully loaded number, not the vendor invoice. That means:
- Build cost (agency or internal engineering time)
- Ongoing costs (model API fees, monitoring tooling, hosting)
- Internal team time to support the rollout
- Opportunity cost (what else the team won't do)
A common mistake: presenting a $30K build cost when the real all-in first-year cost is closer to $75K once integration, adoption support, and ongoing model spend are counted. When the true number surfaces mid-project, the board's next meeting stops trusting your math on the follow-up plan.
The strong version: one page with a total number, and a small table showing where it comes from. Include a "what would kill this budget" line — if model costs run 3x projections, does the ROI still work?
Question 2 — expected return and confidence
ROI on internal AI comes in three flavors:
- Hours saved (dollars in labor)
- Revenue enabled (better conversion, faster response, new segments)
- Risk reduced (fewer errors, less compliance exposure)
Boards trust hours-saved math the most because it's directly measurable. They discount revenue-enabled math heavily unless it's tied to a specific pipeline stage or existing conversion rate. Risk-reduced math is trusted for compliance-heavy industries and treated as color elsewhere.
Whatever number you present, attach a confidence range. "$180K to $240K in labor savings, high confidence" is more credible than "$220K in labor savings" without a range. Directors have watched enough plans miss point estimates that they trust ranges more than precision.
Question 3 — what are we not doing
The single most-skipped question in bad AI plans. A board will absolutely approve a new initiative — but only if they understand what's being deprioritised to make room for it.
The good version of this answer: "The engineering team currently ships X. This project reallocates two engineers for six weeks, which means Y moves from Q3 to Q4. That trade is acceptable because Z."
The bad version: "We'll fit this in alongside existing work." Boards read that as "you haven't thought about capacity." The plan gets sent back for revision.
Question 4 — who's accountable if it goes wrong
An AI plan without a named owner is a plan without teeth. Boards want to see:
- The internal executive accountable for the outcome (not the project — the outcome)
- The external partner or hire responsible for delivery
- The specific metric that will be reviewed at 30, 60, and 90 days
- The kill criteria — what would cause you to stop
Kill criteria are the underrated part. A plan that names its own exit conditions reads as mature. A plan that assumes success reads as unfinished.
Question 5 — where do the risks concentrate
Directors are professional risk-assessors. They will find the risks whether you list them or not. A plan that lists them first, honestly, avoids the "wait, what about..." moment that derails the meeting.
The categories to cover, briefly:
- Data and privacy — where the data lives, who touches the models, how it's audited
- Vendor concentration — how tied you are to a single AI provider
- Adoption — the workflow team's willingness to use the new tool
- Model failure modes — what "wrong" looks like, and what the fallback is
- Regulatory drift — for regulated industries, how policy changes could affect the build
Each risk paired with a mitigation. Two sentences each. Any longer and the room starts skimming.
The document that clears the room
The AI strategy that survives a board is short. Three to five pages, ideally readable in ten minutes.
Structure that works:
- Page 1 — The plan in one paragraph, the number in one box
- Page 2 — The 30-day sprint, 90-day roadmap, 12-month vision
- Page 3 — Budget, ROI range, and what's being deprioritised
- Page 4 — Accountability and success metrics with review dates
- Page 5 — Risks and mitigations
Anything longer usually means the strategy hasn't been forced into a decision yet. Length is not a signal of rigor — it's often the opposite.
What good and bad AI plans look like in practice
The bad plan
- 25 slides, half about the AI market
- A budget slide with one number and no components
- ROI given as a percentage with no baseline
- No named owner beyond "the team"
- Risks in a single slide with generic bullets
The result: approved in principle, deferred in practice.
The good plan
- 3 pages of substance, market context in a two-line appendix
- Fully loaded budget with a breakdown table
- Dollar ROI with a confidence range
- A named executive owner and a 90-day review date
- Five specific risks, each with a specific mitigation
The result: approved with real budget in the same meeting.
Mistakes we see in board-ready plans
Vendor-led framing
A plan that reads like a vendor's pitch gets treated like one. Directors know the difference between "we chose this vendor because" and "this vendor wrote our slide deck."
Overpromising phase one
The most common cause of a plan getting parked at review. If phase one promises 40% cost reduction across five workflows in 30 days, no one on the board believes phase two.
Missing the operating model
A plan without an answer to "who runs this after month three" reads as incomplete. Boards want to know if the AI capability lives inside a specific team or is expected to become a horizontal function.
Ignoring the change management cost
The tech is usually the cheap part. Getting an operations team to adopt a new tool is the hard part. Any plan that doesn't budget explicit adoption support gets discounted by experienced directors.
The role of a diagnostic before the board meeting
An outside audit doesn't replace board work — it makes it faster. When the numbers came from a structured diagnostic instead of an internal debate, the board conversation shifts from "are these numbers real" to "which trade-off do we make first."
A common pattern: the diagnostic runs for two weeks, the action plan is written in three to five pages, and the board meeting is a 30-minute approval instead of a two-hour discussion. The audit's biggest ROI is often the meeting it made unnecessary.
Frequently asked questions
How long should an AI strategy document be for a board?
Three to five pages of substance. Longer than that suggests the plan hasn't been forced into a decision. Directors will happily read a short, sharp plan and skim a long one.
How do we handle risk questions we don't know the answer to?
Name them anyway, and label the mitigation as "learning" rather than fabricating a control. Boards trust honesty about unknowns more than pretend certainty.
Should we present multiple options or a single recommendation?
A single recommendation with one or two rejected alternatives named briefly. Multi-option decks read as "we couldn't decide, help." A recommendation with named tradeoffs reads as "we did the work."
What's the right cadence for board updates on the AI plan?
A 30, 60, and 90-day update rhythm during phase one. Then quarterly once phase two starts, with a written summary rather than a presentation slot.
Where this fits in the bigger arc
A board-ready AI strategy is the output of an AI audit, not the input to it. The audit produces the process maps, the scoring, and the plan. The plan gets refined into the three-to-five-page document that boards approve. If you're working backward from a board meeting on your calendar, the audit is the two weeks that make the meeting go well.
Working with us
Our AI Audit is designed to produce exactly the document above — a plan short enough to be read in ten minutes, backed by numbers a director will believe. See the scope, or read our related post on how to prioritise AI opportunities.
FAQ
Frequently asked questions
What do boards look for in an AI strategy?+
Five things: fully loaded cost, expected return with a confidence range, what else is being deprioritised, a named accountable owner, and honestly listed risks with mitigations. Everything else is context.
How long should an AI strategy document be?+
Three to five pages. Boards trust short plans more than long ones. Longer than five pages usually means the strategy hasn't been forced into a decision yet.
Should we present multiple AI options to the board?+
Present one recommendation with one or two named alternatives briefly explained. Multi-option decks read as indecision. A recommendation with named tradeoffs reads as considered work.
How often should we update the board on AI progress?+
Every 30, 60, and 90 days during phase one, then quarterly once phase two begins. Written summaries carry more weight than presentation slots after the initial approval.
Building something similar?
Let's talk in 30 minutes.