To turn a client brief into a consulting presentation, separate what the client has confirmed from what your team still needs to learn. Then show the conflict that affects scope, offer two genuinely different ways forward, and ask for the decisions needed to prepare a credible proposal. Do this before filling a deck with deliverables and dates.
This is a scope-clarification presentation, not the final proposal. Its job is to help the client and consultant agree on what the work should cover. Once that agreement exists, Presenti’s sales presentation workflow can help you prepare an editable draft for the next conversation. The examples below are fictional; the brief and its unanswered questions are deliberately kept visible throughout.
Read the brief for commitments, not just keywords
Imagine a distributor sends this request:
“Quotations take too long. We want one process for three country teams within six weeks, without replacing our CRM. Sales says requests arrive with missing information; operations says approvals are the bottleneck. We do not have a reliable baseline. Our team can attend one 30-minute session each week.”
A weak deck would turn those sentences into “streamline quotations across three markets in six weeks.” That sounds decisive, but it quietly converts a desired date into a delivery promise and two competing explanations into an established diagnosis.
Read it twice. On the first pass, extract the requested outcome and constraints. On the second, mark anything that would change the method, effort, or promise if it turned out to be wrong. Keep the client’s wording beside your interpretation so the team can see where you have made a judgment.
Sort the input into three kinds of statement
| Statement in the brief | How to treat it | What goes on the slide |
|---|---|---|
| No CRM replacement | Explicit constraint | Work within the existing system; identify who can approve configuration changes. |
| One process for three country teams | Desired outcome, not yet an agreed scope | Ask which steps must be common and which can remain local. |
| Six weeks | Requested timing | Clarify whether this means a recommendation, a tested pilot, or a full rollout. |
| Missing information or slow approvals | Two explanations to investigate | Show both; do not choose a cause without examples. |
| No reliable baseline | Missing input | Request a small set of recent quotations with timestamps and approval steps. |
The distinction matters most when a brief uses the same word for different things. “Standardize” could mean common fields, common approval rules, or an identical process in every country. Write the alternatives out. A clarification question is more useful than a confident slide that hides the ambiguity.
Make the scope conflict the center of the story
In this example, the difficult combination is three teams, six weeks, little access, and no baseline. The slide should not imply that the client is being unreasonable. It should show what must change to make the work practical.
Use a headline such as “Agree on the six-week outcome before choosing the work plan.” Beneath it, distinguish three possible endpoints: a diagnosis, a pilot, or a full rollout. A horizontal sequence is enough. Mark the endpoint the client actually needs; leave the others as later work rather than squeezing all three into the same promise.
Then ask a consequential question: “If a tested pilot is the priority, can one country team provide sample cases and a named reviewer?” This connects an input to a specific choice. “Can you share more information?” does not.
Compare two paths that solve different uncertainties
Do not offer three packages with different names and almost identical contents. In this brief, there are two useful routes:
- Diagnosis first: examine recent quotation journeys across the three teams, agree on the main delay, and propose a common process. The output is a recommendation and a prioritized change list, not a working rollout.
- One-team pilot: choose one country team, test a narrowly defined change in its quotation process, and use the results to decide what to extend. This needs access to cases and a reviewer; it does not prove that the same change will suit all three teams.
Compare the routes using the client’s constraints: required access, people involved, tangible output, and what remains unresolved. Do not assign numerical scores unless the client has agreed on the criteria and scoring meaning. If the brief is too incomplete to estimate effort, leave the commercial quote for the next step.
Build six slides around the unresolved decision
| Slide | Suggested headline | Material to show |
|---|---|---|
| 1 | Choose what “done in six weeks” means | The requested decision and the three possible endpoints. |
| 2 | The brief fixes the system, not yet the solution | Confirmed constraints beside open requirements. |
| 3 | Two explanations need different evidence | Missing-input and approval-delay hypotheses, each with a sample case request. |
| 4 | Start with a diagnosis or a one-team pilot | The two routes, outputs, dependencies, and limits. |
| 5 | A pilot is not a three-country rollout | What the selected route includes, excludes, and requires from the client. |
| 6 | Confirm the route, reviewer, and available cases | Three answers needed before the consultant prepares a scope and quote. |
Keep the full brief in an appendix or accompanying document. In the main deck, repeat only the phrases that explain a choice. A short excerpt beside your interpretation makes disagreement easy to spot without forcing the client to reread the entire request.
Give the AI the ambiguity, not permission to erase it
Prepare a sanitized version of the brief that your organization permits you to use. Remove confidential names or case details when they are unnecessary for the discussion. Then give your drafting tool a precise task:
Create a six-slide scope-clarification presentation for a fictional distributor. The client wants one quotation process for three country teams within six weeks, no CRM replacement, and can offer one 30-minute session per week. Sales suspects missing request information; operations suspects slow approvals. There is no reliable baseline. Separate confirmed constraints, hypotheses, and unanswered questions. Compare diagnosis-first work with a one-team pilot. Do not invent costs, savings, dates, case evidence, or a preferred cause. Treat six weeks as a requested timeframe, not a confirmed delivery commitment. End with decisions on the route, the client reviewer, and access to sample cases.
Read the outline before spending time on the visual design. Replace a generated headline such as “Cut quotation time by 40%” with a statement supported by this brief: “Find which step delays quotations before choosing the change.” The first invents an outcome; the second gives the meeting a purpose.
Turn the meeting answers into a scope
Suppose the client chooses a one-team pilot but cannot provide individual quotation records. That answer changes the work. You might need an observation session or a different starting point; it is not a detail to bury beneath the timeline.
After the discussion, update the selected route, record the still-missing input, and identify who will resolve it. Only then turn the agreed approach into deliverables, responsibilities, and a quote. The useful consulting presentation is the one that makes those choices explicit—not the one that makes an incomplete brief look finished.
