Build Loss Reasons That Separate Buyer Outcomes from Sales Explanations
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A loss list containing “competitor,” “budget,” “project cancelled,” and “poor discovery” asks one field to answer different questions. Competitor describes a destination. Budget might describe something the buyer reported. Project cancelled describes what happened to the initiative. Poor discovery is the selling team’s explanation of its own performance. Selecting one hides the others.
Separate loss information into three layers: the buyer outcome, the buyer-stated reason, and the internal explanatory hypothesis. Attach evidence and uncertainty to each. When buyers provide several reasons, preserve those reasons without inventing a ranking.
This structure addresses a narrow problem: making an individual loss record interpretable before anyone aggregates records into patterns. It does not require a broader CRM redesign.
1. Give each layer one operational question
Define whether an entry describes a decision, reports an explanation, or proposes a contributing cause.
- Buyer outcome: What happened to the purchase or initiative? Examples include choosing another supplier, retaining the existing approach, ending the initiative, or postponing it.
- Buyer-stated reason: What explanation did a buyer contact give? Examples include unavailable funding, an unmet requirement, or an implementation constraint.
- Internal hypothesis: What does our team think contributed? Examples include incomplete discovery, an untested value case, or late involvement of a decision-maker.
Outcomes distinguish purchases that went elsewhere from initiatives that ended. Reported reasons preserve the buyer’s account. Hypotheses identify questions worth investigating or coaching.
Do not require these layers to tell a neat story. A buyer may confirm cancellation without explaining why. The team may suspect weak discovery even when the buyer reports a funding withdrawal. Both belong in the record, but neither automatically proves or disproves the other.
2. Define codes and the cancellation boundary
A category needs an inclusion rule, not just a familiar name. Otherwise, one reviewer uses “budget” for unavailable funds while another uses it for a price objection.
The following coding guide is a hypothetical starting design. Keep the layers separate even if you change the vocabulary.
OUTCOME OTHER_SUPPLIER Buyer confirms another supplier was selected. EXISTING_APPROACH Buyer confirms retaining the current approach. CANCELLED Buyer confirms the current initiative has ended. DEFERRED Buyer confirms it remains intended but is postponed. UNKNOWN Buyer disposition is not established. BUYER-STATED REASON FUNDING_UNAVAILABLE Buyer reports funds unavailable or withdrawn. COMMERCIAL_TERMS Buyer cites price, payment, or contract economics. REQUIREMENT_GAP Buyer cites an unmet requirement. TIMING_CONSTRAINT Buyer cites timing or implementation capacity. ALTERNATIVE_FIT Buyer reports another approach fits better. PRIORITY_CHANGE Buyer reports changed organisational priorities. OTHER_EXPLICIT Buyer gives a reason outside these categories. NOT_OBTAINED No buyer explanation has been obtained. INTERNAL HYPOTHESIS DISCOVERY_GAP A material need may not have been uncovered. VALUE_CASE_GAP Value may not have been established adequately. STAKEHOLDER_GAP Relevant decision-makers may have been missed. RESPONSE_GAP Seller handling or timing may have contributed. OFFER_MISMATCH The offer may not have fitted the need. NOT_ASSESSED The team has not formed a hypothesis.
CANCELLED means the current initiative has ended; DEFERRED means it remains intended but has been postponed. Withdrawn funding alone establishes neither. “Stopped for this planning cycle” is also insufficient: it might describe an ended initiative or a postponed one. Ask whether the current initiative remains intended. Until clarified, use UNKNOWN and retain the reported wording in a paraphrase.
Cancellation does not mean the buyer can never pursue a similar project again. The question is whether this initiative ended, not whether the underlying need disappeared forever.
Other exclusions matter too. A discount request does not establish FUNDING_UNAVAILABLE. Silence does not establish DEFERRED. A seller’s suspicion of weak discovery does not supply a missing buyer explanation.
3. Separate reason collection from reason priority
Recording reasons and ranking them are different tasks. A buyer might mention unavailable funding and limited implementation capacity without saying which mattered most. Preserve both explanations.
Add a primary-reason status alongside the reported-reason entries:
PRIMARY-REASON STATUS BUYER_RANKED Buyer explicitly identifies a leading reason. PRIORITY_NOT_ESTABLISHED Reasons obtained; buyer priority is unknown. NOT_APPLICABLE No buyer explanation has been obtained.
When the status is BUYER_RANKED, identify the primary entry and the evidence for that ranking. When it is PRIORITY_NOT_ESTABLISHED, leave the primary entry unassigned while retaining every reported reason, its source, and relevant context.
NOT_OBTAINED applies only when no buyer explanation has been obtained. It must not replace valid reasons merely because their relative importance is unknown. Where it is used, set primary-reason status to NOT_APPLICABLE.
Do not infer priority from the order in which reasons appeared in an email. If different contacts offer different explanations, retain each account and its origin. A seller-ranked interpretation, if useful, belongs in the internal hypothesis—not in the buyer’s ranking.
4. Use a filled record that preserves the distinctions
Fictional worked example: Northbridge Components is considering a purchasing-workflow replacement. After reviewing the proposal, its project lead reports that finance withdrew funding and the implementation team lacks capacity. The lead explicitly confirms that the current initiative has ended, rather than remaining scheduled for later. The buyer does not rank the explanations.
The seller also notices that its proposal omitted a cost baseline finance had requested. The following filled artifact is a reusable recommended structure, not a claim about a product feature.
OPPORTUNITY
Northbridge Components — purchasing-workflow replacement
Seller status: Closed lost
BUYER OUTCOME
Code: CANCELLED
Description: Project lead confirms the current initiative has ended,
not merely been postponed. A future replacement would
require a new initiative and decision.
Source: Project lead's follow-up email after proposal review.
Uncertainty: Account comes from the project lead; budget owner
has not separately confirmed it.
BUYER-STATED REASONS
R1 code: FUNDING_UNAVAILABLE
Paraphrase: Finance withdrew the initiative's funding.
Source: Project lead's follow-up email.
R2 code: TIMING_CONSTRAINT
Paraphrase: Implementation staff lack capacity for the replacement.
Source: Same email.
Primary-reason status: PRIORITY_NOT_ESTABLISHED
Primary reason: Unassigned
Ranking uncertainty: Contact did not rank R1 and R2.
Explanation gap: How finance selected this initiative is unknown.
INTERNAL EXPLANATORY HYPOTHESIS
Code: VALUE_CASE_GAP
Hypothesis: The proposal may not have given finance enough support
for retaining the initiative's funding.
Supporting observation: Proposal omits the cost baseline finance
requested in an earlier meeting record.
Counterevidence: Project lead reports other initiatives also lost
funding and separately identifies a capacity issue.
Uncertainty: Omission is observable; its causal role is unestablished.
FOLLOW-UP
Questions: Did the missing baseline affect the funding decision?
Was either reported reason decisive?
Action: Ask the contact if willing; otherwise retain uncertainty.
Owner: Opportunity owner.
Review trigger: New buyer evidence or scheduled loss review.The outcome is CANCELLED because the buyer explicitly describes an ended initiative—not because funding disappeared. Both reported reasons remain available even though no primary reason is assigned.
The proposal omission supports an internal hypothesis, not a claim that better selling would have prevented cancellation. The team can improve proposal work without rewriting the buyer’s account or treating the funding decision as fully explained.
5. Attach evidence to the claim it supports
A single evidence note at the bottom can make every entry appear equally supported. Instead, connect each material claim to its own basis.
An email reporting withdrawn funding supports a buyer-reported explanation. It does not establish that the seller’s price was too high. A missing discovery note establishes missing documentation, not necessarily that discovery never happened.
Preserve enough context to interpret each claim:
- Origin: who supplied the information and their relationship to the decision.
- Timing: whether it came before the decision, during notification, or in a later review.
- Basis: buyer statement, documented observation, or seller inference.
- Scope: what the material supports and what remains unresolved.
Paraphrase accurately and retain a reference to the underlying material where appropriate. A polite message saying the buyer is not proceeding does not establish a detailed reason—or distinguish cancellation from postponement.
Internal material remains useful. A proposal, meeting record, or unanswered requirement can make a hypothesis inspectable. It becomes misleading only when presented as the buyer’s explanation without supporting buyer evidence.
6. Make uncertainty specific and resolve edge cases
A general confidence score can hide differences between claims. The outcome may be clear while reason priority is unknown. Prefer a statement such as “supplier selection confirmed; relative importance of price unknown” over an unexplained confidence label.
Keep missing-information states distinct: unknown outcome, no explanation obtained, priority not established, and hypothesis not assessed. Conflicting evidence is another condition, not a reason to erase either account.
The following edge cases are hypothetical.
The buyer says the offer is too expensive
Record COMMERCIAL_TERMS as the reported reason. Establish the outcome separately. Do not automatically add VALUE_CASE_GAP; that hypothesis needs its own rationale.
The buyer names another supplier but gives no explanation
Record OTHER_SUPPLIER, NOT_OBTAINED, and primary-reason status NOT_APPLICABLE. Another supplier’s advertised price does not establish why this buyer selected it.
The buyer says the project is on hold
Ask whether the initiative remains intended but postponed, or has ended. If the buyer confirms continued intent, use DEFERRED. If clarification is unavailable, retain UNKNOWN rather than translating ambiguous language into cancellation.
Different contacts give different reasons
Preserve the accounts separately. A sponsor may report missing funding while an evaluator reports an unmet requirement. Use PRIORITY_NOT_ESTABLISHED unless buyer evidence establishes a ranking.
When evidence changes, add a brief revision note. Explain, for example, that an initially unknown outcome was later confirmed as deferred. Do not silently replace the earlier interpretation and its basis.
7. Keep reviews usable without rewarding certainty
Do not require a lengthy causal essay for every loss. Start with an outcome, reported reasons, priority status, and explicit evidence gaps. Develop the internal hypothesis when the record merits review.
Combine controlled codes with short explanations. Codes support comparison; explanations preserve meaning. Either alone can fail: free text fragments similar cases, while codes can flatten important differences.
- Hypotheses become performance verdicts. Require an observable basis and allow counterevidence rather than recording unsupported blame.
- Unknown entries are discouraged. Review whether evidence was sought appropriately, not whether every record sounds complete.
- Unranked reasons disappear. Check that PRIORITY_NOT_ESTABLISHED retains the underlying reason entries.
- Other becomes a catch-all. Inspect explanations before adding a category for a recurring, distinct meaning.
For older mixed records, retain the original wording while separating recoverable claims. “Lost on price” may support a reported commercial reason if a buyer source exists. Without that source, mark the basis as unclear rather than upgrading an old label into verified evidence.
8. Test interpretation before aggregating losses
A hypothetical pilot could use twelve recent losses, including supplier selections, ended initiatives, postponed decisions, and unresponsive buyers.
- Have two reviewers independently separate outcomes, reported reasons, and hypotheses.
- Require a source for each reported reason and a separate primary-reason status.
- Compare disagreements, distinguishing unclear definitions from missing or conflicting evidence.
- Check CANCELLED against DEFERRED specifically. Funding withdrawal is not enough to settle that boundary.
- Revise unclear definitions, then revisit the records without forcing unresolved cases into definite answers.
Count observable results: records with interpretable outcomes, reported reasons with identifiable sources, unranked explanations correctly retained, and hypotheses with supporting observations and uncertainty. Compare reviewer disagreements before and after revising definitions; agreement alone does not prove accuracy.
Start with one recent loss. If rewriting it reveals an unsupported explanation or an unresolved outcome, preserve that gap. The useful improvement is a record another reader can interpret without mistaking a seller’s theory for a buyer’s decision.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications