How to Handle the Price Objection in B2B Sales

Why the price objection is almost never about the price

Most reps treat "it's too expensive" as a number problem. It almost never is.

The buyer isn't objecting to $29,000 because $29,000 is too high. They're objecting because one of four things is true underneath the sentence — and they picked the safest one to say out loud. Price is polite cover. Price is the objection that doesn't feel like an admission.

Reps who hear the headline and defend the number spend the rest of the call chasing a concern the buyer never actually had. Reps who diagnose first close the deals the script-rehearsers lose.

This matters because the instinct the rep has in the first five seconds — defend or discount — is wrong about three-quarters of the time. Defending a number that wasn't the issue looks like dodging. Discounting a wrong-anchor objection hides the real problem and drags your margin across the next four renewals. The fix isn't a better rebuttal. It's a diagnostic.

The 4 things buyers actually mean when they say "it's too expensive"

Every price pushback on a B2B call maps to one of four root causes. Name the cause and the response follows. Skip it and you're solving a different problem than the buyer has.

1. ROI gap. The buyer has no quantified cost of inaction, so the status quo still feels free. Your price sits on one side of a scale and the other side is empty. "Too expensive" here means "I can't justify the spend to myself, let alone to my CFO." The response is not to defend the price — it's to load the other side of the scale. Put a dollar number on what their current workflow is costing them.

2. Wrong anchor. The buyer is comparing your full-workflow product to a point tool that does 30% of the job. They heard $29K and benchmarked against a $5K call recorder. The price feels wrong because the comparison is wrong. You don't need to defend the number — you need to correct the scope before the number gets evaluated.

3. Budget cycle. This is a real timing objection wearing a price coat. The annual budget was set in October, your tool isn't in it, and the buyer can't cut a PO this quarter without a forcing event. "Too expensive" is code for "I can't find the line item." The diagnostic is: is there a forcing event (FY reset, team expansion, leadership change) that could unlock budget? If yes, time the close to it. If no, the deal is next quarter at best.

4. Authority stall. The person on the call is not the economic buyer, and "too expensive" is their polite way of saying "I can't approve this alone." This is a discovery failure that surfaces as a price objection. The response is not a discount — it's a multi-thread. Ask who else needs to see this, what they'll push back on, and how you can help your champion make the case internally.

The 5-step diagnostic for every price pushback

Run this sequence on every "it's too expensive." It works because it forces the rep to slow down in the two places where deals get lost: the first five seconds after the objection lands, and the question that follows the acknowledgment.

1. Listen — hear the full sentence

The average B2B seller interrupts a buyer inside 7 seconds of an objection landing (Gong, 2022). "It's too expensive…" is a headline. "…for this quarter" or "…compared to what we pay for Tool X" is the story. The rep who steps on the second half of the sentence spends the rest of the call defending a number the buyer wasn't actually objecting to. Let them finish. Capture the exact phrasing, not your interpretation of it.

2. Acknowledge — one sentence, no retreat

"That's fair — enterprise tools are a real commitment." "I hear that a lot from VPs at your stage." "Makes sense — let me understand what's driving that." You haven't conceded the price. You've dropped defensiveness and kept the buyer talking. Skip this step and every response that follows lands as dismissal. The buyer stops volunteering the one thing you need most: which of the four causes is live.

3. Explore — one diagnostic question

This is where the deal is won or lost. One open-ended question, aimed at surfacing the root cause. The exact question depends on what you heard in step 1:

• If it sounded like ROI gap: "What would it cost you to keep doing this manually for another 12 months?"
• If it sounded like anchor: "When you say expensive, what are you comparing it to?"
• If it sounded like budget: "What would need to be true for this to fit next quarter's plan?"
• If it sounded like authority: "Who else needs to weigh in on a number at this level?"

One question. Wait for the answer. Reps who stack two questions let the buyer pick whichever is easiest to answer, and you end up solving the wrong one.

4. Reframe — anchor flip, not ROI pitch

Don't pitch your ROI. Make the status quo expensive. The number you say out loud should be the cost of the buyer's current workflow — leaked pipeline, admin hours, quota missed — not the cost of your product. "Based on your 12 reps and the 8 hours a week of admin we've benchmarked in your industry at $60/hr, that's $374K a year. Our Growth plan is $29K." The math doesn't have to be perfect. It has to be specific and defensible.

5. Close — advance the deal, don't "win" the objection

End with a next step, not a victory lap. "Given that, does it make sense to loop your CFO in for a 15-minute call Thursday?" "Want me to share the ROI doc with your team before we reconvene?" The response is a bridge, not a wall. The goal isn't to close out the objection — it's to move the deal one step forward while the buyer is still engaged.

8 price pushbacks, with the diagnostic that surfaces the real cause

