I keep telling clients a Center of Excellence is not a big department. It is a small group that sets standards, picks the right tools, and stops teams from reinventing the wheel. Most companies need some version of it once automation touches more than one workflow. The minimum structure is usually one business lead who understands the process pain points and one technical partner who can validate what's realistic. Both can start part time. I've seen great results when the business team drives the CoE, because they know where the bottlenecks actually sit. IT should support with governance and security, but the people closest to the work are the ones who pick the right problems to automate first.
1 / A Center of Excellence operates like your internal startup focused on automation tasks. It's designed to unite process with intense dedication. Companies should establish a Center of Excellence because unguided automation often leads to wasted budgets and redundant development. One company we worked with had four teams using different OCR tools to process invoices, all doing essentially the same thing. Through our Center of Excellence, they were able to consolidate efforts and implement a single solution in just two months. 2 / The minimum viable structure includes one operations leader, one developer skilled in RPA or Python, and one analyst fluent in business terminology. With just these three full-time team members, you can run an effective CoE. The team should commit 1-2 days a week to build reusable automation frameworks and templates, and to enforce standardized naming conventions. Without that discipline, automation efforts quickly become unmanageable and result in messy, spaghetti-like systems. 3 / The initiative should be driven by business operations, not initiated just by IT. IT departments often introduce delays with security policies that block operations staff from automating tasks like Excel-based processes. A better model is for IT to define security boundaries, while the business side owns execution. One of our manufacturing clients succeeded by doing exactly that--business operations led a bot-based invoice processing project that updated three ERPs automatically. Within six months, the system was up and running under IT oversight, functioning continuously.
What I've seen is that a Center of Excellence is really just a small group that owns two things: standards and momentum. Companies don't need a big formal program. They need a way to stop every department from building its own version of automation chaos. A CoE gives you one place to define how documents get processed, how data gets extracted, and how exceptions get handled. That alone saves months of rework. The minimum structure is tiny. One business lead who understands the workflow pain, one technical partner who can build or configure tools, and an executive sponsor who clears roadblocks. Most SMBs run this with five to ten hours a week across those roles. And it absolutely should start in the business, not IT. IT can maintain the tools, but only the business knows why invoices get stuck, why documents go missing, or why approvals stall. If the CoE doesn't understand the messy reality, the automation won't stick.