Category

Last updated: June 4, 2026
If you are the COO or CEO with an AI strategy in your head after six months of leadership lunches, two offsites, and a long flight with the CFO, you already know the problem. The board does not vote on conversations. They vote on a document. The strategy that lives in your head loses to the strategy that lives on nine well-built pages every single time, not because the strategy in your head is worse but because a vote requires specificity the head-version was allowed to skip. A workflow shortlist that names "customer service AI" instead of "Tier-1 deposit dispute triage, 4,200 cases per week, current cycle 36 hours" gets deferred, and "deferred" in a board context usually means killed quietly across the next two quarters. In this guide, you'll get the 9-section spine every executable AI strategy plan needs (Executive Summary, Current State, Workflow Shortlist, Sequencing, Operating Model, Data Sovereignty, Budget and Timeline, Kill Criteria, Metrics), what each section has to capture at the level a board will actually approve, and the four sections that quietly lose the vote.
The honest length window: six to ten pages. Shorter and the plan reads as aspirational. Longer and nobody finishes it before the vote, so the Executive Summary on page one becomes the only section that carries the decision. A free AI Assessment populates the Current State and Workflow Shortlist sections with verified data, so the two sections boards interrogate hardest walk into the meeting defensible.
If you want the methodology to build the strategy, see enterprise AI strategy. This post is about the DOCUMENT itself, the nine sections every executable AI strategy plan needs to get past the board. Six to ten pages. Every decision captured. Six to ten pages is not arbitrary. Shorter and the plan reads as aspirational. Longer and nobody finishes it before the vote.
Quick Answer
• What it is: The nine-section document structure every executable AI strategy plan needs: Executive Summary, Current State, Workflow Shortlist, Sequencing, Operating Model, Data Sovereignty, Budget and Timeline, Kill Criteria, Metrics.
• Length: Six to ten pages total. Shorter reads aspirational. Longer never gets read.
• Why it matters: The board approves what the document defends. Vague sections lose budget. Four sections (Workflow Shortlist, Operating Model, Kill Criteria, Metrics) kill most plans before the vote.
Most AI strategy plans fail board approval because they describe ambition instead of decisions. Nine sections, written specifically, force every decision into the open: which workflows, in what order, owned by whom, on whose infrastructure, on what budget, with what kill criteria, measured how. The board does not push back on ambition. They push back on the absence of decisions.
The demand backdrop is real. The Stanford HAI 2025 AI Index reports 78 percent of organizations used AI in 2024, up from 55 percent a year prior. The PwC AI Agent Survey of 300 senior US executives found 79 percent of US businesses already adopting AI agents and 66 percent of adopters reporting measurable productivity gains. Boards are not skeptical that AI matters. They are skeptical that this particular plan, signed under their fiduciary duty, will not become the next pilot that quietly funds itself out of usefulness. The Deloitte State of Generative AI Wave 4 study of 2,773 C-suite respondents found more than two-thirds expect 30 percent or fewer of their generative AI experiments to scale within three to six months. BCG's Where's the Value in AI? report from October 2024 reached the same conclusion from a different angle, finding 74 percent of companies struggling to capture value from AI. The board has read those headlines. They are voting on whether your document is different.
The spine is fixed. The order is fixed. The length per section is approximately fixed. The content inside is what differentiates an executable plan from an aspirational one.
THE NINE-SECTION SPINE
Six to ten pages total. Every section earns its space.
SECTION 01
The whole plan in 300 words. What you will do, in what order, for what budget, against what metric. If a director only reads this page, they can still vote.
LENGTH
1 page.
WHAT IT CAPTURES
The vote-worthy version of the plan.
SECTION 02
Scattered tool inventory, who is using which AI today (officially and unofficially), and an honest read on internal capacity to operate one more system.
LENGTH
1 page.
WHAT IT CAPTURES
The honest baseline.
SECTION 03
Four to six named workflow candidates, each scored on value, feasibility, data readiness, and operating impact. Not departments. Workflows.
LENGTH
1 to 2 pages.
WHAT IT CAPTURES
The actual decision surface.
SECTION 04
Which workflow first, which second, which third, and the specific reason for the order. Quick win at month 3. Compounding capability by month 12.
LENGTH
1 page.
WHAT IT CAPTURES
Order of operations and why.
SECTION 05
Named owner per workflow, named executive sponsor, named technical operator, and the exact escalation path. No teams. People with calendars.
LENGTH
Half page.
WHAT IT CAPTURES
Who owns what, by name.
SECTION 06
Where the data lives during inference. Which jurisdictions. Which contracts. Whether the model trains on your prompts. Whether it can be deployed on-premise.
LENGTH
Half page.
WHAT IT CAPTURES
Where data goes and stays.
SECTION 07
An 18-month spend plan, broken by build, run, and reserve. Quarter-level timeline. First quick win marked at month 3. Reserve sized for the workflow that gets killed.
LENGTH
1 page.
WHAT IT CAPTURES
Money, time, reserve.
SECTION 08
The specific date, measurable threshold, and pre-committed decision rule under which each workflow gets halted. No kill criteria, no executable plan.
LENGTH
Half page.
WHAT IT CAPTURES
When the plan halts itself.
SECTION 09
What proves it works, tied to revenue, margin, or cycle time. Not adoption percentages. Not seat counts. The numbers a CFO will defend in the next earnings call.
LENGTH
1 page.
WHAT IT CAPTURES
Proof the plan delivered.
Nine sections. Six to ten pages. Every decision captured.
Picture a board review at a 380-person specialty manufacturer. The COO walks in with a 24-slide deck titled "AI Strategy." Forty minutes in, the lead director asks the only question that matters: "Which workflow, owned by whom, killed under what condition, measured how?" The deck does not answer any of the four. The board defers the vote and asks for the plan in writing. Six weeks later, the same COO walks in with a nine-page document. Same strategy. Same budget. The Executive Summary names two workflows. Sequencing puts the higher-leverage one first. Operating Model lists the VP of Operations as the workflow owner with the Director of IT as the technical operator. Kill Criteria reads "month 4, cycle-time reduction below 40 percent at the sample size, halt and reallocate." Metrics ties to dispute-resolution cycle time and loaded cost per case. The board approves it unanimously. Same strategy. Different document. Different vote.
The false belief that costs most strategy plans the vote is that the document is downstream of the work. It is not. The document IS the work. The act of writing the nine sections at the right level of specificity forces the leadership team to make the decisions they have spent months quietly avoiding: which workflow first, who owns it on Monday morning, what number triggers a kill, what metric ties to revenue. A plan that is hard to write is a plan that exposes the decisions the team has not made yet. A plan that is easy to write is a plan that hides them. The plan that gets approved is the plan whose author was forced to decide, on the page, before the board did. Boards can tell the difference inside two paragraphs.
Get the two hardest sections written for youThe free 60-minute AI Assessment fills in the Current State inventory and the Workflow Shortlist scores with verified data, so the board reads the two sections they always interrogate hardest and finds answers, not ambition.
Book Your Free AI Assessment →
Four sections do the killing. Every one of them looks fine in a Friday afternoon draft and falls apart under a Tuesday morning board question. If you fix only four sections, fix these.
WHERE PLANS DIE
Same plan. Vague here, the board defers. Specific here, the board signs.
SECTION 03
Vague aspirational items like "AI for customer service" or "AI in finance." Departments, not workflows. The board cannot vote on a department.
THE FIX
Name the workflow, its volume per week, and its current cycle time.
SECTION 05
"The team" or "IT will own it." No person, no calendar, no escalation. Unowned work becomes unowned outcomes.
THE FIX
Name the owner, the sponsor, the operator, and the escalation path.
SECTION 08
No specific date, no measurable threshold. "We will review quarterly." Soft reviews never kill anything. Pilots quietly survive past usefulness.
THE FIX
A date plus a number plus a pre-committed decision rule.
SECTION 09
Vanity metrics. Seat counts. Adoption percentages. Engagement. Not revenue. Not margin. Not cycle time. A CFO will not defend any of those numbers.
THE FIX
Pick metrics a CFO can defend on an earnings call.
The board approves what the document defends. Vague sections lose budget.
Picture a workflow shortlist that died on a Tuesday morning. A 600-person regional bank submits a strategy plan with Section 3 reading "customer service AI, finance AI, ops AI." The lead director asks, "Which customer service workflow, against what current cycle time, replacing what current cost line?" The COO does not have the volume, the cycle time, or the replaced cost. The board sends the plan back. Two months later, the same plan returns with Section 3 reading "Tier-1 deposit dispute triage, 4,200 cases per week, current median cycle 36 hours, target 6 hours, current loaded cost $14 per case." Same workflow. Different document. Approved unanimously.
Section 1 is written last. The Executive Summary is a compression of the eight sections that follow, not a preface to them. Write the eight first, then write the 300-word version of the plan and put it on page one. Section 2 is the hardest section to write honestly, because Current State exposes how scattered the existing tool inventory really is and how thin the internal capacity to operate one more system actually is. Most operators want to skip this section. Boards specifically read it to test whether the rest of the plan is credible.
Section 3 is where executable plans separate from aspirational ones. A workflow shortlist names four to six candidates, scored on value (revenue or margin impact per cycle), feasibility (data and tooling readiness), and operating impact (how much friction shipping it removes). The score is in the document. The methodology behind the score lives in the assessment that produced it. The PwC AI Agent Survey of 300 senior US executives found 66 percent of adopters reporting measurable productivity gains, but only when the workflows are specific enough to measure.
Section 4 is a paragraph that justifies the sequencing. The first workflow is the one with the highest combined score AND the shortest path to a 30 to 90 day quick win. The second compounds on the data or capability from the first. The third is the one that proves the operating model can absorb a parallel build. The 12-month picture matters because boards approve sequenced commitments and defer unsequenced ambition. For a fuller pacing reference, see the 12-month AI roadmap spoke. Section 5 names people. The IBM IBV CEO Study of 2,000 CEOs across 33 countries found 54 percent of CEOs already hiring for AI roles that did not exist a year ago. The board reads this section to test whether the named owner actually exists on the current org chart.
Section 6 captures where data lives during inference and whether the model trains on your prompts. For mid-market operators in regulated industries (financial services, healthcare, legal, defense supply chain), this is often the deciding section. Arkeo deploys a private, on-premise AI workforce where data never leaves the building, under the Assess, Deploy, Manage rhythm, and runs its own operations on the same private agents it deploys for clients (we use what we sell). Sections 7, 8, and 9 are where executive language meets CFO language. In Arkeo's build experience, a scoped single-workflow agent runs about $15,000 to $40,000 and 6 to 10 weeks to production (8 to 12 weeks for a private or enterprise deployment), with the first quick win in 30 to 90 days. Off-the-shelf copilots come in at roughly $20 to $30 per user per month and live in days. Section 8 is the one most operators avoid: kill criteria. The Deloitte Wave 4 finding (more than two-thirds expect 30 percent or fewer of their experiments to scale) is the empirical case for writing kill criteria in advance. Section 9 ties everything to a number the CFO will say out loud. For a worked discussion of board-facing framing, see AI strategy for business leaders.
The blunt truth: most plans fail not because the strategy is wrong, but because Sections 3, 5, 8, and 9 are written vaguely. Vague sections lose budget. The board approves what the document defends.
Walk into the board meeting with the hardest sections defensibleThe free 60-minute AI Assessment populates Current State and the Workflow Shortlist with verified data and scored candidates, so the two sections boards interrogate hardest come back with answers, not ambition.
Book Your Free AI Assessment →
Apply for the free AI Assessment. In 60 minutes you walk away with a 12-month plan tailored to your business. No software demo. No obligation.
Free Planning Session →