From discovery call to client brief
Turn a discovery call into a client brief with a worked example, a reusable template, and questions to confirm before sending.
The call ends with a friendly “sounds good.” Your notes, however, contain three different goals, a deadline mentioned once, and a feature someone described as “probably nice to have.” If you write the proposal straight from those notes, you may promise work the client never approved. A client brief gives both sides a chance to agree on the problem before anyone agrees on the solution.
A useful brief is not a transcript with headings. It is a short account of what the client wants, why it matters, what appears to be in scope, and what still needs an answer. Write it soon after the call, while you can still tell a firm decision from a passing idea.
Start with the reason for the work
Before you list tasks, write one plain sentence about the change the client wants. “Redesign the website” describes possible work; “Help new visitors understand which service to ask for” describes the reason. If you cannot write that sentence without guessing, ask the client before you draft a solution.
Review your notes or, if the call was recorded with permission, its transcript. Look for the current situation, the desired change, the people affected, and any date that has a real consequence. Mark exact words where they matter, especially names, numbers, and promises. A transcript can help you revisit the conversation; it cannot decide which ideas became agreements. For more on working from a recorded conversation, see our guide to interview transcription.
Separate decisions from ideas
In a discovery call, people explore. “Could we add a booking page?” is different from “We need a booking page in the first version.” A brief should not quietly turn the first sentence into the second. Use three small lists when you sort your notes:
- Agreed: something both sides explicitly accepted during the call.
- Suggested: an option to consider, with no commitment yet.
- Unclear: something that needs a name, number, owner, or decision.
Attribution helps when views differ. Write “The sales lead asked for a shorter form; the service team wants more detail” rather than “The form must be short.” If a date sounded tentative, say “target date, to confirm.” Never make a rough estimate look like an approved budget.
Write for the person who missed the call
The brief should let an absent teammate answer five questions: What is happening now? What should change? Who is it for? What work is being considered? What must be decided before work starts? Use short sections and ordinary words. Keep the background long enough to explain the request, but short enough that a reader can spot an unresolved point.
One practical order is: background, goal, audience, proposed work, boundaries, timing, open questions, and next step. Put confirmed facts first. Place assumptions and unanswered questions in their own sections. This makes it harder for a reader to mistake a draft for approval.
Worked example: a finished brief
Fictional example: The call excerpt and business below are invented to show the method. They do not describe an Audiogest customer or an actual project.
“People call us to ask which workshop is right for them. We want the website to answer that first. We could add online booking later, but let’s start with clearer pages.” — fictional discovery-call excerpt
Client brief — Northbank Workshops (fictional)
- Background: Visitors currently call to ask how the workshops differ. The team wants the site to answer common questions before a visitor gets in touch.
- Goal: Help a first-time visitor understand the difference between the workshops and choose a suitable next step.
- Audience: People considering their first workshop. Confirm whether returning participants need separate information.
- Proposed work: Review the existing workshop descriptions, agree on the main questions to answer, and draft clearer workshop pages for the client's review. These are proposed steps, not approved costs or dates.
- Boundary: Online booking came up as a later possibility. It is not part of this first brief unless the client confirms otherwise.
- Timing: No launch date was agreed on the call. The client will confirm whether an event or season sets a deadline.
- Open questions: Which workshops should appear first? Who signs off on the descriptions? Are prices and available places shown on the site? Does the team have current photos it can use?
- Next step: Send this brief to the client for corrections and answers. Use the agreed version to discuss the work, schedule, and price.
Notice what the brief does not do: it does not promise more calls, a rise in bookings, a delivery date, or a budget. Those may become part of the project later, but the excerpt does not support them.
Reusable client brief template
Copy these prompts into a document. Keep the answer “to confirm” when the call does not supply it; an empty space is safer than a confident guess.
- Client and date: [Name] · [Date of conversation]
- Current situation: [What happens today? What problem did the client describe?]
- Goal: [What should be different when this work is done?]
- People affected: [Who will use or receive the result?]
- Work being considered: [What did the client ask for? What options were only suggested?]
- Boundaries: [What is outside this first piece of work, if agreed?]
- Timing and limits: [Confirmed dates, constraints, or “to confirm”]
- Decisions made: [What did both sides clearly agree?]
- Open questions: [What answer is needed, and who can provide it?]
- Next step: [Who reviews this brief, and what happens after review?]
Check the brief before you send it
Read your draft beside the call notes. For each statement, ask: did the client say this, did both sides agree to it, or is it my suggestion? Label suggestions. If a claim matters to the price or schedule, confirm it rather than treating silence as approval.
Check names, dates, quantities, and owners against the source. If a recording was made, replay any unclear passage instead of trusting a guessed word in the transcript. Keep private details out of a brief that will travel beyond the call. If several people attended, confirm whose approval is needed. Give unanswered questions a named owner so they do not disappear in the next meeting.
Then send the brief with a direct request: “Please correct anything we misunderstood, answer the open questions, and confirm whether this reflects the work you want to discuss.” Ask for a reply before you turn it into a plan or price. When the client changes a point, update the brief and make clear which version both sides are using. A few minutes of careful checking can prevent a long conversation about work nobody meant to approve.