Discovery Briefs & Proposal Drafting

Turn a messy discovery call into a tight internal brief and a client-ready proposal

The gap between the call and the proposal

Discovery calls generate an hour of rich, specific information — and then most of it evaporates by the time someone sits down to write the proposal three days later. The account lead reconstructs from memory, misses details, and the proposal reads generic. The fix isn’t a better proposal template; it’s capturing the call faithfully and drafting immediately, while it’s fresh and complete.

Step 1: Call notes to a structured internal brief

Whether you’re working from a transcript (see Lesson 10 for capturing these reliably) or your own raw notes, the first move is the same: convert to a structured internal brief before anyone touches the proposal.

Turn these discovery call notes into a structured internal brief.
Use these sections: Client background, Stated goals, Budget signals,
Timeline, Decision-making process, Concerns/objections raised,
Open questions we still need answered.

Flag anything where I contradicted myself or where the client gave
vague answers we should clarify before writing a proposal - don't
paper over gaps, surface them.

CALL NOTES:
[paste raw notes or transcript]

That last instruction matters. A brief that quietly smooths over “the client never actually answered when they want to launch” produces a proposal built on a guess. Ask Claude to flag gaps rather than fill them.

Step 2: Brief to proposal draft

Once the brief is solid and any open questions are resolved, draft the proposal using your agency’s own past proposals as the tone and structure reference — never let Claude invent your proposal format from scratch.

Using the brief below and matching the structure and tone of our
last two proposals (pasted below as reference), draft a proposal
for this engagement. Include: executive summary, scope of work
broken into phases, timeline, investment (I'll fill in exact
numbers), and next steps.

Do not invent scope items that weren't discussed on the call - if
something is only implied, mark it as [CONFIRM] rather than stating
it as agreed.

BRIEF:
[paste brief from Step 1]

REFERENCE PROPOSALS:
[paste 1-2 past proposals]

Key principle: The [CONFIRM] tag is doing real work here. It turns Claude’s tendency to fill gaps smoothly into a visible checklist for the account lead, instead of a proposal that quietly overpromises scope nobody actually agreed to.

Common failure modes and how to avoid them

Failure Fix
Proposal sounds generic, could be for any client Make sure the brief includes direct quotes from the call, not just paraphrase — feed those quotes into the proposal prompt
Scope creep baked in from the start Use the [CONFIRM] tag instruction; review every scope line against actual call content
Pricing feels off Never let Claude set pricing — always fill in numbers yourself based on your own rate card and margin targets

Watch out: Pricing and legal terms are squarely in the “human judgment” category from Lesson 1. Use Claude for structure and narrative; keep numbers and contractual language under direct human control every time.

Try it: Take notes from your last real discovery call and run them through Step 1. Compare the flagged gaps against what actually ended up in the proposal you sent — you’ll likely find at least one assumption that should have been confirmed first.