Jump to a section
A quarterly report lists price as the reason for most losses. Reading the notes reveals three different stories. Some buyers chose a cheaper competitor, some lost funding and others could not meet an implementation deadline. Each points to a different operating decision.
Capture the buyer's explanation
At close, record the outcome, the competing option if known and a short account of what the buyer said. Include the decision date and distinguish a confirmed reason from the seller's inference. Give no-decision outcomes their own grouping so postponed purchases do not distort comparisons with competitive losses.
Review a comparable cohort
Compare deals for a similar segment, order size and buying process. Read a sample of notes before proposing a price change. Assign one action, such as testing earlier implementation planning, and track whether the same reason recurs. This makes the review a source of commercial learning.
The decision recorded at the end of the proposal workflow in Proposal360 provides a starting point for the loss review.
More to discover in Numerish.
Explore related insights and practical enterprise workflows.



