How to write a business proposal from a discovery call
Turn a discovery call into a proposal that reflects the buyer’s words, makes the scope and price clear, and is easy to act on.
In short: Start with the call transcript, not a blank template, and turn the prospect’s own language into a short account of their problem, the work you will do, the investment and the decision they need to make. Send it promptly as a readable web page, then use engagement signals to guide the follow-up.
A template is useful as a checklist. It is a poor substitute for listening. The proposal should feel like the next sensible step in a conversation the buyer already remembers having.
What a business proposal has to do after the call
A proposal is an external, client-facing pitch, not an internal business plan. Its job is to confirm that you understood the buyer, show a credible route from the current problem to the desired outcome, put a commercial shape around the work and make the next action obvious. Salesforce makes the same distinction: a proposal exists to secure a partnership by demonstrating the value of the service offered (Salesforce, date not shown).
The call has already done much of the selling. Angelique Rewers puts the relationship between the two plainly:
A proposal is not a document. A proposal is a conversation.
The document gives the buyer something they can forward to a colleague, revisit before a budget discussion and use to compare the decision against doing nothing. Research based on 4,564 sales opportunities across 23 countries found that a more selective approach could retrospectively increase sales while bidding on fewer projects (Opportunity Management for B2B Service Organizations, 2024). A clear proposal cannot rescue a poorly qualified opportunity.
Start from the call, not from a template
Immediately after the call, save the recording, transcript and your own notes in the deal record. Before drafting, pull out four things: the exact language used for the problem, the outcome they want, constraints that shape delivery, and how a decision will be made. Those are the raw materials for a proposal that sounds specific without becoming a transcript dump.
Listen again for phrases with emotion or consequence: “We cannot keep missing the launch window,” “sales does not trust the leads,” or “our founder needs a number by Friday.” Keep those phrases intact where possible. They show the buyer you heard the situation and prevent generic capability copy.
Also capture what was agreed, assumed and left unknown. Note the people involved, budget signals, procurement requirements, timing, systems, dependencies and success measures. If the buyer did not give you a success measure, do not manufacture one. State the intended outcome as an assumption and make its confirmation part of the next step.
This is the practical core of how to write a business proposal from a conversation: recall the buyer’s reality accurately, then make a recommendation. proposal.here can take a connected call recording, pasted transcript, notes or call link and draft sections from what the prospect said, using your existing proof, team information and price book. You still need to check facts, choose the recommendation and remove claims the call does not support.
For a useful reference, see this outbound retainer sample, which shows how call details can carry through into a monthly agency proposal.
The nine sections buyers need to make a decision
Use the following business proposal structure as a sequence, not a rigid page count. Here is a consistent hypothetical example: Northstar Studio has spoken with Maya, marketing director at Fieldnote, a B2B software firm that needs a new website before a product launch. Maya said the present site makes their new positioning “look bolted on,” and the launch date cannot move.
Recommendation and context
Write this last, even though it appears first. In a short paragraph, name the situation, recommendation, intended outcome and investment direction. For Fieldnote: “Northstar will reposition and rebuild the Fieldnote website so the product launch has a clear story, an agreed launch path and a site your sales team can send prospects to with confidence.”
Do not open with your agency history. The buyer is scanning for relevance before they reach scope or price.
What we heard
Reflect their words and show the cost of the current state. Separate observations from interpretation: “You told us the current site makes the new product feel ‘bolted on,’ product marketing is rewriting the message in parallel, and the launch date cannot move.”
Include the decision context: “The marketing director will recommend a partner, with founder approval after a review of scope, timing and investment.” This often prevents a later disagreement about what was discussed.
Why we fit
Connect only relevant experience to the problem. For Northstar: “Our work combines positioning and website delivery, so the launch message and the pages carrying it are developed as one piece of work.”
Use one or two proof points that match the buyer’s risk, such as a comparable launch or delivery discipline. Our guide to proposal sections explains what belongs in each part.
Scope
Describe deliverables, activities and boundaries in plain language. Group work into phases: “Phase one confirms the message architecture. Phase two designs and builds the launch site. Phase three covers content population, testing and launch support.”
Then name exclusions and buyer responsibilities. “Fieldnote supplies product screenshots and final legal copy within the agreed review windows; paid media creative and ongoing search work are outside this scope.” Specific exclusions are better than surprising change requests.
Timeline
Show the order of work, review points and dependencies. Avoid dates you cannot control. For Fieldnote: “Work begins after acceptance and kickoff; message approval is the gate before design begins, and launch follows content sign-off and final testing.”
If a fixed date matters, say what has to be true to hit it. “To keep the launch date, Fieldnote will consolidate feedback from its reviewers into one response at each approval point.”
Investment
Make the commercial model easy to read on its own. “The engagement is presented as a one-time positioning and website project, with a separate recurring line only if Fieldnote chooses post-launch optimisation support.”
Use a plain total, payment timing and tax treatment where relevant. Never make the buyer hunt through prose to find the amount.
Proof
Offer evidence that answers the buyer’s main concern. For Northstar, that might be a short case study about a launch site delivered against a fixed date. If your relevant experience is adjacent rather than identical, say so and explain why the delivery method transfers.
Team
Introduce the people who will do the work, not every person at the company. “Your day-to-day lead will be the strategist who runs message workshops, alongside the designer and developer responsible for the approved direction.” State who owns decisions and communication.
Next steps
End with one action and what happens after it. “Accept this proposal to confirm scope and reserve the kickoff slot; Northstar will then send the agreement and schedule the working session.”
Make unresolved assumptions visible. “Acceptance confirms the recommended scope, subject to confirming the final launch date during kickoff.”
How long should a business proposal be?
For a normal services sale, make it only as long as the buyer needs to understand, compare and approve the work. That usually means a concise page with expandable detail or a short document, not a miniature strategy report.
The editing principle is simple:
Simplicity drives sales. If you want to sell more, make people think less.
The exception is a formal RFP or complex project with multiple deliverables. Proton notes that formal RFP responses commonly run around 10 to 15 pages because the buyer expects comprehensive, requirement-led documentation (Proton, October 2025). Follow the requested format, but still write the opening summary for a reader with limited time.
If deleting a section would not change the buyer’s confidence or decision, remove it. Keep technical detail, terms and implementation plans available when they answer a real evaluation question.
Pricing: how to present the investment
Start with a recommendation when the call points to one clear approach. A single recommended investment says, “Based on what you told us, this is the work that solves the stated problem.” It is easier to evaluate than three invented packages designed only to create an anchor.
Offer options when there are genuinely different choices in scope, speed or risk. For Fieldnote, Northstar might show the recommended launch-site engagement and a narrower messaging-only option, explaining what the narrower route does not include. Do not call a stripped-down scope “good,” “better” and “best” if it will not meet the launch need Maya described.
Separate one-time and recurring lines. Put the outcome beside the investment without claiming a return you cannot substantiate. Give payment timing, what triggers each payment and what happens if scope changes. A payment workflow can make the handoff from acceptance to payment less fragmented, but the commercial terms still need to be clear.
Send a page the buyer can read between meetings
Send the proposal while the conversation is fresh, ideally with the review meeting already on the calendar. Rewers advises presenting the proposal live and co-creating the solution with the client before that presentation, rather than treating the send as the end of the sales process (YouTube, April 2025). For a complex deal, walk through the recommendation with the decision group.
A live web page is often more practical than a PDF attachment because it is easier to open and read on a phone between meetings. It also lets you correct a small error without competing file versions. proposal.here publishes a branded live link that reads on a phone, although it does not export PDFs, so teams that require a PDF submission should use a workflow that meets that requirement.
Watch what happens after sending, but do not treat an open as intent. Section-level time is more useful: if the buyer spends time on scope, prepare for delivery questions; if they revisit investment, ask whether the commercial structure fits their approval process. Our reader activity guide explains how to use those signals without being intrusive.
When they stall on investment, do not send a vague “checking in” note. Ask: “Is the question total budget, payment timing or which scope is necessary for launch?” Then listen. Discounting before you know the objection often makes the proposal less credible.
Five mistakes that lose momentum after discovery
- Starting with a generic template makes the buyer work to find their own situation.
- Rewriting the problem in consultant language loses the specificity the buyer gave you.
- Promising outcomes, dates or integrations that were not agreed creates risk for the sale and delivery.
- Giving three arbitrary price tiers avoids making a recommendation and shifts the burden back to the buyer.
- Sending a PDF with no review plan turns an active conversation into a passive document hunt.
Proposal writing is not a separate creative exercise. It is disciplined recall, clear commercial thinking and a follow-up plan. If you need to test a call-first process, you can create a workspace and draft proposals before deciding whether publishing is right for your team.
Frequently asked questions
How to write a business proposal after a sales call?
Write the proposal from the call record: extract the buyer’s problem language, desired outcome, constraints, decision process and open questions. Turn those into a short summary, what-you-heard section, scoped recommendation, timeline, investment and next step. Check every promise against what was actually discussed before sending.
What sections should a business proposal include?
A practical business proposal format includes a summary, what you heard, why you fit, scope, timeline, investment, proof, team and next steps. Add terms, technical detail or procurement information only when the buyer needs them to approve the work. Each section should answer a decision question, not fill a template slot.
How long should a business proposal be?
A services proposal should be as short as possible while still making scope, responsibility, timing, investment and acceptance clear. A formal RFP may need more detail because the buyer has submission requirements. Use a concise summary first, then place supporting detail where readers can find it without obscuring the recommendation.
How do I turn a discovery call transcript into a proposal?
Read the transcript once to identify the buyer’s exact phrases, success criteria, constraints and decision path. Build the proposal around those details, then use your own case studies, delivery process and pricing to show a credible response. Do not copy the transcript verbatim or invent certainty where the call left something unresolved.
Should I send a proposal as a PDF or a web page?
Send a web page when you want a link that is easy to read on a phone, simple to update and capable of showing section-level engagement. Send a PDF when the buyer’s procurement process or submission instructions require one. In either case, schedule the review conversation instead of relying on the document to do all the selling.
Sources
- How to Write a Business Proposal That Wins Clients, Salesforce, date not shown
- Opportunity Management for B2B Service Organizations: A Framework, Evidence and Application, SSRN, September 2024
- How to write a business proposal: A step-by-step guide, Proton, October 2025
- How To Present A Business Proposal To A Client, Angelique Rewers, April 2025
- How Long Should Your Proposal Be?, Proposify, date not shown