Sales Proposal Writer

A proposal should make the buyer feel understood before it sells anything. If the first page is about the vendor, the buyer stops reading. Start with their situation, confirm the diagnosis, and only then present the solution.

Structure

Use this order, and keep the whole document under three pages for a typical mid-market deal:

1. Situation summary — two to three sentences mirroring back what the buyer said in discovery. Quote them where possible. This signals the vendor was listening.
2. Impact of the problem — make the cost of inaction concrete. Use numbers from the discovery conversation. If no numbers surfaced, use a reasonable range and note it as an estimate.
3. Proposed approach — what the vendor will do, at a high level. Emphasize outcomes, not activities. 'Your team will be able to X' beats 'We will deliver Y.'
4. Scope and deliverables — one section per phase or workstream. Be specific enough to be credible, loose enough to avoid scope arguments before the contract is signed.
5. Investment — present price as a single number or a small range. Do not itemize unless the buyer asked for it or the deal is complex enough to require it. Itemized pricing invites nickel-and-diming.
6. Next step — one clear action with a suggested date. 'If this looks right, the simplest path forward is a 30-minute call on Tuesday to align on the start date.'

Tone and length

Write in plain English. No jargon, no buzzwords, no passive voice. If a sentence does not add information the buyer needs to make a decision, cut it.

A proposal that takes more than five minutes to read will not get read in full. Err short. Appendices are fine for technical specs or legal terms — keep the body clean.

Common mistakes to avoid

Do not lead with a company bio or awards page — it signals the proposal is a template. Do not list features the buyer never asked about. Do not include a generic ROI calculator that was not built from the buyer's actual data — it undermines credibility more than it helps.

Customization cues

Every proposal should contain at least three details that could only apply to this specific buyer: their team size, a specific pain they named, a named stakeholder. If those details are not there, the proposal reads as a mail merge and will be treated like one.

Escape hatch

For a small or transactional deal, a well-structured email works better than a formal document. Use the same structure — situation, value, scope, price, next step — but in three short paragraphs.