Common Sales Objections: The 12 We Logged on 371 Calls, and How to Answer Each

The common sales objections we hear most often are about price, an existing provider and a request to "send me information". Price came up on 43 of 371 discovery and evaluation calls our team logged over four months. An existing provider followed on 37 calls, and "send me information" on 34. Below are all 12 categories, with the buyer's recorded wording and our suggested response to each.

After the list come the four types, a four-step method, and what buyers in 12 separate deals said and did.

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Common sales objections: the 12 Spona logged

Our team logged objections in 12 categories on 371 discovery and evaluation calls over four months. Price led the list on 43 calls. An existing provider came second on 37, and "send me information" third on 34. Accuracy, budget and contract timing filled the rest of the top half.

The table holds all 12 categories with the buyer's recorded wording for each. The wording is the phrase our team logged for that category, not a line we wrote for this post. The response column is our suggestion, drawn from how our team answers each objection. We did not log what happened next, so none of these is "the one that worked".

One call can carry several objections. Each category counts a call once. So the counts are not additive, and we give no total. Nor can we say how many buyers raised no objection at all.

These were conversations with people who had agreed to talk. The brush-offs on a first cold dial are a different list. Our cold call scripts post gives five lines for those. The ICP in the first response is the ideal customer profile you agree before any search runs.

Sales objections: the four types

RAIN Group sorts objections into four types: need, urgency, trust and money. Cognism uses BANT's four instead: budget, authority, need and urgency. Three types match, but RAIN has trust where BANT has authority. In RAIN's terms, a buyer objects because they doubt the problem, the timing, you or the price.

We grouped our 12 categories into RAIN's four types. The grouping is ours. Two of the categories could sit in more than one place.

Two placements need a note. "Send me information" is an urgency objection, not a request for a deck. The buyer has no reason to decide this week.

"Need to ask manager" is about urgency as much as authority. The recorded wording says the manager needs to see the test first. The test has not happened yet.

We do not total calls by type. A single call can carry a price objection and a trust objection. A type total would count that call twice. Read the bar chart in the first section as twelve separate counts on the same 371 calls.

Objection handling: the four steps

To handle an objection, listen to all of it, understand it, respond to the most important part, then confirm the point no longer stands. Those are RAIN's four steps: listen fully, understand completely, respond properly and confirm. The LAER model, which stands for listen, acknowledge, explore and respond, is the same idea. It folds the confirmation into the response.

1. Listen. Let the buyer finish, then wait a beat. Gong studied 67,149 sales meetings. Top performers answered an objection with a question 54.3% of the time, average performers 31.0%. In Gong's data on demo calls, the average rep's knee-jerk reply ran 21.45 seconds. Top reps paused longer. Gong reports a correlation, not a cause.

2. Understand. Ask what sits behind the words before you answer them. "The price looks high before we know how much we can use" is not a price objection yet. It is a missing usage number. "My manager needs to see the test first" names an approver and a test. Ask who the approver is and what the test must show.

3. Respond. RAIN's rule is to "address the most important objection first". Take one objection at a time. Answer it with a fact, a test or a next step, never a speech. Each suggested response in our table is a check, a test or a next step, not a rebuttal.

4. Confirm. Ask whether that settles the point. If the buyer says no, you have found the real objection. The loop starts again from step one.

Price and budget: the most common objections

Three logged categories sit here, and price is the largest of the twelve. "Price is too high" came up on 43 calls and "No budget" on 29. "Concern about duplicates" came up on 19.

The recorded wording tells you what the objection really is. "The price looks high before we know how much we can use" means the buyer has no usage estimate yet. The price per record is not the problem. The unknown number of usable records is.

Our suggested response moves the comparison. Judge cost after verification, deduplication and the agreed ICP filter, so the buyer compares cost per usable record. On Spona the price per lead shows at checkout before you buy, and every search starts with a free sample. A lead costs $0.008 to $2.00 depending on the search type and plan.

"No budget" gets a different suggested response: a defined paid pilot with an agreed ceiling. On Spona the Free plan carries 3,000 one-time credits, and each new search session costs 1,000 credits. Subscription fees are refundable for 14 days if you spent no credits. The ceiling is the buyer's number, not a discount you offer.

