How to Build a Business Case for Microsoft Copilot: What UK Boards Need to See

UK boards reviewing significant technology investments typically focus on four questions:

What is the financial return and over what period? Boards expect a credible ROI analysis, not just productivity promises. For Copilot, this means specific time-saving estimates by role family, converted to monetary value at fully-loaded employment cost, with a clear statement of the assumptions underlying the calculation.

What evidence supports the productivity claims? A business case built on Microsoft's own productivity research will receive more scrutiny than one built on internal pilot evidence from the organisation itself. Boards are rightly sceptical of vendor-supplied ROI claims; they are more receptive to evidence generated by the organisation's own teams.

What are the risks and how are they managed? Risks include: data security (what data does Copilot access, and how is it governed), compliance (how does Copilot use align with regulatory obligations, particularly in regulated sectors), and adoption risk (what is the confidence in achieving the adoption rates that the financial case depends on).

What happens if adoption is lower than projected? Boards have experienced enough technology investment cases where projected adoption did not materialise to ask this question. A credible business case presents a range of adoption scenarios and the financial case under each.

The Copilot financial case is best built in three stages:

Internal pilot evidence. Before the board business case, run a genuine pilot with at least 50 to 100 users across two or three representative role families. Measure actual time savings and actual adoption rates. These internal numbers, from real employees in the organisation, are the most credible evidence available.

Role-family financial model. For each major role family in scope, calculate: average licence cost per user per year, expected time saving per user per week (from pilot evidence), and financial value of that time saving at the role's fully-loaded employment cost. The net annual value per user minus the licence cost gives the per-user ROI. This calculation, summed across the licenced population at different adoption rate scenarios, gives the financial model.

Breakeven analysis. At what adoption rate does the programme break even? At what adoption rate does it deliver the projected ROI? These are the numbers boards will focus on. If the breakeven adoption rate is very low (say, 25% of licenced users achieving modest time savings), the investment case is robust. If it requires high adoption rates to break even, the adoption risk dimension becomes more material.

For a Copilot investment at significant scale, the financial case should be accompanied by a strategic case that positions the investment in the context of the organisation's broader strategy.

Competitive positioning. What is the Copilot adoption status of the organisation's main competitors and sector peers? A board that understands that competitors are deploying Copilot at scale will weigh the investment decision differently from one that does not have this context.

Talent attraction and retention. Organisations that offer AI-augmented working environments are increasingly at an advantage in attracting the talent profile (younger, digitally confident professionals) that most organisations are competing for. This is harder to quantify than productivity savings but is a real factor in the talent market.

Operating model evolution. Where does the organisation expect to be in three to five years, and how does Copilot deployment contribute to getting there? A business case that connects Copilot to the operating model strategic direction (rather than presenting it as a standalone productivity tool) is more compelling to a board thinking about long-term value creation.

For UK boards specifically, the strategic case should address the ICO and data governance dimensions explicitly. Boards with FCA-regulated members will want to understand how Copilot deployment aligns with regulatory expectations on AI use. Pre-emptive engagement with this question builds board confidence rather than triggering defensive scrutiny.

A Copilot business case presentation to a UK board should be structured to address the four board scrutiny questions in order:

Open with the financial summary. The board decision is fundamentally a financial one. Lead with the investment, the projected return, the adoption rate assumptions, and the breakeven analysis. This establishes the financial frame before the supporting evidence is presented.

Present pilot evidence. Share specific, named results from the internal pilot: 'The [role family] team piloting Copilot has achieved [specific time saving] on [specific tasks], with [adoption rate] after [period]. Here is what they have told us about their experience.' Real voices from real employees are more persuasive than any vendor case study.

Address risk proactively. Present the data security, compliance, and adoption risk dimensions before board members ask. Proactive risk presentation signals rigour; waiting to be challenged signals that risks were not fully considered.

Provide a clear recommendation with three scenarios. Best case, base case, and downside case, each with their financial implications and the specific actions the programme will take to achieve the base case and protect against the downside.