The Proposal Is Not Where You Win the Deal
By the time you send it, the client should already know the answer.
Most proposals fail not because the solution is wrong or the price is too high, but because the proposal is doing the selling. It should not be. The selling should be done before the document is written. A proposal should confirm a decision the client has already made in their head.
The pattern that loses: a consultant has a good introductory conversation. The client seems interested. The consultant says "I'll send through a proposal." Then they spend hours crafting a document that explains their approach, lists deliverables, justifies the price, and adds testimonials for credibility. They send it. Then they wait. The client goes quiet. Maybe a follow-up email gets a "we're still reviewing it" response. More often, silence.
What happened? The proposal was doing work that should have been done in conversation. The client had unresolved questions, unspoken concerns, or a vague understanding of what they were buying. The proposal landed on a foundation that was not ready.
The pattern that wins: the scoping conversation covers everything the proposal will contain, in dialogue. By the end of that conversation, the client knows the approach, understands the deliverables, has discussed the price range, and has asked every question they need answered. When you say "I'll send through the proposal," what you are really saying is "I'll put everything we just agreed on into a document." The proposal becomes a receipt for a conversation, not a pitch.
The practical difference is in the scoping conversation itself. It needs to cover four things before the meeting ends.
First, the problem. Not your understanding of the problem, but theirs. Let them describe it in their own words. Ask follow-up questions until you can repeat it back and they say "yes, exactly." If you cannot articulate the problem in their language, you are not ready to propose a solution.
Second, the approach. Walk them through how you would solve it. Not the technical details, but the shape of the engagement. "We would start with X, then move to Y, and deliver Z." Watch their face. If they are nodding, you are aligned. If they look uncertain, ask what is bothering them. Resolve it now, not in a document they will read alone.
Third, the investment. Never let the price be a surprise in the proposal. Introduce the range in conversation. "For something like this, you are typically looking at $X to $Y depending on scope." If the client does not flinch, you have budget alignment. If they do, negotiate now while you have the relationship in the room, not later via email.
Fourth, the decision process. Ask directly: "If the proposal matches what we have discussed today, what happens next on your end? Is there someone else who needs to approve this? What is your timeline?" This tells you whether you are talking to the decision maker and whether there are unseen obstacles.
If all four are covered in the scoping conversation, the proposal writes itself. It is a short document that says: here is the problem you described, here is the approach we discussed, here is the price we agreed on, here is how we start. The client reads it and thinks "yes, this is what we talked about." They sign.
The uncomfortable truth is that most consultants use proposals as a substitute for difficult conversations. It feels easier to write about the price than to say it out loud. It feels safer to explain your approach in a document than to defend it in real time. But the proposal is where difficult conversations go to die. If you cannot say it to their face, it will not land in a PDF.
Win before the proposal. Build what pre-sells you.
When your positioning, content, and product do the convincing, the proposal is a formality. That is what the 12 Principals programme builds around your expertise over twelve months.
