What are the actual sections of a winning proposal?
The sections follow the order a client makes a decision in, which is why the blueprint starts with their world rather than with yours.
- A value-based title. Names the outcome rather than the deliverable, so the document is about their future from the first line.
- The situation appraisal. Your diagnosis of what is going on, including the pain.
- Outcomes and value. How things will be different, in direction rather than invented numbers.
- Options. Three ways to work together.
- Terms. What the engagement covers and what it does not, kept short enough that nobody has to read the how to decide.
- Next steps. Exactly how to say yes.
- An appendix, if supporting documentation truly helps.
Notice what is missing. No company history, no team bios up front, no methodology tour. Traditional proposals are full of material that does not help anybody decide, and every extra page competes with the four questions that do.
How do I open a proposal so it doesn't read like a summary?
Open with your interpretation of their situation rather than a recap of the meeting. I call this the situation appraisal, and the distinction between diagnosing and repeating back is the whole point of it.
Most consultants write a section headed "what we heard" or "what you told us." The trouble is that it adds nothing. Anyone can repeat back what they heard, and that is not what a client is paying thousands of dollars of your expertise for. They want your reading of it, filtered through your years of doing this work.
Don't skip the pain
Then there is the mistake I see most often. Consultants write a version of "you're doing well, but you could be doing better," which motivates nobody. Name the negative outcomes they are living with because the problem is unsolved. People move to relieve pain far more readily than to capture an incremental gain, and a proposal without pain in it makes your work read like a vitamin instead of a painkiller.
What it should feel like to read
The client should reach the end of that section thinking you understand their situation better than the last three people who looked at it.
Why should I offer three options instead of one?
Three options raise the odds of a yes, and the arithmetic is simple enough to hold in your head. One option gives your client two choices: take it or leave it. Call that a coin flip. Three options give them four choices, and three of the four are a version of yes.
How the three usually differ:
| What changes | Who it suits |
|---|
| Option 1 | Narrower scope, faster | A client testing the water or working to a smaller budget |
| Option 2 | The recommended engagement | Most clients, most of the time |
| Option 3 | Broader, deeper, more support | A client who wants the outcome secured |
Structure changes outcomes more than most consultants expect. In the classic compliance study, how a request was framed moved agreement from 22.2% to 52.8% for the identical larger ask. The proposal is the same work either way; the shape of the choice is what changes the answer.
One caution worth stating: the options should differ in scope and depth, never in how well you do the work.
I spend ages on every proposal and I'm still not sure I'm doing it right
Spending hours on a proposal and still feeling uncertain is a signal about the conversation that came before it, not about your writing. Proposals are never the problem. They are a symptom of a problem that sits earlier in the process.
Match the symptom to its actual cause:
- Pricing all over the map. A pricing problem and a sales conversation problem.
- Proposals take forever to write. A discovery problem: you are guessing at information you should have asked for.
- Clients say you are too expensive. A messaging problem and a sales conversation problem, because the ballpark was never established on the call.
- You are not sure what they want. Discovery again, and the value questions are where that gets fixed.
When the discovery is done properly, the proposal writes itself in an hour, because every section is populated with things the client already told you.
Leah's take
The proposal is where consultants try to make up for everything that did not happen earlier. You are not sure what they really need, so you add detail. You are worried about the price, so you add more scope. You want to seem thorough, so you add your methodology and your team bios and a case study.
None of that is what the client is deciding on. They are answering four questions: what will this do for me, how does it work, how much does it cost, and how do we move forward. Everything that is not one of those four is between them and the decision.
The section that earns you the work is the one at the front, where you tell them what you think is going on. Not what they told you. What you make of what they told you. That is the moment a client thinks: she gets it, and she sees something I have not been able to see myself.
So write that section first, write it as an expert rather than a note-taker, and do not flinch from naming what it is costing them. Then give them three ways to say yes, make the last page dead simple, and walk them through it live if you can.
