The brief
The Source for Consulting Professionals

TLDR: We used to let a signed brief stand in for a real conversation about scope, and twice that let a client and our team walk into a contract meaning two different things by the same deliverable. A single thirty-minute discovery call, run by someone senior enough to say no to the wrong engagement, now sits between every quote and every signature. It has cost us a handful of deals we would rather not have won.
The brief read cleanly enough: full SEO management, monthly reporting, a target of measurable ranking improvement inside two quarters. We quoted it, the client signed it, and three weeks in we discovered that "SEO management" meant something different on each side of the table. We had scoped technical SEO, content and link building. The client had scoped all of that plus a full site redesign they assumed was bundled in, because a previous agency had once done exactly that for the same monthly fee.
Nobody had lied. The brief was genuinely ambiguous, and neither side had asked the question that would have surfaced it, because the brief felt specific enough to skip the conversation.
Why a Good Brief Is Not the Same as a Shared Scope
A brief is written by one side, usually under time pressure, and it captures what that side already knows to specify. It cannot capture the assumptions neither side realised they were making, because an assumption by definition is the thing nobody thought to write down.
Harvard Business Review's collection on risk management makes a point that applies well beyond finance: the risks that damage a relationship are rarely the ones anyone debated and got wrong; they are the ones nobody named at all. An operational efficiency problem inside a consulting engagement usually starts exactly there, in the unnamed assumption sitting quietly inside an otherwise reasonable document.
The cost of that gap does not show up on day one. It shows up in week three or four, once work is underway and unwinding a wrong assumption means redoing scoped hours, and by then both sides are frustrated for reasons that feel personal even though the actual cause was a conversation that never happened.
What the Call Actually Covers
The discovery call is not a sales call dressed up as due diligence. It has four questions we ask every time, in the same order, and we do not move to a quote until all four have real answers rather than assumed ones.
- What does success look like in your own words, not in the language of our proposal?
- Who on your side approves scope changes, and how fast do they usually respond?
- What has a previous vendor done for you that you are assuming carries over here?
- What would make you consider this engagement a failure even if every deliverable on the brief is technically complete?
That last question has caught more mismatches than the other three combined. It surfaces the unwritten expectation almost every time, because it forces the client to describe the outcome rather than the task list, and outcomes are where the real disagreement usually lives.
The Deals We Walked Away From
We have used the call's findings to decline work, which is the part clients do not expect from a sales conversation. Twice this year the answer to "what would make this a failure" described an outcome we had no honest path to deliver inside the proposed budget or timeline, once because the client's real target was a revenue figure our channel mix could not move on its own, and once because the internal approval chain described in question two would have added weeks to every decision we needed made in days.
A meeting that exists to catch the wrong engagement before signature will, by design, sometimes end the engagement before it starts. That is the trade we made on purpose. JPMorgan Chase Institute's research on cash flow and buffer days is a reminder of how thin the margin for a wasted engagement really is in a small service business: the hours spent unwinding a mis-scoped contract are hours that a firm our size cannot easily absorb twice in the same quarter.
What Changed Since We Added It
The call adds thirty minutes and, occasionally, a delay of a day or two while the right person on the client side becomes available. Against that, we have not had a scope dispute reach the point of a difficult conversation since the requirement went in, and the proposals we do send after the call close faster, because both sides are quoting the same engagement rather than two versions of it. It is a small enough process change that any digital marketing agency our size could add it this week, and the way we run it now has become one of the first things we walk new hires through.
