Lost Deal Postmortem
One-page postmortem doc per lost deal, saved to shared folder. CRM deal record updated with categorized loss reason and link to postmortem. Tags routed to product, marketing, or AE manager as relevant. 60-day re-engagement task scheduled where applicable.
Before you start
- Closed-lost deals tagged in CRM with reason field
- Access to call recordings and email threads for the deal
- Sales leadership review cadence to consume the output
- Closed-lost deal record (prospect, ACV, stage at loss, loss reason)
- Full activity history (calls, emails, meeting notes)
- Competitor information if the deal was lost to a competitor
The steps
- Pull all deal artifacts — Gather: every call recording transcript, every email in the thread, the proposal that was sent, deal stage transitions with timestamps, and the final loss reason logged by the AE. Time-order them. Note any gaps (e.g., 14-day silence between stages 3 and 4).
- Identify the inflection point — Find the moment the deal cooled. Usually one of: a specific objection that wasn't resolved, a competitor entering, a champion leaving, a pricing surprise, or a slow procurement step. Anchor the postmortem on that single event — not a vague 'they ghosted'.
- Categorize the loss reason — Map the loss to one of: (a) lost to competitor, (b) lost to internal build, (c) no decision / status quo, (d) budget cut, (e) wrong fit / disqualified late, (f) timing pushed, (g) champion lost. Add subcategory if 'lost to competitor' (which one and why they won).
- Extract verbatim prospect quotes — Pull 3-5 direct quotes from the prospect that capture their reasoning. Use call transcripts whenever possible. Avoid paraphrasing. These quotes are the most valuable artifact for product, marketing, and other AEs.
- Draft postmortem doc — One-page format: Deal summary (company, ACV, sales cycle days), Loss category, Inflection point, Verbatim quotes, What we'd do differently next time (3 bullets), and Pattern flag — does this match other lost deals this quarter? Save in a shared 'Sales Postmortems' folder.
- Tag for product, marketing, and AE feedback — If the loss reason involves a product gap, tag the relevant product manager. If it involves messaging, tag marketing. If it involves AE behavior, share privately with the AE's manager. Each tag includes the specific quote that triggered the routing.
- Schedule a 60-day re-engagement check — For status-quo and timing losses, set a re-engagement task in the CRM for 60 days post-loss. Include the postmortem link so the next outreach can reference what was learned. Do not re-engage immediately — let context shift.
If it goes wrong
AE recorded loss reason as 'price' but transcripts show different concerns
Trust the transcripts over the AE-entered reason. Update the CRM field with the corrected reason and flag for AE manager — pricing is often the easy answer that hides the real issue.
Call recordings missing or not transcribed
Use email threads as primary source. Note 'call recordings unavailable' in the postmortem and require the AE to add notes from memory. Push to fix recording coverage at the org level.
Postmortems pile up but no one reads them
Run a monthly review meeting with sales leadership using the postmortems as the agenda. If the meeting doesn't happen, kill the SOP — postmortems with no consumer are wasted effort.
All OpenLabor playbooks