Back to all articlesLoss analysis

Choose a Primary Loss Reason When Several Factors Contributed

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A buyer says the proposal was expensive, implementation would take too long, and a required feature was missing. The account owner selects price. A product reviewer selects functionality. A manager selects timing. Each label sounds plausible, but none is defensible until someone explains which evidence makes that factor decisive.

Choose a primary loss reason only when the available evidence supports one factor as the best explanation for why this opportunity did not proceed. Preserve the other factors as contributors, and record uncertainty when the evidence cannot distinguish them. A required dropdown is not evidence that a single primary cause exists.

The worksheet below provides a practical way to compare buyer statements, the sequence of events, and counterfactual questions without turning an interpretation into a fact. It addresses one lost opportunity—not statistical causation or patterns across deals.

1. Define the decision you are trying to explain

Before choosing a reason, write down the buyer decision and the point at which it occurred. Otherwise, reviewers may explain different events while believing they disagree about the same one.

These are different outcomes:

  • The buyer rejected the proposed solution.
  • The buyer selected another supplier.
  • The buyer deferred the entire project.
  • The buyer stopped participating, and the seller closed the opportunity without a confirmed buyer decision.

Missing functionality might explain rejection of one solution, while a budget freeze explains why the wider project stopped. A lack of response establishes neither by itself.

Use a short outcome statement: what happened, when it became known, and how it was confirmed. If the buyer decision is unconfirmed, say so. Do not quietly convert a seller's administrative closure into a buyer's stated rejection.

Then set the evidence cutoff. A later conversation can justify revising the record, but it should not be presented as information the reviewer possessed at the original decision point.

2. Separate candidate reasons from supporting evidence

Start by listing every material explanation without selecting a winner. For each candidate, distinguish three things: what the buyer communicated, what happened, and what the reviewer inferred.

  • Buyer communication: a specific statement about a requirement, objection, constraint, or decision.
  • Observed event: a proposal revision, cancelled evaluation, completed test, or other documented step.
  • Reviewer inference: an interpretation connecting that evidence to the loss.

A buyer describing a proposal as expensive establishes a price concern. It does not establish that a lower price would have secured the purchase. Likewise, an unfinished feature establishes a gap, but not necessarily a disqualifying gap.

Record the speaker's role and basis of knowledge. A project lead may understand implementation constraints but not have final purchasing authority. An executive may confirm cancellation without knowing every evaluation detail. Neither title nor proximity to the seller makes every statement equally informative.

Preserve the original communication or a reference to it alongside a concise paraphrase. If only a salesperson's recollection is available, label it as recollection rather than treating it as a direct buyer record.

3. Reconstruct the sequence before testing explanations

Chronology helps distinguish an early objection from the eventual stopping point. Record when each factor appeared, what happened in response, and whether the opportunity continued afterward.

Continuation is useful evidence, but it is not a verdict. A buyer may continue evaluating despite a serious concern. Conversely, the final objection may be a convenient explanation rather than the decisive one. The sequence matters because it lets reviewers test these possibilities instead of assuming either.

Look for transitions: when did active evaluation become conditional, when was a condition tested, and when did the buyer stop? Also note whether a proposed remedy was merely offered, explicitly accepted, or actually evaluated.

A discount offered after rejection does not prove price was resolved. A roadmap discussion does not prove a missing capability became acceptable. Keep the status of each remedy visible.

4. Use counterfactual questions to test decisiveness

A useful counterfactual asks whether changing one factor, while leaving the others unchanged, would have changed the buyer's decision. It is a structured question, not a claim that an alternate outcome has been proven.

  • If price had met the buyer's expectation, would the unchanged solution and schedule still have been rejected?
  • If the missing functionality had been available, would the existing price and schedule have allowed the buyer to proceed?
  • If implementation had fit the deadline, would the remaining concerns still have prevented selection?

Ask about remaining blockers rather than inviting agreement with a preferred label. A question such as whether resolving the feature gap would have left another barrier is more informative than asking the buyer to confirm that functionality was the problem.

Where follow-up is appropriate, keep it brief and optional. Do not repeatedly contact an unresponsive buyer simply to complete an internal record.

For each answer, identify its status: directly addressed by the buyer, supported indirectly by events, or unanswered. Do not fill an unanswered counterfactual with the reviewer's confidence. Several plausible stories can fit the same incomplete record.

5. Filled worksheet: a fictional multi-cause loss

Fictional worked example: All organizations, events, time intervals, and commercial details in this example are hypothetical. The worksheet is a recommended review design, not a description of a product feature.

Decision and evidence boundary

Opportunity: A fictional distributor evaluating a purchasing workflow system.

Outcome being explained: The buyer rejected this proposed solution and continued its search. The project itself was not cancelled.

Evidence cutoff: The review includes the evaluation record and the project lead's closing email. No subsequent buyer confirmation is available.

Decision participants: The project lead coordinated the evaluation. The operations sponsor confirmed the mandatory workflow requirement. The economic decision-maker did not participate in the closing exchange.

Hypothetical event sequence

  1. Initial proposal: The project lead described the price as above the planned allowance and requested a lower-cost scope.
  2. Revised scope: The seller reduced optional services. The project lead agreed to continue evaluation but did not confirm final budget approval.
  3. Workflow review: The buyer identified a missing approval-routing capability. The operations sponsor confirmed that this capability was required for selection.
  4. Implementation discussion: The seller's proposed workaround added setup work and moved the expected launch beyond the buyer's preferred date.
  5. Closing communication: The project lead said the buyer would not proceed because the required routing was unavailable. The message also noted the workaround's schedule impact and continuing price pressure.

