Turn a consulting discovery call into a clearer project scope

Describe the problem and its boundaries

Summarise what the client wants to understand or change, and what is outside the engagement. Use the client’s language where it is clear, then explain any necessary technical terms. Avoid expanding a local process issue into a whole-company transformation simply because the consultancy has broader capabilities. If the boundaries are still uncertain, name that uncertainty and propose a proportionate way to resolve it before committing to detailed deliverables.

Separate desired outcomes from deliverables

An outcome is the change the client wants to achieve; a deliverable is what your team agrees to produce. A process map may support a better handover, but producing the map does not automatically implement organisational change. Explain the relationship and the client’s contribution. This distinction prevents the proposal from promising an outcome that depends on decisions, resources or adoption work outside the consultancy’s agreed control.

Record assumptions and dependencies

List the information, access and decisions needed for the work. Confirm who provides them and what happens if they arrive late or remain unavailable. Be specific about stakeholder interviews, internal review and approval points. These details are not administrative decoration. They determine whether the work can be carried out as intended. Where an assumption is central to the scope, check it with the client rather than burying it in small print.

Agree how the work will be evaluated

Define what a useful output looks like and who will review it. For a diagnostic, that might mean answering a specified question with evidence and identifying unresolved issues. For a workshop, it might mean documenting agreed responsibilities and actions. Avoid vague acceptance criteria such as “improved performance” where the scope does not establish a way to assess it. A clearer review process helps both the sponsor and the delivery team make practical decisions.

Make the next step explicit

After discovery, send an accurate summary and ask the client to correct misunderstandings. State whether the next step is confirming scope, involving another stakeholder or preparing a commercial proposal. Assign an owner and an agreed date where possible. Feed recurring scoping problems back into the outreach offer. If the first message attracts people expecting a different type of engagement, the most effective fix may start before the discovery call.

Use a discovery summary before a polished proposal

Write a short account of what the client wants to decide, what is known about the situation and what remains unclear. Share it for correction before investing in a detailed proposal where appropriate. This can expose differences in understanding early. A sponsor may use the same word as the consultant while expecting a very different kind of output. Resolving that difference is more valuable than refining the design of a document built on the wrong premise.

Keep the summary neutral about the eventual engagement. If the evidence suggests a smaller diagnostic rather than the broader project originally discussed, say so. Discovery should inform the recommendation, not merely collect language to justify a predetermined offer. Record any important assumptions about access, sponsorship or decision authority so the proposal can address them explicitly.

Connect every deliverable to a purpose

For each proposed output, explain who will use it and which decision or activity it supports. A findings report, workshop or process map should have a clear reason to exist. Remove deliverables that are included only because they appeared in an earlier proposal. A shorter scope with a coherent contribution can be easier for a client to evaluate and easier for a project team to deliver well.

Check dependencies between outputs. A workshop may require interviews first; a recommendation may depend on access to relevant records. Make those relationships visible. If the client cannot provide an essential input, the scope may need to change. This creates a practical discussion about what can be achieved rather than leaving the delivery team to discover the limitation after work has begun.

Agree how change will be handled

Consulting work can reveal information that changes the original understanding. Establish how the team will raise new issues and how the sponsor will decide whether they belong within the engagement. A change process should be proportionate and understandable. It does not need to make every small adjustment difficult, but it should prevent a materially different project from emerging without an explicit agreement.

Record who can approve scope changes and what information they need. Explain the possible effect on deliverables, timing and responsibilities without presenting commercial questions as an obstacle to sensible work. Clear arrangements help both sides respond to evidence. They also protect the relationship by making it less likely that the client and consultant develop different expectations about what has been added.

Prepare the delivery handover before the sale closes

Identify what the project lead will need from the sales process: the discovery summary, confirmed scope, assumptions, stakeholder context and commitments made during negotiation. Keep a record of exclusions and unresolved questions as well as the positive proposition. A successful handover should let the delivery team begin with the same understanding the client accepted.

Where the salesperson and delivery lead are different people, arrange an internal review before the final scope is agreed. The delivery lead may identify a missing dependency or an output that needs clearer definition. Resolving those issues before commitment is better than treating them as an onboarding surprise. The proposal becomes more credible when the people responsible for delivering it have helped confirm that its boundaries and responsibilities make practical sense.