Handling objections from what your customers actually say

Almost every sales team has an objection document. Twenty or so lines, “it's too expensive”, “we don't have time”, “we already have a tool”, each followed by a well turned answer. It was written one afternoon by whoever sold best at the time, and it has hardly been opened since.

The problem is not the quality of the answers. It is that the objections come from the seller's imagination, not from customers' mouths. And in the field, a customer almost never says “it's too expensive” the way the document expected.

Why generic objection lists fail

A generic list has three flaws, and they add up.

• It is written on the customer's behalf. The wordings are the ones the seller imagines, so they are clean, direct and easy to counter. Real objections are fuzzier: “I need to see how it fits with everything else”, “we are not sure it is the right time for the team”.
• It handles the stated objection, not the real one. “It's too expensive” can mean the value has not been shown, the budget sits elsewhere, or the person cannot sign. Three situations, three different answers, one line in the document.
• It does not say what works. A written answer has never been tested. Nobody knows whether it ever moved a single conversation forward, or with which kind of customer.

An objection you have never heard in those words teaches you nothing. The one your customers repeat in their own words teaches you almost everything.

The material already exists: it is in your calls. Every discovery, every demo, every negotiation holds objections voiced by real buyers, and answers that did, or did not, move the exchange forward.

Building your objection map from your calls

An objection map is not a list of answers. It is a record of what was said, classified, then linked to what happened next. Five steps are enough.

1. Capture the exact wording

Write down the sentence the way the customer said it, not your summary. “Too expensive” is a summary. “For a team of six, that is a lot compared to what we pay today” is an objection: it holds a team size, a comparison and a reference point.

Keep the minimum context too: which customer, which type of exchange, at what point in the call. Without it, the sentence no longer reads six months later.

2. Classify by family

Six families cover most objections in B2B sales. They are there to group, not to box in: one sentence can belong to two families.

• Price: the amount, the billing model, the comparison with what is in place.
• Timing: not now, after next quarter, once some project is done.
• Trust: the size of your company, data security, references in the sector.
• Status quo: “we get by with spreadsheets”, “it's not a priority”.
• Competitor: a tool already in place, a competing offer, a long standing supplier.
• Internal decision: another department's budget, a committee, someone who was not on the call.

3. Look for the objection behind the objection

The stated objection is rarely the real one. It is often the easiest one to say. The table below gives common readings and a question to check them, as an illustration: the right reading always depends on the call.

4. Note what moved the conversation forward

This is the step almost nobody takes, and it is the most useful one. For each objection you capture, look at what followed in the call: did the customer pick it up, ask a concrete question, agree to a next step? Or did the conversation cool down?

Tell apart an objection that was handled, where the answer led to something other than silence, from one that was merely answered, where you spoke and the customer moved on without being convinced. In the moment, the two look alike. On review, they look nothing alike.

After a few dozen calls, you know which answers really work. They are often different from the ones in the original document.

5. Measure frequency by persona and by stage

An objection does not weigh the same everywhere. Price can dominate with small teams and nearly vanish with larger ones, where the internal decision takes all the room. Trust can weigh during discovery and fade after the demo.

So count objections by group of customers and by stage of the cycle. That split is what tells you what to prepare before a given call, rather than one list meant to fit everyone.

A method to answer: acknowledge, dig, reframe, confirm

Once the real objection is identified, the answer almost always follows the same four beat movement.

• Acknowledge. Rephrase without contradicting. The customer should feel their objection was heard, not that it triggered a prepared comeback.
• Dig. Ask a question before answering. That question is what brings out the real objection, and it saves you from answering the wrong one.
• Reframe with customer proof. Answer with what a comparable customer said or went through, in their own words if possible. A peer's sentence weighs more than your pitch.
• Confirm. Check that the answer landed: “Does that answer your question, or is there something left?” Without this step, you do not know whether the objection was handled or just set aside.

Illustrative example: a price objection

The following dialogue is an illustration, not the transcript of a real call.

Customer: “For a team of six, that is a lot compared to what we pay today.”

Seller: “I understand, you are comparing it with your current tool. What do you pay today, and what does it cover?”

Customer: “Not much, to be honest. We rewrite the call notes by hand after every call.”

Seller: “A customer of a similar size told us exactly that: their team spent the end of each day writing notes nobody read. How much time does it take you? And is that the point that matters most in your comparison?”

The stated objection was about price. The real one was about a value nobody had quantified. The question brought it out, the customer proof reframed it, and the last question checks that it landed.

Illustrative example: a timing objection

Customer: “It's interesting, but get back to us in January.”

Seller: “Understood. What will be different in January?”

Customer: “Our new head of sales starts then, and they will make the call.”

Here, timing was hiding an internal decision. The right next step is not a follow-up in three months: it is to offer a conversation with the incoming person, or to prepare what they will want to see.

From a frozen script to a living map

Keeping the playbook alive: one review a month

An objection map goes stale. A new competitor appears, a price change shifts the objections, a new segment brings its own. A one hour monthly review is enough to keep it accurate, around five questions.

• Which objections appeared this month, and which disappeared?
• Which come up most, and with which customers?
• Which answers moved the exchange forward, with the customer's exact sentence?
• Which competitors are mentioned, and in what terms?
• What do we remove from the playbook because nobody says it anymore?

Doing this by hand means listening back to hours of calls. That is why we do it for you: every exchange is transcribed then analysed, and the passages where the customer objects, where the objection is handled and where a competitor is mentioned are tagged. The assistant can then count which objections come up most, citing for each one the exact passages the count comes from. And personas show the recurring themes of each group of customers, in their own words.

The decision stays yours: a tag is a suggestion, and the team chooses which answer goes into the playbook.

Checklist

• Capture the customer's exact sentence, not your summary.
• Put it in a family: price, timing, trust, status quo, competitor, internal decision.
• Write down the real objection you suspect behind it, and the question that checks it.
• Note whether the answer moved the exchange forward or not.
• Count objections by persona and by stage of the cycle.
• Keep in the playbook the answers that worked, with the customer sentence that proves it.
• Review the map once a month, and remove what nobody says anymore.

The best objection document is not the best written one. It is the one where every line comes from a real call, and every answer has already proved itself.