Back to all articlesLoss analysis

Record Competitor Outcomes Without Turning Hearsay into Fact

Alactic Editorial9 min read

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

A buyer mentions another supplier during a stalled deal. The seller adds that supplier to the loss record. Later, a report counts the opportunity as a confirmed competitor purchase—even though nobody established whether the buyer evaluated, selected, or bought anything.

Prevent that drift by recording the competitor name separately from the claim about what happened. Distinguish a named alternative, an evaluated competitor, a reported selection, and a verified outcome. Attach each claim to its source, scope, date, and limits. A closed-lost opportunity can have an unknown destination; closing your deal does not establish someone else’s win.

The practical artifact below is a completed, hypothetical competitor-evidence matrix. Use it as a record design, not as a claim that any particular CRM already provides these controls.

1. Separate your deal status from the buyer’s outcome

Two questions often get compressed into one field: did our opportunity close, and what did the buyer do instead? The first may be clear while the second remains unresolved.

A buyer might stop your evaluation, postpone the project, retain an existing supplier, choose another vendor, or divide the work. A seller can know that their opportunity is lost without knowing which of those outcomes occurred.

Keep these facts separate:

  • Our opportunity status: the disposition of your sales opportunity.
  • Alternative named: the supplier or other option mentioned in connection with the opportunity.
  • Claim about that alternative: mentioned, evaluated, selected, purchased, or another explicitly defined outcome.
  • Evidence status: what supports the claim and what remains uncertain.

Do not require a competitor name just to complete a loss record. That encourages sellers to replace missing information with a plausible answer. Provide explicit choices such as outcome unknown, no alternative identified, and buyer reported no purchase. Those mean different things and should remain distinguishable.

2. Define four evidence states without treating them as an automatic ladder

These states describe what the available evidence supports. They are not stages that every record must eventually complete.

  • Named alternative: a supplier or option appears in a relevant conversation or source. There is no established evaluation or selection.
  • Evaluated competitor: evidence indicates the buyer actively assessed the supplier for the relevant project. This does not establish a final decision.
  • Reported selection: a source reports that the buyer chose the supplier. Preserve whether the source is the buyer, an intermediary, or a public statement.
  • Verified outcome: a specific outcome has been checked against evidence that directly supports it, under a documented internal standard.

Verification must name the outcome being verified. A direct buyer confirmation may verify selection without verifying a signed agreement, payment, implementation, or continued use. Do not let a generic verified label silently cover all of those claims.

For this recommended design, treat an outcome as verified only when a reviewer can identify the exact claim, inspect a relevant primary source, and explain why it supports that claim for the opportunity’s scope and decision period. A primary source might be a dated statement from the buyer responsible for the decision. An intermediary’s confident account remains second-hand unless it is independently checked.

Evidence strength and outcome progress are separate dimensions. Clear evidence that a supplier was evaluated does not become evidence of a purchase. An uncertain report of a purchase should not erase well-supported evaluation history.

3. Build a matrix that preserves the claim and its limits

Use one evidence entry per material claim. A single opportunity may need several entries if different sources describe different events or scopes.

The following fields form a usable minimum:

  • Opportunity and scope: the project, team, product, or workstream the evidence concerns.
  • Alternative: a normalized supplier name, or an explicit unknown value.
  • Claim: a narrow statement of what reportedly happened.
  • Evidence state: named alternative, evaluated competitor, reported selection, or verified outcome.
  • Source and proximity: who supplied the information and whether they participated in the decision, relayed it, published it, or inferred it.
  • Evidence reference: a retrievable note, message, document, or public source, with appropriate access restrictions.
  • Dates: when the event reportedly happened and when the information was recorded.
  • Limits: what the evidence does not establish, including unresolved scope or timing.
  • Review action: the owner, next check, and reporting treatment.

A confidence score alone cannot replace these fields. A high score does not tell a reviewer whether the evidence concerns a shortlist, an award, or a completed purchase. If scores are useful locally, keep them secondary to the explicit claim and source.

4. Hypothetical worked example: a completed competitor-evidence matrix

All organizations, suppliers, dates, and situations below are fictional. The entries illustrate a recommended operating practice, not customer results. The matrix is presented as individual record cards so each claim retains its context.

Entry A: direct buyer confirmation

  • Opportunity and scope: Alder Services, support-system replacement for its central operations team.
  • Alternative: Cedar Systems.
  • Claim: the buyer selected Cedar Systems for this project.
  • Evidence state: verified outcome—selection only.
  • Source and proximity: the buyer’s project lead, who participated in the decision, directly confirmed the selection in a follow-up email.
  • Evidence reference: retained buyer email linked to the opportunity; the seller’s note paraphrases the confirmation and identifies the sender.
  • Dates: selection reported as 8 September; confirmation received and recorded on 10 September.
  • Limits: no evidence of a signed contract, payment, deployment, or use by other teams.
  • Review action: sales operations reviewed the email on 11 September. Include in verified selections; exclude from verified purchases and deployments.

