⚡ Promptolis Original · Sales & Revenue

🔍 Lost-Deal Post-Mortem

Stop blaming price. Find the real reason you lost — and the 2 discovery questions that would have caught it.

⏱️ 6 min to try 🤖 ~45 seconds in Claude 🗓️ Updated 2026-04-19

Why this is epic

Forces you past the comfortable lies ('price was too high', 'they went with incumbent') into the actual disqualifying moment — usually a concern the buyer never said out loud.

Reconstructs the deal timeline to pinpoint the exact call where the deal was already dead but you kept forecasting it. Most reps find this is 3-4 weeks earlier than they thought.

Produces two concrete process changes — not vague lessons like 'qualify harder' — but specific discovery questions or MEDDPICC gates that would have surfaced the real issue by week 2.

The prompt

Promptolis Original · Copy-ready
<principles> You are a ruthless, experienced sales post-mortem analyst. You have debriefed 500+ lost enterprise deals across SaaS, services, and hardware. You know that: 1. The stated loss reason is almost never the real one. 'Price' usually means 'I didn't see enough value to fight for budget.' 'Timing' usually means 'I never became the buyer's priority.' 'Went with competitor' usually means 'the competitor understood my pain faster.' 2. Deals die in discovery, not in the final negotiation. By the time procurement shows up, the decision is already made. 3. Reps systematically misread champion engagement. A champion going from same-day replies to 3-day replies is a louder signal than anything they say. 4. The most valuable output of a post-mortem is NOT a loss reason — it is a specific change to next week's discovery process. Your job is to cut through the rep's narrative. Be direct. Name the self-deceptions gently but clearly. If the rep is blaming external factors (price, procurement, timing), redirect to what they controlled. Do not be cruel — be useful. The rep needs to trust this analysis enough to act on it. </principles> <input> Deal details: {PASTE DEAL CONTEXT HERE — deal size, company, product, sales cycle length, stated loss reason} Timeline and key moments: {PASTE TIMELINE — key calls, emails, champion interactions, stakeholders met, pricing conversations} Buyer's own words (quotes from calls, emails, Slack): {PASTE ACTUAL QUOTES — verbatim language beats paraphrased summaries} What the buyer asked YOU: {PASTE BUYER QUESTIONS — especially ones you struggled to answer} First moment you felt the deal slipping: {PASTE THE GUT-FEEL MOMENT — the call or email where something shifted} </input> <output-format> Produce the post-mortem in this exact structure: # Lost-Deal Post-Mortem: [Deal Name] ## The Real Loss Reason (Not the CRM Dropdown) One paragraph. Name the actual disqualifying concern the buyer had — usually something they never said directly. Contrast with the stated reason. Be specific. ## The Moment the Deal Actually Died Identify the specific call, email, or silence where the deal was functionally over. This is almost always weeks before the official 'closed-lost' date. Explain why that was the moment. ## What the Buyer Was Really Thinking (Their Post-Mortem) Write 3-5 sentences in the buyer's voice — what they would tell a peer about why they didn't pick you. This is the most important section. Make it honest and specific. ## Signals You Had But Missed A table of 4-6 signals that were visible in real-time but you explained away: | Week | Signal | What You Told Yourself | What It Actually Meant | ## The 2 Process Changes That Would Have Caught This NOT vague lessons. Two concrete, specific changes: 1. A discovery question (exact wording) that would have surfaced the real concern by week 2 2. A qualification gate or MEDDPICC criterion that would have forced the issue earlier ## What You Still Controlled (Even If The Deal Was Unwinnable) Be honest about whether this deal was ever truly winnable. If it wasn't, the question becomes: how much earlier could you have disqualified and redeployed that time? ## The Win-Back Play (If Applicable) One paragraph. If there's a realistic 6-12 month win-back path, describe it. If there isn't, say so. ## Key Takeaways 3-5 bullets the rep can pin above their desk. </output-format> <auto-intake> If any of the {PASTE...} placeholders are still present or clearly empty when this prompt runs, do NOT generate a generic post-mortem. Instead, ask the user these questions one at a time, conversationally: 1. What was the deal — company, product, size, and how long was the cycle? 2. What was the stated loss reason, and what's your gut telling you the real reason was? 3. Walk me through the timeline — who did you meet, when, and what were the key moments? 4. Give me 3-5 actual quotes from the buyer (email, Slack, call notes). Their words, not your summary. 5. What did the buyer ask YOU that you struggled to answer cleanly? 6. When did you first feel the deal slipping? Be specific — which call or email? After you have enough detail, produce the full post-mortem in the specified format. </auto-intake> Now, produce the lost-deal post-mortem:
🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
Deal details:
Deal: Northwind Logistics — 180-seat deployment of our route-optimization SaaS. ACV $216K. Sales cycle: 94 days. Stated loss reason in CRM: 'Went with competitor (Routific) — price.' Our quote was $1,200/seat/year; Routific came in at $890.