"I do not want to pay again for people already in our CRM" is a fair objection. Our suggested response is a process. Deduplicate by email, domain and company identifiers before the purchase, and our data hygiene post gives the merge rules. On Spona an exclusion list sits on every plan, and enrichment of your own list charges only for the fields it adds.

We keep a separate log of 12 deals against another data vendor. Three buyers there put the price question in their own words. A founder at a French company of 11 to 50 staff chose Spona over Cognism. Their words: "Let us prove the segment with one list before committing to a larger contract".

A founder at a UK company of 11 to 50 staff switched away from ZoomInfo. Their words: "We need a usable list each month, not another annual seat". A head of sales at a US company of 11 to 50 staff chose Spona over Seamless.AI. Their words: "The useful measure is how many records the rep can use immediately".

We logged the outcome of each deal, not the response that came before it. Treat these quotes as what buyers wanted, not as proof that a line works.

How do you handle a price objection?

Ask what the buyer measures "high" against. A seat price, last year's list, a competitor's quote and a cost per record are four different comparisons. Each needs a different answer. Then move the comparison to cost per usable record after verification and deduplication.

The UK founder above gave the comparison that matters most. A seat the team does not use is the expensive option, whatever it costs a month.

Incumbent and competitor objections

"Already have a provider" came up on 37 calls, and "We use Sales Navigator" on 21. Both are need objections. The buyer has a tool and a habit. The question is what the tool misses, not whether it is good.

Expect them. 6sense surveyed 2,509 business buyers. Of those, 81% had chosen a preferred vendor before they spoke to sales, and 85% had set their purchase requirements first. Kompyte asked more than 400 US sales leaders about their pipelines. They called 57% of deals competitive, and competitors won 32% of those.

Our suggested response to the incumbent is to keep the buyer's current workflow and test the missing accounts. For Sales Navigator, use the profiles the reps have already selected as the test set for exportable contact data. Navigator shows the people. The contact data comes from somewhere else, and our Sales Navigator pricing post covers what each tier includes.

The deal log records outcomes, not responses. Three buyers in it kept both tools. A VP of sales at a US company of 51 to 200 staff, on ZoomInfo, kept both. Their words: "We will keep our current workflow, but we need more people at regional accounts".

An SDR manager at a UK company of 51 to 200 staff, on Apollo, kept both as well. Their words: "We will keep the sequencer and bring in data when our saved search runs out". A sales director at a UK company of 51 to 200 staff, on Cognism, did the same. Their words: "Our calling team likes the numbers; we still need more target companies".

Two deals were lost. A VP of sales at a US company of 101 to 500 staff stayed with ZoomInfo. The team preferred its existing workflow, even with extra coverage on offer.

An SDR manager at a US company of 51 to 200 staff chose Apollo. Browser-led prospecting mattered more to that team than batch discovery.

How do you respond to "we already have a vendor"?

Do not argue with the incumbent. The reps chose it and know it. Ask which accounts or contacts the current tool cannot reach today, then test exactly those. Every buyer who kept both tools in our log named such a gap: regional accounts, an exhausted saved search, more target companies.

Our ZoomInfo reviews post lists the gaps that tool's own users report most. It gives you the questions to ask.

Timing and authority objections

Four categories stall a deal without rejecting it: "Send me information", "Contract timing", "Need to ask manager" and "Not a priority". "Send me information" is the biggest of them, on 34 calls. It is also the third largest objection overall.

The stall is the real risk, not the no. Matt Dixon's team studied about 2.5 million sales conversations for their JOLT research. Between 40 and 60% of deals ended with the customer doing nothing. Less than half of those losses went to the status quo; the rest went to indecision.

Forrester's report found that 86% of B2B purchases stall at some point. The same report counts 13 people in an average buying decision, and 89% of purchases involve two or more departments. Research by Gartner puts the typical buying group for a complex B2B solution at six to 10 decision makers. Those buyers spend only 17% of their purchase time meeting potential suppliers.

"My manager needs to see the test first" is therefore the normal case, not a brush-off.