Entry B: second-hand information

  • Opportunity and scope: Birch Distribution, regional scheduling project.
  • Alternative: Harbor Software.
  • Claim: an implementation adviser reports that Birch chose Harbor Software.
  • Evidence state: reported selection—second-hand.
  • Source and proximity: an external adviser relayed information attributed to a buyer contact; direct involvement in the final decision is unconfirmed.
  • Evidence reference: dated call note identifying the adviser and the information chain.
  • Dates: decision date unknown; report received on 12 September.
  • Limits: buyer confirmation, final scope, and contract status are unknown. Several sellers repeating the adviser’s account would still represent one underlying source.
  • Review action: account owner to seek clarification during an appropriate existing follow-up. Include in reported selections only; do not count as a verified purchase.

Entry C: ambiguous public announcement

  • Opportunity and scope: Maple Group, internal case-management project.
  • Alternative: Beacon Works.
  • Claim: a public announcement names Maple Group and Beacon Works as collaborators.
  • Evidence state: named alternative—relationship announced, project relevance unresolved.
  • Source and proximity: a public statement published by Maple Group.
  • Evidence reference: saved source address and dated summary in the evidence record.
  • Dates: announcement published on 14 September; underlying agreement date unspecified.
  • Limits: the statement does not identify the case-management project, establish a competitive evaluation, or confirm a purchase. It could concern a different workstream.
  • Review action: reviewer to check project relevance before changing the state. Exclude from competitor-selection and purchase totals.

Entry D: unsupported seller inference

  • Opportunity and scope: Willow Logistics, dispatch-workflow project.
  • Alternative: Northstar Tools, seller-suspected only.
  • Claim: the seller suspects Willow purchased Northstar Tools because communication stopped after a pricing discussion.
  • Evidence state: unsupported hypothesis; no buyer-supported alternative or outcome established.
  • Source and proximity: seller inference, not buyer information.
  • Evidence reference: seller note documenting the reasoning; no corroborating source.
  • Dates: inference recorded on 15 September; no known decision date.
  • Limits: silence does not establish evaluation, selection, purchase, or the reason for disengagement.
  • Review action: retain the hypothesis separately from the factual competitor field. Record outcome as unknown and exclude it from competitor outcome counts.

5. Ask the next question that resolves the actual uncertainty

Follow-up should test the claim, not invite agreement with the seller’s theory. Asking whether the buyer chose a named supplier can anchor the conversation to an unsupported assumption.

Start with the missing decision fact: whether the project proceeded, was deferred, or ended without a purchase. If it proceeded, ask what option was selected and for which scope. If the buyer confirms selection, establish whether they mean a preferred option or a completed agreement only when that distinction matters to your analysis.

Match the question to the gap:

  • Named alternative: establish whether it was actually evaluated for this project.
  • Reported selection: establish who made the decision and whether the report describes a final choice.
  • Public announcement: establish whether it concerns the opportunity’s scope.
  • Unsupported inference: ask neutrally about project status rather than asking the buyer to validate the suspected competitor.

Do not pursue confirmation indefinitely. Set a proportionate review point, then leave unresolved claims visibly unresolved. Unknown is a useful result when the alternative is manufactured certainty.

6. Make reports obey the evidence boundary

A careful record still fails if a dashboard treats every populated competitor field as a win. Define reporting groups from evidence states and exact outcomes, not merely from names.

Keep named alternatives and evaluations available for their own analysis. Show reported selections separately from verified selections. Use a verified-purchase category only when the evidence actually establishes a purchase under your documented standard.

Every outcome report should state its inclusion rule and expose the unknown group. Otherwise, readers may mistake the subset with known destinations for all lost opportunities. If you calculate a share, label the denominator: all closed-lost opportunities and opportunities with verified selections answer different questions.

Preserve an event history when later evidence arrives. A reported selection can later become a verified selection, or a buyer can reverse a decision. Store what changed, why, and when rather than rewriting the earlier record as though the final information had always been known.

7. Repair overstated records without destroying their history

When an ambiguous note has already become a confirmed purchase, correct the claim first. Do not merely attach a caveat while leaving the stronger reporting category intact.

  1. Retrieve the earliest available evidence and identify the strongest claim it actually supports.
  2. Downgrade the outcome state where necessary, retaining the original entry in the change history.
  3. Record the correction reason, reviewer, date, and remaining uncertainty.
  4. Recalculate affected reports and tell their owners which conclusions may need revision.
  5. Check for copied records that repeat the same unsupported source.

Separate honest corrections from performance judgment where possible. If sellers expect uncertainty to be treated as poor work, they have an incentive to supply confident answers instead of accurate limits.

There is a trade-off: source-linked review takes more effort than a mandatory competitor dropdown. Keep the initial capture short and reserve detailed review for claims that will enter outcome reporting. Do not collect unnecessary documents or personal information merely to make a record look stronger; a relevant, access-controlled reference may be enough.

8. Run a bounded evidence check before the next report

For a hypothetical first pass, review ten recently closed-lost opportunities with competitor names. For each, check whether the source is retrievable, the claim is explicit, the scope matches, and the reporting category stays within the evidence.

Record how many entries are supported as written, how many need a narrower claim, and how many remain unknown. Also count claims that changed category because of new evidence separately from claims corrected because the original record overstated its source.

The immediate success measure is not fewer unknowns. It is fewer records where the report says more than the evidence supports. Before the next loss review, assign an owner to correct those mismatches and confirm that the revised report preserves the distinction between a competitor being mentioned and a buyer actually choosing one.

Loss analysisEvidence qualityCRM dataSales operations

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