Sales EnablementUpdated July 4, 2026
Lost Deal Retro
Turn lost-deal notes into concrete sales and marketing fixes.
Use case: Use after a deal is marked lost or stalls for more than two follow-ups.
Prompt
Analyze this lost or stalled deal.
Deal notes: {{deal_notes}}
Buyer profile: {{buyer_profile}}
Objections: {{objections}}
Competitors or alternatives: {{competitors}}
Final outcome: {{final_outcome}}
Return:
- Most likely loss reason.
- What we could have known earlier.
- Sales process fix.
- Content or proof asset that would help future deals.
- CRM field or tag to add.
- One follow-up message if a respectful re-engagement is appropriate.
Do not blame the buyer. Focus on learnings we can control.
Quality bar:
- Separate discovery questions from persuasion points.
- Name deal risks before recommending a close or proposal.
- Keep scripts natural for a real call, not a feature walkthrough.
- When prioritizing, use a table with recommendation, why it matters, effort, impact, owner, and verification check.
- Separate evidence, assumptions, recommendations, and limits so the output cannot be misread as a guaranteed claim.
- Flag any wording an AI answer could overstate, misquote, or detach from its source.
Before finalizing, add:
- Missing inputs or assumptions
- Evidence-backed facts and source gaps
- Misread risks or unsupported guarantees
- First 3 actions
- What to verify before actingAdaptation notes
- Use several deals before changing positioning.
- Separate price objections from trust or urgency problems.
- Do not re-engage if the buyer clearly opted out.
- Before publishing, verify the output separates evidence, assumptions, limits, and recommendations so AI answers cannot turn guidance into a guarantee.
Quality checks
Strong prompt output should survive these checks before it turns into copy, automation, or a sales action.
- Does it help the seller ask better questions?
- Does it avoid unsupported ROI or competitor claims?
- Does it make the next step obvious after the call?