Back to all articlesLoss analysis

Distinguish a Price Loss from an Unclear Value or Scope Decision

Alactic Editorial10 min read

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

A lost deal marked as price can conceal several different decisions: the buyer could not authorise the spend, selected less work, did not see enough value, or simply gave no usable explanation. Those are not interchangeable findings.

For price loss analysis, code the narrowest conclusion the record supports. Keep the buyer’s stated reason separate from the analyst’s interpretation, and record what remains unknown. An expensive label alone does not establish a budget constraint, a value objection, or an equivalent lower-priced alternative.

The practical goal is not to find a more sophisticated label for every loss. It is to stop an ambiguous record from becoming a confident explanation in the next sales report.

1. Separate a price reference from a supported loss reason

Price can appear in a conversation without being established as the deciding factor. A buyer may discuss cost during evaluation, then stop because the project is cancelled. A salesperson may remember a pricing objection more clearly than a later change in priorities.

Use three distinct judgments when reviewing the record:

  • Price mentioned: there is evidence that cost or spending was discussed.
  • Price linked to the decision: the buyer connects spending, affordability, or perceived worth to the final outcome.
  • Mechanism supported: the record explains whether the issue was a budget ceiling, a scope choice, a value concern, or something else.

The first judgment does not establish the second. The second does not necessarily establish the third.

Also distinguish buyer-reported explanations from verified circumstances. A buyer’s statement that funding was unavailable supports a buyer-reported budget constraint. Unless the record contains more evidence, it does not establish the organisation’s total financial capacity or prove that no exception was possible.

This distinction preserves useful information without pretending to know the buyer’s internal decision process.

2. Use a small set of evidence-based codes

A workable coding scheme needs room for uncertainty. Otherwise, reviewers will force unclear cases into whichever category sounds closest. The following is a recommended operating design, not a claim about fields available in any particular CRM.

  • Budget ceiling stated: the buyer identifies a spending limit and links that limit to the decision. Record the amount, period and coverage if available.
  • Different-scope selection: the buyer chooses an alternative with a material difference in work, coverage, timing or service. Record only known differences.
  • Value concern stated: the buyer explicitly connects the decision to insufficient expected benefit or justification for the spend.
  • Price concern, mechanism unclear: the buyer links cost to the loss, but the record does not distinguish affordability, scope or perceived value.
  • Reason undisclosed: the buyer does not provide a usable explanation. A refusal to explain belongs here, not automatically under price.

Keep price mentioned as a separate flag if it is useful for analysis. That lets a team retain the commercial context without treating every mention as a confirmed cause.

Use an additional category such as multiple supported factors only when the record genuinely supports more than one explanation. Do not use it as a substitute for deciding what is known.

3. Filled hypothetical price-loss decision table

Fictional worked example: all cases, amounts and records below are hypothetical. This decision table is presented as one case per entry so it can be copied into a review document without requiring a particular software layout.

Case A — An explicit budget ceiling

  • Available record: the proposed annual service costs $24,000. The buyer’s final email states that approved spending for that service is capped at $18,000 for the current year and that the purchase cannot proceed within that limit.
  • Primary code: budget ceiling stated.
  • Price mentioned: yes; directly linked to the decision.
  • Supported conclusion: the buyer reports a current-year spending ceiling below the proposed annual amount.
  • Not supported: the buyer saw insufficient value; the supplier’s price was above market; a different amount would necessarily have won the deal.
  • Evidence gap: whether other decision factors existed and whether the ceiling applied beyond the current year.
  • Report wording: lost with a buyer-stated annual budget ceiling; other decision factors not established.

Case B — A differently scoped alternative

  • Available record: the buyer selects a $12,000 annual alternative instead of a $20,000 annual proposal. The buyer’s decision summary states that the selected purchase covers one team, while the proposal covered three teams. The buyer says the current requirement is limited to one team.
  • Primary code: different-scope selection.
  • Price mentioned: yes; lower total spending accompanies the narrower purchase.
  • Supported conclusion: the selected purchase has a lower total price and narrower documented coverage.
  • Not supported: the alternative is cheaper for equivalent scope; either supplier offers better value; the buyer could not fund the broader proposal.
  • Evidence gap: equivalent-scope costs and the buyer’s assessment of any other differences.
  • Report wording: buyer selected a narrower purchase for the current requirement; like-for-like price comparison unavailable.

Case C — An unsubstantiated expensive label

  • Available record: the buyer’s final message describes the offer as too expensive and confirms the purchase will not proceed. No budget, comparison, scope explanation or benefit assessment is provided.
  • Primary code: price concern, mechanism unclear.
  • Price mentioned: yes; linked to the decision, but not explained.
  • Supported conclusion: the buyer expressed a price concern when declining.
  • Not supported: a hard budget ceiling, an equivalent cheaper option, or insufficient perceived value.
  • Evidence gap: what expensive meant in this decision.
  • Report wording: buyer cited expense; affordability, scope and value interpretations remain unresolved.

