Artificial Intelligence

How to Build the Business Case for AI in Public Sector and Cultural Institutions: A Guide for Internal Champions

Blue icon of a person with a gear, representing user settings or account configuration.
Prabal Laad
Blue calendar icon with a grid representing days and two rings at the top.
June 3, 2026

If you work in operations, IT or a department lead role at a public sector or cultural organisation, the chances are you have already spotted where artificial intelligence could help. You see the overstretched team, the hours lost to manual reporting, the single administrator pulled in five directions at once. The problem is rarely the idea. The problem is that AI has not been discussed at leadership or trustee level, the budget is not yours to spend, and you are the only person making the case. This guide is for that person - the internal champion. It shows how to turn a personal conviction into an approved, funded initiative that your board, your finance team and your trustees can say yes to.

Why Most AI Business Cases Fail Before They Reach the Board

The single biggest reason good AI ideas never get funded has nothing to do with the technology. It is that the person making the case frames it as a technology investment, while the people approving it are weighing an operations decision. Leaders are not asking "is this clever?" They are asking "does this solve a real problem, at a sensible cost, with manageable risk?" Frame your proposal around the second question and you are already ahead of most.

The second reason is vagueness. Decision-makers approve specific requests and quietly defer everything else. "Approval to explore AI for our reporting" invites a polite "let's revisit that later." A precise ask - a defined budget, a named owner, a timeline and a first milestone - gives them something concrete to approve.

It also helps to understand where hesitation comes from. In public bodies, reluctance usually stems from a familiar mix: genuine fears about getting it wrong, skill gaps, communication and policy immaturity, and operational hurdles. A strong business case anticipates each of these rather than pretending they do not exist.

Start With the Problem, Not the Technology

Before you mention a single tool, describe the problem in concrete terms and put a number on it. How many staff hours go into producing board papers each month? What does it cost to bring in external consultants to backfill capacity? How long does a fault report take to log and chase? The status quo is never free, but its cost is usually invisible until someone makes it visible. Quantifying the price of doing nothing is what transforms a "nice to have" into a decision worth taking.

A Five-Part Framework for a Business Case That Gets Approved

A business case that wins approval is not a long document. It is a short, disciplined argument. These five parts cover everything a board needs.

  1. Define the specific problem and its cost. Pick one process, not the whole department. Describe it plainly and attach a figure to the time, money or risk it currently consumes.
  1. Quantify the benefit conservatively. Estimate the time or cost saved, and then understate it. Numbers you can defend under questioning are worth far more than ambitious ones you cannot.
  1. Make a specific ask. State the exact investment, the timeline, who owns the project after launch, and the first visible milestone. Specificity signals that you have thought it through.
  1. Address risk and governance up front. A few lines on data protection, security and a Data Protection Impact Assessment pre-empt the obvious objections - and reassure trustees that the accountability resting on them is being handled. Showing you have considered the risks builds credibility rather than undermining it.
  1. Propose a pilot, not a transformation. A small, time-boxed proof of concept with a measurable outcome is far easier to approve than a sweeping programme, and it gives everyone an exit if it does not deliver.

A useful discipline: if the core case does not fit on a single page, the thinking is not finished. Leaders read the one-pager, ask a couple of questions and decide. Everything else is supporting material.

Speak Each Stakeholder's Language

The same proposal lands differently with different audiences, so tailor how you present it.

Trustees care about mission, public trust and reputation - and they are already accountable for AI-related risk whether or not they have discussed it. Show how the initiative protects, rather than endangers, the organisation's standing.

Finance and budget-holders will scrutinise the financial logic the way they would any capital proposal: cost, payback period and clear measures of success. Give them defensible figures and the metrics you will track.

IT and security colleagues want to know how the tool handles data, how it integrates, and whether it fits the systems you already run - which is why solutions that extend a trusted Microsoft 365 environment meet far less resistance.

Frontline staff simply want their day to get easier. Their support matters: an initiative the workforce quietly resists is one that tends to fail, so show how it removes friction from their work.

Navigating a Trustee-Controlled Budget

In publicly funded and cultural institutions, the money usually sits with trustees, and additional spend requires formal justification. That changes how you make the case in two ways. First, align the request to the organisation's strategic objectives, not just to operational need - trustees fund initiatives that advance the mission. Second, time your proposal to the budget cycle and any review windows, so it lands when decisions are actually being made. It is also worth noting that the 2025 update to the Charity Governance Code now expects organisations to have a clear approach to technology and AI, which makes a well-documented case easier to justify, not harder.

From Champion to Mandate: Building Momentum

The fastest way to convert a personal project into organisational backing is to deliver a quick win and then make sure people hear about it. A pilot that resolves a long-standing frustration or frees up a measurable chunk of someone's week is worth more than any slide. Share that result in stakeholder meetings and internal updates. Momentum is persuasive: once leaders and colleagues see something working, support tends to follow, and the mandate you lacked at the start begins to form around the evidence.

How VE3 Helps Internal Champions Make the Case

VE3 works alongside the people driving AI from the inside. A focused discovery workshop maps where AI could genuinely help, identifies the highest-value and lowest-risk opportunities, and quantifies the potential benefit - producing exactly the assessment, numbers and risk view that become the backbone of a board-ready proposal. The effect is to turn a champion's instinct into a structured, credible business case, backed by a partner experienced in delivering within regulated public sector environments.

The gap between spotting an opportunity and getting it funded is rarely about the technology - it is about how the case is made. Build it as an operations decision, ground it in real numbers, address risk honestly, and start small. With the right framework, an internal champion can turn conviction into funded action.

Want help shaping your AI business case? Talk to VE3 about a discovery workshop.

Woman sitting on couch wearing a white cable-knit sweater and blue jeans, holding a phone with one hand.
  • © 2026 VE3. All rights reserved.
LinkedIn logo in white on a gray circular background.Facebook social media icon with white f on a gray circular background.Gray circle with white X symbol, indicating a close or cancel button.Gray play button icon within a rounded square with a subtle drop shadow on a white background.