What a proposal is actually for
It is not a summary of your conversations and it is not a brochure. A proposal is a document your champion forwards to people who were never on a call, and it has to survive being read without you in the room.
That single fact settles most of the format questions. It has to be short enough to be read in full, specific enough that a stranger understands what is being bought, and written in the customer's language rather than yours.
The test before you send
Give it to someone who knows nothing about the deal. Can they tell you what problem this solves, what changes, what it costs, and what happens next? If not, the people deciding will not be able to either.
The structure
Three pages. Five sections. The first page carries the decision.
Their situation, in their words
Two or three sentences describing what happens today and what it costs them. Use the phrasing they used on the call, not your product vocabulary.
This section does more work than anything else. A reader who sees their own problem accurately described extends trust to everything after it.
Page 1Their words, not yoursWhat changes
The outcome, stated concretely. "Your team stops re-entering customer details in three places, and a handover takes minutes rather than a morning."
Not a feature list. Features answer how; a proposal reader is still deciding whether.
Page 1Outcome, not featuresWhat it costs, on the same page
Price, what is included, and the commercial shape: term, payment timing, what happens at renewal.
Putting price on page one alongside the outcome frames it as an exchange. Hiding it on page five is noticed by every buyer and trusted by none.
Page 1Never buriedHow it happens
The first thirty days: what you do, what they need to provide, who is involved, when they see something working.
This is where deals are quietly lost. Buyers who have been through a bad implementation are more worried about the next ninety days than about your features.
Page 2Answers the real fearWhat happens next, with a date
One specific action with a name and a date attached. "If this looks right, we start on the 14th. I will call on Thursday to answer questions."
A proposal that ends with "let me know your thoughts" has no forcing function and converts into a chase.
Page 2Dated next step
Anything else, including detailed terms, security documentation, and technical specification, belongs in an appendix or a linked document.
What to cut
| Cut | Why |
|---|---|
| Company history and mission | Nobody buys on the basis of when you were founded |
| A feature matrix | Invites line-by-line comparison with a cheaper option |
| Multiple pricing tiers "for flexibility" | Turns a yes/no decision into an internal debate |
| Adjectives: seamless, powerful, innovative | Carry no information and signal a template |
| Case studies of companies unlike them | Reads as filler and quietly says you have no relevant example |
| Legal terms in the body | Necessary, but not what page one is for |
The pricing-tiers row is the one people resist. Offering three options feels generous and usually creates a stall: the buying group now has two arguments to settle rather than one. Present the option you recommend, and mention the alternative in a sentence if a real choice exists.
How to send it
Walk through it live first for anything significant. Fifteen minutes on a call, then send. A proposal that arrives cold is read by someone forming objections you cannot answer.
Send it as a document, not a slide deck. Decks are built to be presented; documents are built to be forwarded and read alone, which is what actually happens.
Write the covering message for the forwarder. Two or three lines your champion can send onwards without editing. They will forward your email, not rewrite it, so make it forwardable.
Copy the second contact, with your champion's agreement. If you have done the work in multi-threading the deal, the proposal should not be the first time anyone else in the organisation encounters what you are proposing.
After you send
Book the follow-up before you send it, not after. "I will call Thursday at 10" turns a wait into an appointment.
Treat a proposal as sent, not as progressed. In pipeline terms a proposal sitting unopened is not a stage forward. The exit criterion is that they have read it and responded, which is one of the honest staging rules in our guide to the weekly pipeline review.
Expect the price conversation, and know what is underneath it. Most objections at this stage are not about the number, and our guide to handling price objections without discounting covers how to tell which kind you are dealing with before you respond.
If it goes quiet, do not send the same proposal again. Silence after a proposal usually means the internal conversation went badly or a stakeholder appeared, not that the document was mislaid. The recovery sequence in what to do when a prospect goes silent applies.
One last discipline. When a proposal converts, note what you did differently; when it does not, record the real reason from a fixed list. After a dozen of each you will know which section of your proposal is doing the work, and that is worth more than any template.
Frequently asked questions
- How long should a proposal be?
- Two to three pages for most small-team deals, with anything longer in an appendix. The length signals effort to the writer and signals work to the reader, and only the reader's opinion affects whether it gets read.
- Should a proposal include the price on the first page?
- Yes. Burying it is transparent and it is the first thing anyone looks for. Putting it early, next to what they get, frames it as an exchange rather than a number to be found and reacted to.
- Should you present a proposal or email it?
- Walk through it live if the deal is significant, then send it. A proposal that lands cold with no conversation gets read by someone with no context, and the objections form before you can answer any of them.
- How many options should a proposal contain?
- Two or three at most, and only if the choice is real. More options shifts the decision from whether to buy to which to buy, which sounds helpful and usually produces a stall while people debate.
- Should a proposal have an expiry date?
- Only if it is genuine, such as a price that actually changes or capacity that is really limited. An invented deadline that passes with no consequence teaches the buyer that nothing you say about timing is true.