Sales Objection Handling Scripts for Every Common Pushback

The deal was dead on the call. The prospect said "your price is too high," my rep said "well, let me see what discount I can get approved," and I watched a 40,000 dollar deal turn into a 28,000 dollar deal in nine seconds. The objection was not even real. It was a reflex. And we paid 12,000 dollars to confirm it.

That is the core problem with objection handling: most reps treat every objection as a fact to be solved instead of a feeling to be understood. The script below fixes that. None of these responses are clever. They are calm, they buy you information, and they keep you from negotiating against yourself.

The one move underneath every script

Before any specific response, you do the same thing: you slow down and you ask before you answer. The instinct is to rebut. The skill is to understand.

An objection is not a no. It is a request for more information delivered as a complaint. Answer the complaint and you lose. Answer the request and you win.

Research from Gong on closing calls shows that top performers respond to pricing pushback with a question far more often than with a justification. They are not defending. They are diagnosing. HBR has made a similar point for years about negotiation: the side that asks the next question controls the conversation.

The four families of objection

Almost every objection you will ever hear falls into one of four buckets. Recognize the bucket and you are halfway to the response.

Now the scripts. Read them out loud. They are written to be spoken, not admired.

The word-for-word scripts

=== PRICE ===

THEY SAY: "It's too expensive."
YOU SAY:  "Totally fair to raise that. Just so I understand,
          is it too expensive versus your budget, versus a
          competitor, or versus the value you're seeing so
          far? Those are three different conversations."
[Then shut up. Their answer tells you the real objection.]

THEY SAY: "Can you do better on price?"
YOU SAY:  "I can have that conversation. Before I do, if price
          weren't an issue, is this the solution you'd move
          forward with today? I want to make sure we're solving
          the right thing before we talk numbers."

THEY SAY: "Competitor X is cheaper."
YOU SAY:  "They are, and I won't pretend otherwise. The teams
          who choose us over them usually do it because of
          {specific outcome}. Is that outcome worth the gap to
          you, or is this purely a budget call right now?"

=== TIMING ===

THEY SAY: "Let's revisit next quarter."
YOU SAY:  "Happy to. So I plan it right, what changes next
          quarter that makes this easier? If the answer is
          'nothing specific,' it might be worth figuring out
          the real blocker now rather than rediscovering it
          in 90 days."

THEY SAY: "We're too busy to implement right now."
YOU SAY:  "That's exactly why most teams put it off, and exactly
          why the cost keeps compounding. What if I showed you
          the lightest possible version to start, the one that
          takes your team under an hour a week?"

=== AUTHORITY ===

THEY SAY: "I need to run this by my boss / team."
YOU SAY:  "Makes sense, this shouldn't be a solo decision. What
          questions will they ask that I haven't answered for
          you yet? Let's make sure you walk in fully loaded so
          it's not your credibility on the line."

THEY SAY: "Send me something I can forward."
YOU SAY:  "Will do. One thing first, what's the single number
          or outcome that would make this a clear yes for them?
          I'll build the one-pager around that instead of a
          generic overview."

=== TRUST / STATUS QUO ===

THEY SAY: "We already use X / we're fine for now."
YOU SAY:  "Good, sounds like you're not in crisis, which is the
          best time to look. Out of curiosity, if X is working,
          what's the one thing you wish it did that it doesn't?"

THEY SAY: "I've never heard of you."
YOU SAY:  "Fair, we're not the loudest name in the space. The
          teams who do know us tend to be {their peers}. Would
          it help to talk to one of them before you decide
          anything?"

THEY SAY: "Just send me information." [the brush-off]
YOU SAY:  "I can, but generic info usually gets ignored, and I'd
          rather not waste your inbox. Give me one sentence on
          what you're trying to fix and I'll send only the part
          that matters. Deal?"

How to deliver these without sounding like a robot

The words are half of it. The delivery is the rest.

• Acknowledge first, always. "Totally fair." "Makes sense." You are not agreeing with the objection, you are agreeing they have the right to raise it. This drops their guard.
• Ask, then stop talking. The silence after your question is where the truth lives. Reps who fear silence answer their own questions and lose the information.
• Never discount on the first ask. The fastest way to teach a buyer to push is to fold when they do. If price comes up, isolate it before you ever touch the number.
• Label the emotion when it is obvious. "Sounds like this got burned before." Naming the fear deflates it. This is the same muscle you use in a discovery call, where the whole job is to surface what is unsaid.

Discounting is not objection handling. It is objection avoidance with a price tag. Handle the objection and you often keep the price.

Where objections actually come from

Most objections are not created on the closing call. They are created earlier, by weak discovery. If you never established the cost of the problem, "too expensive" is inevitable, because expensive is always relative to a value you forgot to build. The r/sales regulars repeat this constantly: a deal that dies on price usually died in discovery and just took a few weeks to fall over.

So the best objection handling is upstream. Nail your discovery questions, confirm the cost of inaction, and half these objections never surface. The other half, you have a script for.

Practice this before you need it

Read these out loud until they are reflexes, not recitations. Roleplay the price one with a colleague who is trying to rattle you. The goal is that when a real buyer says "too expensive," your mouth opens and the question comes out before your fear does.

Then build a full motion around it: pair these scripts with our cold call scripts and the rest of the template library, and use the sales toolkit to map which objections are killing the most pipeline so you know which script to drill first.

Which objection trips you up the most? Bring your worst one to the community and we will rebuild the response together.