Objection Handling

Selling was treated for a long time as a job for people who are good with words. When a customer said no, skill meant finding the sentence that would turn the no around. New hires were handed a single sheet of paper listing the ten refusals that come up most often, each with a prepared answer underneath.

The trouble with that sheet is that it treats everything a customer says as the same kind of thing. Call it a refusal and the salesperson is left with two moves: back off, or cut the price. Sofia at Pagedeck started out doing exactly that. A company of about forty people said they had no budget, she said she would follow up next quarter, and she hung up. Three months later that company bought a similar product at a similar price. The budget had not been missing. What the contact could not produce was a reason to take up the line with his own manager.

A refusal and an objection look alike and are not the same sentence. A real refusal is short and carries no reason. Not interested, and that is the end of it. An objection runs longer and comes with a reason attached. Too expensive, not the right time, we already use something else — each of those arrives with an explanation behind it, and explaining means the decision is still being turned over. Nobody explains a decision they have already closed. Which is why a meeting where no objection came up is usually not a meeting that went well; it is a meeting where the other side never started evaluating. An hour of steady nodding rarely turns into a contract.

There is a second reason objections arrive as vague sentences: the person sitting across the table seldom decides alone. Past a certain company size the choice is made by a working-level contact, that person's manager, a procurement team, and a security reviewer, and that group is called the buying committee. The too-expensive line a contact passes along is often not their own view but a quote from someone who is not in the room, so answering the line as stated reaches nobody who actually objected.

That is why the work has its own name. Objection handling is not a technique for overcoming what someone says; it is a procedure for pulling the real obstacle out from behind the sentence and checking whether it is the kind of obstacle that can be moved. It usually runs in four steps.

1. Let the sentence finish. Start answering halfway through and the other person swallows the condition they were about to add, and the actual reason is frequently inside that condition.
2. Ask what it means. Too expensive can mean there is no budget, or that there is no case to take to whoever signs, or that it loses to something else competing for the same money. Those are three different problems.
3. Bring evidence that fits the problem you confirmed. If the missing piece is a case for the signer, the answer is not a discount but counting up, together, how many hours a month the current way is costing and turning that into a number.
4. Ask whether this is the last obstacle. Put the question as: if this part were solved, could we move ahead? A clear yes leaves one thing to do. A vague answer means there is a reason that has not been said out loud yet.

The five terms under objection handling split into two groups. The types sort customers by what they are stuck on; the technique deals with how to get past the place where they are stuck. The first four are diagnosis and the last one is treatment.

Four terms sit in the types group, and what they catch on is money, timing, change itself, and competition.

1. Price objection — putting the decision off because the price is too high. It comes up more than any other and is taken at face value more often than it should be. If too expensive arrives after a quote of five thousand dollars a year, it can mean there is no five thousand dollars, or it can mean there is no sentence available to explain what that five thousand buys back. For the first, splitting an annual commitment into quarters or starting with fewer seats does the work; for the second, the number stays where it is and the case gets built. Swapping the two is costly. Offer a discount where the blocker was a missing case and the price drops while the approval stays exactly as stuck as before.
2. Timing objection — saying this is not the right moment. Some of these are real: a quarter closing, a reorganization, another system already mid-rollout. Others are just a way of saying it is not urgent. The way to tell them apart is to try to fix the next date. Propose picking it back up the second week of June, when the reorganization ends, and if a date gets agreed it was the first kind. If it comes back as call me later, it was the second, and then the honest problem is urgency rather than timing, so showing what keeps leaking during the delay has to come before any talk of dates.
3. Status quo bias — the pull toward leaving things the way they are. Unlike the first two this is not a judgment about the product but about the cost of switching. People have to learn a new tool, old material has to be moved, and if it goes badly the person who chose carries it. The thing being competed against here is not a rival product. It is doing nothing.
4. Competitor objection — hesitating while weighing another product. It matters whether they already use the other one or are still choosing, because the first case carries a switching cost and the second does not. Either way, running the other product down tends not to work: the customer has already chosen it or thinks well of it, so attacking the product reads as attacking their judgment. What gets used instead is putting the two side by side and talking about which situations suit which, rather than which is better.

One term sits in the technique group.

5. Feel-felt-found — a three-beat pattern of acknowledging the feeling, citing another customer who felt the same way, and reporting what that customer found once they went ahead. You take the concern as reasonable, add that the company that adopted it last spring had the same worry, and close with what turned out to be true two months later. Because it introduces new information without telling anyone they were wrong, it lands especially well where the resistance is to changing at all. The whole thing collapses without a real case in the third beat, though. With nothing concrete to report, the acknowledgment reads as filler and the customer hears a script being followed.

The four types are kept apart because the answers differ. Offer a discount against a timing problem and all the customer learns is that the price has room in it; hand a feature comparison to someone who does not want to switch and the table is one more thing on a desk. In real conversations they overlap, and the sentence that comes out first is often not the one blocking the deal. So before answering, check: asking whether solving this one thing would let them proceed usually reveals whether it is the real obstacle.

"Price isn't really the issue, it's more that now is awkward for us."

Two objections stacked in one sentence. The first half is politeness and the second half is the point, so reaching for a discount here answers a problem the customer never raised.

"Should we count up how many hours a month the current setup is costing you?"

An offer to build the value into a number instead of cutting the price, so the contact has something to carry to the person who signs.

"If that part were solved, you'd be able to move ahead this quarter?"

A check on whether the objection on the table is the last one. An answer that goes soft here means a reason is still being held back.

All three lines came up in order during a conversation between Pagedeck and a company of forty-five people. The discovery call had already established that time lost hunting for documents was the problem, so when too expensive arrived Sofia offered arithmetic instead of a discount. Twelve of the forty-five worked in documents daily, each losing about two hours a week to searching, which came to ninety-six hours a month. The contact wrote the number down, which is usually the sign that the objection has run out.

Then he went quiet at the last question. What remained was not price but a security review. Putting internal documents on an outside service needed sign-off from the information security lead, and that person had been against it from the start. Too expensive had been the sentence a contact reached for because he did not think he could win that argument. What Sofia did next was not adjust the price but assemble the security documentation and get a separate meeting with the reviewer. Without that last question the company would have taken a discount offer and gone quiet, and it would have been logged as lost on price.

The most common mistake is reading objection handling as winning an argument. The word handling sounds like hitting something back, and on days when the comeback lands well the customer adds nothing further, which looks like a win. That silence is not agreement, though. It is a closed conversation. People stop volunteering their remaining concerns once their judgment has been contradicted, so the second objection that never surfaced does not disappear — it goes back inside the company, and a few days later a short note arrives saying they have decided to pass. Deals that die without an explanation usually die this way.

Believing a good list of answers is enough goes wrong just as often. The lines that come back really are fairly predictable, so ten stock sentences with model responses underneath feel like preparation. But the same sentence means different things at different companies. Too expensive holds no budget, no case for the signer, and outranked by something else all at once, and a list answers all three the same way. Deliver a prepared answer without checking and the conversation moves two steps backward: the customer concludes you were not listening, and the salesperson, unable to see why it failed, reaches for a discount next. Money given away that way shrinks the margin without producing a contract. None of which makes the list useless. It just belongs on the side where you pick the question to ask back, not the side where you pick the answer.