You had a good meeting. The buyer liked you. Then the proposal went to people who weren't in the room, and it has to win without you there to explain it.
Lead with their problem
Open with a short summary of what the buyer told you: what they need, what's going wrong today and what a good outcome looks like for them. When a reader sees their own situation described accurately, they trust the rest of the document.
Keep it short enough to finish
A committee member skimming between meetings should understand your offer from the first page. Put the summary, the scope and the price up front, and move background, team bios and detailed procedures into an appendix. Length isn't proof of effort. Clarity is.
Use the buyer's words. If they called it "overflow delivery" in the meeting, don't rename it "supplemental logistics capacity" in the document.
Make the scope impossible to misread
Spell out what's included and what isn't. Service area, schedule, response times, who does what on site, how issues are reported. Ambiguity in a proposal becomes a dispute in the contract.
Price it so nobody needs to call you
Show the price in the structure the buyer will compare it in. If they're comparing per job rates, give a per job rate. If they need a monthly number for budgeting, give one. Put any assumptions next to the price, not on the last page.
For help building the number itself, see pricing strategy.
Prove you've done this before
Use references and specifics from work you've actually done. A short quote from a current client, with their permission, beats a page of claims.
End with the next step
Say exactly what happens if they say yes: who they'll hear from, how onboarding works and how soon you can start. Make saying yes easy.
Why proposals stall after they're sent
- No owner on their side. Ask who will present it internally, and give that person what they need to argue for you.
- Questions nobody can answer. Every unanswered question becomes a reason to wait.
- No date. Agree on when you'll follow up before you send it, then follow up on that date.
- A surprise in the terms. If something in the proposal wasn't discussed in the meeting, flag it in the cover note instead of hoping nobody notices.
A quick checklist
- Their problem in the first paragraph
- Scope with inclusions and exclusions
- Pricing in the buyer's format, assumptions alongside
- Proof from real clients
- A clear next step and a named contact
We write and review proposals as part of our proposal development work. If you have one going out soon, book a free strategy call.
Questions people ask
How long should a vendor proposal be?
As long as it needs to be for the buyer to decide, and no longer. A clear summary up front lets busy readers stop early and still understand the offer.
Should I include my price in the first proposal?
If the buyer has asked for one, yes. A proposal without pricing usually stalls while someone asks for it.
