Every stalled B2B deal has an objection behind it, whether or not anyone said it out loud. The buyer who goes quiet after a strong demo. The champion who suddenly cannot get budget approved. The procurement contact who keeps asking for one more reference call. These are objections in disguise, and most teams handle them by improvising. A few gifted reps do it well and everyone else fumbles, which means your forecast depends on who happens to be on the call.
This guide covers objection handling the way a revenue team needs it: what it is, the four types of objections you will actually hear, a four step objection handling framework (plus LAER), scripts for the five most common objections, and how to capture all of it inside Salesforce so the knowledge stops living in your best rep's head.
What Is Objection Handling in B2B Sales?
Objection handling is the process of responding to a prospect's concerns or pushback during a sales cycle in a way that addresses the real issue and moves the deal forward. It is not winning an argument. It is finding the reason behind the stated concern, answering it honestly, and helping the buyer decide with confidence.
If you searched for "what is objection handling," that is the short answer. The longer one is that an objection is engagement, not rejection. A buyer who challenges your security model is telling you security is the gate they must clear before buying. The buyer who says nothing and disappears has already decided, and you never got to respond.
Why the Stated Objection Is Rarely the Real One
Many objections are smokescreens: a cover story standing in for the thing actually bothering the buyer. "It's too expensive" might mean the budget is not approved, the ROI is unclear, or a competitor quoted lower. A useful move is to ask, "If we solved that completely, what else would we need to work through before moving forward?" Gong's write-up on smokescreen objections and the other types reps run into uses this same idea, and it works because it forces the buyer to put the remaining concerns on the table.
Why Objections Get Harder in B2B
In B2B you are rarely persuading one person. A buying committee brings several stakeholders, and each carries a different worry. Finance worries about cost, IT about integration risk, the end user about disruption to daily work. Handling one objection well does nothing if you ignore the others. The objections that kill deals are often the ones you never hear, raised by a skeptic in a meeting you were not invited to.
That is why most "no decision" outcomes are really objection problems. Nobody convinced the buyer that the change was worth the risk, and nobody asked what was holding them back. If you want to know who those silent stakeholders are, start with a stakeholder map before the next call, not after the deal slips.
The Four Types of Sales Objections
Nearly every B2B objection falls into one of four buckets. Spotting the bucket quickly tells you which response to reach for, instead of guessing.
Price and Budget
"It costs too much." "We have no budget this quarter." These are the most common and the most misread. Price objections are rarely about the absolute number. They are about perceived value relative to cost, or about budget timing. The answer is almost never a discount. It is quantified ROI and the cost of doing nothing.
Need and Priority
"We're fine with spreadsheets." "This isn't a priority right now." These challenge whether the problem is worth solving at all, and they usually point back to shallow discovery. The buyer does not feel the pain sharply enough to act. Quantify the status quo: hours lost, deals slipping, data scattered across tools.
Trust and Risk
"We've never heard of you." "How do I know this works for a company our size?" In enterprise deals the buyer carries reputational risk if the vendor fails. References, case studies, security documentation, and a scoped pilot are the tools that answer this one.
Timing and Authority
"Let's revisit next quarter." "I need to run this by my boss." These are the hardest to read because they can be genuine or a polite brush off. Either there is a competing initiative, or there is a decision maker you have not met. If it is the second, work out who the economic buyer is before you invest more time.
The Objection Handling Framework: Four Steps and LAER
Methods from Sandler to Challenger to MEDDIC style selling can be boiled down to one repeatable sequence. The power is in running it in order, every time, until it is automatic. This is the objection handling framework we recommend teaching.
Step 1: Acknowledge
Validate the concern before you answer it. "That makes sense, a lot of teams raise that early." Buyers need to feel heard before they listen, and acknowledgment lowers the temperature so you do not sound like you are launching a canned rebuttal.
Step 2: Understand
Ask the question that uncovers what is underneath. "When you say expensive, do you mean the total contract, or the per seat cost compared with what you expected?" Specificity is the goal. You cannot respond well until you know which problem you are solving. This is the step most reps skip, jumping straight from objection to rebuttal, and it explains most mishandled objections. Good discovery call questions make this step easier because you already know the buyer's context.
Step 3: Respond
Now, and only now, you answer. Tailor the response to what you learned. Use proof: a customer story, a metric, a reference. Skip the feature dump. Connect the answer to the concern the buyer actually has.
Step 4: Confirm
Close the loop. "Does that address it, or is there still something there?" Confirmation stops the objection from resurfacing three weeks later and tells you whether you resolved it or just talked.
The LAER Objection Handling Framework
If your team already uses LAER (sometimes searched as "laquer"), it maps cleanly onto the four steps: Listen, Acknowledge, Explore, Respond. Listen means letting the prospect finish without interrupting or formulating your reply while they talk. Acknowledge is step one above. Explore is step two. Respond is steps three and four combined. The value of LAER is the explicit Listen step, which is where reps with a strong close instinct tend to cut corners. Use whichever label your team will actually remember, as long as discovery happens before the rebuttal.
Objection Handling Scripts for the Five Most Common B2B Objections
Scripts are not for reciting. They are starting points so reps have a structure to internalize and adapt. Each one below follows the four steps. For a longer library, see our objection handling script guide, and if your reps work the phones, the cold call objection handling playbook covers the openers.
"Your price is too high"
Do not reach for a discount. Acknowledge: "Pricing matters, and you should compare carefully." Understand: "Are you comparing us to a specific alternative, or is it about the budget you set this year?" If value is unclear, do the math with them: "Your team spends about twelve hours a week building account plans by hand. Across eight account managers, that is close to a hundred hours weekly. What is that worth?" If you do flex on price, trade rather than give: "I can work on the per seat price if we move to a two year term." Every free concession teaches the buyer to ask for the next one.
"We already use a competitor"
Never bash the incumbent. Acknowledge the choice and look for the gap. "Sounds like it's doing some things well. What made you open to a conversation about alternatives?" The fact that they took your call means something is not working. Your job is to find out what.
"We don't have budget"
Separate "no budget" from "not a priority." If it is timing, get a commitment for the next cycle and stay close. If it is priority, you have a value problem. Ask what would need to be true for this to earn budget, and who decides.
"Send me some information"
Often a polite brush off. Agree, then book the next step: "Happy to. So I send only what's relevant, can we take fifteen minutes Thursday to walk through it together?" If they refuse a next step, you have learned how real the interest was.
"We need to think about it"
The most dangerous stall, because it sounds friendly. Surface the hesitation: "Of course. When teams say that, it's usually the price, whether it fits their situation, or getting buy in from someone else. Which is closest?" Then confirm: "If we resolve that, are you in a position to move forward?" A written mutual plan helps here, which is where a sales close plan earns its keep.
Want to see how this plays out with real accounts? Book a walkthrough of CRUSH.
How to Prevent Objections Before They Surface
The best objection handling happens before the objection is spoken. Strong reps raise likely concerns themselves, on their terms, with proof already in hand. This is preempting, and it moves control of the narrative back to you.
Preempt With Proof
If financial services buyers always ask about SOC 2, put the documentation on the table in the demo. If manufacturing buyers worry about adoption among field reps, bring an adoption story to the second call unprompted. Preempting builds credibility because it shows you understand the buyer's world, and it lets you frame the answer instead of scrambling when the question lands.
Map Objections to Stakeholders
Different roles raise predictable objections, so write them next to each name on the account plan. Finance raises ROI and budget. IT raises security and integration. End users raise usability and change load. Executives raise strategic fit. Then prepare targeted proof for each person instead of one generic pitch that satisfies no one. A solid sales call plan bakes this in before the meeting starts.
Arm Your Champion
Your champion is your objection handler when you are not in the room, and most reps leave them unprepared. Give them a one page answer sheet for procurement, IT, and finance. Role play the hard questions with them. If a skeptic raises a concern after you have left, your champion should be able to answer it or at least know who can.
Coach, Capture, and Measure Objection Handling in Salesforce
A framework only works if the team uses it, and it only improves if you can see what is happening. Three habits make the difference.
Coach Against the Four Steps
Pull a recorded call where an objection came up and grade it: did the rep acknowledge, ask a clarifying question, respond with proof, confirm? Most calls fail at step two. Pair call review with role play on the five most common objections until the sequence is reflexive. When a buyer raises price live, the rep's instinct should be a question, not a discount. For a wider view of how to run this, see our guide to sales coaching.
Capture Objections as Account Data
Objections are some of the most valuable intelligence your company collects, and most of it evaporates after each call. For Salesforce teams, log each objection against the opportunity and account: the category, which stakeholder raised it, the response used, and whether it resolved or stalled the deal. Over a quarter you build a library of real objections and proven responses that surfaces to reps in the moment, and new hires ramp faster because they inherit the team's collective experience. If your account plans already live in Salesforce, Salesforce account planning is the natural home for this.
Measure Whether It Works
A framework you cannot measure is a suggestion. Compare win rate on deals where a price objection was raised against your baseline. Track stage conversion before and after rollout, and watch sales cycle length, since objections handled early remove friction early. Look at the data in aggregate too. If a large share of your closed lost deals cite the same competitor on price, that is a positioning problem for marketing and product, not a rep problem.
Objection Handling FAQ
What is objection handling?
Objection handling is the process of responding to a buyer's concerns during a sales cycle so the real issue is addressed and the deal keeps moving. It means listening fully, finding the true driver behind the objection, and answering with proof or a reframe instead of a rebuttal or a discount.
What is an objection handling framework?
It is a repeatable structure for responding to buyer pushback. The most common version has four steps: acknowledge the concern, understand the issue underneath it, respond with relevant proof, and confirm it is resolved. LAER (Listen, Acknowledge, Explore, Respond) is a close cousin.
What are the most common B2B sales objections?
They fall into four groups: price and budget, need and priority, trust and risk, and timing and authority. Price is cited most often, but it frequently masks unclear ROI or a budget timing problem.
How do you respond to a price objection without discounting?
Find out what the buyer is comparing against, then reframe around total value and the cost of staying with the current process. If you offer flexibility, trade it for something such as a longer term so the price keeps its meaning.
How do you coach reps on objection handling?
Grade recorded calls against the four steps and run regular role play on the common objections. Focus on step two, because most reps jump from objection to rebuttal without asking a single question.
Where should objection data live?
In your CRM, logged against the opportunity and account with the category, the stakeholder, and the response used. That turns scattered anecdotes into patterns you can coach against and share with marketing and product.
Objection handling is a discipline, not a talent. It rests on discovery, stakeholder mapping, proof, and a shared memory of what your buyers actually say. Prolifiq CRUSH is a Salesforce native account planning platform that lets your team map every stakeholder in a deal, document their likely concerns by role, and walk into each conversation prepared instead of reactive. Because it lives inside Salesforce, the plans and objection intelligence stay attached to the opportunity where deals move. If you want a repeatable way to turn pushback into progress, take a look at CRUSH.