Candidate: price

  • Buyer evidence: The initial proposal exceeded the planned allowance; price pressure remained in the closing communication.
  • Sequence evidence: Evaluation continued after the revised scope, without confirmed budget approval.
  • Counterfactual question: Would an acceptable price have overcome the missing routing capability?
  • Answer status: No direct answer. The sponsor's mandatory requirement suggests that lowering price alone would not have been enough.
  • Evidence strength: Strong evidence of a concern; insufficient evidence that price determined rejection.
  • Proposed treatment: Contributing factor, with budget approval unresolved.

Candidate: missing functionality

  • Buyer evidence: The operations sponsor identified routing as mandatory; the closing communication connected rejection to its absence.
  • Sequence evidence: The requirement was examined before rejection, and the proposed workaround did not satisfy the buyer.
  • Counterfactual question: Would providing routing have made the proposal selectable?
  • Answer status: Partly supported, not fully established. The buyer made routing a condition of selection, but did not confirm that resolving it would remove every remaining objection.
  • Evidence strength: Strong support for a decisive blocker; incomplete support for an eventual purchase.
  • Proposed treatment: Best-supported primary reason.

Candidate: timing

  • Buyer evidence: The workaround would miss the preferred launch date.
  • Sequence evidence: The schedule issue arose from the proposed response to the functionality gap. No separate immovable deadline was confirmed.
  • Counterfactual question: Would an on-time workaround have been acceptable?
  • Answer status: Unanswered.
  • Evidence strength: Supported as a contributor, but weakly supported as an independent decisive factor.
  • Proposed treatment: Contributing factor linked to the workaround.

Completed decision record

Primary reason: Missing required functionality.

Rationale: The buyer confirmed the requirement and explicitly connected rejection to the missing capability. Price remained a concern, but evaluation continued after scope revision. The documented timing objection concerned the workaround rather than a separately confirmed deadline.

Contributors: Price pressure and workaround-related schedule impact.

Confidence: Supported, with a stated limitation: the available record does not establish that providing the capability would have resulted in purchase.

Unresolved question: Whether the revised commercial proposal would have received budget approval if the functionality requirement had been met.

Revision trigger: New buyer evidence that a different factor independently prevented selection, or that the routing requirement was not actually mandatory.

6. Choose a primary reason—or explicitly decline to choose

The worked example supports functionality as the primary reason because several pieces of evidence align. It does not establish functionality as the sole cause, nor does it prove that fixing the gap would have won the opportunity.

A practical decision rule is to select a primary reason when one candidate has a documented connection to rejection, relevant evidence supports that connection, and competing explanations have weaker support as the decisive factor. Use this as a judgment standard, not a numerical causal model.

Other evidence patterns need different outcomes:

  • Multiple independent blockers: The buyer confirms that either an unaffordable price or an unmet mandatory requirement would independently prevent selection. Record both; no unique primary is established.
  • Interaction between factors: The proposed workaround creates both extra cost and unacceptable delay, and the evidence does not distinguish which mattered most. Preserve the combined mechanism rather than forcing a winner.
  • Insufficient evidence: Several concerns were raised, but the buyer's final decision is unexplained or unconfirmed.
  • Contradictory evidence: Relevant participants give incompatible explanations that the available record cannot reconcile.

If your recording system requires one value, use a clearly defined uncertainty value where available and explain the unresolved candidates in notes. If no suitable value exists, flag the record for an agreed exception process. Do not silently convert an arbitrary selection into a confirmed reason.

7. Resolve reviewer disagreement by locating the evidence gap

Ask each reviewer to complete the same short statement: the proposed primary reason, the evidence connecting it to rejection, and the strongest evidence against that interpretation.

This makes disagreement actionable. Reviewers may have different evidence, interpret the same statement differently, or use incompatible meanings of primary. One may mean the earliest obstacle, another the final objection, and another the factor the seller could most readily change.

For this review, primary means the best-supported decisive factor in the buyer's decision. It does not mean the most actionable lesson. A contributing factor can still warrant attention.

Avoid resolving the dispute by counting mentions or adding unsupported scores. Repeated price discussions may reflect negotiation rather than decisiveness. A single well-supported mandatory requirement may be more informative than several general objections.

Keep the review bounded. Seek a missing document or one appropriate clarification if it could materially change the conclusion. Otherwise, record the disagreement and uncertainty. If later evidence overturns the choice, retain the original rationale and document what changed rather than rewriting the history as though the answer had always been clear.

8. Apply the worksheet to one opportunity tomorrow

Choose a recently closed opportunity with competing explanations. Before reviewing it, prepare a record containing the outcome, evidence cutoff, candidate reasons, buyer statements and roles, event sequence, counterfactuals, evidence strength, primary decision, contributors, and revision trigger.

Have two reviewers complete their initial interpretations independently, then compare the supporting evidence. The aim is not agreement at any cost. It is an auditable explanation—or a precise account of why the explanation remains uncertain.

Use these observable completion checks:

  • Every candidate has either an evidence reference or an explicit missing-evidence note.
  • Buyer statements, observed events, and reviewer inferences are distinguishable.
  • Each counterfactual is marked answered, indirectly supported, or unanswered.
  • The final record preserves contributing factors and the strongest unresolved alternative.
  • The rationale explains why one factor was selected, or why no unique primary could be established.

A completed review should let another reader follow the decision without guessing what the reviewer knew. That is a more useful outcome than a confidently populated field with no defensible reasoning behind it.

Loss analysisSales operationsBuyer evidenceCRM practices

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