Home › Prompts › Any chat AI › Objection-handling playbook from lost deals

Objection-handling playbook from lost deals

Build a practical objection playbook from your real call notes and lost-deal reasons, with honest responses, proof points and discovery questions.

Any chat AISalesRuleStack original

Works with: ChatGPT · Claude · Gemini · Grok · Microsoft Copilot · Perplexity · Meta AI · DeepSeek · Mistral Le Chat

Written for Any frontier chat model (GPT-6, Claude 5.5, Gemini 4 Argon, Grok 4.7) · Updated 2026-10-18

Note: Review and test before use. Provided as is, without warranty. See Terms.

Here are notes from [N] sales calls and lost-deal reasons for [product], sold to [buyer role] at [company type]:
<notes>
[paste notes]
</notes>

Build an objection-handling playbook:
1. List the top [8] objections by frequency, quoting one real example each.
2. For each: what the buyer is really worried about, two questions to ask before answering, a short honest response (under 60 words), and the proof point to share ([case studies, data, demos] from the list below only).
3. Mark objections where we should walk away or refer elsewhere because we're not a fit.
4. Add a one-page cheat sheet version for reps.

Approved proof points: [list]. Do not invent customers, numbers or features.

Replace everything in [square brackets] with your own details.

Settings & parameters

• Any capable chat model; long-context models handle full call transcripts

Variations

• Role-play: "Play a skeptical [buyer role] using these objections; score my answers."
• Email follow-up templates for the three most common objections.

Tips

• Remove customer names and personal data from call notes before pasting unless approved.
• Revisit the playbook monthly with new call notes; objections shift with the market.