A lost-reason field is useful only when the result changes a decision. A list containing only “price” and “other” usually hides more than it explains. Build a small vocabulary that separates the customer’s explanation from your team’s interpretation.
Keep the first category list manageable
Start with distinct outcomes such as no decision, timing, missing requirement, commercial terms, competitor selected, and not a qualified fit. Add a brief free-text note for context rather than creating a category for every unusual story. Review whether people can consistently tell adjacent categories apart before using them in a dashboard.
Record how you know
Include an evidence label: customer stated, observed outcome, or salesperson inference. A customer choosing another supplier does not prove price was the deciding factor. If the reason is unknown, preserve that uncertainty and decide whether a follow-up question is appropriate. Do not turn a required field into pressure to invent an explanation just to close the record.
Connect patterns to an action owner
Review reasons by relevant segment and period, keeping counts visible. A few losses from a large prospect may not describe your entire market. If missing functionality is recurring, record the specific requirement and send a summarized pattern to the appropriate owner. If no-decision losses dominate, investigate qualification and the buying process before discounting the product.
Working record
| Item | Record or check | Decision rule |
|---|---|---|
| No decision | Customer did not proceed with any option | Examine buying-process qualification |
| Timing | A named dependency postponed the project | Capture a realistic revisit trigger |
| Missing requirement | Specific needed capability absent | Validate requirement and segment |
| Unknown | No reliable explanation obtained | Do not replace with a convenient guess |
Worked example — illustrative, not measured
Illustrative note: “Competitor selected; customer stated that local support hours were required.” This is more useful than “lost on price” inferred from an unanswered discount offer. The action is to examine support coverage or qualification, not automatically lower the price.
Put this into practice
- Define each category with a positive and negative example.
- Add an evidence label and concise context field.
- Review a small sample together to align interpretation.
- Change categories only with a mapping for historical reporting.
A mistake to avoid
Do not compare category percentages after renaming or merging categories without explaining the change. Apparent improvement may be a reporting-definition change rather than better sales performance.
Basis and limitations
Methodology: this is an original editorial planning framework, not a vendor feature claim or a hands-on product test. Adapt the suggested checks to your project.