⚡ Promptolis Original · Sales & Revenue

🛡️ Sales Objection Handler — The 7-Pattern Library

Translates any sales objection into the underlying real concern — then gives you the exact counter-response that moves the deal forward without sounding rehearsed.

⏱️ 4 min to prep 🤖 ~60 seconds in Claude 🗓️ Updated 2026-04-20

Why this is epic

Most objection-handling training teaches canned responses ('feel-felt-found'). Buyers recognize these in 2 seconds and tune out. This Original produces responses that sound like you, not like a sales script.

Names the 7 universal objection patterns (price, timing, authority, trust, competition, features, pain-unclear) and shows you which REAL concern is hiding behind each — because the stated objection is almost never the real one.

Produces 3 response variants per objection (soft, direct, reframe) so you can pick the right tone for the specific buyer personality — not the generic 'overcome objection' playbook.

The prompt

Promptolis Original · Copy-ready
<role> You are a sales enablement strategist with 15+ years in enterprise B2B sales. You have personally closed deals ranging from $5k to $2M+ and trained 500+ reps on objection handling. You know the psychology behind the stated objection and the real concern underneath. You are direct. You will tell a salesperson when their objection is actually a disqualification signal (the deal is dead, just not said aloud yet). </role> <principles> 1. Stated objection ≠ real objection 70% of the time. Diagnose underneath. 2. 7 universal patterns: price, timing, authority, trust, competition, features, pain-unclear. 3. One clarifying question before responding. Never first-strike with a counter. 4. Name the objection explicitly — it's disarming, not weak. 5. Canned responses lose deals. Authentic responses in your voice win them. 6. 'No' = 'not right now.' 'Not now' = sometimes 'not ever' in disguise. </principles> <input> <objection>{the exact words the buyer said, if possible}</objection> <context>{product, deal size, sales stage, relationship}</context> <buyer-role>{decision-maker, influencer, end-user}</buyer-role> <prior-signals>{what they said earlier that seemed positive or negative}</prior-signals> <your-read>{what do you suspect is the REAL issue}</your-read> <timeline-pressure>{is there a real deadline or artificial urgency}</timeline-pressure> </input> <output-format> # Objection Analysis: [Stated objection] ## The Real Concern Which of the 7 patterns + what's probably actually happening. ## The Clarifying Question (before you respond) The one question to ask first. ## 3 Response Variants - Soft (preserves relationship, slower deal cycle) - Direct (risks some but tests seriousness) - Reframe (shifts the frame entirely) ## Which Variant for This Buyer Specific recommendation based on their profile. ## What NOT To Say 3 common mistakes that kill this specific objection. ## The Disqualification Signal Check Is this actually a dead deal? ## Follow-Up Strategy If they don't close today, when to follow up. ## Key Takeaways 3 bullets. </output-format> <auto-intake> If input incomplete: ask for exact objection, context, buyer role, prior signals, your read, timeline. </auto-intake> Now, handle the objection:
🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
<objection>'Your price is about 40% higher than what we budgeted. We'd love to work with you but at that price it's going to be tough to get approved.'</objection>
<context>B2B SaaS, $80k/year deal, Series B startup as the buyer, deal in final stage (already demo'd + technical eval done).</context>
<buyer-role>VP of Product, has budget authority up to $100k but needs CFO approval above $75k.</buyer-role>
<prior-signals>Great fit on product. Champions on buyer side love us. 2 weeks ago VP said 'this is exactly what we need.'</prior-signals>
<your-read>Feels like the 'CFO approval' is the real issue, not the price itself. He might be afraid to bring it to the CFO.</your-read>
<timeline-pressure>They want to implement by Q3 start (2 months away). Real pressure.</timeline-pressure>
🤖 Output

Objection Analysis: '40% over budget, tough to get approved'

A sales objection handling framework is a structured approach to decoding what buyers actually mean vs. what they say — based on 15+ years of B2B enterprise sales data showing that 70% of stated objections mask a different underlying concern. Your specific objection ('40% over budget, tough to get approved') combined with your read ('CFO approval is the real issue') points to pattern 3: Authority, not Pattern 1 (Price). The VP already loves the product — he's scared of the CFO conversation, not the number.

The Real Concern

Pattern: Authority (not Price). Classic signal: 'love to work with you BUT [external authority] might not approve.' When a buyer uses 'we' language about their own approval process, they're outsourcing the 'no' to someone they haven't even asked yet.

What's probably happening:

  • VP likes the product, wants it
  • VP hasn't actually talked to CFO yet
  • VP is imagining a painful CFO conversation and pre-emptively negotiating down
  • The '40% over' number might even be inflated — he's creating wiggle room

Real ask: he needs either (a) enough ammunition to sell it to CFO, or (b) a concession that makes the CFO conversation easier.

The Clarifying Question

Before you respond to the price itself, ask:

> 'Got it — let me make sure I understand the approval process. Have you already talked to your CFO about this, or are you anticipating that conversation?'

Why this works: 90% of the time, answer is 'no, I haven't talked to them yet.' That changes the entire negotiation — he's negotiating against an imaginary CFO, not a real one.

3 Response Variants

Soft (preserves relationship, longer cycle)

> 'Totally understand. I want to help you get this approved without overextending your budget. What if I put together a 1-page business case you can take to your CFO — ROI projection, implementation timeline, how it addresses the specific problem we talked about? That way when the conversation happens, you're not alone in the room making the case.'

Why: gives VP a gift (ammunition), doesn't concede on price, buys a 7-day timeline, demonstrates partnership.

Direct (tests the seriousness)

> 'I hear you on the budget. Here's what I'm weighing: if your CFO says no to $80k for a product that demonstrably solves [problem they have], something else is wrong — maybe they don't see the problem the same way you do. Before I discount, let's make sure we're aligned on the actual problem we're solving. Can you walk me through how the CFO understands the issue?'

Why: reveals whether VP has actually positioned this as important to CFO. Often shows VP hasn't done the work internally — which is fixable.

Reframe (shifts the frame)

> 'Let me ask a different question: if I told you I could make this $50k — but with half the features you demo'd — would that be better or worse for you internally? I ask because we built this specifically to solve [problem X], and removing features would hurt what you're trying to do. I'd rather figure out payment terms or phasing than cut value.'

Why: implicitly teaches that a 40% cut means a feature cut. Opens door to phased payment, contract terms, or year-1 discount in exchange for longer commitment.

Which Variant for This Buyer

Use the Soft variant. Your read is he's afraid of the CFO conversation. The 1-page business case is exactly what he needs. This protects relationship + doesn't discount + advances deal.

The Direct variant is risky because his champions already love you — no need to test. The Reframe variant opens discount conversations you don't need yet.

Specific next-message draft:

> 'Totally understand where you are. Before I think about discount — have you had the CFO conversation yet, or is that still ahead? I want to help you get this approved. If it's helpful, I can put together a 1-page business case with ROI, timeline, and the problem framing — so you have the facts in front of you for that meeting. Would that help?'

What NOT To Say

1. 'Let me see what I can do on price.' — You just told them discount is available. 40% ask becomes the new floor.

2. 'What would it take to get this done?' — Invites them to dictate terms. They'll say 50% off and you'll negotiate against their number instead of the real concern.

3. 'I can't go below $X but...' — Defensive. Price-anchoring battle. Avoid entirely until you've addressed the real concern.

The Disqualification Signal Check

Real deal (keep engaging): VP genuinely champions internally, clear business case exists, CFO approval process is defined.

Your situation shows all 3. This is a real deal, NOT dead.

Signals it WOULD be dead: VP stops responding for 5+ days, 'we're reconsidering direction,' champion leaves role, budget decision made without you in the loop.

Follow-Up Strategy

If he doesn't close in the next 2 weeks:

  • Day 3: Send the 1-page business case (after you build it).
  • Day 7: 'Hey, have you had a chance to share the business case with the CFO? Happy to jump on a call with both of you if helpful — sometimes easier than emails.'
  • Day 14: If still no, that's the real signal. 'I want to respect your process — what's the honest read? Is this still moving forward, or should we pause?'

Offering to join the CFO call at Day 7 is often the closer move. VPs are usually relieved to not carry the pitch alone.

Key Takeaways

  • This is an Authority objection, not Price. VP is scared of the CFO conversation, not of $80k.
  • Soft variant is right for this buyer. Build the 1-page business case; don't discount yet.
  • Offer to join the CFO call on Day 7. That's often the move that closes these.

Common use cases

  • B2B SaaS sales reps handling price pushback
  • Founders closing enterprise deals themselves
  • Consultants negotiating project pricing
  • Agency owners fielding 'we're going with another firm' objections
  • Solopreneurs pitching high-ticket services ($5k+)
  • Account managers renewing contracts with hesitant stakeholders
  • Reps preparing for a specific upcoming objection-heavy call

Best AI model for this

Claude Sonnet 4.5 or Opus 4. Sales psychology requires nuanced multi-dimensional reasoning. Mid-tier and above.

Pro tips

  • The stated objection is 70% of the time NOT the real objection. 'Too expensive' usually means 'I don't see enough value' or 'I'm not the decision-maker.' Dig.
  • Before responding to an objection, ask ONE clarifying question. Buys you time + often buyer answers their own objection.
  • Don't over-rehearse responses. If you sound practiced, you sound slick. Natural pauses are fine.
  • Name the objection explicitly: 'It sounds like price is the main concern — is that right?' This is disarming, not weak.
  • If the objection is 'we're going with another vendor,' that's the most actionable one. Ask WHY — often reveals a real gap you can address.
  • Never apologize for your price. Price is a reflection of value. If you apologize, you signal doubt.

Customization tips

  • Before every deal call, map the 7 objection patterns against what you know — which is likely to come up? Prep 1-2 variants for each.
  • Record your calls (with permission). After losing a deal, revisit the objection moments. Pattern-match what you missed.
  • Build a personal library of objections + responses that worked for YOU. Generic scripts are thin; your voice library is gold.
  • If you lose 3 deals to the same objection type, it's not the objection — it's your positioning. Fix upstream (messaging, ICP, discovery).
  • Teach your own team using this framework. Running this Original for each deal-in-progress for 30 days improves team close rate measurably.

Variants

Enterprise Deal Mode

For $50k+ deals with multiple stakeholders. Handles multi-party objection patterns.

SMB Pricing Mode

For smaller deals where price is the dominant objection. Scripted value-reframing.

Competitive Deal Mode

When buyer is comparing you to specific named competitor. Displacement strategies.

Frequently asked questions

How do I use the Sales Objection Handler — The 7-Pattern Library prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Sales Objection Handler — The 7-Pattern Library?

Claude Sonnet 4.5 or Opus 4. Sales psychology requires nuanced multi-dimensional reasoning. Mid-tier and above.

Can I customize the Sales Objection Handler — The 7-Pattern Library prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: The stated objection is 70% of the time NOT the real objection. 'Too expensive' usually means 'I don't see enough value' or 'I'm not the decision-maker.' Dig.; Before responding to an objection, ask ONE clarifying question. Buys you time + often buyer answers their own objection.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals
P

Curated by

Every Promptolis Original is hand-crafted and reviewed before publishing — built from scratch for 2026-grade LLMs.

Last reviewed on · About Promptolis