What to Send a Client After a Discovery Call

Send two things, in order. First, a short written recap the same day: the problem you heard, the outcome they want, the constraints they named, and the next step. Then, once they confirm the recap is right, the priced proposal. Confirming scope before pricing it is what stops a proposal from being rejected over a misunderstanding.

What should you send right after a discovery call?

Send a recap, not a proposal. It is short enough to read on a phone and specific enough that the client can correct it. Four things belong in it:

• The problem, in their words. Not your service category. If they said "we lose leads between the form and the sales team," write that.
• The outcome they described. What changes for them if this works.
• The constraints they named. Budget range, deadline, an internal approver, a platform they cannot move off.
• The next step and when. "I will send scope and pricing by Thursday" is a next step. "Let me know your thoughts" is not.

Why send a recap before the proposal?

Most rejected proposals are rejected on scope, not on price. The client reads a number attached to work that is not quite what they thought they were buying, and the gap between those two things reads as expensive. A recap surfaces that gap while it costs nothing to fix.

This runs against the common advice to get a proposal out within 24 hours. Speed is worth something, but speed applied to the wrong scope just gets you a fast no. The recap is the part that should be fast. The proposal should be right.

There is a second benefit. A client who replies "yes, that is right, though the deadline is actually end of Q3" has just given you a written confirmation of scope and a correction you would otherwise have priced wrongly.

How soon should you follow up?

Send the recap the same day, ideally within a few hours. Send the proposal when it is accurate, which for most service work is two to four days later.

A proposal that lands an hour after the call reads as a template with a name pasted into it, because that is usually what it is. The client can tell. Time spent between the recap and the proposal is visible in the specificity of the scope, and specificity is what makes the document persuasive.

What goes in the proposal that follows?

The proposal turns the confirmed recap into a decision. It restates the problem, sets out the recommended approach, defines scope and exclusions, prices the work against milestones, and states the terms of acceptance. The full section-by-section structure is covered in how to write a business proposal, and the pricing structure in how to price a proposal.

One thing worth deciding before you send: whether this proposal is meant to function as the agreement itself, or whether a separate contract follows it. That choice changes what the terms section has to carry. See is a signed proposal a contract.

What should you not send?

Leave out the capability deck, the full case-study library, and the company overview. The client is holding one question after a discovery call, which is whether you understood their situation. Every attachment that is not about their problem competes with the one that is.

Two more to skip: a price given verbally on the call and then contradicted in writing, and a proposal sent to someone who told you they are not the approver. If a discovery call surfaced an internal decision-maker you have not met, the recap is the moment to ask how they prefer to see this presented.

Start From A Template

Once the recap is confirmed, the proposal is mostly structure you should not be rebuilding each time. Start from the free proposal templates: the consulting proposal template for advisory work, the web design proposal template or software development proposal template for build work, or the freelance contractor proposal template for solo engagements. Each one already separates scope, exclusions, milestones, and payment terms, so the confirmed recap drops into a structure the client can approve.