Module 1 · ~13 min
What a proposal actually is · and why most proposals lose deals before they are even presented
“Most proposals are price lists dressed in professional formatting. The ones that close deals are something else entirely — a reflection of understanding so precise that the prospect feels seen rather than sold to.”
The word 'proposal' is one of the most misunderstood terms in sales. Most salespeople think of it as a document that presents the product and the price. It is not. A proposal is a formal expression of the understanding that has been built across every preceding conversation — a structured confirmation that the salesperson has listened, diagnosed correctly, and identified a specific solution to a specific problem. When it is built from that foundation, it closes. When it is not, it fails — regardless of the quality of the product it describes.
Why most proposals fail before they are read
The most common reason proposals fail is that they are generic. They describe the product in detail — the features, the format, the access, the infrastructure — but they do not describe the specific problem the prospect has, the specific consequences of that problem, or the specific way the product addresses their particular situation. A generic proposal asks the prospect to do the work of connecting the product to their context. Most prospects will not do that work. They will simply not feel compelled.
The second reason proposals fail is that they arrive too early. When a proposal is written and sent before the salesperson has genuinely understood the prospect's situation, it arrives without the context required to make the investment feel justified. The prospect reads the price and evaluates it without the full picture of what it would create for them. In that evaluation, the price almost always feels too high.
The third reason proposals fail is that they are never truly presented. They are sent as an email attachment and left to do the work of a conversation. A proposal that lands in an inbox is a document to be filed. A proposal that is walked through in a meeting, with the salesperson present to guide the experience, is a conversation that produces decisions.
What a proposal is actually for
A proposal has three jobs. The first is to confirm discovery — to demonstrate that the salesperson understood the prospect's situation so accurately that the proposal feels like a natural conclusion to the conversations that preceded it, not a sales pitch that follows them. When a prospect reads a well-built proposal, their most common reaction is not 'interesting' — it is 'yes, that's exactly right.' That reaction is the product of great discovery, not great writing.
The second job is to make the value case specific. Not 'here is what the Buyer Ecosystem does' but 'here is what the Buyer Ecosystem does for your specific situation, given what you told me about the challenge you are facing and the outcome you are trying to achieve.' The specificity is everything. A prospect who reads a proposal that speaks directly to their situation does not need to imagine how the product might apply — it is already applied.
The third job is to make the investment feel proportionate. Not cheap — proportionate. The investment should appear in the proposal in direct relationship to the value case that precedes it. When the value case is clearly articulated and the prospect has followed the logic of how the Buyer Ecosystem addresses their specific situation, the price is evaluated against the value — not in isolation. That evaluation, done correctly, almost always lands in the salesperson's favour.
The proposal as the final expression of the Bridge Call journey
For a prospect who has been through two, three, four, or five Bridge Calls, the proposal is the moment when everything that was discussed across those conversations is formalised. It is the document that says: I heard everything you told me, I built something specific for your situation, and here is the path from where you are to where you want to be.
When a prospect experiences a proposal that genuinely reflects their conversations, the emotional response is often significant. They feel understood — which is a rare and powerful experience in any commercial relationship. They feel that the salesperson has taken their situation seriously — which creates reciprocal seriousness in the evaluation. And they feel that the proposal arrived at the right moment — not pushed on them before they were ready, but offered when the relationship had genuinely prepared the ground for it.
Hold on to these
- A proposal is a confirmation of discovery — it should feel like a natural conclusion to the conversations that preceded it
- The three jobs: confirm discovery, make the value case specific, make the investment feel proportionate to the value
- Generic proposals fail because they ask the prospect to do the connection work — specific proposals do it for them
Reflection · write it down
Think about the last proposal you wrote or were involved in. Was it generic or specific? Did it confirm what was discovered in conversations, or did it introduce new value points? What would you change about it now?
Saves automatically · come back to it whenever.
What you walk away with
A fundamental reframe of what a proposal is and why it works or fails — you understand that the proposal is built in the Bridge Calls, not on the day you write it.