When to Hire a Consultant Instead of a Full-Time Employee

The question comes up regularly in our discovery calls: should we hire someone full-time for this, or bring in a consultant? The answer depends less on budget than most people assume. It depends on the nature of the problem, the timeline, and what the organization needs to be able to do after the engagement ends. This article lays out the considerations we walk clients through.

Problems that suit a consultant ¶

Consultants are well-suited to problems that are time-bounded, require an outside perspective, or involve expertise the organization does not need permanently. A post-merger integration, a one-time strategy reset, or a governance review are examples. The work has a beginning and an end, and the organization does not need someone on staff to maintain the output once it is done.

Consultants are also useful when the problem involves internal politics that make it difficult for an insider to ask the necessary questions. An external party can ask things that would be awkward coming from a colleague, and can surface disagreements that have been avoided because no one wanted to own the conflict.

Problems that suit a full-time hire ¶

If the work is ongoing and requires deep institutional knowledge, a full-time hire is almost always the right answer. A consultant can design a new operational process, but someone inside the organization needs to run it. A consultant can facilitate a strategy conversation, but someone inside the organization needs to hold the leadership team accountable to the decisions made.

The mistake we see most often is organizations hiring a consultant to do work that should be done by a permanent role, and then finding themselves in the same situation twelve months later because no one was hired to maintain what the consultant built.

The hybrid approach ¶

In some situations, the right answer is both: a consultant to design and stand up a new capability, and a full-time hire to run it once it is established. This requires planning the handoff from the beginning of the engagement, not as an afterthought at the end.

We build handoff planning into every engagement where it is relevant. The deliverables are designed to be used by someone who was not in the room when they were created. That is a different design constraint than producing a report for the leadership team that commissioned it, and it affects how we write and structure the work.

The consultant-versus-hire question is worth thinking through carefully before you start either process. Getting it wrong is expensive in both directions. If you are unsure, it is a reasonable topic for a discovery call.