How to Handle Sales Objections (With Word-for-Word Responses)

In short

An objection is the buyer telling you what must be resolved before they can say yes. It is usually a better sign than silence.
Tell a real concern from a reflex before you answer, and do it with a question, never a rebuttal.
Use four steps on every objection: pause, clarify, answer, check. Most lost deals skip the first or the last.
Most price objections are discovery failures: price was raised before the cost of the problem was established.
Review teaches the next call. Only something live can help on the objection that is happening now.

Every rep has a story about the deal that died on one sentence. "It's too expensive." "We're happy with what we have." "Just send me some information." What gets said less often is that the sentence did not kill the deal. What the rep did in the next four seconds did.

This guide is a working method rather than a script to recite. It covers what an objection really is, the five you will hear most, a four-step pattern that works on all of them, and word-for-word responses you can adapt to your own product and voice.

What an objection really is

An objection is a buyer telling you something they need resolved before they can say yes. That makes it, awkwardly, a good sign: people do not object to things they have stopped thinking about. The deals to worry about are the ones that end in a polite silence.

There are two kinds, and telling them apart is most of the skill. A concern is a real condition: "we would need it to work with our CRM." A reflex is the buyer protecting their time from a stranger: "we're not looking right now," "just send me something." Treat a reflex like a concern and you end up arguing with a wall. Treat a concern like a reflex and you steamroll a buyer who was about to tell you exactly what they need.

You cannot tell which one you are facing from the sentence alone, which is why the first move is always a question and never an answer.

The five objections you will hear most

Objection	What it sounds like	What it usually means	First move
Price	"That's more than we expected."	Value has not been tied to a cost the buyer feels today, or budget has not been discussed	Ask what they were expecting and what they are comparing it with
Timing	"Not now, maybe next quarter."	Either a real constraint or a polite no	Ask what would have to be true next quarter that is not true today
Authority	"I need to run this by my boss."	You are not talking to the decision-maker, or the person you are talking to is not yet convinced	Ask how decisions like this normally get made, and who else cares about the problem
Status quo	"We're fine with what we do now."	The cost of the current way has not been made visible	Ask what happens when the current way goes wrong
Competitor or trust	"We're already talking to someone else."	They are comparing options, which means they are in the market	Ask what they like about the other option and what would make them choose differently

A four-step method that works on any of them

Pause, clarify, answer, check. It is deliberately boring, because the point is that you can run it while your pulse is up.

1. Pause

Do not answer inside the objection. A one-second pause does two things: it keeps you from reciting a rebuttal to the wrong question, and it shows the buyer you heard them. Answering instantly signals that you have heard this a thousand times, which is exactly how it lands.

2. Clarify

Ask one question that turns the objection into information. "When you say expensive, what are you comparing it with?" "Help me understand: is it the amount, or whether it would pay back?" "What would you need to see to feel comfortable?" The answer tells you whether you are facing a concern or a reflex, and which layer of the objection you are on.

3. Answer

Answer the real objection, not the surface one, in a sentence or two, with something specific: a figure from the buyer's own situation, a customer example you are entitled to cite, a way to reduce their risk. Then stop talking. The silence after a good answer is not yours to fill.

4. Check

"Does that address it, or is there more behind it?" Objections come in layers, and the first one is rarely the last. Skip the check and the second layer surfaces two weeks later in a quiet email thread, where you cannot do anything about it.

Word-for-word responses

Adapt these to your own voice and product. They work because each one starts with a question and ends with a next step, not because of the exact words.

"It's too expensive"

"That's fair, and I'd rather you say it now. Can I ask what you were expecting, and what you're comparing it with?" Then, depending on the answer: "If we could show it pays back inside the timeframe you care about, would the number still be the issue?"

Do not discount first. A discount offered before value is established teaches the buyer that the price was negotiable all along, and that your first number was not real.

"Not now, maybe next quarter"

"Makes sense. What changes between now and next quarter?" If the answer is something real, such as a budget cycle or a project finishing: "Then let's put a date in the calendar for when that happens, and I'll send what you'll need by then." If the answer is vague: "Is it that the timing is wrong, or that it isn't a priority? Either is fine to say."

