BW-301a · Module 3
Proposal Post-Mortems
5 min read
Most proposal post-mortems go like this: the team asks the client for feedback, the client says something vague and kind, the team concludes the proposal was fine and the decision came down to price. This tells you almost nothing and improves nothing.
A disciplined post-mortem interrogates the proposal itself — its structure, its argument, its section lengths, its close — before it interrogates the outcome. The proposal is evidence. The loss is the verdict. Your job is to reconstruct the crime.
- Read the Proposal as the Client Did Before calling the client, read your own proposal as a skeptical evaluator would — selectively, looking for reasons to doubt. What sections drag? Where did the argument lose momentum? Which sections assumed knowledge the client did not have? Where was the close weak? Most post-mortem findings are visible in the proposal itself before you get a single word of client feedback.
- Audit the Credibility Ladder For each rung of the credibility ladder (problem, solution, execution, risk), grade yourself honestly. Did you establish problem credibility with client-specific language or with generic categories? Did your case studies genuinely parallel this engagement? Did you name the risks or avoid them? A credibility ladder audit often reveals the exact rung where the reader's confidence collapsed.
- Interview the Decision and Not Just the Decision Maker When you do speak with the client, do not ask "why did you choose the other vendor?" Ask instead: "Which section of our proposal gave you the most confidence? Which gave you the least?" These questions extract specific structural feedback that generic questions miss. A client who says "we loved your approach but weren't sure about execution" has just told you your execution credibility was insufficient — the case studies did not close the gap.
Do This
- Read the proposal self-critically before collecting client feedback
- Run the credibility ladder audit on every lost proposal
- Ask specific structural questions ("which section gave you the most/least confidence?") rather than generic outcome questions
- Track findings across multiple post-mortems to identify structural patterns — a weakness that appears in three consecutive losses is a system problem, not a situational one
Avoid This
- "We lost on price" — price is almost never the only reason, and believing it prevents structural improvement
- Accept vague positive feedback ("it was a great proposal, it just wasn't the right fit") as useful data
- Skip the post-mortem on wins — wins have as much to teach about what worked as losses have about what did not
- Treat every loss as unique — patterns in losses are the only reliable improvement signal you have