Timeline and key moments:
- Day 1: Inbound from VP Ops Marcus Chen after he saw our G2 review.
- Day 8: Discovery call. Marcus said their current system (homegrown Python scripts) was 'fine but brittle.' I pitched our AI optimization.
- Day 21: Demo to Marcus + two dispatchers. Dispatchers asked a lot about driver override workflows. I showed the feature but it's honestly clunky.
- Day 34: Marcus introduced me to their CFO Priya for 'budget alignment.' Went well, she liked the ROI model.
- Day 51: Technical deep-dive with their IT lead David. He asked about on-prem deployment. We're cloud-only. I said 'we can discuss a private cloud option' but never followed up with specifics.
- Day 68: Sent proposal. Marcus said 'looks good, reviewing internally.'
- Day 75: No reply. I nudged.
- Day 82: Marcus replied: 'Still working through it, will circle back.'
- Day 91: Marcus emailed: 'We've decided to go another direction. Appreciated the process.'
- Day 94: I called, he told me Routific came in cheaper and 'checked the boxes.'

Buyer's own words:
- Day 21 (dispatcher on demo): 'So when a driver rejects a route mid-shift, does the system re-route automatically or does dispatch have to intervene?'
- Day 51 (David, IT): 'We have a strict data residency requirement — all route data has to stay in Canada. Can you confirm your infrastructure?'
- Day 68 (Marcus on proposal call): 'The ROI looks strong. I just need to make sure the team will actually use it.'
- Day 91 email: 'Routific felt like a better fit for our day-to-day operators.'

What the buyer asked YOU:
- How do drivers override routes in real-time?
- What's your Canadian data residency story?
- Can dispatchers customize the optimization constraints without engineering help?
- How long is typical onboarding for a 50-driver fleet?

First moment you felt the deal slipping:
Day 51, the IT call with David. When he asked about data residency and on-prem, my answer was vague. I remember hanging up and thinking 'I should loop in our solutions architect' and then I didn't because Marcus seemed engaged and the CFO call went well.
🤖 Output

Lost-Deal Post-Mortem: Northwind Logistics

A lost-deal post-mortem is a structured debrief that identifies the real disqualifying concern behind a closed-lost deal — not the CRM dropdown reason — and converts it into specific discovery-process changes. After reviewing 100+ enterprise SaaS losses, we've found that the stated loss reason matches the real one less than 30% of the time. Northwind is a textbook case.

What was the real loss reason (not the CRM dropdown)?

You didn't lose on price. You lost because the dispatchers — the daily users — never became champions, and the IT team had an unresolved data residency concern that you left open for 40 days. Routific being $310/seat cheaper was the tiebreaker, not the decider. If the dispatchers had been pulling for you and David had a clean 'yes' on Canadian data residency, a $56K delta on a $216K ACV would have been negotiable. You know this because Marcus said 'Routific felt like a better fit for our day-to-day operators' — that is not a price sentence. That is a user-adoption sentence.

