How to handle a sales objection: the 8 you will hear, and the data that pre-empts them

What a sales objection is, and why it is good news

A sales objection is a reason the buyer gives for not moving forward: the price, the timing, the tool they already pay for, the person who has to sign. Knowing how to handle a sales objection is knowing how to respond: you understand the objection, check whether it is real, answer it with proof and confirm the buyer is ready for the next step. Most guides stop at the reply. This one adds a layer they skip: many sales objections were readable in public data before you dialed, and a rep who looked first does not have to ask.

An objection is not a refusal. A prospect who has no interest ends the call or never replies. A prospect who says "it is too expensive" or "we already use something" is weighing you against something else, which means they are still weighing. The objection tells you what the comparison is. That is why sales objections cluster late in a deal, at the discovery and demo stages, and why the step that deals with them sits between the presentation and the close in the seven sales process steps.

This guide opens with what you came for: the eight sales objections you will hear in B2B discovery calls and demos, with a reply for each and the data that pre-empts it. The method, the types and the practice come after.

How to handle sales objections: the 8 you will actually hear, and the data that pre-empts each

These are the objections of discovery and demo calls, when the buyer knows what you sell and is deciding whether to go further. The opening objections of a cold call are a different family, covered in the next paragraph. For each of the eight, the table gives the type of objection, what public data tells you before the call, and where that data comes from.

Two limits to keep in mind. Website Technologies sees what is visible from the prospect's website: a CRM or an internal sales tool often does not show there. And a job post that names a tool is a clue about a renewal, never a certainty: you still confirm it on the call. Enrich Companies, Search Leads and Import Leads from Target Companies read LinkedIn, so they need your LinkedIn account connected through the Derrick Chrome extension.

"Send me an email" and "not interested" are not in the eight on purpose. They arrive in the first seconds of a cold call, before the buyer knows what you sell, and they call for a different reflex. The replies for them, with the three other openers you will hear on the phone, live in our B2B cold call script.

1. "It is too expensive"

The price objection is rarely about the number. It is about the number compared with something: another vendor, last year's budget, or the cost of doing nothing. Reply by asking which comparison they are making: "Too expensive compared with what you pay today, or compared with what you expected?" Then reframe the price against their scale. Knowing before the call that the company has 400 employees and is hiring six sales reps lets you talk about cost per rep instead of a total that sounds large on its own.

2. "We have no budget"

No budget is often a qualification that did not happen earlier: the question of who pays and when should have come before the demo. Our guide on how to qualify a sales lead covers it; here, only the data layer matters. A company that opened three roles in the team you sell to this month, or announced a funding round, has money moving somewhere. Check the hiring signal and the latest news before you call, so you know whether "no budget" means "frozen" or "not for you yet".

3. "Not the right time"

Timing objections are honest more often than rep folklore suggests, so treat them as information. Ask what would make it the right time, and when that happens: "What has to be true for this to be a priority, and is that this quarter or next?" Then date the follow-up to the event they named, not to an arbitrary four weeks. The data you pulled before the call helps here too: a role posted last week in the relevant team is a reason to ask whether the new hire will need the tooling you sell.

4. "We already use X"

This is the objection data pre-empts best. If the prospect's website shows the tool they run, you already know the comparison before you dial, and you can prepare the one or two things your product does differently for teams using that tool. "We tried something like this and it failed" belongs to the same family: knowing what they run today tells you what replaced the failed attempt. The spoken reply to "we already use a solution" on a first call lives in the cold call script; in a demo, your job is to have done the homework.

5. "I need to talk to my boss"

Authority objections tell you the committee is bigger than your contact. Answer by helping, not by pushing past them: "Of course. What will your manager want to see to say yes, and would it help if I joined that conversation?" Before the call, list who else sits in the buying committee at the account, and check that your contact holds the role you think. Our guide on selling to decision-makers covers how to reach them.

6. "Show me the ROI"

A buyer asking for ROI is doing their job: they need a number to defend internally. Do not answer with a generic case study. Build the calculation with their inputs, on the call if you can: time saved per rep, number of reps, cost of the current way. Headcount and industry pulled beforehand give you the order of magnitude, so the first version of the calculation is theirs, not a template.

7. "It has to go through security and procurement"

This is less an objection than a process, and the worst reply is surprise. Ask for the checklist and the timeline, and send what you have: a data processing agreement, a security page, a list of subprocessors. Knowing the prospect's country and industry before the call tells you whether you are about to enter a regulated sector, where the review is longer and the documents more specific.

8. "We are locked into a contract"

A contract ends. Ask when: "When does it come up for renewal, and who decides whether you renew?" Then work backwards: a renewal decision is usually made two to three months before the date. A job post that names the tool in place can hint that a renewal is being prepared, but it is a clue to confirm in the conversation, never something to state as fact.

The four types of sales objections, plus the one nobody names

Sorting sales objections by type helps you reply to the real concern rather than the words. The classic grid has four types; B2B deals add a fifth.

The type matters because the same words can hide different types. "Too expensive" from someone who cannot sign is an authority objection dressed as a money one. Ask one question to find the type before you answer.

How to handle a sales objection in 5 steps

