← Back to Objeq

How to handle sales objections: the 14 you actually hear, and the first line to say back

Updated September 22, 2026 · By the Objeq team

Short answer. Don't answer the words. Answer what the words are protecting. Every objection on this page gets the same three-move treatment: acknowledge it so the buyer stops defending it, ask one question that separates the real version from the costume version, and only then say the thing you wanted to say. Most reps do it in the opposite order. They hear "it's too expensive" and defend the price, when the buyer was protecting themselves from being blamed for a bad decision, not from the number. Below are the 14 objections reps actually hear, with the opening line for each one, and the five fears they all reduce to.

Start Objeq free, 3-day trial

From $99 / seat / mo after the trial · card up front, charged only when the 3 days end · cancel in one click · full refund within 14 days of the first charge

Want to see it work before you read 2,000 words? Give it your hardest objection and watch it answer. No signup, nothing to install.

Every objection is one of five fears wearing different words

A hundred objections is an unlearnable list. Five is a skill. Objeq's engine classifies every objection it hears into five families, and these five are not a marketing grouping invented for a blog post. They are a contract inside the product: the same five tags the live engine emits, the extension renders and the database stores. Each family is defined by a sentence the buyer never says out loud, which is the part that makes it usable on a call.

FamilyWhat the buyer never says out loudWhat it sounds like instead
The Gap"I don't know if that distance is worth it."Price, cost, cheaper elsewhere, budget
The Puzzle"One piece is missing and I can't tell you which.""Send me information", "can you send references", missing feature
The Loop"I'll manage a while longer like this.""Not a good time", "we're happy with how we do things"
The Scar"I've tried before, and I don't want to be that person again.""We tried something like this and it didn't work"
The Alibi"I don't want this to be on me.""I have to talk to my boss", "I need to think about it"

The five names and the five unspoken sentences are taken verbatim from the product's own fear map, the single file the engine, the dashboard and the extension all read from. The mapping in the third column is how the families usually surface, not a rule: the same words can carry a different fear depending on who said them and when. That ambiguity is the whole reason a rep needs help mid-call rather than a laminated card. Longer version: the 5 fear families behind every sales objection.

The money objections

Three objections that all sound like price and are three different problems.

"It's too expensive." Don't defend the price. It usually masks a fear of overpaying, of being blamed, or of uncertain value. Acknowledge it, isolate it, "if price weren't the issue, would this be a yes?", reframe cost against the cost of the problem, and only then talk numbers. Full treatment: handling "it's too expensive".

"I can get it cheaper elsewhere." Verify it's real first: "cheaper how, same scope, same support?" Half the time the comparison collapses on inspection. If it's real, don't race to the bottom. Reframe from price to the cost of being wrong. If price is genuinely the only criterion, walk politely. Full treatment: "I can get it cheaper elsewhere".

"We don't have budget." Two species, and they need opposite moves. "No budget, period" is rare and usually means a company in real distress. "No budget for this" is common and means your problem hasn't earned a line item yet. The question that separates them: "if this were a top-3 priority, would the budget question still block it?" Then sell the priority, not the product. Full treatment: "we don't have budget".

The stalls, which are the ones that quietly kill deals

None of these four sound like a no. That is exactly why they are more dangerous than a no. A no ends the call and frees the hour. A stall keeps the deal in the pipeline for six weeks and then dies without ever being treated.

"I need to think about it." Never answer with "sure, take your time". Listen to how it arrives: "obviously I need to think about it, right? You didn't expect me to close now." That is not an objection, that is a prospect asking you to agree the call is over, and "of course, that's fair" is you agreeing. "Thinking about it" is a container holding price, authority, fear of change or plain politeness. Pry it open while you are still on the call. Full treatment: "I need to think about it".

"Just send me an email." Agree instantly, then attach one qualifying question to it: "Happy to. So I don't bury you in noise, what should it focus on?" A real prospect answers with specifics. A brush-off answers with "oh, just general info". Now you know which call you're on. Full treatment: "just send me an email".

"Now's not a good time, call me next quarter." Ask one thing: "what changes next quarter?" A real answer, a budget cycle, a reorg, a launch, means it's a genuine timing issue, so book a dated follow-up right now. A vague answer like "things should calm down" means timing is a costume for a different objection, and that one is what you treat. Full treatment: "now's not a good time".

"Can you send some references or case studies?" Find out what the proof is for: "Absolutely, what would a convincing case study need to show for this to move forward?" A specific answer, same industry, same team size, a named metric, means real diligence, so deliver exactly that. A vague answer means the request is a stall wearing a suit. Full treatment: reference and case study requests.

The authority objection

"I have to talk to my boss / my partner." Treat it as good news. It is a process signal, not a rejection. But never let your pitch travel secondhand, because the version that reaches the decision maker is your pitch filtered through somebody who cannot answer a follow-up question. Ask what the boss will care about, build that case together, and ask for a seat: "want me to join that conversation so you don't have to defend numbers you didn't make up?" Full treatment: "I have to talk to my boss".

The competition objections, including the one that isn't a competitor