Our suggested responses all turn the stall into a decision, a date or a name. For "send me information", agree which decision the information should help make, then send only what serves that decision. For contract timing, record the renewal date and test incremental coverage before it. For the manager, agree on the approver and the sample acceptance criteria.

For "not a priority", tie the next step to the first actual campaign date. Our lead qualification checklist covers how to confirm the approver early. Our gap selling post gives the questions that put a cost on waiting.

One deal in our log stalled on contract timing. A RevOps director at a US company of 201 to 500 staff, on ZoomInfo, made no decision. Their words: "The extra contacts are useful, but we cannot change the contract this quarter". The renewal was still several months away.

Trust, data and security objections

Three logged categories question the data itself. "Accuracy concern" came up on 31 calls and "Coverage concern" on 26. "Need integration" came up on 16.

Accuracy. "How do we know those emails are still valid?" is the recorded wording, and it deserves a precise answer. Our suggested response is a recent verification timestamp and a controlled verified-only send. In Spona's audit, 2,941 of 3,017 records were correct on person, employer and title. That audit does not measure email validity, so the send is still the test.

On enrichment of your own list, Spona charges only for returned values, and for an email only when it is verified. The source and check timestamp come with every purchased field at 0 credits. A verified email costs 5 credits and a mobile number 35. Company data costs 3 credits.

Our cold email deliverability post explains how to run the verified-only send without hurting your domain.

Coverage. Our suggested response to "Will you cover our niche outside the largest cities?" is a stratified list of exact target accounts. Pick accounts by region and size, then check each one. Do not judge a sample from the easy cities.

One switch in our deal log turned on this point. An agency owner at a US company of 11 to 50 staff switched away from Lusha. Their words: "The next campaign includes stores and local owners, not just office-based companies". Spona's brick-and-mortar data covers local businesses with physical locations, which is why that request is testable.

Integration. Our suggestion for "Will the export fit the fields in our CRM?" is a sample CSV mapped to the existing import fields before anyone buys. On Spona, HubSpot is the only native CRM integration, on the Premium and Expert plans. Salesforce takes a CSV import, and CSV export is on every paid plan.

In our deal log, a head of sales at a German company of 11 to 50 staff chose Spona over Apollo. Their words: "We spend too long stitching together the missing fields".

Security. Data handling did not appear as a category in the call log, but it stopped a deal. A RevOps manager at a German company of 51 to 200 staff, with Lusha as the other vendor, made no decision. Their words: "We need the data-handling review finished before the pilot can start". The review stayed incomplete.

The review has a familiar shape in both of our markets. Under UK GDPR Article 28, a controller "shall use only processors providing sufficient guarantees". The processing runs under a contract or other legal act, in writing. It must require the processor to make available "all information necessary to demonstrate compliance" and to allow audits.

In the US, buyers often ask for a SOC report. It is a CPA examination of a service organization's system-level controls, and it helps users assess the risks of outsourcing. Our suggested response is to send your contract terms and any SOC report you hold before the pilot starts.

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Common sales objections FAQ

What is a sales objection?

A sales objection is a reason the buyer gives for not moving to the next step. It can be the price, the timing, the current tool, the data or the approval they need. It is information, not rejection. The 12 categories above are the forms it took on our calls, and each one names something you can test or settle.

Which framework works best for handling objections?

Use RAIN's four steps: listen, understand, respond, confirm. The LAER model covers the same ground with acknowledge and explore in the middle. Allego's "4 P's" of probe, paraphrase, pivot and progress add the next step at the end. Pick the version your team will follow on every call, as long as it ends with the buyer confirming the point no longer stands.

How do you handle objections in sales calls?

On a first cold call, the objection is usually a brush-off. The answer is a short line that keeps the call going. Our cold call scripts post gives five of those lines, and our cold calling tips cover tone and timing. The gatekeeper post handles the person before the buyer.

On a discovery or evaluation call, use the four steps above and the suggested responses in the table.

Should you send information when a buyer asks for it?

Yes, after you agree which decision it should help make. "Send the details and I will review them" was the third most frequent objection we logged, on 34 of 371 calls. A deck sent with no decision attached leaves the buyer nothing to decide. A one-page comparison sent for a named meeting, with a date to discuss it, is a next step.