Lost Deal Analysis

A consistent loss reason taxonomy, honest seller debriefs, regular interviews with lost buyers and a monthly pattern review that feeds pricing, product and the sales playbook.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Lost Deal Analysis, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

192

Starter tasks

💼 Sales & Revenue

Lost Deal Analysis

Interviewing lost prospects, tagging loss reasons consistently and feeding patterns back into pricing, product and the sales playbook.

  1. Scope and entry rules for full loss reviews
  2. Loss reason taxonomy with written definitions
  3. Required closed-lost fields in the CRM
  4. Twelve-month baseline of closed-lost deals
  5. Win-loss programme owner and charter
  6. Lost-buyer interview guide
  7. Interview request emails and confidentiality wording
  8. Loss evidence log and interview archive
  9. Seller loss debrief form
  10. Close-out rule for deals that go dark
  11. Two-day seller debrief habit
  12. Weekly closed-lost reason quality check
  13. Monthly lost-buyer interview quota
  14. Monthly loss pattern review meeting
  15. Monthly loss share by reason tracker
  16. Quarterly win-loss report
  17. Quarterly loss feedback session with product managers
  18. Pricing loss extract for the pricing owner
  19. Timing-loss revisit list
  20. Quarterly seller versus buyer reason audit
  21. Annual loss taxonomy refresh
  22. Running a non-defensive lost-buyer interview
  23. Laddering questions that get past the first answer
  24. Decoding price as a loss reason
  25. Telling no-decision losses from competitive losses
  26. Coding interview notes into loss themes
  27. Reading small loss samples without overreacting
  28. Finding the moment a deal was really lost
  29. Writing a one-page loss case study
  30. In-house versus third-party win-loss interviews
  31. Adding won-deal interviews for contrast
  32. Fixing the top controllable loss reason
  33. Pricing and packaging proposal from loss evidence
  34. Product gap evidence pack for the roadmap
  35. Playbook edits drawn from loss patterns
  36. Head-to-head analysis of losses to one competitor
  37. First win-loss readout to the leadership team
  38. Post-mortem on a lost strategic deal
  39. Executive feedback call to a lost strategic account
  40. Loss lessons session at the sales kickoff
  41. Annual year-on-year loss review
  42. First loss review as a new sales manager
  43. Personal loss log for an individual seller
  44. Lightweight loss analysis for a small sales team
  45. Interviewing several members of a lost buying committee
  46. Loss watch period after a price change or launch
  47. Analysing lost renewals and expansion deals
  48. Loss driver analysis by segment, deal size and source
  49. Early warning signals mined from lost deal calls
  50. Measuring the revenue effect of loss-driven changes

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Scope and entry rules for full loss reviews

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Reviewing every closed-lost deal sounds thorough but buries a team in deals that were never real.

First tasks

  • Count last quarter's closed-lost deals by the furthest stage each reached
  • Draft the stage and value threshold for a full loss review
  • Estimate the monthly review volume under the draft rule
  • Agree the rule with the sales leader and publish it to the team

Loss reason taxonomy with written definitions

Free-text loss reasons such as 'went another way' or 'budget' cannot be counted, and a dropdown of twenty overlapping options is little better. A short two-level taxonomy, perhaps six to eight primary reasons with a handful of sub-reasons each and a one-sentence definition for every code, is what lets you compare this quarter with the last.

First tasks

  • Export last quarter's free-text loss reasons into one sheet
  • Group them into six to eight primary reasons with draft definitions
  • Ask a second manager to code ten past losses using the draft
  • Rewrite any definition the two of you applied differently
  • Publish version 1.0 of the taxonomy to the sales team

Required closed-lost fields in the CRM

Moving a deal to closed-lost usually takes one click, which is why so many records hold nothing useful. Making a primary reason, a sub-reason, the competitor chosen and a short note required at that moment means every loss leaves evidence behind without anyone chasing it later.

First tasks

  • Write the field list and picklist values from the taxonomy
  • Hand the specification to whoever administers the CRM
  • Close a test deal as lost and time how long the form takes
  • Remove any field that sellers skipped or misread during the test

Make it yours.

Install Lost Deal Analysis, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.