Analyze · Call-Transcript & Objection-Pattern Analysis

Analyze a Lost Deal's Final Call

Diagnose exactly why an agency deal died by re-reading the final conversation with fresh eyes.

foundermanagerIntermediate2-3 hours per loss review
When to use
Run this any time a meaningful deal goes closed-lost. Especially valuable when the CRM reason ('budget' or 'timing') doesn't match your gut. Use the output in win/loss retros or to update qualification criteria.
The prompt
You are a sales analyst trained to perform honest loss reviews on agency deals. You ignore the CRM-stamped loss reason and re-derive it from the transcript.
Agency: [AGENCY_NAME] — [SERVICES]
Deal context: [DEAL_CONTEXT]
Stated CRM loss reason: [CRM_LOSS_REASON]
Final call transcript (and prior call summary if available):
[CALL_TRANSCRIPT]
Reconstruct why the deal actually died. Identify: (1) the moment(s) of true hesitation, (2) unresolved objections, (3) any rep mistakes (over-talking, missed cues, unclear next steps), (4) external factors prospect named, (5) whether the CRM loss reason matches the evidence. Conclude with one clear primary cause and one secondary cause.

- Quote exact lines as evidence — no paraphrase as fact
- Do NOT default to the CRM loss reason — challenge it
- Tag prospect emotion only when explicit
- Separate rep-controllable causes from prospect/market causes
- If evidence is ambiguous, say so — don't force a conclusion
Sections: (1) Pivotal Moments (chronological, quoted), (2) Unresolved Objections, (3) Rep-Controllable Issues, (4) External Factors, (5) CRM Reason vs. Reality, (6) Primary + Secondary Cause, (7) Two things to do differently on the next similar deal.
Variables
  • [AGENCY_NAME] — Your agency name
  • [SERVICES] — What you sell
  • [DEAL_CONTEXT] — Prospect, deal size, length of sales cycle, who was involved
  • [CRM_LOSS_REASON] — What the rep marked the deal as lost for
  • [CALL_TRANSCRIPT] — The final call transcript (closed-lost notification call or last meaningful conversation)
Example input
Agency: PixelHaus — web design + Webflow
Deal: Halcyon Wellness, $25k site + $2,500/mo, 6-week cycle, decision involved CEO + ops lead
CRM loss reason: "budget"
Final call transcript: 35-minute closed-lost call. Key moment — Prospect: "Honestly, your designer never showed us anything similar to a wellness brand — we couldn't picture it. We went with a smaller studio that brought 4 wellness mockups to their second call."
Example output
**Pivotal Moments**
- Line 78: "your designer never showed us anything similar to a wellness brand" (regret + concrete)
- Line 134: "the smaller studio brought 4 wellness mockups to their second call" (vivid comparison)
- Line 201: "the price wasn't crazy, honestly" (directly contradicts CRM reason)

**Unresolved Objections**: vertical/portfolio fit — surfaced in call 2 per prior summary, never directly answered.

**Rep-Controllable**: no vertical case studies sent before proposal; no mockup or visual artifact in deck; didn't probe "have you seen us do wellness?" objection.

**External Factors**: smaller competitor delivered speculative mockups — a tactic outside our standard process.

**CRM Reason vs. Reality**: CRM said "budget". Transcript directly refutes this. Real loss = portfolio/vertical proof gap + competitor's mockup tactic.

**Primary cause**: missing wellness-vertical proof. **Secondary**: lost the visual-imagination battle to a competitor who showed, didn't tell.

**Next time**: (1) require 2 vertical-relevant case studies in the deck for any sub-$50k deal, (2) offer a paid 1-week directional concept sprint when prospect signals "can't picture it".
Pro tips
  • Run on EVERY lost deal above your minimum threshold — this is how you build a real loss-reason library
  • Compare Claude's verdict to the CRM-stamped reason — when they disagree 3+ times, your CRM reasons are decoration
  • Feed the 'next time' notes back into rep coaching and qualification updates
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts