AI centre of excellence: what one looks like in a mid-sized company
A small group with real decision rights does more for AI adoption than a large team with none.

A small group with real decision rights does more for AI adoption than a large team with none.
TL;DR
Most mid-sized organisations we work with already have an AI centre of excellence. They just do not call it that. It is the two or three people everyone asks which tool to use, which data is safe to paste in, and whether that vendor demo was any good. The question is whether that group has the authority and the time to do the job properly.
This guide covers what an AI CoE does, which structure suits a company your size, who should be in it, and how to set one up in a quarter.
An AI centre of excellence is a small team that sets the standards for how an organisation uses AI and helps everyone else meet them. It works as a central hub for AI expertise, governance, and use, so that individual experiments add up to something the business can scale.
The name comes from large enterprises, where a CoE may hold data scientists, engineers, and dedicated governance staff. In a mid-sized business it is usually far smaller. What matters is that someone owns the decisions and has the time to make them.
Without one, the same pattern appears in almost every organisation we meet. Someone in marketing pays for an assistant on a personal card, finance uses a different one, and nobody in leadership can say which company information has gone where. That is how shadow AI grows, and banning the tools rarely stops it.
A working CoE makes a short list of decisions once, for everyone, and keeps them current.
Governance deserves early attention as agents gain autonomy. Only one in five companies has a mature governance model for autonomous AI agents, and a CoE is the natural place to build one before it is needed.
There are three common structures, plus a lighter version we recommend for most companies of 50 to 500 people.
| Model | How it works | Best for | Watch out for |
|---|---|---|---|
| Centralised | One core team owns standards, platforms, and most delivery | Early adoption where strong control matters | Becoming the bottleneck for every request |
| Federated | A central team sets standards; AI leads in each function run local use cases | Larger organisations with several business units | Uneven quality between functions |
| Hybrid | Central control for high-risk systems, local experimentation for low-risk use | A mix of regulated and everyday work | Unclear lines on what counts as high risk |
| AI council | Four to six people from the business, part-time, with one accountable lead | Companies of 50 to 500 people | Meetings that discuss but never decide |
The first three follow the centralised, federated, and hybrid models used in larger enterprises. The council is our own recommendation for mid-sized organisations, which rarely have the headcount for a dedicated team and rarely need one. Our current view is that a council works until several teams are building their own workflows, at which point a federated model makes more sense.
A CoE works like the quality function in a factory. Quality sets the standard, checks the output, and teaches the line what good looks like. If quality starts building the product itself, everything queues at its door. A CoE that insists on delivering every AI project ends up in the same place, which is why the advice from Microsoft's Cloud Adoption Framework is to shift towards an advisory role once approval delays and knowledge bottlenecks appear.
Each person giving a few hours a week is a reasonable starting shape. If the lead has no protected time, the council becomes a monthly meeting with no follow-through.
A small, cross-functional team that sets AI standards, approves tools, prioritises use cases, and measures results for the whole organisation. In a mid-sized company it is often a part-time council with one accountable lead.
It needs the functions of one: someone deciding which tools are approved, which use cases go first, and how results are measured. It rarely needs a large dedicated team to do that.
A Chief AI Officer is the person accountable for AI across the organisation. The CoE is the group that helps that person set standards and spread what works, and it is often led by a CAIO, a Head of AI, or an outsourced equivalent.
For companies of 50 to 500 people, four to six people giving part of their week is usually enough to start. Larger organisations tend to move towards a federated model with AI leads in each function.
Look at the decisions it made, the use cases that moved into daily work, and the measured change in those workflows against a baseline. Policy documents published and meetings held tell you very little.
If you would like to see which of the five readiness dimensions your CoE should tackle first, the AI Readiness Diagnostic gives you a scored picture in about five minutes.
Ready to move from reading about AI to getting your organisation ready for it? Start with the diagnostic.
Take the AI Readiness Diagnostic