Your reps do not need another objection script

I have never been convinced by the usual objection-handling exercise.

Someone plays the buyer and says, "It is too expensive." The sales rep reaches for a line they were taught. The manager decides whether the response sounded confident. Then everyone moves on to the next objection.

It looks like practice, but very little has been learned. Nobody stopped to ask what "too expensive" meant in that particular conversation.

Maybe the buyer genuinely does not have the budget. Maybe they have not seen enough value. Maybe they are worried about implementation and using price as safer ground. Or maybe they simply want to see how quickly the rep will offer a discount.

Those are four different conversations. Giving them one polished answer is not objection handling. It is guessing.

The problem starts with the word handling

We often talk about handling an objection as if the objection were something in the way. Get past it, neutralise it, move the deal forward.

Buyers can feel that mindset immediately. They say something important and, before they have finished explaining it, the rep starts answering. The response may be technically good. It may even come from the company playbook. But it lands badly because it answers the wrong problem.

I would rather see a rep become curious.

"When you say it feels expensive, what are you comparing it with?"

That question is not clever. It does not need to be. Its job is to slow the conversation down and make the objection more specific.

The buyer might be comparing your price with a competitor, with doing nothing, with an internal solution, or with a budget set before they understood the scope. Until you know which one, there is very little worth defending.

The same words can mean very different things

Consider a phrase every salesperson has heard.

"Send me some information."

It could mean the buyer is interested but needs something concrete to share with a colleague. It could mean the explanation was too vague. It could mean the timing is wrong. It could also be a polite way to end the call.

A scripted rep hears the phrase and sends the standard deck.

A thoughtful rep tries to understand what should happen next.

"Of course. What question would the information need to answer for this to be worth continuing?"

The wording can change. The important part is that the rep does not pretend all versions of "send me something" are the same.

Price objections work the same way. So do competitor objections, requests to think about it, and the familiar "we are happy with our current supplier." The surface language is only the beginning.

Listen before you solve

In most cases, the rep does not need a better rebuttal. They need one more useful piece of information.

There are a few questions I would much rather hear than a rehearsed response:

• "What is the main concern behind that?"
• "Compared with what you expected, where does it feel off?"
• "What would need to be true for this to make sense?"
• "Is this something you want to solve now, or is the priority simply elsewhere?"

None of these questions should be used mechanically. A question that ignores what the buyer has just said will sound as scripted as any rebuttal.

The rep still has to listen, decide what matters, and ask the question that belongs in that moment. That judgement is the skill.

Not every objection should be overcome

This part is often missing from sales training.

Sometimes the buyer is right. The product is too expensive for the value they would receive. A required feature is missing. The timing is genuinely poor. The person on the call has no reason to prioritise the problem.

Good objection handling does not mean dragging every conversation towards a yes. It means finding out whether there is a real path forward.

If there is, explore it. If the objection reveals a mismatch that cannot be fixed, say so. A clean no is better than three months of vague follow-ups and a forecast nobody trusts.

This is also where managers need to be careful with feedback. A rep should not receive a low score simply because the buyer did not agree. Sometimes the most commercially mature response is to stop pushing.

What realistic practice looks like

A useful roleplay needs more than an objection written on a card.

The person playing the buyer should know why they are objecting, what they are not saying yet, and what would make them open up. The rep should receive only the information they would realistically have before the conversation.

Take a price conversation.

The weak version says: "The buyer thinks the price is too high. Handle the objection."

The stronger version gives the buyer a reason. Their CFO has frozen new software spending until next quarter. They like the solution, but they are nervous about asking for an exception after another implementation went badly. They will talk about price first because admitting the internal risk feels uncomfortable.

Now the rep has something real to discover. If they immediately discount, they miss the point. If they ask about the decision, the timing, and what happened with the previous implementation, the conversation changes.

That is much closer to the job.

Build practice from conversations your team actually has

The best material is probably already inside the business.

Look at deals that stalled. Listen to calls where the energy changed. Ask reps which moments they dread. Speak with customer success about the conversations that become tense after the contract is signed. Then remove anything confidential and rebuild those moments as practice.

For each scenario, keep the brief simple:

• What does the buyer say first?
• What is really behind it?
• What information will they share if the rep asks well?
• What will make them lose trust?
• What would a credible next step look like?

You do not need a script for the rep. In fact, giving them one defeats the purpose. Give them an objective, enough context to begin, and a counterpart who behaves like a person rather than an objection machine.

Afterwards, the feedback should focus on observable choices. Did the rep acknowledge the concern? Did they ask before answering? Did their response fit what the buyer actually said? Did they force a next step, or agree one that made sense?

Then run it again. The second attempt is often where the learning happens.

Where AI practice helps

This is one of the places where AI roleplay can genuinely be useful. Not because AI has a magic response to every objection, but because a rep can try the same difficult moment more than once.

They can hear how a memorised line lands. They can ask a better question. They can take a different route and compare the result. A manager does not have to play the reluctant buyer for every person on the team, and nobody has to perform badly in front of their colleagues before they are ready.

But the quality of the practice still depends on the quality of the scenario. A generic buyer with random resistance teaches generic behaviour. The situation needs a believable reason, a little history, and room for the conversation to move.

That is why we build company-specific scenarios in Negology. The aim is not to teach people a library of perfect answers. It is to help them recognise what is happening, stay present, and make a better decision while the conversation is still alive.

If you are reviewing how your team currently trains, start with one objection from a real deal. Do not write the answer. Write what the buyer might actually mean, and let the rep practise finding out.

For more on building these skills, read our guide to sales communication training. If you want to turn your team's real conversations into realistic practice, explore Negology's sales training solution.