The discovery call is a sales artifact. The proposal is a sales artifact. The case studies are sales artifacts. By the time you are reviewing a statement of work, you have heard a curated version of the firm — the team they wish they had on every engagement, the timelines they hit when conditions were ideal, and the outcomes they would put on a billboard. None of that tells you whether this engagement, with your data, against your constraints, will land. What follows are seven questions we recommend every buyer ask, and the reason each one separates the firms that ship from the firms that bill.
1. Who, by name, will be on the engagement — and what is their utilization this quarter?
Most consultancies pitch with senior architects and staff with juniors. This is not a moral failing; it is an economic reality of leveraged staffing. The question is not whether it happens but how much. Ask for named resources, their roles, the percentage of their time committed to your project, and what else is on their plate. If the answer is “we’ll confirm at kickoff,” assume the bench is thin and the people on the call are not the people doing the work. The follow-up that pressure-tests this: “If your senior architect is pulled into a fire on another account, what happens to our timeline?“
2. What does week-by-week deliverable cadence look like for the first six weeks?
A vendor who cannot describe weeks one through six in concrete terms — artifact by artifact — is selling you a research project, not an engagement. You want to hear specifics: schema audit deliverable in week two, data quality scorecard in week three, semantic layer prototype in week four. The shape of the cadence matters more than the contents. A flat “discovery / design / build / deploy” gantt is a red flag because it gives both sides license to slip. Tight, named weekly milestones force the firm to commit to a sequencing plan they have actually run before.
3. What is your knowledge-transfer plan, and how is it enforced contractually?
Every firm will tell you they prioritize knowledge transfer. Few will agree to make payment milestones contingent on it. Ask whether the final invoice can be tied to your team passing a documented runbook test, or to a successful handoff drill where their consultants are demonstrably out of the critical path. The willingness to put even a small percentage of fees behind enforceable transfer is the cleanest signal of intent. The firms that resist will explain that knowledge transfer is “continuous and embedded” — which means it is unmeasurable, which means it is optional.
4. What does a successful exit look like, and what would cause you to recommend ending the engagement early?
A consultant who cannot describe their own exit criteria is planning to extend. Force the conversation. What capabilities, processes, or artifacts must be in place for them to recommend wind-down? Under what circumstances would they tell you the engagement is no longer the right use of your money? A firm with strong opinions about when to leave is a firm that has thought about the problem from your side of the table. A firm that hedges is one whose pricing model rewards staying.
5. Show me a project that did not go well. What happened, and what did you change?
This is a calibration question. Every consultancy has had projects miss. The ones that have learned will describe the failure crisply, name what they changed in their methodology, and point to where the change shows up in their current process. The ones that have not will either deflect (“client wasn’t ready”) or produce a sanitized version that sounds rehearsed. The candor of the answer correlates almost perfectly with the candor you will get during the engagement when something is going sideways.
6. What is your model for handling scope changes, and what was the last one you walked away from?
Every engagement faces scope drift. The question is whose interest the change-order process serves. Ask for the actual change-order template. Ask how many they raised on their last engagement and how many were initiated by them versus the client. Ask for the last one they declined to bill — and why. Firms that bill every scope adjustment have a revenue model that rewards drift. Firms that absorb small adjustments and reserve change orders for material expansions are operating in your interest as well as theirs.
7. Who owns the IP — code, models, documentation, dashboards — and what is your reuse policy?
This question separates platform vendors masquerading as consultants from actual advisors. Read the IP clause carefully. If the firm retains rights to “methodology and frameworks” that include code, dashboards, or model logic produced on your engagement, you are paying for work you cannot fully own. Ask explicitly: can we take everything produced under this SOW and engage another firm to extend it without licensing back from you? A clean “yes” is the answer you want. Anything else is a vendor lock-in vector you should price into the deal.
The firms worth hiring will answer all seven of these without flinching, because they have already had every one of these conversations with buyers who knew what to ask. The firms that bristle, deflect, or promise to “circle back with the team” are telling you exactly what kind of engagement you are about to sign.