12 questions to ask before hiring a supply chain consultant

Choosing a supply chain consultant is hard when every website sounds the same. The best way to compare them is to ask the same questions and listen carefully to the answers. Here are twelve questions, grouped by topic, along with what a good answer sounds like.

Fit and experience

1. What size of business do you usually work with?

A consultant who mostly serves large enterprises may bring methods that are too heavy for a plant of 80 people. Look for someone who works with businesses like yours and can talk about the constraints you face, such as small teams, limited IT support and messy data.

2. What problems are outside your lane?

This is one of the most useful questions you can ask. A good consultant will tell you clearly what they do not do. If the answer is “everything is in scope,” be careful.

3. Can you explain your method in plain language?

You should understand how the consultant will reach an answer. If they cannot explain how they set safety stock or rank supplier risk without jargon, your team will struggle to maintain the result.

Method and data

4. What data do you need from us?

A good answer is specific: item lists, usage history, lead times, open orders and supplier details. The consultant should also say what happens when the data is incomplete, because it almost always is.

5. Will you work with our existing systems?

Most small manufacturers do not need new software to fix planning. A consultant who starts with your ERP exports and spreadsheets respects your budget and your team’s time. New tools should only be recommended when they solve a specific problem.

6. How do you check that the results make sense?

Look for a review step with your planners or buyers. People who work with the parts every day can spot a bad reorder point instantly, and their input makes the result more trustworthy.

Scope and commitments

7. How do you define the scope?

The scope should be agreed in writing before work starts. It should name the question, the data, the deliverables and the timeline. At Statadventure we use a simple rule: free call first, scope agreed before we start.

8. What happens if the scope needs to change?

Projects do uncover surprises. A good consultant will explain how changes are discussed and agreed, rather than simply growing the work.

9. Do you promise specific savings?

Be wary of any consultant who promises a percentage saving before seeing your data. Honest consultants talk about what they will deliver, not guaranteed outcomes, because results depend on your data, decisions and follow-through.

10. How long will it take?

The answer should depend on the scope and on how quickly you can provide data. For focused work on one product family or supplier set, a few weeks is realistic once the inputs are confirmed.

Deliverables and handover

11. What exactly will we receive?

Ask for examples of the format: a working spreadsheet, a reorder table loaded into your ERP, a risk map or an action list with owners. Be cautious if the main deliverable is a presentation.

12. How will our team keep this running after you leave?

The answer should include written rules, a training session and tools your team owns. If the result only works while the consultant is involved, it is not really yours.

How to use these questions

Ask the same questions of every consultant you are considering, and write down the answers. Compare how specific each one is, rather than how impressive it sounds. You might also ask for a short, sample-based review of your data before committing to a larger piece of work.

If you are still deciding whether you need outside help at all, read consultant or full-time hire and what a supply chain consultant actually does. The full hiring guide is on our supply chain consulting page.

Frequently asked questions

Should we ask for references?

It is reasonable to ask how a consultant has handled similar problems and to request examples of deliverable formats. Respect that some clients prefer confidentiality, and judge the consultant mostly on how clearly they explain their method.

Is a small trial project a good idea?

Often, yes. A short, clearly scoped first step, such as a review of one product family’s reorder points, lets both sides see how they work together before committing to more.

What should be in the written scope?

At minimum: the question being answered, the data you will provide, the deliverables you will receive, the timeline and who owns each step. If any of these are missing, ask for them before work starts.

How do we compare consultants fairly?

Use the same twelve questions with each one, write down the answers and compare how specific they are.