Skip to content
, home

Guide

How to choose a technology consultant

By Campion Fellin · Published · Updated

How do I choose the right technology consultant for my problem?

Choose based on your problem, not the pitch. Look for someone who has solved problems like yours, who will do the hands-on work rather than only advise, and who asks good questions before proposing a solution. Ask how they will report progress and what they will leave behind when they finish. If your problem is broad and needs a large team, a firm may fit better; if it is specific and difficult, a senior independent consultant is often the better choice.

Start by describing the problem

Before talking to anyone, write a few sentences about what has been difficult, what you have already tried, and what a good outcome would look like. This makes it easier to compare consultants, and a good one will use it to ask sharper questions.

What to look for

  • Relevant experience with problems like yours, described in specifics rather than buzzwords.
  • Willingness to do the engineering, not only produce recommendations.
  • Questions before answers: a good consultant wants to understand the situation first.
  • Clear, plain communication about risks and tradeoffs.
  • A plan for handing the work back to your team.

Red flags

  • A detailed solution proposed before they understand the problem.
  • Promises of certainty on problems that are genuinely uncertain.
  • Vague answers about who will actually do the work.
  • No plan for documentation or handover.
  • Pressure to sign a long engagement before any results.

Questions to ask in the first conversation

  • What would you want to look at first, and why?
  • Tell me about a similar problem you worked on. What went wrong along the way?
  • How will you report progress, and how often?
  • What will we have when the engagement ends?
  • What kinds of problems are not a good fit for you?

Frequently asked questions

Should a technology consultant give a fixed price?

For well-defined work, a fixed price can be reasonable. For diagnosis or recovery, where the problem is not yet understood, a short, time-boxed first phase is usually more honest: it produces a clear picture, after which the rest of the work can be estimated properly.

How do I know if I need a consultant at all?

If your team has the skills and the time, you may not. A consultant is most useful when a problem has resisted several attempts, when no one has the relevant experience, or when you need an independent view before a major decision.

How we help: Senior engineering leadership

Let's talk

What’s stuck?

Tell us what’s been difficult, what you’ve tried, and what a good outcome looks like. A few sentences is enough.