Analyze · Win/Loss Analysis
Diagnose Why a Specific Big Deal Was Lost
Run a structured post-mortem on a single high-stakes loss using the CRM trail and any buyer interview notes you have.
foundermanagerrepAdvanced⏱ 2 hours
When to use
Use right after losing a deal worth >2x your average ACV, especially one you expected to win. Best with the full activity log and at least one debrief transcript or summary. Don't run on small deals.
The prompt
You are an analytics-minded sales leader for a digital marketing agency. You run blameless post-mortems on individual deal losses, grounded only in documented activity and buyer-voiced reasons. Agency: [AGENCY_NAME] — [SERVICES] | Deal: [DEAL_DETAILS] (company, service, ACV, deal stage history, key stakeholders, competitor if any) | Activity trail: [ACTIVITY_LOG] (CRM activities in chronological order — emails, meetings, proposals, gaps.) | Buyer feedback: [INTERVIEW_TRANSCRIPT or DEBRIEF_NOTES] Diagnose why this specific deal was lost. Build a timeline of pivotal moments (good and bad), identify the 2-3 root causes ranked by contribution, separate factors we controlled from factors we didn't, and produce 3 specific process changes that would have changed the outcome. - Every root cause must point to a specific moment in the activity trail or a verbatim quote from the buyer. - Distinguish "we controlled" from "out of our hands" — be honest about both. - No rep-bashing — frame as process, qualification, or coverage gaps. - If you don't have evidence for a root cause, say "insufficient evidence" rather than guessing. Output: (1) Deal one-liner. (2) Pivotal moments timeline (5-8 bullets, dated). (3) Root causes ranked by contribution with evidence. (4) Controlled vs uncontrolled split. (5) 3 specific process changes.
Variables
- [AGENCY_NAME] — Your agency name
- [SERVICES] — Service lines
- [DEAL_DETAILS] — Company, service, ACV, stages, stakeholders, competitor
- [ACTIVITY_LOG] — Chronological CRM activity log
- [INTERVIEW_TRANSCRIPT] — Buyer debrief transcript or notes
Example input
Agency: Northstar Digital — Paid Search Deal: BrewHaus, $72k ARR, lost to AdVenture. Stakeholders: Demand Gen Mgr (champion), VP Marketing (econ buyer). 41-day cycle. Activity log: Day 1 inbound demo request. Day 3 discovery with DG Mgr. Day 10 proposal v1 sent. Day 17 VP joins call — first time. Day 24 AdVenture re-engages per buyer. Day 30 proposal v2 with revised reporting mockup. Day 38 buyer asks for attribution detail; reply 4 days later. Day 41 lost. Debrief notes: "We liked your team but AdVenture's reporting walkthrough was sharper, and we'd already paused on you for 4 days waiting on attribution detail."
Example output
Deal one-liner: $72k Paid Search lost to AdVenture after late VP engagement and a slow reply on attribution detail. Pivotal moments: Day 1 inbound. Day 3 single-threaded with DG Mgr. Day 17 VP joins — late. Day 24 competitor re-engages. Day 30 reporting mockup helps. Day 38 attribution question. Day 42 reply (4-day gap). Day 41 lost. Root causes (ranked): 1. Slow response on attribution question — 4-day silence cited verbatim by buyer. (Controlled.) 2. Late multi-threading — VP joined day 17 of 41. (Controlled.) 3. Competitive reporting demo was sharper. (Partially controlled — perception.) Controlled: response speed, multi-threading cadence, reporting demo quality. Uncontrolled: existing AdVenture relationship. Process changes: (1) SLA: <24h response on technical questions in late-stage. (2) Require econ-buyer access by day 7 or stage gate. (3) Build a live attribution walkthrough as standard PS demo asset.
Pro tips
- Run this with the AE present but not driving — they'll catch missing context the log doesn't show.
- Always pair the CRM log with at least a short buyer debrief — log-only post-mortems miss the why.
- Convert the 3 process changes into stage gates in your CRM the same week or they evaporate.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts