12 Questions to Ask a Consultant Before You Hire One

The proposal arrived as a nicely designed PDF: logo, scope, price and a timeline with little arrows. What it didn't say was what happens in week three, when your team opens the new system and has no idea where to start.

Hiring a consultant is one of those decisions where mistakes cost the most, because you don't see the error on signing day. You see it months later. These 12 questions work for any consultant, whether they handle processes, software or implementations, and vague answers tell you as much as good ones.

A heads-up: we're consultants too, so the list applies to us just as much. Ask us anything on it.

Before You Talk Price: The Process

1. What will you ask me about my operation before proposing anything? A good answer describes how they'll learn how you work: who's involved, where things get stuck, what happens today. Red flag: the first meeting is a demo or a price.

2. What would you recommend not automating or changing? A good consultant tells you what to leave alone. Someone who wants to automate everything is selling hours, not results.

3. What do you need from my team, and how much of their time will it take? No project runs itself. If the answer is "nothing, just relax," the project will hit reality in week two.

Experience and Proof

4. Have you worked with companies my size and in my industry? Can I talk to one? Good answers include concrete examples, even anonymous ones, and a willingness to give you a reference. Red flag: logos and generalities only.

5. What certification or formal relationship do you have with the tool, and how can I verify it? A certification can be checked. For monday.com, certified partners are listed in its public directory. Red flag: "we're experts" with no way to confirm it.

6. What was your hardest project, and what did you learn? Anyone who says nothing has ever gone wrong either doesn't remember or isn't telling you. An honest answer about a mistake is worth more than ten success stories.

Money and Ownership

7. What exactly does the price include, and what costs extra? Ask for the breakdown: setup, integrations, training, support. Ask whether the price includes sales tax too (IVA, in Mexico). Red flag: one number with no written scope.

8. When it's finished, who owns the account, the boards and the documentation? You do. You should have admin access and everything documented, so you're not dependent on the consultant forever. Red flag: any answer that leaves you tied to one person.

9. What happens if the scope changes midway? It almost always does. An agreed way to handle it is a good sign. Never having thought about it isn't.

After Kickoff

10. How will you train my team, and will there be follow-up afterward? The best answer is role-based sessions with real data and a check-in a few weeks later. Red flag: one recorded video and nothing else. We cover why this matters so much in this article.

11. If something breaks in month two, what happens? There should be a clear answer: who responds, how fast, and whether it costs extra.

12. How will we know it worked? Before starting, agree on what will be measured: hours saved, response times, errors. Without that, either everything "worked" or nothing did, and nobody can prove it.

How to Use the List

You don't need all 12 to come out perfect. Look for patterns: if four or five answers are evasive, you already have your answer. And compare at least two consultants with the same questions, because differences are much clearer side by side.

When You Don't Need a Consultant

If your team is small and your case is simple, doing it yourself can be the right call. We wrote about that, including the risks, in Certified Consultant or DIY?

See how we work with each client

Want to Test the List on Us?

Book a free consultation and ask all twelve. If any answer doesn't convince you, better to know before you decide.