Diverse group of professionals talking around a conference table in an office setting

Build vs. Buy: When to Hire an OCM Consultant vs. Build an Internal Change Team

by Kevin Rillo, Vice President, OCM Center of Excellence, Judge Learning Solutions

August 25, 2026

A while back, I wrote about why engaging an OCM consultant is crucial for successful organizational transformation. Since then, the question I get most often hasn’t been whether change management matters. Every leader I talk to has already accepted that. The question now is more practical: should we build this capability in-house, or bring in outside help?

It’s a fair question, and it deserves a real answer instead of a sales pitch. So let’s walk through how I actually advise clients to think about it.

Start With the Question Behind the Question

When someone asks me “build or buy,” what they’re usually really asking is one of three things:

Can my internal team handle this on top of everything else they’re doing?

Do we have the specific expertise this program requires?

Is this a one-time need, or a capability we’ll need again and again?

Get honest answers to those three, and the build-vs-buy decision mostly makes itself.

The Case for Building Internally

If your organization runs change programs constantly, such as new product launches, recurring system updates, and ongoing process improvements, there’s a real argument for building permanent internal capability. You retain institutional knowledge. Your change practitioners understand your culture, your politics, and your history without a ramp-up period. Over time, an internal team is often more cost-effective than repeatedly paying for external expertise.

But building internal capability well takes longer than most organizations expect. You’re not just hiring a person; you’re building a discipline. That means defining a methodology, establishing governance, training managers to reinforce change instead of just announcing it, and giving your change function enough organizational authority to actually influence a program rather than just support it from the sidelines. Done halfway, an internal OCM function becomes a communications team with a fancier title, and it won’t hold up under the pressure of a major transformation.

The Case for Bringing in Outside Help

Here’s where I’d push back on a common assumption: bringing in an OCM consultant isn’t an admission that your team can’t handle change. It’s a recognition that large-scale transformation and steady-state operations require different muscles.

Bring in outside expertise when:

The program is large, complex, or unlike anything you’ve done before. An ERP replacement, a merger integration, or a corporate separation touching tens of thousands of employees across multiple countries is not the same challenge as rolling out a new expense tool. You need practitioners who have done this specific type of change before, not people learning the pattern in real time on your dime.

Your internal team doesn’t have the capacity, not a capability shortfall. This is the scenario I see most. Your people are good at change management. They just can’t do it and their day jobs at the same time during a 12-month transformation. Augmenting with senior consultants lets you scale up without permanently expanding headcount you won’t need once the program winds down.

You need a methodology-neutral perspective. Internal teams sometimes get attached to a framework or a way of doing things because it’s what they know, not necessarily what the program needs. An outside practitioner who’s fluent across ADKAR, Kotter, Bridges, and custom hybrids can assess your specific context and recommend the approach that actually fits, rather than forcing your program into a familiar shape.

You’re managing change fatigue across multiple, overlapping initiatives. If your organization has three or four transformations running at once, and your internal team is already stretched managing business as usual, external capacity isn’t a luxury. It’s what keeps the wheels on.

A Middle Path: Augmentation, Not Replacement

The build-or-buy framing sometimes implies it’s all one or the other. In practice, most of the successful programs I’ve been part of use a hybrid model. Internal team members own the relationships, the institutional context, and the long-term capability. Senior external practitioners embed directly into the workstreams that need immediate, specialized capacity, working inside your existing PMO structure and governance rather than standing up a parallel one.

This is worth spelling out because it changes the real question. It’s not “internal team or consultant.” It’s “which parts of this program need external capacity, and for how long?” That’s a much easier conversation to have with your leadership, and a much easier budget line to justify.

Questions to Ask Before You Decide

Before committing either way, I’d want honest answers to:

Has our internal team led a program of this size and complexity before, or would this be a first?

Do we have the bandwidth to run this change program on top of existing responsibilities, without burning people out?

Is this a one-time transformation, or the first of several we’ll need to manage over the next few years?

Do we have a clear, agreed-upon methodology, or are we starting from scratch?

What’s the real cost of getting this wrong, in delayed adoption, lost productivity, and leadership confidence, versus the cost of bringing in outside expertise?

That last question is the one people underweight most often. The cost of under-resourcing change management rarely shows up as a line item. It shows up as help-desk tickets, shadow processes, and a transformation that technically launched but never actually changed how people work.

The Bottom Line

There’s no universally right answer to build vs. buy. There’s only the right answer for your specific program, your specific team, and your specific timeline. What I’d caution against is defaulting to “we’ll handle it internally” simply because bringing in outside help feels like an extra cost. On a major transformation, the real extra cost is usually the one you don’t see coming: the adoption gap that shows up six months after go-live, when the technology works fine and almost nobody is using it the way it was designed.

Whether you decide to build, buy, or blend the two, the goal is the same: making sure your organization’s investment in change actually turns into value realization.

Not sure which model fits your next transformation? Reach out to our OCM Center of Excellence and we’ll help you think it through.