How to write a Microsoft 365 Copilot adoption business case

Why you need a business case at all

In many organisations, the Copilot licences were already purchased before anyone asked whether there was a plan to drive adoption. The purchase was made at senior level, often driven by Microsoft's sales process or a board-level directive about AI readiness. So the idea that you now need to make a business case for an adoption programme can feel redundant, surely the fact that the licences exist is the business case?

The problem is that a structured adoption programme requires two things that a licence purchase does not automatically provide: budget (for the programme itself) and protected time (for participants and the facilitator). Both of those require approval, and approval requires a case. Before you write anything, it helps to know exactly what your unused licences are costing, that number is usually the most powerful opening line.

A structured nine-week programme like the Copilot Bootcamp Kit costs between £497 and £1,997 depending on the tier you need. That is a fraction of the annual licence cost for most organisations, but it still needs a decision-maker's sign-off, and that decision-maker will want to understand what they are approving and why.

The five elements of a strong business case

1. The problem

Start with where you are now, not where you want to be. What is your current active adoption rate? What does the Microsoft 365 admin dashboard show in terms of Copilot usage over the past 30 days? How many of your licensed users have used Copilot at all this month?

If you do not know these figures, find them before writing anything else. They are available under Reports in the Microsoft 365 admin centre. The number is almost always lower than leadership assumes, typically 15–30% of licensed seats in unstructured deployments. That number is your opening line.

Frame the problem in financial terms: "We are currently paying £X per month for Copilot licences. Based on active usage data, Y% of those licences are being used. The unused portion represents £Z in monthly spend with no current return." That framing makes the problem concrete and urgent without being alarmist.

2. The options

A good business case presents options rather than just a recommendation. For a Copilot adoption programme, the realistic options are typically three:

• Do nothing, continue with the current unstructured approach and accept that adoption will remain low
• Run internal training, invest internal resource in designing and delivering a training programme without a structured framework
• Use a structured programme kit, deploy a purpose-built adoption framework with minimal internal resource required

The purpose of listing options is to make the recommendation look like a considered judgment rather than a preference. It also gives the decision-maker something to respond to, most people approve options rather than open-ended requests.

3. Costs and benefits

For each option, set out what it costs and what it is likely to produce. The cost of doing nothing is not zero (it is the ongoing cost of unused licences plus the opportunity cost of productivity that is not being realised. At £30 per licence per month for 50 users at 25% adoption, the organisation is paying for 37.5 unused licences per month) roughly £1,125 per month in waste, or £13,500 per year.

The benefit of a structured programme should be expressed as an adoption rate improvement and translated into financial value. Use conservative estimates, a structured programme typically lifts active adoption from 20–30% to 60–80% over nine weeks. If you apply the ROI framework from our article on measuring Copilot ROI, a 50-person team at 70% adoption with a 37% time saving produces more than £160,000 in annual time value against an £18,000 licence cost. The programme kit costs a fraction of a single month's licence spend.

4. Risks

A business case without a risk section looks naive. For a Copilot adoption programme, the realistic risks are:

• Participation risk, staff may not engage if the programme is not supported visibly by leadership. Mitigation: secure a named senior sponsor before launch.
• Facilitator capacity risk, the programme requires one to two hours per week from the facilitator. Mitigation: agree protected time in advance and name the facilitator explicitly in the business case.
• Measurement risk, without a baseline measurement before the programme starts, it is harder to demonstrate improvement. Mitigation: capture current adoption rate from the admin dashboard before week one.

5. The recommendation

State your recommendation clearly and briefly. Specify the option you recommend, the cost, the timeline, the named owner, and the success metric. If your recommendation is to run a pilot first, see our step-by-step guide on how to run a Microsoft 365 Copilot pilot programme. A recommendation that says "I propose we run the Copilot Bootcamp Kit with [Name] as facilitator, starting [date], targeting 70% active adoption by week nine, at a cost of £[X]" is one that can be approved in a single meeting.

The cost of doing nothing

The most powerful framing in any business case for a Copilot adoption programme is the cost of inaction. Most organisations instinctively treat doing nothing as the safe option. It is not. Every month that passes with low adoption is a month in which licence fees are paid for unused seats, a month in which competitors who have invested in structured adoption are building a productivity advantage, and a month in which the habits that make Copilot genuinely useful are not being formed.

The window for structured first adoption is not infinite. Once staff have formed the habit of ignoring Copilot (which happens within the first few months of a failed rollout) reversing that takes more effort than getting it right the first time. The cost of doing nothing is not just the wasted licence spend. It is the harder, more expensive re-adoption work that comes later.