How to Brief a Sales Consultant (And What to Withhold).

Most businesses brief a sales consultant the way they brief a supplier: here is the problem, here is the budget, tell us what you would do.

That produces a proposal rather than a diagnosis, and a proposal written from incomplete information is a guess with a price on it. The quality of the engagement is set in the first two conversations, and it is set mostly by what you choose to tell.

What to put in front of them

The last twenty opportunities, with outcomes. Not the CRM export. The actual story of each: who it was, what they wanted, what happened, and — the important part — what the buyer said when it stalled. Closed-lost reasons in a CRM are almost always wrong, because whoever logged them had an incentive to be generous to themselves. What a consultant needs is the version you would tell a peer over a drink.

Your real conversion maths. How many conversations produce a proposal. How many proposals produce a signature. How long each takes. If you do not know these numbers, say so — that is itself a finding, and pretending otherwise wastes the first month.

The deals you lost to “no decision” rather than to a competitor. These are the most diagnostic opportunities you have, and most businesses forget them because nobody beat you. A pipeline that dies in silence has a different problem from one that loses on price, and the fixes have nothing in common.

Your worst client, and why you took them. This tells a consultant more about how your business actually qualifies than any ideal-customer document. Everyone has an ICP written down. Very few of them describe the accounts that were actually signed.

The commercial constraints, in full. Minimum deal size, capacity limits, what you cannot deliver, what your margin structure will not tolerate. A strategy built without these produces pipeline you cannot serve, which is worse than no pipeline.

What you have already tried, and how it failed. Including the agency that did not work. Especially the agency that did not work. The details of that failure — what was sent, to whom, what came back — are the closest thing to prior test data your market has produced.

What to withhold, deliberately

This is the part nobody says out loud.

Withhold your diagnosis until they have given theirs. If you open with “our problem is lead volume”, you will get a proposal about lead volume. A capable consultant will often disagree with your framing, and you want to hear that disagreement before you have anchored them to it. Describe symptoms first. Give your theory second, and ask them to argue with it.

Withhold the budget number in the first conversation. Not to negotiate — to test. A consultant who cannot scope the work before hearing the number is scoping to the number. State a band if you must, but let the diagnosis come first.

Withhold your preferred fix entirely. “We think we need an SDR” is a conclusion, and if you hand it over, you have hired someone to validate it. You already know how to buy an SDR — and what one actually costs. What you are buying is the judgement about whether it is the right instrument at all.

Do not withhold anything about the state of the business. Runway, churn, a key person leaving, an acquisition in progress. Anyone worth hiring will build a strategy around real constraints, and one built around a rosier version of your business is worthless the day it meets reality. This is the withholding that actually costs money.

The questions a good one will ask you

Use these as a filter. If the first meeting does not include most of them, you are talking to someone selling a package.

• What happens to a deal after the first meeting goes well?
• Who has said no to you, and what did they say instead of yes?
• What is the smallest engagement a client can start with, and why that shape?
• Which of your current clients came from outbound, and which came from referral?
• What can you not deliver, at what volume does it break, and what happens then?
• What has your team already tried, and what did the replies say?
• Who inside your business will hate this and why?

That last one is the highest-signal question in the list. Every commercial change has someone whose work it complicates, and a strategy that ignores them fails in month three for reasons nobody attributes correctly.

The three briefs that produce bad engagements

The outcome brief. “We need thirty meetings a month.” It sets a target without a mechanism, and it invites exactly the volume behaviour that has stopped working. Any provider who accepts this without interrogating it is planning to hit it with sends.

The prescription brief. “We need an outbound sequence into the finance sector.” You have specified the answer. The only remaining question is price, and you have converted a strategic purchase into a procurement exercise.

The everything-is-fine brief. Selective history, best-case numbers, and the difficult parts left out. It produces a plan for a company that does not exist, and the correction arrives in month two at your cost.

What the first month should produce

Regardless of who you engage, the first month should return something you can disagree with: a written diagnosis specific enough to be wrong. Not a summary of what you told them. A view — about the buyer, the message, the shape of the pipeline problem — that you could argue against with evidence.

If month one produces only a plan of activity, you have bought motion. If it produces a claim about why the pipeline is not working, you have bought judgement, and you can test it.

The bottom line

Brief on symptoms, withhold your conclusions, and disclose everything about the state of the business. Then judge the response on whether it tells you something you did not already know.

The engagements that work start with an uncomfortable first meeting — one where somebody says the message is the problem, or the buyer definition is wrong, or the offer is not different enough to be chosen. How we run that first phase is set out on our sales consulting page.

That conversation is the product. Everything after it is execution.