Open with one paragraph on the prospect's problem and how you fix it. Follow with scope, a timeline, and one clear price, not three options. Keep it to 3 to 8 pages for most B2B deals. Send it, then follow up within three business days instead of waiting for a reply that may never come on its own.
What you need before you write it
Have these three things ready before you open a blank document:
Notes from your discovery call: the exact problem the prospect described, in their words
A rough budget number or deal size, even if it's a range
The name and title of the person who actually signs off, not just your main contact
Also decide which kind of proposal you're writing. A solicited proposal responds to a request the prospect already sent you, usually an RFP. An unsolicited proposal follows a sales call where nobody asked for a document yet; you're sending one anyway to move the deal forward.
This works well for B2B service pitches, SaaS sales, agency proposals, and consulting engagements. It does not replace a formal RFP compliance matrix for government or large enterprise procurement. Those need a structure built around the issuing agency's own checklist, not a general template.
Method 1: writing a solicited proposal (responding to an RFP)
Start by reading the RFP itself twice before you write a single sentence.
Read the full RFP twice. Note every "must include" line separately from the "nice to have" ones.
Mirror the RFP's own section order and numbering in your response. Don't reorganize it around your own pitch structure.
Answer every required item, even the ones that feel like a formality.
State pricing only in the section the RFP asks for it, not earlier.
Attach only the documents the RFP lists. Extra attachments slow down a procurement reviewer; they don't impress one.
To confirm it's ready, check your draft against the RFP's own requirements list line by line. A missing required section is the single most common reason a compliant vendor gets disqualified before anyone reads the pitch itself.
Read Also: How to Write a Business Proposal that Actually Gets Signed
Method 2: writing an unsolicited proposal (after a sales call)
Start from the prospect's problem, not your product.
Open with the problem in the prospect's own words, pulled from your call notes.
State your solution in two or three sentences. Save the detail for later sections.
List deliverables and a realistic timeline, week by week if the project is short.
Show one pricing recommendation. Add optional add-ons below it if needed, but lead with a single number.
Add one proof point, a short case study or a specific client result with a real figure.
Close with one next step and a date, not a general "let's talk soon."
To confirm it's ready, read it back as if you were the prospect and nobody had briefed you. If you can't tell what to do next within ten seconds of reaching the end, cut the closing section down further.
What happens after you hit send
Most guides stop at "send it." What happens next decides whether the deal moves.
An analysis of 16.5 million cold emails found that a proposal's first follow-up pulls an average 8.4% reply rate, with a steady drop on every touch after that. A separate dataset covering more than 2 million sales emails across 100+ industries found the opposite skew at the top of the funnel: 79.4% of all replies came from the initial send, and only 20.6% came from follow-ups. Read together, the two numbers say the same thing from different angles: your first send has to do most of the work, and the follow-up is there to catch the reply that got buried, not to rescue a weak proposal.
Send your first follow-up two to three business days after the proposal goes out. Not the next morning, and not a week later. Reference the specific proposal by name or topic instead of a generic "just checking in," and give the prospect one new piece of information, a data point, a case reference, or a direct question, so there's something to actually respond to.
Solicited vs. unsolicited: which method fits your deal
Method | Best for | What you need first | What the prospect sees first |
|---|---|---|---|
Solicited (RFP response) | Government, enterprise, and formal procurement deals | The RFP document, its compliance checklist, and the submission deadline | A response structured in the RFP's own section order |
Unsolicited (after a sales call) | B2B service and SaaS deals, warm prospects | Discovery-call notes, a ballpark budget, the decision-maker's name | A short, personalized pitch built around their stated problem |
Troubleshooting: when the proposal doesn't work
The prospect opened it, then went quiet. This is the most common outcome, not a sign the deal is dead. Send your first follow-up two to three business days later and name the specific proposal instead of writing "just checking in." If three well-timed follow-ups get nothing back, the problem is usually the offer or the price, not the cadence.
It reads like every other template. A Quora answer on proposal templates puts it plainly: customize each proposal to the work you're bidding on rather than filling in boilerplate. A prospect can tell within a paragraph whether you copied their industry's placeholder text or actually referenced their call.
It never reaches the person who signs off. If your main contact isn't the final decision-maker, ask directly during discovery who approves budget. Address that person by name in the proposal's executive summary even if they weren't on your call.
The prospect stalls comparing pricing tiers. A 2026 Salesforce report found 57% of sales professionals say customers now take longer to decide than they used to, and stacking three or four pricing options onto a proposal tends to add to that delay rather than create flexibility. Lead with one recommended option and list add-ons separately if you need to show range.
FAQ: How to Write a Sales Proposal that Gets Read
How long should a sales proposal be?
Most B2B sales proposals run 3 to 8 pages. Short, transactional services can work in 1 to 2 pages, while enterprise or government RFP responses can run 20 to 50 pages when the issuing organization requires it.
What's the difference between a sales proposal and a business proposal?
A sales proposal is narrowly focused on a specific offer, its price, and a close. A business proposal is broader and often includes more company background and context, though the two terms get used interchangeably in practice.
Do I need to use a proposal template?
A template gives you a starting structure, not finished content. Treat the sections as a checklist and replace every placeholder line with something specific to the prospect you're pitching.
How soon should I follow up after sending a proposal?
Two to three business days is the range that shows up across cold-email and proposal-tracking data. Following up the next morning tends to read as pushy, and waiting a full week lets the prospect's attention move elsewhere.
Should I include multiple pricing tiers?
Lead with one recommended option instead of two or three side-by-side tiers. Multiple options give a buying committee more to debate, which tends to slow the decision rather than speed it up.
Before you send the next one
The structure matters less than what you put inside it: the prospect's actual problem, one clear price, and a specific next step. A solicited proposal succeeds by matching the RFP's own checklist exactly. An unsolicited one succeeds by reading like it was written for one person, because it was. Either way, the work after you hit send timing the follow-up and reaching the actual decision maker decides as much of the outcome as the document itself.