Every guide proposes a method, from three steps to seven. They share the same core: listen, understand, respond, confirm. Ours adds one step the others leave implicit, checking the objection against what you already know.

1. Listen to the end. Let the buyer finish, even if you have heard the objection a hundred times. Interrupting tells them you did not hear this one.
2. Acknowledge it. Repeat the objection in your words: "So the concern is the timing, not the product." You show you understood, and they correct you if you did not.
3. Check it against the data. Compare what they say with what you found before the call. "No budget" from a company that just raised money is worth a second question. "We already use X" when their website shows X means the objection is real and you prepared for it.
4. Respond with proof. A number, a customer example in their industry, a calculation with their inputs. An opinion does not overcome sales objections; evidence does.
5. Confirm and move. Ask whether the answer covers the concern, then propose the next step: "Does that answer the question on timing? If so, can we book the call with your manager for next week?"

Step 3 is where most of the time goes when you prepared nothing, and where almost none goes when you did. That is the core idea of this guide: objection handling starts before the call.

Objections vs obstructions, and when to walk away

An objection or an obstruction?

An objection is a concern you can address: price, timing, a missing feature. An obstruction is a way of ending the conversation without saying no: "send me something", "circle back next year", repeated with no detail. Test it with one specific question. An objection gets more specific when you ask ("the budget is set in January"); an obstruction gets vaguer ("we will see"). Treat the first with the five steps above; treat the second as a soft no and ask directly whether it is one.

When to walk away

Walk away when the objection is a true mismatch you cannot fix: the buyer needs a feature you do not have, their volume is far below what makes your product worth it, or the decision-maker has said no after seeing the full picture. Say it plainly and leave the door open: "It sounds like we are not the right fit today. If that changes, I would be glad to talk again." A clean exit keeps your pipeline honest, and the stage where deals stall is easier to read when dead deals are closed rather than parked.

Prepare before the call: how to handle sales objections with a pre-call checklist

Pick the sales objections you hear most often. The checklist below tells you what to pull for each account before the call, and what it costs in credits for the number of calls you prepare. Each data point is counted once per account, even if it pre-empts several objections.

A worked example. Your team hears "we already use X" and "no budget" most. For 50 calls, the stack check costs 2 credits per account and the hiring signal 1 credit: 50 accounts times 3 credits comes to 150. The stack check accounts for 100 of them, all on a paid-only feature, so this preparation needs the Mini plan, at 9 euros a month for 4,000 credits. The free plan's 100 credits a month cover the hiring signal for those 50 accounts, plus a company enrichment for each, but not the stack check. Add three news articles per account and the total for the same 50 calls doubles to 300, still well inside the Mini plan.

Ten minutes of reading per account turns into one pass over the whole list. The time you get back goes where it matters: preparing the one or two replies each account is likely to need.

Where the pre-call data comes from: the app, Sheets, Claude and the API

The same data points are available on four surfaces. Pick the one that matches how you prepare.

• The Derrick web app is the default for a list of accounts: import the list, add a column per data point, read the result before the call. Nothing to install.
• The Google Sheets sidebar does the same inside a spreadsheet, if your call list already lives there. Derrick runs from the sidebar, not from formulas.
• Claude or ChatGPT through the Derrick MCP fits the rep preparing one important call: ask "what does this company run on its website, and is it hiring sales people?" and get the answer in the chat. MCP comes with the Plus plan and above; LinkedIn operations need the Chrome extension connected.
• The Derrick API fits a sequence that should pull the data by itself: when a meeting is booked, a workflow calls the API and writes the stack, the open roles and the latest news into the CRM record before the rep opens it. API access comes with the Plus plan and above, and works with Zapier, Make and n8n.

The point of the API and MCP routes is that nobody has to remember to check. The data is in front of the rep because the workflow put it there. See the full list of Derrick features for the other data points you can add.

Practice objection handling: 3 ways to rehearse

Preparation covers the objections the data can see. The others you handle with practice.

1. Role-play the top three. Once a week, one rep plays the buyer and uses the three objections the team heard most in the past month. Swap roles. Ten minutes is enough if it happens every week.
2. Review recorded calls. Pick two calls where an objection came up: one where the deal moved forward, one where it stopped. Compare what the rep said in step 2 and step 4. The difference is usually in the acknowledgment, not the argument.
3. Keep an objection log. After each call, note the objection, its type and what happened next. After a month, the log tells you which objections to prepare for with data, and which ones need a better reply. It also shows which questions from our list of buyer intent questions surface the objection early instead of at the end.

Five objection handling mistakes that cost deals

• Answering before you understand. The reply to "too expensive" depends on the comparison, and you do not know it until you ask.
• Arguing. Winning the argument loses the deal. The buyer should leave the objection feeling heard, not corrected.
• Discounting at the first price objection. A discount answers the words, not the concern, and teaches the buyer that objecting pays.
• Asking what you could have known. "What tools do you use today?" costs the buyer's patience when their website already shows it. Save your questions for what data cannot tell you: priorities, politics, timing inside the company.
• Not confirming. Skipping step 5 leaves the objection half open, and it comes back at the close.

Objection handling is a skill you practice and a preparation you do before the call. The practice is yours. The preparation can be one pass over your list the morning before your calls.