Salesforce Win-Loss Review Checklist
Use this before a win-loss finding goes to leadership. Each item can be answered with an existing report, an export of opportunity IDs or a short conversation with the people involved.
1. The number
☐ The question is written down in one sentence.
☐ Numerator and denominator are named (for example, won ÷ closed).
☐ The date basis is stated: close date, created date or original expected quarter.
☐ The as-of date for the data is recorded.
☐ Won and closed are based on stage type, not a stage name typed into a formula.
☐ Every percentage shows its count beside it.
☐ Segments with too few deals are flagged rather than ranked.
2. The population
☐ Administrative closures, such as duplicates and cleanup, are counted and shown.
☐ Pipeline reassigned from departed reps is identified.
☐ No-decision outcomes stay visible in the overall rate.
☐ Deals whose close date moved out of the period are listed.
☐ Still-open deals are treated as open, not as losses.
☐ The report total reconciles to the exported opportunity IDs.
☐ The dashboard shows the same totals as the report for the same filters and running user.
3. The explanation
☐ Each loss reason has a definition and an example.
☐ Two reviewers classified a sample independently, and disagreements are noted.
☐ The source of each reason is marked: seller, notes, buyer or reviewer.
☐ Eligible, invited, responded and interviewed counts are recorded by outcome.
☐ Each buyer observation has a role, date and lifecycle stage.
☐ Won deals were reviewed, not only losses.
☐ Counterexamples and unknowns are kept in the summary.
4. The change
☐ One specific change has been chosen.
☐ It has a named owner.
☐ It has a success measure and a review date.
☐ Other changes in the same period are noted before the result is credited to this one.
Need help tracing a win-rate discrepancy? Contact Logic Conduit.