You know what’s worse than writing a long and detailed proposal that doesn’t get you the sale?
Writing a long and detailed proposal that doesn’t even get read in the first place.
And let’s face it, very few people will be looking forward to reading a 17-page breakdown of work to be done, even more so when the first page goes "We discussed XYZ" and "Acme Inc. called us to address problem such and so". Why would you write that? They already know – they themselves told you! (Yes there’s a reason for recapping previous conversations, it’s so that you enable the secondary sale with stakeholders that weren’t in the conversation, but that’s a story for another day and besides, you can write it in a better format than "We discussed XYZ". But I digress.)
Proposals are wrong in many ways. Not only because they’re usually too long and because people usually don’t read them much less act upon.
No, the very concept of a proposal is wrong.
You propose a solution with a scope of work and a price. Great.
Now your buyer gets to consider your proposal and raise objections, or make a counter proposal, or they might start tinkering with scope or specs or price.
But they said yes and they wanted your work! So then why the hell do you have to write that damn proposal only to see it become the reason your deal slows down?!
Because a proposal is the wrong concept. And, your proposal should be the confirmation of the verbally agreed sale, not the tool that does the selling for you.
Instead of writing a proposal, write a project outline, or a workshop outline, or a coaching agreement.
Because when you write an outline, you then get to co-develop the outline with your buyer.
And when you write an agreement, your positioning is "This is what we discussed and agreed upon previously, in a formal write-up. Do you agree to proceed Y/N?"
That’s much stronger positioning and messaging than "Hey, I’m proposing something, let me know what you think…"
And positioning and authoritativeness are required for you to land your sales. Your buyer wants to trust not just you, but also trust that you’re the guy or gal for the job. And a proposal makes you look needy instead of authoritative, just because of the label and the psychological positioning of it.
Write agreements, write outlines, write definitions of work. And yes, include terms, pricing and logistics in it.
Just don’t call it a proposal.