Case D — A buyer declines to explain

  • Available record: the buyer confirms that the purchase will not proceed and declines to discuss the decision. A salesperson’s note speculates that price was probably the issue. There is no buyer statement supporting that interpretation.
  • Primary code: reason undisclosed.
  • Price mentioned: no buyer-supported reference in the available record.
  • Supported conclusion: the buyer declined to explain the loss.
  • Not supported: price, budget, scope or value as the reason.
  • Evidence gap: the decision rationale itself.
  • Report wording: reason undisclosed; salesperson’s price hypothesis retained separately and not counted as a confirmed price reason.

The table’s most important column is effectively not supported. It prevents a defensible observation from expanding into an unsupported commercial story.

4. Test budget, scope and value separately

A stated budget ceiling is most interpretable when the proposed amount and the ceiling refer to the same period and coverage. An annual proposal and a monthly spending reference cannot be compared without resolving that mismatch. If the record does not resolve it, retain the budget statement but mark the comparison as incomplete.

For scope, identify what was actually purchased rather than assuming the buyer compared identical offers. Relevant differences may include the number of teams covered, work included, duration or service responsibilities. Only record differences documented in the available material.

A scope difference does not prove that scope alone caused the loss. It does mean that the evidence cannot support a simple like-for-like price conclusion.

Value requires its own evidence. In a separate hypothetical example, a buyer explains that the expected time savings did not justify the annual spend. That supports a stated value concern. It does not prove the offer objectively lacked value, nor does it establish that the buyer lacked funds.

If a buyer states both a spending ceiling and insufficient expected benefit, preserve both. If neither is identified as decisive, report multiple supported factors with no established primary cause rather than choosing the explanation that best suits an internal narrative.

5. Preserve evidence without turning notes into facts

For each reviewed loss, retain a compact evidence record:

  1. Decision evidence: a faithful paraphrase of what the buyer communicated about the final outcome.
  2. Source and timing: the relevant email, message or conversation note and its date.
  3. Commercial context: the amount, period and known scope needed to interpret the statement.
  4. Classification: the code and a short explanation of why it fits.
  5. Limitations: what the available record cannot establish.

A detailed contemporaneous call note can be useful evidence. Label it as a salesperson-recorded account rather than silently treating it as a buyer-authored statement. A bare dropdown selection provides much less basis for interpretation.

When records conflict, do not resolve the conflict by choosing the preferred explanation. Compare dates, decision relevance and specificity. An early budget concern may coexist with a later statement that the project was cancelled. If the final reason remains uncertain, retain the conflict and code the case accordingly.

One short evidence-based rationale is more useful than a long narrative that mixes observations and assumptions.

6. Recover ambiguous cases without pressuring the buyer

If follow-up is appropriate and the buyer has not declined further discussion, ask one neutral question that distinguishes the unresolved explanations. A hypothetical follow-up could ask whether the decision mainly reflected a spending limit, a smaller requirement, insufficient expected benefit, or another factor.

Offer room for an answer outside those categories. Otherwise, the question can manufacture the certainty the review is supposed to test. Do not turn a post-loss clarification into an attempt to reopen negotiations.

If the buyer declines to explain, stop seeking the explanation. Keep the case as undisclosed. Silence after a clarification request adds no evidence for price.

Common coding failures also need a recovery path:

  • An expensive label became a budget code: recode it as an unclear price concern unless a spending ceiling is documented.
  • A lower total became a like-for-like price loss: inspect known scope differences and remove the equivalence claim if it is unsupported.
  • A seller hypothesis became a buyer reason: move the hypothesis into a separate note and correct the reported classification.
  • A later explanation changes the finding: retain the earlier classification and record why the code changed.

Do not rewrite historical records to make them appear more complete than they were. A transparent correction is more useful than an apparently certain history.

7. Report supported reasons and unknowns together

A report titled price losses should explain what it includes. Does it count only stated budget constraints, every buyer-linked price concern, or every deal with any cost discussion? Those produce different totals.

Separate counts for budget ceilings, different-scope selections, stated value concerns, unclear price concerns and undisclosed reasons. Also show how many reviewed records lack enough evidence for a specific explanation.

Hypothetical reporting example: a review of 20 deals previously labelled price finds five stated budget ceilings, four different-scope selections, three stated value concerns, six unclear price concerns and two undisclosed reasons. The defensible finding is that the original price label combined several types of evidence. It is not that all 20 buyers rejected the same value proposition.

The trade-off is a less tidy dashboard. More cases may remain unresolved, and comparison with old categories may require a note. In return, managers can see which conclusions are grounded and which would require more evidence.

Do not remove unknowns from the denominator without saying so. A percentage based only on explained losses answers a different question from a percentage based on all reviewed losses.

8. Run a small coding check before changing the report

As a recommended pilot, select ten recent losses currently labelled price. Have two reviewers independently assign codes using the filled decision table’s structure. This is a proposed review exercise, not a performance benchmark.

Track three observable measures: how many cases have a traceable evidence reference, how many receive the same code from both reviewers, and how many cannot support the original price explanation.

Discuss disagreements at the evidence level. Was the spending period unclear? Did one reviewer assume equivalent scope? Did a seller inference become a buyer fact? Update the coding guidance to address those specific failure cases, then repeat the check on the next review batch.

The immediate deliverable is a corrected set of loss records with explicit limits—not a pricing recommendation. A useful review leaves the next reader able to distinguish what the buyer said, what the evidence supports, and what nobody yet knows.

Loss analysisSales operationsCRM dataEvidence quality

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