The Objection-Handling Library
Objections are not random. The same handful come up on almost every deal. Handle them off the cuff and the same objection sinks deals at the same point, again and again, because the best answer lives in one person's head.
The cost of not having one
When objections are handled on instinct, the same one lands differently on every call. One rep has a great answer to “it's too expensive”, another fumbles it, and you lose deals at the exact same point without realising it is always the same point.
A library fixes that: the recurring objections, with the response that actually works, written down and used by everyone. It does not just save deals, it turns your best person's instinct into something the whole team can run.
What good looks like
This is the standard. A real objection-handling library:
- Is built from the objections you actually hear. Your real, recurring ones in the prospect's own words, not a textbook list.“It's too expensive”, “now's not the time”, “we already use X”.
- Has one agreed best response for each. The answer that actually works, so every rep handles it the same way.Not five options, the one that wins.
- Understands before it answers. Each response starts by clarifying the real concern, not by arguing back.“Too expensive compared to what?” before any defence of price.
- Separates a real objection from a no. It helps the rep tell a genuine concern from a polite brush-off, and respond differently.“I need to think about it” usually hides a specific worry.
- Is used and kept alive. A living document the team actually opens, and adds to as new objections appear.A new objection on a call, captured the same week.
The test: a new hire facing your most common objection would give the same strong answer your best closer would.
What it looks like in practice
Here is a worked set for a B2B service business. The value is in the middle column, the real concern behind the words, which is what tells you how to respond.
Three questions to build yours:
- What are the three objections you hear on almost every deal?
- For each, what is the response that has actually worked, not the one you wish worked?
- Which “objections” are really just polite ways of saying no, and how do you tell?
How to build it yourself
- 1List the objections you actually hear. Go through your last twenty deals and write down the objections in the prospect's own words. The list is shorter than you think.
- 2Sort the real ones from the brush-offs. Mark which are genuine concerns and which are polite nos. They need completely different responses.
- 3Write the response that has worked, not the clever one. For each, capture the answer that has actually turned a deal around. Your best closer's real words, not a textbook line.
- 4Lead each response with a question. Start by understanding the concern before you answer it. A clarifying question beats a rebuttal almost every time.
- 5Trace the recurring ones upstream. If the same objection comes up every time, it is usually a gap earlier in the process. Constant price objections mean value was not established in discovery.
- 6Make it a living document. Put it where the team works, and add to it as new objections appear. A library nobody updates goes stale in a month.
Build it faster with AI
Short on time? Paste this into ChatGPT, Claude, or any AI assistant. It will interview you and produce a first draft. Treat it as a draft, and only that. A model cannot weigh the nuances of how your business actually sells, and it cannot install the process into your CRM or run it for you. But it is a fast way to a solid first version.
You are a B2B sales expert. Help me build an objection-handling library from the objections I actually hear, not a generic list. First, ask me these one at a time, and wait for each answer: 1. What do you sell, and who do you sell it to? 2. What are the objections you hear most often, in the prospect's own words? 3. For each, what have you tried, and what has actually worked? 4. Which of these tend to be real concerns, and which are polite ways of saying no? Then, using my answers, produce: - A short library of my real, recurring objections - For each: what is usually behind it, a clarifying question to ask first, and an agreed response - How to tell a real objection from a brush-off - Which objections point to a weakness earlier in my process (for example, price objections often mean value was not established) Keep it specific to my business and my buyers. No lines that sound like a robot. Do not pad it.
Writing down your objections and the best answers takes an afternoon, and you can do it with the steps above. The value is not the document, it is everyone actually using the best response instead of improvising, and noticing that the same objection keeps coming up because of something earlier in the process. That needs real calls reviewed and the team coached, not a wiki nobody opens. We build the library from your real calls, fold it into your process, and keep it sharp as new objections appear, so deals stop leaking at the same point every time.
Book your 20-minute call →