The decision to hire a consulting partner is almost always made on the wrong criteria. Firm brand. Slide quality. Seniority of the partner in the room. Whether the proposal felt tailored (it usually was not — the same deck runs for every prospect in the same sector).
These criteria are correlated with winning pitches, not with delivering outcomes. The firms that win pitches and the firms that deliver outcomes overlap, but they are not the same set.
Clients who tend to get the best outcomes from consulting relationships — not just in our experience of the industry, but consistently across the field — evaluate on a different set of questions. Not "how impressive was the pitch?" but "who will actually be in the room, and what have they done before?" Not "do they have a methodology?" but "can they explain what they will do in the first 30 days without referencing the methodology?" Not "do they have sector expertise?" but "have they done this specific thing, in a context similar to ours, and can they tell us what went wrong?"
These are harder questions to ask, and harder to answer honestly.
The seniority gap
The most consistent complaint from clients who have had poor consulting experiences is some version of the same observation: the people who sold the engagement were not the people who delivered it.
This happens structurally. Large consulting firms are built around a model where senior partners win work and junior consultants — often recently graduated, often in the role for the first time — deliver it. The firm's margin depends on this structure. The client's outcome depends on it not working that way.
The question to ask in the first meeting is not "who leads this engagement?" but "who will be on-site, and what is their personal track record of delivering this type of work?" Press for names and CVs, not grade levels and org charts. If the answer is vague, that is informative.
The methodology trap
Every consulting firm has a methodology. Frameworks are branded, diagrams are printed, and the methodology is presented as the intellectual property that justifies the fee. In practice, methodologies are rarely the thing that determines whether a programme succeeds.
The reason is simple: a methodology describes what to do. It does not describe how to handle the situation where the stakeholder who committed to the programme departs six weeks in, or where the data turns out to be fifteen years of inconsistently formatted spreadsheets, or where the scope was wrong from the start and the client does not yet know it. Those situations require judgment, not diagrams.
The question to ask is: "Walk me through an engagement that did not go to plan. What happened and what did you do?" The quality of that answer — its specificity, its honesty, its evidence of learning — tells you more about a firm's delivery capability than any methodology deck.
References and the evidence problem
Most consulting references are selected. Firms present the clients who are most likely to give a positive account. This is not dishonest — it is rational — but it means that references tell you what a firm is capable of in its best circumstances, not what it looks like when things get hard.
The more useful reference question is not "would you recommend them?" but "describe a moment in the engagement where something did not go as expected, and how the team handled it." Clients who have been through genuinely difficult moments with a consulting team will answer this question specifically. If they cannot, the engagement was either straightforward or the relationship was managed rather than delivered.
What good looks like
The distinguishing features of a consulting relationship that tends to produce outcomes rather than just activity:
Honest scoping. A good partner tells you before the contract is signed what is outside scope, what they would not do, and what they are uncertain about. Anything that is certain at the pitch stage and uncertain during delivery is a scoping failure, not a discovery.
Named delivery people. You know, before signing, exactly who will be in the room and what their specific track record is. Not titles — names and evidence.
Defined exit. The end state of the engagement is defined before it begins. Not in terms of hours delivered or phases completed, but in terms of what the client's team will be able to do when the consultant has left.
Explicit knowledge transfer. A good partner is not interested in creating dependency. The most useful thing an external consultant can do is make themselves unnecessary. If a firm does not have a clear answer to how they transfer knowledge, they have an incentive to stay longer than necessary.
If you are evaluating consulting partners for an AI or technology delivery programme and want a direct conversation about fit, our contact page is the right place to start. We will give you an honest view of whether we are the right match for what you need — and if we are not, we will tell you.