The playbook
Deal Loss Analysis: Template and Field Guide
This deal loss analysis template turns a broad task into a record another person can use. It captures deal, reason, evidence, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| deal | Record the deal associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| reason | Record the reason associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| evidence | Record the evidence associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| segment | Record the segment associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| lesson | Record the lesson associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with deal. Use the same reference throughout the record so notes are not attached to the wrong item. Then record a consistent reason supported by the conversation. This establishes the information required before the worksheet becomes a request for action.
Next, separate fit timing competition and delivery concerns. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as using a generic price reason for every lost deal, rather than a broad instruction to “improve performance.”
Finally, review patterns by source offer and segment. Put ask what specifically prevented the decision and retain uncertainty in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Using a generic price reason for every lost deal |
| Action | Ask what specifically prevented the decision and retain uncertainty |
| First check | Record a consistent reason supported by the conversation |
| Follow-up check | Review patterns by source offer and segment |
| Outcome to define | losses with useful documented reasons |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If reason changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep losses with useful documented reasons connected to the item so the team can later assess whether the action was useful.
Use observable customer milestones when assessing progress. A seller sending a message is an activity; a buyer agreeing to a next meeting is a different event. Recording both helps the team locate the actual constraint.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now