The playbook
Deal Loss Analysis: Checklist
Use this deal loss analysis checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect losses with useful documented reasons. Check an actual customer or opportunity record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Ask what prevented the decision and retain the buyer's actual explanation where available. Separate confirmed reasons from the seller's inference. Review recurring problems in fit, timing, trust, scope, and delivery rather than collapsing everything into price.
Before you use the checklist
Name the exact item being checked and its purpose. Gather deal, reason, evidence, segment, lesson. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Record a consistent reason supported by the conversation | A dated observation showing how deal was verified | sales operations lead |
| Separate fit timing competition and delivery concerns | A dated observation showing how reason was verified | record owner |
| Review patterns by source offer and segment | A dated observation showing how evidence was verified | sales manager |
Check the failure path
- Look specifically for this failure: using a generic price reason for every lost deal.
- Ask what specifically prevented the decision and retain uncertainty. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check lesson.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Record a consistent reason supported by the conversation,” a meeting about the subject is not the evidence itself. Retain the relevant deal and reason, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents learn why suitable opportunities did not become customers deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow losses with useful documented reasons using a consistent definition so later reviews can connect execution quality with useful results.
Make communication preferences and conversation status visible to the responsible owner. An automated action should not continue blindly after a meaningful reply or a request to stop. Route uncertain cases to a person.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now