How to Know When You Need a Consultant

Most companies default to the same instinct when they hit a hard problem: find a consulting firm. Sometimes that's exactly right. Often, it's overkill — the problem is real and important, but it doesn't need a project team, a multi-month engagement, or a six-figure budget. It needs someone who has already dealt with something similar.

The questions worth asking first

Before reaching for a large engagement, it's worth being specific about what kind of help the problem actually requires.

Is this a one-time decision or an ongoing capability gap? A single hard decision — how to structure a market entry, whether a pricing model makes sense, how to evaluate a specific vendor — usually needs a second opinion from someone experienced, not a team. A genuine capability gap that will recur (you don't have anyone who understands a whole function) is a different problem, and might justify a hire or a longer engagement.

Do you need a strategy, or do you need someone who's already run the play? A lot of "strategy problems" are actually execution problems in disguise. If someone in your position has faced this exact situation before, their experience is often more useful than a fresh analysis.

How much of the problem is actually unique to your business? Frameworks are generic by design. If your problem is genuinely specific — your market, your team, your constraints — what helps most is someone who has worked inside a similar specific situation, not a generic methodology applied to your numbers.

When a large engagement is the right call

Some problems really do need a team: a company-wide transformation, a process that touches every department, something that requires weeks of on-the-ground data-gathering before any recommendation is credible. If that's genuinely the shape of the problem, a larger engagement is the honest answer.

When a direct conversation is enough

For a lot of everyday business problems, the fastest and most useful path is a direct conversation with someone who has solved something similar — not a proposal process, not a multi-week ramp-up. That's the gap EnlightIn is built to close: describe the problem, find someone with directly relevant experience, and talk to them.