Boards do not fund technologies. They fund plans they can judge, from people who seem to understand the risks. An AI plan that reads like a vendor summary gets polite questions and no budget.
What follows is the shape that tends to work in a regulated business, and the questions a sceptical non-executive will ask.
What belongs in the plan
- The problem, in operational terms. Not "adopt AI". "Validation is the critical path on four of our six system projects this year, and we are hiring contractors at a premium to absorb it."
- Scope, narrow and specific. Two or three use cases, named, with the systems and teams involved. A plan covering everything will be read as a plan covering nothing.
- Sequencing with a decision point. Pilot, evaluate against criteria set in advance, then decide. Boards respond well to a stated stopping condition, because it shows you have considered failure.
- The regulatory position, stated plainly. What stays a human decision, how you would answer an inspector, which standards apply. In this industry that paragraph does more for credibility than any projection.
- Honest cost, five years. Including validation, review time and revalidation — see what AI actually costs.
- What you will stop doing. The most persuasive line in any plan, and the most often missing.
The three questions you will be asked
"What happens if it gets something wrong?" The right answer is specific: here is the error type we expect, here is who catches it, here is what it costs when they do, and here is the one failure mode that would be serious and how the design prevents it reaching a record.
"What does this do to our regulatory risk?" Answer honestly in both directions. It adds a system to validate and maintain. It can reduce risk where it makes evidence more consistent and traceability continuous. Claiming only upside is how you lose the room.
"Why now, and why us?" If the honest answer is that competitors are doing it, say so and give the operational reason as well. Boards in this sector have seen enough technology cycles to recognise fashion, and they trust the person who distinguishes it from need.
What weakens a plan
- Vendor numbers presented as your numbers. A "70% reduction" from a case study is a vendor's claim about someone else's process. Use your own baseline or none.
- No baseline at all. If you cannot say what the current process costs and how often it goes wrong, you cannot show improvement later. Measure first — see validation metrics that matter.
- Headcount reduction as the benefit. In a quality function this reads as reducing oversight, which is the opposite of what you want a board to approve.
- A plan with no end state. Pilots that fund more pilots.
If you want the strongest single slide: the current cost and error rate of the process, the pilot result against pre-set criteria, and the decision you are asking for. Everything else is supporting material.
Structure for the pilot itself is in running a 90-day GxP AI pilot, and the strategy work in AI strategy.
Where to go next
Explore GxP Copilot for AI-native validation, TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.