Reconstruct what was known at each stage, separate confirmed buyer feedback from internal explanations and compare a consistent set of losses. Look for a process or fit issue you can test. Avoid rewriting uncertain outcomes as comforting stories about price, competitors or an individual salesperson.
Choose a review sample before choosing a conclusion
Define the period, segment and deal stages you will examine. Include quiet losses and decisions to retain the current process, not only competitive tenders with detailed feedback. A sample selected because its records support a preferred explanation cannot tell you much about the broader pattern.
Separate losses from opportunities that remain genuinely undecided. State your rule for classifying stalled conversations, including how long you have waited and what the last agreed step was. These rules are internal reporting choices, not facts about the buyer's intentions. Keeping the distinction visible prevents a pipeline label from becoming an invented account of why someone did not purchase.
Reconstruct the sequence without hindsight
Build a short timeline from the original inquiry, qualification, scope discussion, proposal and final contact. Note what your team knew at each point. A requirement discovered late may have been reasonably hidden, or it may reveal a question that should have been asked earlier. You can investigate that difference without blaming the person handling the deal.
Use contemporaneous notes where available and identify gaps. Memory tends to compress uncertainty into a tidy explanation after an outcome is known. Retain conflicting accounts, such as a contact praising the demonstration while a later reviewer raises an integration concern. Both may be accurate descriptions of different parts of the decision.
Treat buyer feedback as a perspective with limits
Invite feedback respectfully when appropriate, making it clear that the buyer does not owe a justification. Ask which factors mattered and whether the offer or process was unclear. Avoid arguing with the answer or reopening the sale under the guise of research. If the contact only knows one part of the decision, record that limit.
Distinguish a stated reason from your interpretation and from an unverified competitor claim. A buyer saying another offer felt easier to implement does not prove its implementation is universally better. Nor does an incumbent win necessarily mean your price was wrong. The useful finding concerns the buyer's comparison in that situation, together with the evidence you can substantiate.
Choose one change with an observable purpose
Compare patterns by segment and stage. Losses before a decision owner is identified may suggest qualification questions; late surprises about unsupported requirements may suggest clearer scope boundaries. The appropriate response depends on the process you observe. A small review cannot establish a universal market rule.
Select one change for the next set of relevant opportunities and define what you will inspect. You might check whether proposals now reach the necessary reviewers or whether unsuitable requests are recognised earlier. Better qualification can reduce the number of proposals while making effort more focused. Do not judge the change only by total proposal volume, and do not guarantee improved win rates from a limited review.
Fictional example: a supplier reviews ten proposals
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional supplier examines ten lost proposals from one quarter. Four contained requests outside its current capabilities, three stalled before a decision owner was confirmed and three ended with the customer retaining an incumbent. The team keeps these categories separate and marks the details it could not verify with buyers.
For the next review period, it adds an early scope check and a question about how the purchase will be approved. It also investigates what made retaining the incumbent attractive, without assuming that price was the cause. The supplier will inspect whether unsuitable opportunities are recognised sooner and whether decision roles are clearer before proposal work begins. The counts are invented to illustrate a review, not a benchmark, and the case does not claim that these changes will produce more contracts.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Define the review period, segment and classification rules.
- Reconstruct the timeline using original notes where possible.
- Keep buyer statements separate from internal explanations.
- Mark gaps and limits in feedback from one contact.
- Test one process change with a clear observation plan.
Common questions.
Should the salesperson run the review?
They should contribute context, but another colleague can help challenge hindsight and keep the conversation focused on process rather than personal defence.
What if buyers will not provide feedback?
Use the evidence you have and label the limits. You can still inspect qualification, scope clarity and agreed next steps without inventing a reason for the final decision.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse AccelerateLink.
Found an error or a missing qualification? Send an editorial correction.
Find my next move.
Use a practical tool to turn this idea into a clearer starting point.
Find my next move