A won proposal gets celebrated and a lost one gets quietly absorbed, and both reactions skip past the same real information, what actually drove the decision. Most teams never systematically ask why, which means whatever's actually working, or not working, in how proposals get built stays a guess instead of something known.
A win-loss review isn't a victory lap or a blame exercise. It's a genuine, honest look at what actually drove the decision, in either direction.
A won or lost proposal both carry real information most teams never capture
A win might have happened despite a weak point in the proposal, and a loss might have had nothing to do with anything actually within your control. Reviewing both, not just losses, is the only way to find out which is actually true.
Interview the actual decision-maker when possible, not just your own team's guess
Your own team's theory about why a deal was won or lost is a guess, however informed; the client's actual decision-maker knows the real reason. Ask directly when the relationship allows it, rather than relying entirely on internal speculation.
In Stelaah, a proposal's full history and the client's engagement with it stay on the record, giving a win-loss review a real, factual starting point instead of relying purely on memory. See how estimates works.
Separate price from everything else that actually influenced the decision
"They went with someone cheaper" is often an incomplete answer that obscures other real factors, timeline, perceived expertise, a stronger existing relationship. Dig past the first, easiest explanation to the fuller picture.
Review wins as carefully as losses, not just the disappointing outcomes
A win reviewed as carefully as a loss can reveal what's actually working, the specific thing in the proposal or pitch that resonated, so it can be repeated deliberately rather than attributed vaguely to a good pitch.
Turn patterns across several reviews into one real change to how proposals are built
A single review is one data point; the real value comes from noticing a pattern across several and translating it into one concrete change to how proposals get built or presented, not a list of scattered observations that never gets acted on.
A simple checklist
If you do nothing else, do these five things:
- Review wins as carefully as losses, not just the disappointing ones.
- Ask the actual decision-maker directly when the relationship allows it.
- Dig past price to the fuller set of factors that actually mattered.
- Look for patterns across several reviews, not just one instance.
- Turn the pattern into one real, concrete change to the process.
Do that, and every proposal decision, won or lost, becomes real information you can act on, not a moment that just gets celebrated or absorbed.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