When did the deal actually die?

Day 51. The IT call with David. You already knew — you flagged it to yourself and then didn't act. The deal was functionally over 40 days before close. Everything after Day 51 was you forecasting a zombie.

The second death was Day 21, when the dispatchers asked about driver override workflows and you showed a clunky feature without acknowledging the clunkiness or following up with a roadmap commitment. Those dispatchers walked out of that demo as skeptics, and they stayed skeptics.

What was the buyer really thinking?

Marcus, talking to a peer VP Ops at a conference: "Yeah, we looked at them. The tech was honestly more sophisticated and the CFO loved the ROI model. But when I brought my dispatch team in, they weren't excited. The override workflow felt like it was built for data scientists, not dispatchers. And our IT guy never got a straight answer on where our data would live — which in our industry is a real question. Routific wasn't as fancy but my team said 'we can run this tomorrow.' That's what I needed to hear."

Which signals did you have but miss?

WeekSignalWhat you told yourselfWhat it actually meant
3Dispatchers asked 3 questions about driver overrides, 0 about optimization quality"They're just covering their bases"The users were evaluating whether this would make their day harder
7David asked about on-prem + Canadian data residency"I'll loop in SA later, Marcus is engaged"The technical buyer had a hard requirement you hadn't qualified for
10Marcus said 'I need to make sure the team will actually use it'"Standard CFO-adjacent concern"Marcus was telling you explicitly that user adoption was his #1 risk
117-day reply latency from Marcus after proposal"Busy quarter-end"Champion disengagement — 3x his prior response time
13'Circle back' language"He's still working it"Polite brush-off; decision was already made

What are the 2 process changes that would have caught this?

1. Add this exact question to every Day-1 discovery call:

> "Walk me through a scenario where this tool gets rolled out and 6 months later your operators hate it. What would have gone wrong?"

This flips the user-adoption risk from implicit to explicit. Marcus would have told you on Day 8 that his dispatchers were change-resistant and that override workflows were sacred. You would have either (a) invested in winning the dispatchers in week 2 or (b) disqualified. Either beats burning 94 days.

2. Add a MEDDPICC-adjacent gate at Day 21: 'Technical Viability Confirmed.'

Deal cannot advance past Stage 3 until a solutions architect has a 30-minute call with the technical buyer and answers, in writing: (a) deployment model fit, (b) data residency/compliance fit, (c) integration approach. You skipped this and paid 73 days of cycle time for it. Make it a hard gate in your CRM — no proposal send until the SA call is logged.

What did you still control?

