Skip to article
Bridge

Turn a discovery call into a scoped proposal draft

A proposal is only as good as the discovery call behind it. Decide before the call which facts the proposal needs, ask for each one, and write the draft from the transcript rather than memory. Then check every scope line, date and assumption against what the client said before you send it.

Why proposals drift from the call

Most proposals are written a day or two after the discovery call. By then, the client's exact words have become your summary of them.

Small drifts add up. A "nice to have" turns into a deliverable, a soft deadline becomes a hard one, and the budget signal gets forgotten. The fix is to plan the call around the proposal you will write.

Before the call: list what the proposal needs

Start from your proposal template and work backward. Every section you will fill needs a fact from the client.

Read what you already know: the inquiry, any intake form and earlier emails. Then write down only the gaps.

  • Goal: the outcome the client wants, in their words.
  • Scope: what is in, and what they have said is out.
  • Constraints: deadlines, systems, approvals and anything already decided.
  • Budget signals: a range, a past spend or how they plan to pay.
  • Decision process: who signs off, who else weighs in and by when.

During the call: ask for each fact

What you needA question that gets itWhere it goes
Goal"What would make this project a success six months from now?"Objectives
Scope"What should we definitely not take on?"Scope and exclusions
Constraints"Is there a date or event this has to be ready for?"Timeline and assumptions
Budget"Have you set aside a range, or done similar work before?"Pricing options
Decision"Who else needs to approve this, and how do they decide?"Next steps

A proposal outline built from the call

Keep the draft in the same order as the client's priorities. Each section should trace back to something said on the call.

  • The situation: the problem in the client's own words.
  • Objectives: two or three outcomes you will deliver against.
  • Scope: deliverables, plus a short exclusions list.
  • Approach and timeline: phases with dates tied to their stated constraints.
  • Pricing: one to three options that fit the budget signal.
  • Assumptions and open questions: anything the call left unclear.
  • Next steps: who approves, and by when.

Check the draft against the transcript

Before sending, read the draft beside the transcript. You are looking for anything the client didn't say.

  • Every deliverable maps to a request on the call, or is marked as your recommendation.
  • Dates match what was said, not what would suit you.
  • Items the client called optional stay optional.
  • Anything you guessed moves to assumptions or open questions.

Example: a website redesign inquiry

This example is illustrative. A retailer's marketing lead says they need a new site "before the spring catalog" and mentions a blog "eventually." Their last redesign cost about the same as your mid-range package.

The draft puts the site launch before the catalog date and lists the blog as an optional phase. It offers two pricing options around that past spend, and asks who besides the marketing lead approves.

Doing this in Bridge

With a calendar connected, Bridge builds a Brief for the call. Its Preparation tab gathers the calendar description and context from earlier meetings and connected tools, plus intake answers if the call was booked through a Bridge booking page.

Put your gap list in the Notepad, which travels into the live meeting. Full preparation details and the live private notepad need a paid plan.

After the call, ask the recap's Assistant to draft the proposal sections from the notes and transcript. It answers from that meeting unless you turn on more sources.

  • Custom recap template: describe the five facts above, and Bridge generates a template you can apply to each discovery call. Custom templates need a paid plan.
  • Knowledge Base files: upload your proposal template or rate card, then turn on Search files so the Assistant can use them. File storage needs a paid plan.
  • Google Docs: with Google Docs connected, a preset action creates a document from the meeting notes. Productivity connectors like Google Docs need a paid plan.

What you end up with

  • A discovery recap with the goal, scope, constraints, budget signals and decision process.
  • A proposal draft whose scope lines trace back to the call.
  • A short list of open questions to settle before or with the proposal.
  • A follow-up email confirming next steps.

Sources & further reading