Many consulting projects begin with a simple question: can this consultant help us? A management consulting discovery call turns that question into an initial shared understanding of the need and the decision ahead. It helps both sides assess fit, identify missing information and choose a next step. It is not enough on its own to diagnose causes or approve a final solution. Good preparation makes the call useful even when the outcome is a decision not to start a project.
Before the call: define the question you need answered
Start with what is happening, rather than the name of the solution you want to buy. Instead of saying “we need a new system”, say “our quotations are late, and we do not know where the work gets stuck”. This leaves room to examine processes, authority, data and technology. Explain the decision ahead: do you need to understand causes, compare options or implement a decision already made?
Prepare a one-page brief covering the problem, affected people, when it started and previous attempts to address it. Include available figures with their period and source, and separate what you know from what remains unverified. Mention important deadlines and constraints, such as limited staff availability or dependence on a supplier. A long presentation is unnecessary. The aim is to begin with facts that can be examined while acknowledging unanswered questions.
Choose participants and share only what is needed
Initially, a person who understands the problem and can explain its context may be enough, provided it is clear who can authorise an engagement. A process owner or another department may need to join when the issue crosses boundaries. You do not need every department at the first meeting. Too many participants without clear roles can turn the call into a collection of opinions rather than a focused discussion.
Start with summaries and examples stripped of names and sensitive information. Before sharing detailed files, establish what is needed and why, whether you are authorised to share it, who will receive it and which channel is appropriate. Discuss confidentiality arrangements, including a non-disclosure agreement where needed, and how files will be stored and deleted. Do not send a complete customer database or employee files simply to speed up introductions. Specific details can be requested later if necessary.
During the call: understand the problem before choosing a solution
Agree the purpose of the discussion and available time at the start. Explain what happens and its impact, then allow room for questions: when does the delay occur? Does it affect every case? What changed? How was the figure calculated? What has already been tried? Good questions separate observations from explanations and reveal differences in how departments define the problem.
Discuss dependencies: a quotation may depend on technical information, credit approval or a supplier response. Identifying that connection does not establish the cause of a delay. Record possible explanations as hypotheses to test against evidence. It is reasonable for a consultant to say “we do not know yet” and explain what must be reviewed before making a recommendation.
Test whether the consultant is a good fit
Ask about experience with similar problems and request an example explaining the consultant’s role and approach without disclosing another client’s confidential information. Ask who will actually do the work, how your team will participate and which expertise is unavailable. Specific answers are more useful than a long list of credentials or client names. Reputation alone does not establish suitability for the assignment.
Discuss independence and conflicts of interest, particularly if the consultant benefits from recommending a product or supplier. Observe communication: do they listen and accurately restate your need, or promote a ready-made solution before understanding it? Warning signs include pressure to buy immediately, large unsupported promises, unclear delivery responsibilities and avoiding questions about confidentiality or cost.
Separate agreed deliverables from expected business outcomes
A diagnostic report, options comparison, workshop or improvement plan can be agreed with a deadline, acceptance criteria and clear responsibilities. These are deliverables that can be specified in the engagement. Sales growth or cost reduction also depends on management decisions, market conditions, resources and implementation. Explain assumptions, the expected contribution and responsibility boundaries instead of promising a certain business result before examining the evidence.
Clarify the commercial basis before additional work starts. Does the call itself carry a fee? Is the next assessment paid? What does the price include? There is no single duration or fee policy covering every consultant. Where information is incomplete, a limited assessment may be appropriate before pricing a larger assignment. A request for clarification should not become an unagreed commission.
Practical example: from a broad complaint to a defined next step
This is a hypothetical illustration, not a client case or a promise of results. A service company manager says, “We need a system to speed up quotations.” Before the call, she prepares a summary showing that 12 of 40 quotations were sent after the internal target deadline last month: 30%. The figure describes lateness under the company’s definition. It does not prove that the system is the cause.
The consultant asks when the clock starts, whether requests contain complete information, which approvals are needed and how simple quotations differ from complex ones. The summary contains no timestamps for handoffs between departments. The consultant therefore does not recommend buying software or promise a specific reduction in delays. Instead, they propose examining an agreed sample of quotations and speaking with sales and pricing staff to locate waiting time.
The call ends with an initial agreement: within 2 working days, the manager will send a log with customer details removed, after obtaining internal approval to share it. Within 3 days of receiving it, the consultant will send a proposal for a limited assessment, specifying scope, deliverables and fees. Paid assessment work will not begin before approval. The useful result is a clearer question, required evidence, an owner and a deadline, rather than a premature solution.
After the call: record what was agreed
Send a short summary of the understood problem, the decision ahead, available facts, untested assumptions and information requested. Distinguish agreed actions from suggestions still under consideration. Give each action an owner and deadline. State whether the next step requires a proposal, approval or confidentiality arrangement before data is exchanged.
The next step may be a proposal, a meeting with the decision maker, a limited assessment or postponement. Not proceeding may be the best decision if expertise, information or resources do not fit the need. If a proposal follows, review scope, exclusions, deliverables, timing, fees and acceptance arrangements before approving it. A call summary does not replace an engagement agreement.
Frequently asked questions
Do I need all the data before calling? No. Prepare what is available and identify gaps honestly. The call can help determine which data matters, but it cannot turn unverified information into facts.
Is the call free, and will it end with a quotation? This depends on the provider’s arrangement and should be clarified beforehand. More information may be needed before pricing, and the call may conclude that no project is required.
How long should the call take? Agree a duration suited to the complexity of the need and the participants. Set a realistic purpose and leave time for questions and next steps instead of trying to diagnose an entire organisation in one conversation.
Before ending the conversation
Check that you can answer 5 questions: what need have we understood? What remains uncertain? Does the consultant’s expertise fit? What information will we share and under which arrangements? Who will do what, by when, and at what cost, if any? If the answers remain vague, clarify them before moving to an engagement.
Further reading
Read the foundational guide to management consulting for context on the consultant’s role. ISO 20700:2017 provides general guidelines for delivering management consultancy services, while the CIPD reference supports evidence-based thinking. The steps and example in this article are practical editorial guidance, not quotations from the standard or mandatory discovery-call requirements.