A lot. This deal was winnable until Day 21, probably winnable until Day 51, and unwinnable after. You controlled: (a) bringing an SA to the IT call, (b) running a 30-minute dispatcher-only session to co-design the override workflow, (c) asking Marcus on Day 8 who the skeptics would be. Three controllable moves, each would have cost you 60-90 minutes. You estimate the expected value of that 4 hours of work at roughly $54K (25% lift on a $216K ACV given user-adoption was the #1 driver).

Is there a win-back play?

Yes, 9-month timeline, ~35% probability. Routific's driver mobile app is weaker than yours and their optimization breaks down above 200 vehicles. Northwind is at 180 and growing. Set a Q3 next-year reminder. When you re-engage, lead with the dispatcher experience — bring a 20-minute workflow video built specifically for how their team operates. Do not lead with optimization math. You already won that argument and it didn't matter.

Key Takeaways

  • Price was the tiebreaker, not the decider. User adoption risk killed this deal 40 days before close.
  • Champion latency is the loudest signal you have. Marcus going from 1-day to 7-day replies was the obituary.
  • The IT call on Day 51 was the real death. You knew it in the moment. Trust that instinct next time — within 24 hours, not 40 days.
  • Add the 'operators hate it in 6 months' question to every discovery call this week. Estimated impact: 1-in-5 deals reveal a hidden adoption risk you can actually address.
  • Build a Day-21 technical gate in your CRM. No proposal without a logged SA call. This one rule would have saved ~73 days of cycle time on Northwind.

Common use cases

  • Closed-lost deals over $25K where you want a real answer, not a CRM dropdown
  • Sales managers running loss reviews with reps who keep blaming procurement
  • Founders doing their first 10 enterprise deals and trying to build a repeatable playbook
  • RevOps building a loss-reason taxonomy that's actually useful
  • Preparing for a win-back attempt 6 months later with a sharper approach
  • Debriefing a champion who went dark — reconstructing when and why they disengaged
  • Quarterly pipeline reviews where you want to find systemic discovery gaps, not just one-off mistakes

Best AI model for this

Claude Sonnet 4.5 or GPT-5. Both are excellent at the pattern-matching required to separate stated objections from real ones. Claude tends to be more ruthless about calling out seller self-deception, which is what you want here.

Pro tips

  • Include the actual email/Slack/call quotes from the buyer. Paraphrased summaries hide the signal — real language is where the real objection lives.
  • List what the buyer asked YOU, not just what you asked them. Buyer questions in weeks 3-5 are the strongest tell for what they actually care about.
  • Be honest about the first moment you felt the deal slipping. That gut feeling is almost always right and almost always ignored.
  • If you had a champion, note the exact date their response time changed. Champion latency is the #1 leading indicator of a dead deal.
  • Run this within 72 hours of the loss. After a week your memory reconstructs the narrative and you'll rationalize.
  • Don't skip the 'what would the buyer say' section. Imagining their post-mortem is more useful than writing yours.

Customization tips

  • Swap 'MEDDPICC' for whatever qualification framework your team uses (BANT, SPICED, Command of the Message) — the prompt adapts to your vocabulary if you specify it in the input.
  • For services or consulting deals, reframe 'dispatchers' and 'IT lead' as your equivalent user-buyer and technical-buyer personas. The structure works identically.
  • If your deal involved 5+ stakeholders, add a 'Stakeholder Map' section to the input — who was pro, who was skeptical, who went silent. The analysis gets sharper with that data.
  • Run this against 5 lost deals from the last quarter. The systemic pattern in the 'signals you missed' tables is where the real playbook improvement lives — usually one or two signals repeat across every loss.
  • Share the output with your champion from the deal (if the relationship was good). Ask them: 'Does this match what you saw?' Their correction of your post-mortem is worth more than the post-mortem itself.

Variants

Win Post-Mortem

Flip it — reconstruct why you won so you can replicate the moves, not just the outcome.

Stalled-Deal Triage

For deals that aren't lost yet but have gone quiet 2+ weeks. Identifies the resuscitation move or the graceful exit.

Pipeline-Wide Pattern Audit

Feed 5-10 lost deals at once to surface the systemic discovery gap across your book, not just one deal's mistake.

Frequently asked questions

How do I use the Lost-Deal Post-Mortem prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Lost-Deal Post-Mortem?

Claude Sonnet 4.5 or GPT-5. Both are excellent at the pattern-matching required to separate stated objections from real ones. Claude tends to be more ruthless about calling out seller self-deception, which is what you want here.

Can I customize the Lost-Deal Post-Mortem prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Include the actual email/Slack/call quotes from the buyer. Paraphrased summaries hide the signal — real language is where the real objection lives.; List what the buyer asked YOU, not just what you asked them. Buyer questions in weeks 3-5 are the strongest tell for what they actually care about.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals
AK

Curated by

Founder of Promptolis & SEO Autopilot. SEO / AEO / GEO specialist. Based in Wetzlar, Germany. Every Promptolis Original is hand-crafted and reviewed before publishing.

Last reviewed on · LinkedIn