Every sentence on the left below sounds like a price objection. Most of them aren't. Run the explore question in the right column before you touch the number.

Notice the right column contains no closing lines. Every explore question ends with a pause. If your response can be delivered without waiting for a reply, you're pitching, not diagnosing.

How to reframe the anchor — the move reps skip most

The cost-of-inaction reframe is the part that separates closers from discounters. Most reps can listen, acknowledge, and explore — then they pitch ROI. Pitching ROI means talking about your product's outcomes: "reps save 8 hours a week, so you'll get 3× on the investment." That's a product story. The anchor flip is a buyer story.

The anchor flip takes the buyer's current state and makes it expensive. Same numbers, opposite direction:

• Generic ROI pitch: "Our Growth plan at $29K delivers an estimated 3× return — roughly $87K in value."
• Cost-of-inaction reframe: "You have 12 reps. Our benchmark says reps lose 8 hours a week to admin. At an average loaded rate of $60/hour, that's $374K a year leaking out the back of your sales org. The $29K isn't a cost — it's the invoice for recovering $345K."

The reframe works because the buyer was mentally anchored on $0 (the status quo) and $29K (your price). The cost of inaction inserts a third number — $374K — that makes $29K look like the bargain it actually is. Three moves to run it well: use the buyer's own inputs (their rep count, their admin hours), cite a defensible industry benchmark (Salesforce State of Sales, Pavilion, or RevOps Co-op are all acceptable), and hand them a single-line takeaway they can repeat to their CFO verbatim.

4 discount traps that kill margin (and still lose the deal)

Discounting isn't always wrong — but undiagnosed discounting is almost always expensive. Research from Price Intelligently suggests roughly 60% of discounts fix the wrong problem because the objection wasn't about price in the first place. Four traps show up most often:

1. Pre-emptive discounting. The rep floats "we have some flexibility" before the buyer has even pushed back. The buyer now knows the number is negotiable and the floor becomes the ceiling. Never offer a discount before you've run Explore.
2. Discounting an anchor objection. The buyer compared you to a $5K point tool, you dropped to $24K, and they still didn't sign — because the real issue was scope, not number. You lost margin without moving the deal. Fix the anchor first; the price takes care of itself.
3. Discounting to rescue a stalled deal. Two weeks past the expected close date, the rep offers 15% off to "get it unstuck." The deal was stuck on authority (the economic buyer hasn't seen the case), not price. The discount clears the last hurdle only on paper — the CFO still asks the same question and the deal pushes another month, at a lower number.
4. Volume discounts without trades. Every discount should be traded for something the buyer gives up: multi-year commitment, logo rights, reference clause, case study participation. A discount with nothing on the other side of the trade is a margin leak dressed up as a close.

Handling the price objection live — on the call

Frameworks work in roleplays. Live calls don't wait for the rep to remember which root cause maps to which question. The buyer says "it's too expensive" and the rep has seven seconds before the silence gets heavy.

This is the gap Gangly's Live Call Coach fills. On a connected Zoom or Google Meet call, the coach listens, detects the price-objection keywords ("expensive," "budget," "cheaper," "flexibility"), tags the likely root cause from context, and surfaces a tailored diagnostic question plus three proof points — on screen, while the rep is still on the call. The rep runs the conversation. The coach runs the lookup.

What live coaching on the price objection actually gives you after 50+ calls:

• Reaction time. The right explore question surfaces inside two seconds of the keyword landing. The rep doesn't have to rummage through memory under pressure.
• Tailored proof. The cost-of-inaction number uses the account's actual rep count and benchmark. Enterprise call gets an enterprise reference. Series B call gets a peer at the same stage.
• Root cause tagging. The cause (ROI gap / anchor / budget / authority) is tagged automatically and pushed to the post-call note, so pipeline pattern work doesn't depend on rep memory on a Friday afternoon.

Close the loop — log every price objection, kill the pattern at the source

The most expensive price objection isn't the one you lose a deal on. It's the one you lose three deals on — because nobody logged the first two. Pattern capture turns price objection handling from a calls-are-hard story into a pipeline-level one.

The loop is short. Every price objection gets tagged by root cause, resolved (or not), and logged against the deal. After 20 calls, patterns emerge: anchor objections spike when a specific competitor is in the evaluation; ROI gap objections cluster at a specific company size; authority stalls show up when discovery skipped mapping the buying committee. Post-Call Notes captures this automatically, and the cluster-level fix — a stronger ROI calculator, a sharper competitive battlecard, a tightened discovery script — gets prioritized instead of guessed at in next month's QBR.

For the full framework that sits behind this post, see the sales objection handling framework. For the call that happens before the price objection even shows up, see the discovery call framework that wins deals. And if your team keeps losing calls to any objection, not just price, start with how to win more sales calls.

Frequently asked questions