"Just send me some information"

"Happy to. So I send the right thing, what would you most want to be able to tell your team after reading it?" That question usually surfaces either the real interest or the real no. Then: "I'll send that today. Can we agree a time to talk it through, so it doesn't sit in your inbox?"

"I need to talk to my boss"

"Of course. What do you think they'll ask?" Then: "Would it help if I joined that conversation, or if I put the answers to those questions in a page you can forward?" You are doing two things: finding out what the decision-maker cares about, and finding out whether this person can actually sell it internally.

"We already use someone else"

"Good, that tells me you've already decided this matters. What's working well with them?" Then: "And if you could change one thing?" Never attack the incumbent. Every minute spent criticising them is a minute the buyer spends defending a choice they made.

"We're fine as we are"

"Fair enough. Can I ask what happens today when [the problem you solve] goes wrong?" The status quo is rarely as comfortable as it is described. Your job is not to disagree; it is to let the buyer describe the last time it cost them something.

Mistakes that quietly lose the deal

Arguing. Winning the point produces a buyer who lost it, and who goes quiet.
Answering the surface. A price objection that is really "I'm not sure this works" gets a discount instead of proof.
Discounting first. It answers a question the buyer did not ask and gives away margin for nothing.
Raising price before pain. Most price objections are discovery failures: the number arrived before the buyer had said, in their own words, what the problem costs. See discovery call questions that actually qualify.
Talking too long. A ninety-second reply to a one-line objection reads as defensive.
Skipping the check. Layered objections are not resolved by answering the first layer.

Objection handling live versus in the review

Reviewing recorded calls is how a team learns which objections it hears and which answers work, and it is worth doing every week. What review cannot do is help with the objection that is happening now. By the time anyone has watched the clip, the buyer has decided what the next step is.

That gap is what a live copilot is for. Crack Sales listens to the call through system audio, so nothing joins the meeting, and when an objection lands (it reads price, timing and knee-jerk objections, among other signals) it shows one line, inside a 1.3-second budget, grounded in your own Sales Brain: the objections your buyers actually raise and the proof you are allowed to cite. The rep still decides what to say. How it works, including what it deliberately does not do.

Build an objection library from real calls

Write down the objections your reps actually hear, in the buyer's own words, and rank them by how often they come up. For each one, keep the best answer, the proof behind it, and the follow-up question. Revisit it monthly. A library built from real calls beats one built in a workshop, because buyers never object in the words the workshop predicted.

In Crack Sales the same idea runs automatically: questions a rep could not answer on a call are collected as gaps, and the Sales Brain is rewritten from them each week, so the next call starts from a better library than the last one did. Why that loop matters.

A one-page checklist

Pause for a second before answering.
Clarify with one question, not a rebuttal.
Decide whether it is a concern or a reflex.
Answer the real objection in a sentence or two, with something specific, then stop.
Check: "Does that address it, or is there more behind it?"
Before you hang up, agree the next step with a date.

Try it on your own calls

Reading about objection handling is not the same as doing it at speaking speed. If you want to see what a live suggestion looks like on your own pipeline, Book a demo for a 15-minute intro call. A free 21-day trial on your own calls starts after it, and here is how the trial works.

Frequently asked questions

What is the best way to handle a price objection?

Ask what the buyer is comparing the price with before you respond, tie the number to the cost of the problem in their own words, and do not discount first. If the objection is really about confidence that the product works, more proof will help and a lower price will not.

How many objections are normal on a sales call?

There is no reliable universal number; it varies with deal size, stage and the buyer. What matters more is whether each objection is acknowledged, clarified and checked, rather than dropped. Counting objections handled versus dropped on your own calls is far more useful than comparing against a benchmark.

Should I address objections before the buyer raises them?

Sometimes. If you know a concern is common in your market, such as security review or integration effort, a brief mention in your agenda can save a stalled deal later. Do not invent objections the buyer has not shown signs of having.

Try it on your own calls

A free 21-day trial on your own sales calls starts after a 15-minute intro call. Book a demo or read how the trial works.

Keep reading

Home · Product · Solutions · Pricing · Help centre · FAQ · Blog · Security · Privacy · Terms