"We already have a vendor." Never attack the incumbent. The prospect chose them, so attacking the incumbent is calling the prospect wrong. Ask what's working, "what do you like most about them?", and then the crack question: "if you could change one thing about how it works today, what would it be?" Sell into that answer. Full treatment: beating the incumbent.

"We're also talking to your competitor." Thank them for the honesty, never disparage the alternative, and then make the move most reps skip: help write the evaluation criteria. "Smart. What's on your comparison list? Can I suggest two tests worth running on all of us?" Whoever frames the evaluation usually wins it. Full treatment: the competitive bake-off.

"We're happy with how we do things." The status quo is the biggest competitor in almost every deal and the only one with no sales team. Don't argue that they're wrong, make the status quo defend itself. Ask what "happy" means in numbers: "what's your close rate on calls where the prospect pushes back?" Contentment usually survives on never having been measured. Full treatment: the status quo objection.

The trust objections

"I've never heard of you." Never fake bigness. Inflated "we work with leading companies" talk collapses under one follow-up question and takes your credibility with it. Own the size, then replace brand trust with verifiable trust: a specific founder story, checkable facts, straight talk about your limits, and proof they can run themselves in days. Full treatment: selling as the unknown vendor.

"We tried something like this before and it didn't work." The most honest objection you will hear, and the one most likely to be answered with the worst possible line. Don't say "we're different". Every vendor says that and the scar has heard it. Investigate the failure like a doctor instead: "what exactly happened?" The diagnosis either finds a fixable cause, setup, adoption, wrong tool, or it disqualifies the deal honestly, which is also a win. Full treatment: selling after a scar.

The product objection

"Your product is missing X." Don't promise the roadmap and don't argue that X doesn't matter. Ask what job X does: "what would you use X for, day to day?" Half the time your product does that job another way. Sometimes X is a checklist item copied off a competitor's feature page. And sometimes it's real, in which case saying so now saves you a churned customer later. Full treatment: the missing-feature objection.

The best handled objection is the one that never gets raised

Everything above is treatment. Prevention is cheaper. Raise the objection yourself, first, on your terms, and it arrives as a presentation instead of a confrontation. Three moves do most of the work: inoculation ("you might wonder whether reps will actually use this, here's the week-four data"), anchoring the price before the reveal, and naming the elephant ("we're newer than the big platforms, here's what that means for you"). Full treatment: objection prevention.

Why this list is not enough, and we'd rather say so

You can read this page in ten minutes and you will still freeze. That is not a knock on the page, it is the nature of the problem. Objection handling looks like knowledge and behaves like reflex. The gap between the two is the few seconds between the buyer finishing their sentence and you starting yours. In that window you have to notice which objection it was, remember which of the fourteen it maps to, pick the opening question, and say it in a voice that sounds like a person rather than a script. Reps pass the roleplay on Tuesday and freeze on Thursday, and everyone in sales management has watched it happen.

Which is the whole reason this company exists. Objeq is a Chrome extension that sits next to the call, hears both sides through the browser tab, works out which of the five fears the buyer just expressed, and writes one line on the rep's screen for them to say. Only the rep sees it. It works on Meet, Zoom, Teams and browser dialers like GoHighLevel, in Hebrew and in English. $99 a seat a month for Starter, $149 for Pro, 3-day trial. If you'd rather compare it against the tools you already know, start with the best real-time sales coaching tools or Objeq vs Gong.

FAQ

What is the best way to handle a sales objection?

Don't answer the words, find out what they're protecting, and do it with a question rather than a rebuttal. Acknowledge, ask one separating question, then answer. The most common mistake is the opposite order: hearing "it's too expensive" and defending the price, when the buyer was protecting themselves from being blamed for a bad decision.

How many sales objections are there really?

The wording is endless, the fear underneath is not. Objeq's engine sorts every objection into five families: The Gap, The Puzzle, The Loop, The Scar and The Alibi. Each is defined by a sentence the buyer never says out loud. Five is learnable in an afternoon. A hundred is not learnable at all.

What should you never say when handling an objection?

"Sure, take your time", which agrees the call is over. "We're different", to a buyer who was burned before. Anything that attacks the incumbent, because the buyer chose the incumbent. And "we work with leading companies", said by a company nobody has heard of.

Is objection handling a script or a skill?

Both, and confusing them is why objection training rarely survives contact with a call. The opening move is close to scriptable, which is why this page can give you one per objection. What happens after the buyer answers is not. Scripts are learned in quiet rooms, objections arrive mid-sentence.

Does Objeq work in Hebrew?

Yes, natively rather than translated: live transcription, objection detection and the whisper itself. Roughly 99% of real Objeq usage today is Hebrew calls. English is fully supported too, and this page is written in it.

Sources on this page: the five fear families, their internal tags and the sentence under each one are taken from Objeq's own fear map, the single file the live engine, the rep dashboard and the Chrome extension all read their labels from. The fourteen treatments are condensed from Objeq's published objection playbook, one article per objection, each linked above. Prices and trial terms are Objeq's own, listed on the pricing page. No third-party statistic is quoted on this page, because we could not verify one we were willing to stand behind.