Practical guide

Use lost reasons to learn, not blame

Last materially reviewed 2026-09-20

Quick answerSeparate an observed reason from a convenient assumption and review patterns only after checking record quality.
What to know

Keep observed reasons separate from assumptions

A buyer may explicitly choose another approach, postpone the project or decide the product is unsuitable. In other cases the team simply loses contact. Those outcomes should not be collapsed into a confident reason such as price. Record what is known and preserve uncertainty where necessary. Capsule’s opportunity outcomes provide a place to organize the decision, but the quality of the explanation depends on evidence rather than a mandatory dropdown selected just to close the record.

What to know

Use a small meaningful vocabulary

Choose reasons that lead to different improvements. “No current need,” “required capability absent” and “timing deferred” may imply different actions. Avoid a long taxonomy that colleagues cannot distinguish consistently. Include an unknown category rather than forcing every case into a story. Keep a short narrative when it explains an important exception. The categories should help the team learn, not create a performance ranking from information that was never reliable enough for that purpose.

What to know

Review patterns cautiously

A handful of losses may suggest questions, but it does not establish a general market truth. Check sample size, how the reasons were obtained and whether the cases are comparable. If price appears often, ask whether it was stated by the buyer or inferred internally. If a capability gap recurs, compare it with qualification and product-fit guidance. Do not revise the whole offer based on a small collection of convenient explanations that conceal different underlying situations.

What to know

Connect learning to one change

Choose a bounded improvement, such as clarifying an early requirement or changing the stage evidence. Record the hypothesis and review later outcomes without claiming causation prematurely. Keep lost records available according to the organization’s policies; deleting them to improve a conversion report defeats the purpose. Continue to the pipeline review and thirty-day CRM review so the information informs practical decisions rather than becoming another chart that no one knows how to act on.

Continue when useful

Next: Run a pipeline review that changes next actions

End with a small number of accountable decisions, not a tour through every deal.

Open Run a pipeline review that changes next actions →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Capsule opportunity stages — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20