The decision to bring in an external consultant is rarely made with full clarity. It's usually triggered by a crisis, a deadline, a gap that's become impossible to ignore, or a board that's losing patience. But the more important question, one that most organisations ask too late, is whether the problem they're solving for requires a consultant, or whether it requires building something internal that will still be there after the engagement ends.
What consultants are goodat
External consultants bring three things that internal teams genuinely struggle to replicate: outside perspective, concentrated expertise, and the political neutrality to say things that insiders can't.
The outside perspective is valuable when an organisation has been too close to a problem for too long, when the assumptions baked into every internal conversation are part of the problem itself. Concentrated expertise matters when the challenge is genuinely specialised and the organisation doesn't need that expertise permanently. And political neutrality is often the most underrated value, a recommendation that would be dismissed from an internal team can land very differently when it comes from an external party with credibility.
What consultants are not good at
Consultants are not a substitute for internal conviction. If leadership isn't aligned on the direction, a consultant's recommendation doesn't create alignment, it just gives the disagreement a new focal point.
They're also not good at sustained execution. The gap between a consulting recommendation and operational reality is where most engagements quietly fail. A 90-day strategy project can produce an excellent diagnostic and a credible roadmap. It cannot produce the organisational muscle to execute that roadmap, that comes from internal capability built over time.
The build vs. buy framework
A simple way to think about this decision: ask whether the capability you need is core or contextual.
Core capabilities, the things that directly drive your competitive advantage and need to compound over time, should almost always be built internally. Contextual capabilities, functions that need to be done well but aren't your source of differentiation, are reasonable candidates for external support.
A content and brand strategy agency, for example, makes sense for a manufacturing company whose core capability is precision engineering, not storytelling. It makes less sense for a media company that should be building that muscle in-house.
The hybrid model that often works best
The most effective approach for many organisations is neither pure consulting nor pure internal build, it's a structured knowledge transfer. Bring in external expertise to solve the immediate problem and build the framework, with an explicit mandate to transfer capability to an internal team during the engagement.
This requires a different kind of consulting relationship, one where the consultant's success is measured not just by the quality of the deliverable, but by whether the organisation can operate independently when they leave. Not every consultant will embrace this model. The ones who do are usually worth significantly more than their day rate.
The question worth asking at the start
Before signing any consulting engagement, ask one question: In 12 months, do we want to be better at this, or do we want this done? If the answer is 'done', bring in the consultant and let them own it. If the answer is 'better', structure the engagement around learning, not just delivery. That clarity, made explicit at the start, changes the entire nature of the relationship.
