- Format
- Definition
- Territory
- Cross-cutting
- Basis
- First-hand
Reviewed
Definition
How to choose a consultant, and when not to
How to choose a consultant: check readiness first, then vet on scoping behaviour, named delivery, refusals and artefacts rather than credentials. Includes the checks this studio would fail.
Reviewed by Ameya Sahasrabudhe and Swati Thakur,
Choose on demonstrated judgment, not on polish
Asked how to choose a consultant, the compressed answer is: make the candidates demonstrate judgment on your case before you commit, and weigh behaviours over credentials. Four behaviours carry most of the signal - whether they can explain how they would work in plain terms, whether the person you meet is the person who does the work, whether they can say what a defined piece costs before building it, and whether they have ever told a prospect no. Decks, logos and certificates are cheap to produce; those four behaviours are not. Everything below is those checks made concrete, plus the prior question most guides skip: whether you should be hiring anyone at all yet.
First check whether you are ready to hire anyone
The clearest readiness signal, straight from the practitioner corpus, is whether you can describe the problem in one sentence with a number attached. “We lose track of leads” is a complaint; “we miss about a third of after-hours calls and never call back” is a project. A consultant hired against a complaint will spend the engagement defining it - at consulting rates - and a vague brief is how discovery phases breed further discovery phases. If no sentence-with-a-number exists yet, the cheapest next step is not a vendor call; it is instrumenting the problem until the sentence can be written. A free self-run readiness check exists for exactly this test, and passing it is what makes every check below usable, because each one measures the candidate against your number.
The checks, in the order they pay off
The table lists the checks a buyer can actually run in one or two calls, what to ask, and what a substantive answer sounds like. None of them requires technical depth; all of them require the seller to be specific about your case rather than fluent about their method.
| Check | What to ask | What a good answer sounds like |
|---|---|---|
| The how | ”Walk me through how you would approach our specific number” | A mechanism in plain terms, with what they would need from you and what could make it fail |
| Who delivers | ”Who exactly does the work, and will I meet them before signing?” | Named people, in the room now - not a partner who hands off after the signature |
| Scoping | ”What does the first defined piece cost, and what is out of scope?” | A price and a boundary before work starts, however small the piece |
| Refusals | ”What work do you turn away?” | Specific categories, with reasons - a firm that refuses nothing is selling capacity, not judgment |
| The exit | ”What do we own and run ourselves when you leave?” | Artefacts your team operates without them, named in the contract |
| Evidence | ”Show me something I can verify myself” | Checkable specifics - shipped work, public records, named mistakes - not testimonials |
The cost question deserves one added note, because “how much does it cost to hire a consultant” has no honest general answer: it depends entirely on the shape of the engagement, and a seller who quotes confidently before understanding your case has answered a different check - badly. What a buyer can legitimately demand is the scoping behaviour in the table: published shapes and ranges, and a price for the first defined piece before it begins.
The red flags are behaviours, not resumes
Every red flag worth acting on is the inverse of a check above. The seller cannot explain the how beneath the second question. The senior person who pitched will not name who delivers - the bait-and-switch pattern buyers complain about more than any other. Discovery is proposed with no priced destination. Nothing has ever been refused. The deliverable, pressed for specifics, resolves to a document about the work rather than the work. References deserve a flag of their own: they are weak evidence even when offered, because no seller supplies a bad one - which is why the evidence check above asks for something verifiable instead, and why a candid “here is what went wrong on our own projects” is worth more than three arranged phone calls.
Every guide to choosing a consultant is written by a consultant
Including this one - buyers ask for vetting advice “no vendors please” precisely because the genre is authored by its subjects, and a guide that hides that is already failing its own evidence check. The honest use of a vendor-authored guide is to turn it on its author, so, applied to this page’s: Foxnut Studios publishes its own working rules - named delivery, response commitments, and what it refuses - and its shipped record with named mistakes on the record of what Foxnut Studios has shipped. And the checks it would fail today, stated plainly: it has no publishable named client case study yet, and a two-person senior-only bench means execution volume is a check it fails by design - a buyer needing many hands should choose a firm shaped for that. The remaining checks, run against the consulting practice that publishes this library, are the reader’s to score. The founders have sat in the buyer’s chair, and the check that decided it for them is not the one guides usually lead with. At Viviva Colors, their own art-supplies brand, the website conversion rate had capped out around 2.5 percent against a Shopify industry average near 3, so they went out to buy conversion-rate optimisation help. The first filter was the obvious one, proof of work: only candidates who had demonstrably done this before. It did not narrow the field enough. The second filter decided everything: each remaining candidate was invited to a one-hour freewheeling brainstorm with the entire team on the real problem. Within minutes it was clear which consultants would take the team along and get the job done, and which would talk down from a position of authority, deliver the gospel truths of conversion optimisation, and leave it at that.
They hired the candidate without the best credentials: the one most respectful of the team, quickest to incorporate its suggestions, and honest enough to name his own gaps in this particular market. The team welcomed him, looked forward to the weekly meetings, and went out of its way to implement his ideas because it respected him as a person as well as an expert. Conversion nearly doubled, past the Shopify benchmark. The rule the founders now state from that purchase: a consultant has to get under the hood of your organisation, extract truth from the people who do the work, and be welcomed while doing it - so between a highly capable consultant your team will not get along with and a good one it will, choose the second every single time. A brilliant project poorly implemented loses to an average project well implemented, twice on Sunday. That is the biggest rookie mistake buyers make with this list.
Foxnut Studios works on briefs like this one from Bengaluru and Paris. If you want the shape of that before you talk to anyone, here is the shape of each engagement, and its range.