BW-301a · Module 1
The Three Proposal Structures
5 min read
Most proposal writers pick a structure by habit or by copying the last proposal that worked. This is how organizations develop a house style that stops winning. Structure is not aesthetic preference — it is a strategic choice that should be made after reading the client, not before opening a template.
Three structures dominate serious proposal writing. Each is a coherent argument made in a different order. The mistake is not choosing one of the three — it is choosing the wrong one for the situation.
- Problem-First Opens by naming and diagnosing the client's problem before presenting any solution. Works when: the client is still defining the problem, the client has underestimated the problem's scope, or you have proprietary insight into the problem's root cause. Tactical advantage: positions you as a diagnostician before a vendor. The client reads your solution already agreeing with your framing. Risk: if the client knows exactly what they need and wants a price, the prolonged diagnosis reads as stalling.
- Solution-First Opens with the proposed solution — what you will do and what it will produce — before establishing context. Works when: the client has already scoped the work, you are responding to a formal RFP with mandatory structure, or your solution is genuinely novel and the reader needs to see it to care about the supporting argument. Risk: the client may reject the solution before understanding the reasoning that justifies it. Use this structure only when you are confident the solution will compel continued reading.
- Story-Arc Moves through a narrative arc: current state, desired future state, gap between them, how you close the gap. Works when: the client is internally divided, the decision involves change management as much as vendor selection, or you are writing for a non-technical executive audience that responds to narrative. The story-arc structure is the slowest of the three — every section earns its place only by pulling the reader toward the resolution. Cut any section that does not advance the arc.
Do This
- Choose the structure based on what the client already believes about their problem
- Match the opening to the client's level of problem clarity
- Use problem-first when you have insight the client does not yet have
- Use solution-first when the scope is already agreed and you are competing on execution
Avoid This
- Default to last year's winning proposal structure without checking if the situation is similar
- Use story-arc structure for RFP responses that have mandatory section ordering
- Open with your company's history and capabilities regardless of structure choice
- Mix structures within a single document — the reader senses the inconsistency even when they cannot name it