Turn a Discovery Call Into a Proposal That Lands
The fastest way to write a proposal is opening the last one you sent and swapping the company name and the price. It's also the easiest way to send a document that answers questions this buyer never asked while skipping the one thing they actually said mattered. A rep closing out a busy week can send three proposals in an afternoon this way, each one technically accurate and each one slightly missing the specific reason each buyer said yes to a second call.
Warning
A reused template optimizes for how fast you can send something. It doesn't optimize for whether this specific buyer sees their own stated priority reflected back at them.
A proposal that could be sent to any prospect is a proposal that persuades none of them specifically.
Why the last template is the wrong starting point
Every deal has its own stated priority, and a template built for a previous deal was structured around that deal's priority, not this one. Reusing it means the new buyer's actual concern gets mentioned in passing instead of leading the document. A template that opened with "reducing support ticket volume" for the last customer doesn't automatically fit a new prospect whose stated goal on the discovery call was cutting new-hire onboarding time, even if both prospects are buying the same product.
Take a proposal built from last quarter's version, still opening with the previous customer's priority around support automation. This quarter's prospect never mentioned support tickets once, their whole discovery call was about onboarding speed. A buyer reading a proposal that leads with a concern they never raised reasonably wonders whether the rep was actually listening, and that impression is hard to undo once it's made, even if the pricing and terms further down the page are exactly right.
Before: open the last proposal, swap the company name and pricing numbers, send it.
After: give Claude this deal's actual stated goal, solution, and pricing, and let it structure a one-page proposal that leads with what this buyer specifically said mattered.
A process for a proposal built around this buyer
- 1
State the buyer's own stated goal, not your product's features
Pull the specific goal from your call notes, in close to their own words. That's what the proposal should open with, not a general description of what your product does.
- 2
Give the real pricing and contract terms
State the actual numbers: contract length, price, team size covered. A proposal with placeholder numbers reads as unfinished even if everything else is sharp.
- 3
Ask for a fixed structure, not an open brief
Ask specifically for their goal, your solution, pricing, and an implementation timeline, in that order. A fixed structure is what makes a one-pager scannable instead of a wall of text.
- 4
Check the buyer's stated priority is still visible at a skim
Read just the headers and first line of each section. If their stated goal isn't clearly present at that level, it's buried too deep to do its job.
We're proposing a 12-month contract at $18,000 a year for a 50-person team. Their stated goal on the discovery call was reducing onboarding time for new hires. Turn this into a one-page proposal: their stated goal, our solution, pricing, and a 3-step implementation timeline.
”When more than one stakeholder was on the discovery call and they mentioned different priorities, it's worth naming both explicitly rather than picking just one, since a proposal that only addresses the loudest voice in the room risks losing a quieter but equally important decision-maker.
Two stakeholders were on the call: the ops lead cares about onboarding time, and the finance lead mentioned wanting predictable per-seat pricing. Make sure the proposal speaks to both priorities, not just the first one.
”
Inside Claude Tutorial
Structuring around one buyer's stated priority is transferable.
Leading a document with what the specific reader said they cared about, instead of a general pitch, applies well beyond sales proposals. The app has a full lesson on it, with practice that carries over to any persuasive document.
Folding in an objection you already handled
If a pricing or scope objection came up on the call, the proposal is the place to address it in writing, not hope it doesn't resurface. Leaving it out reads as avoidance once the buyer notices it's missing. A buyer who raised a real concern on the call and sees no acknowledgment of it in the proposal is left to wonder whether the concern was heard at all, or simply ignored.
Tip
Ask Claude to work the objection's reframe directly into the relevant section, not as a separate FAQ tacked onto the end. Addressed where it's relevant, it reads as confidence. Tacked on at the end, it reads as an afterthought.
During the call they pushed back on price compared to a competitor, and we reframed around total cost of ownership. Work that reframe directly into the pricing section of this proposal, not as a separate note at the end.
”The same principle applies to a concern that wasn't fully resolved on the call, something you promised to follow up on. Naming it directly in the proposal, with the answer, shows the buyer their concern was taken seriously rather than quietly dropped.
They also asked a question we didn't have a firm answer to on the call, about data residency for EU customers. We've since confirmed we support it. Add a short note addressing that directly in the proposal, since it was left open on the call.
”Continue reading
- Turning a Messy Call Transcript Into CRM-Ready Notes: where the buyer's stated goal and pricing details this proposal relies on get captured in the first place.
- Handling a Pricing Objection Without Getting Defensive: building the reframe this proposal folds in.
- Writing a Follow-Up Email That Doesn't Read Like a Recap: what to send alongside the proposal so it doesn't arrive with no context.