An AI Center of Excellence Without an Engineering Budget Is a Governance Function, Not a Team

The instinct to wait until there's budget for a real team is the mistake. A Center of Excellence was never supposed to be a headcount line. It was supposed to be the place where an organisation's judgement about AI lives, so every team doesn't relearn the same lessons and repeat the same mistakes. Somewhere along the way, the enterprise vendors turned that into a staffing plan.

Open the frameworks from Microsoft, Oracle or Tredence and the assumption is buried in the first paragraph: a CoE has a lead, a group of engineers, a platform team, and a roadmap for building internal tools. That's a fine model if a company already has forty engineers and a mandate to hire ten more. It is useless to the leader who has none of that and isn't getting it this year. The frameworks don't fail because they're wrong. They fail because they answer a question nobody in this position actually asked.

What a CoE actually does, stripped of the org chart

Strip out the headcount and a Center of Excellence has exactly three jobs: decide what good AI use looks like here, catch the bad uses before they cause damage, and make sure what one team learns doesn't die with that team. None of those three jobs require an engineer. They require someone with standards, and a place for those standards to live where people actually check them before acting.

Most failed CoE attempts at this scale don't fail because nobody had standards. They fail because the standards lived in one person's head, got shared in a Slack message once, and were forgotten within a quarter. The governance function existed for exactly as long as someone remembered to enforce it manually.

The received wisdom says wait for budget. That's backwards.

The standard advice, repeated across every enterprise CoE guide, is to secure executive sponsorship and headcount before doing anything structural. That advice is written for a company that was always going to get the budget eventually. It is bad advice for a leader who is the budget. If the plan for AI governance depends on a hire that isn't coming, the plan is not a plan, it's a wish with a Gantt chart.

The actual sequence runs the other way. Build the judgement first, as something that runs without a team, and let it prove itself before anyone argues about headcount. A CoE that only works once it's staffed is not a CoE. It's a proposal.

The operating model for one person with standards and no build team

This is the part the enterprise frameworks skip because it doesn't fit their pricing model. The alternative is not a lighter version of the corporate CoE. It's a different shape entirely.

One person, or a small leadership group, owns the standards. Not a charter document, an actual working system: what counts as an acceptable AI-assisted decision here, what gets flagged for review, what the org has already tried and rejected. That system needs to be running, not written. A PDF that says "use good judgement" is not governance. A system that a team can query before they act, that answers with the standard already applied, is.

That's the exact gap Mindmake's AI brain product is built to fill. It's not a chatbot that knows the market. It's the leader's own standards, judgement and pattern recognition, running as something the rest of the organisation can actually use without that leader personally reviewing every decision. The CoE function without the CoE staff.

Why the enterprise frameworks can't say this

Microsoft's Cloud Adoption Framework, Oracle's AI CoE guidance, and Tredence's operating model all sell into companies that already have platform teams and are deciding how to organise them. That's a legitimate business. It is not this business. A vendor whose CoE guide assumes a build team is not going to recommend against building a team, that would be recommending against its own audience.

The honest version of that structure is simple: a framework written for staffed teams will always assume staffing is the answer, because staffing is what the framework is for. That's not a conspiracy, it's just what happens when the guide and the buyer are the same shape.

What this looks like in the first ninety days

No hiring plan, no platform selection, no six-month rollout. The sequence is: name the three or four decisions where bad AI use would actually hurt (a client-facing output, a pricing call, a hiring screen), write down what "good" looks like for each one in enough detail that someone else could apply it, and put that standard somewhere it gets checked before the decision gets made, not after. That third step is where most attempts quietly die, because "somewhere it gets checked" usually means a person who gets busy and stops checking.

The fix isn't more discipline from that person. It's removing the dependency on them remembering. A running system that holds the standard and gets consulted does not get busy and does not forget.

The gap worth naming honestly

There's no published benchmark for how many single-leader CoEs succeed against how many staffed ones, because nobody's built that dataset and anyone who claims otherwise is guessing. What is checkable is the assumption embedded in every framework currently cited for this question: engineering budget as a precondition. That assumption is either true for the reader, or it isn't. For the leader asking this question, it almost certainly isn't, and no amount of enterprise framework detail changes that starting condition.

A Center of Excellence built without an engineering budget is not a failure mode of the real thing. It's the actual answer for the actual population of leaders asking this question, and the frameworks that ignore that population are answering someone else's problem.

Questions people ask next

Can one person run an AI Center of Excellence alone?

Yes, if the function is treated as governance and standards rather than a build team. The three real jobs, deciding what good use looks like, catching bad use early, and retaining what's learned, don't require engineers, they require a system that holds the standard and gets checked before decisions get made.

What's the difference between a CoE and an AI governance policy document?

A policy document is written once and gets forgotten. A CoE, even a one-person one, has to be a running function that gets consulted before decisions happen, not a reference that people are supposed to remember to check.

When does an AI CoE actually need dedicated engineers?

When the standards need to be enforced automatically across large volumes of output, or when the organisation is building its own AI tools rather than governing the use of existing ones. Most leaders asking this question are doing the latter.

What should the first thing a leader builds be, if not a team?

A running system that encodes what good AI-assisted decisions look like in the two or three areas where a bad call actually costs something, and that gets checked before, not after, the decision is made.