0
Objection-handling script for sales calls from real deal notes
⁂auto-checked, 2 hours oldAauraNovice
The prompt
Build an objection-handling reference for our sales team, using real patterns from actual lost/stalled deal notes, not generic sales training content.
Deal notes (lost or stalled deals, with reasons given if known): deal_notes
Do this:
1. Cluster the objections into actual recurring categories (don't list 20 unique one-off objections, find the 4-5 real patterns underneath them).
2. For each pattern, distinguish: is this a genuine product gap (the objection is basically correct and we should say so honestly), a positioning/timing issue (the prospect isn't wrong but there's a reframe that helps), or a pure misunderstanding (they have inaccurate information we can correct)?
3. For genuine gaps, don't write a script that argues around them, write the honest acknowledgment plus what we'd recommend instead, reps sound worse trying to spin a real gap than admitting it.
4. For reframes and misunderstandings, give a specific response script (not 'address their concern'), including one clarifying question the rep should ask before responding, since objections are often not what they first sound like.
5. Flag the single most common objection pattern by frequency across the notes, that's the one that most needs a company-level fix, not just a better sales script.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 2 hours ago |
Example output
4 patterns identified across 15 deal notes: (1) 'too expensive for our size' appeared in 6 notes, (2) 'not sure it integrates with our stack' in 4, (3) 'need to check with IT/security' in 3, (4) 'timing, revisit next quarter' in 2. Pattern 1 classified as positioning issue, not a genuine gap, since deals in this cluster were mostly mid-market prospects being shown enterprise pricing by default; reframe script provided steering to the correct tier earlier in the call. Pattern 2 classified as a genuine gap for one specific integration (Salesforce) mentioned in 3 of 4 notes, honest response script given: acknowledge directly, offer the workaround that exists, don't oversell a roadmap date we're not sure of. Pattern 3 classified as misunderstanding, most prospects assumed a security review was required when our actual SOC 2 report often satisfies it; clarifying question and correction script given. Most frequent, flagged for company-level attention: pattern 1 (pricing tier mismatch), a sales-script fix won't solve this alone, recommend fixing the default tier shown in demos.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.