When to hire a consultant and when to solve it internally

The case for hiring a consultant is not always obvious, and it should not be. External advisory is a real cost, and the organisations that get the most from it are usually the ones that were clear about what they needed before they picked up the phone. This article is an attempt to make that decision more legible.

Three conditions where outside help adds value ¶

The first is when the people closest to the problem are also part of the problem. This is not a criticism. It is a structural reality. When a leadership team has been operating inside a set of assumptions for two or three years, those assumptions become invisible. An outside perspective does not have better information; it has different information, because it is not carrying the same history.

The second is when the organisation needs a decision to be made and the internal process keeps producing the same stalemate. A structured external process can sometimes break that loop, not because the consultant has authority, but because the format creates a different kind of conversation.

The third is when the cost of getting it wrong is high enough that the fee is a reasonable hedge. A strategic misstep that costs six months of runway is more expensive than a six-week sprint.

When to solve it internally ¶

If the problem is well-defined and the organisation has the internal capacity to address it, a consultant is probably not the right tool. External advisory works best on problems where the diagnosis is unclear or where the internal process has already failed.

If the main thing you need is execution support. More hands on a project. A consultant is also not the right fit. That is a staffing question, not an advisory question.

The introductory call at Clear Lantern Hub is designed to answer this question honestly. If the problem is better solved internally, that is what the call will say.