Objection Handling

An objection is information: the buyer is telling you what stands between them and a yes. Most poor handling comes from answering the words instead of the concern behind them. You slow down, find the real issue, answer it with truth and evidence, and check it landed. The standard: no argument, no pressure, no invented proof, no promise the owner has not approved, and a clear next step even when the answer is "not now".

When to use

• "They said it's too expensive; how do I reply?"
• "Prospect says they're happy with their current supplier."
• "Their IT team is worried about security."
• "Write responses to our top objections for the team."
• Reviewing call notes where the deal stalled on a specific concern.

What you need

• The exact words of the objection and the context: who said it, when, at what stage, what came before. From call notes, the email thread or the owner.
• The deal record: discovery notes, pains, metrics, competitors (see discovery-qualification if not scored yet).
• Approved proof: case studies, references, security documents, product facts, pricing rules and discount authority, from memory or the owner.
• The team's objection library if one exists.

Method

1. Classify the objection.
   • Brush-off: a reflex to end the conversation, usually early ("send me some info", "not interested", "we're all set"). Needs curiosity, not a rebuttal.
   • Real objection: a genuine concern that can be resolved with information, proof or a change in approach.
   • Condition: a true constraint you cannot change (no budget until next fiscal year, legally barred, the product genuinely cannot do it). Do not fight a condition; plan around it or disqualify honestly.
2. Find the real concern with the sequence listen, acknowledge, explore, respond, confirm:
   • Listen to the end without interrupting or preparing a rebuttal.
   • Acknowledge without agreeing or arguing: "That's a fair thing to weigh up."
   • Explore with one or two open questions: "Too expensive compared with what?" "When you say timing, what's happening between now and then?" "What would need to be true for this to be worth it?"
   • Isolate: "If we could sort that out, is there anything else that would stop you going ahead?"
3. Respond to the concern you found, with evidence specific to it.
   • Price. Find which kind it is, then answer that:
     • value gap (they do not believe the return): rebuild the case in their numbers from discovery, conservatively, showing the working;
     • budget timing (money exists later): phase the start or align it to their budget date;
     • comparison (another quote): compare like with like on scope;
     • approval (above someone's signing limit): help the champion build the case for the person who signs. Never cut price to answer a price objection. Changes to price or terms are the owner's decision and are traded for something (see negotiation-prep).
   • Timing or priority. Ask what is more important right now and what this problem costs each month it waits. If it really is lower priority, agree a date to revisit and log it.
   • No need, or happy with the current tool. Ask how they handle the specific pain today and what they would improve. The status quo usually wins unless the cost of inaction is clear; if it is not, accept that.
   • Competitor. Never criticise them. Ask which criteria matter most and how each option scores; offer proof on those criteria. If the competitor is the better fit for this buyer, say so; it earns trust and future referrals.
   • Authority. "Who else will want a say, and what will they care about?" Offer material or a meeting that helps the champion.
   • Risk and trust (security, references, size of company). Provide the real documents (security policy, certifications the owner actually holds, data handling), an approved reference customer, or a pilot with clear success criteria. Never claim a certification, integration or customer you do not have.
   • Missing feature. Ask what they need it for; often the job can be done another way. If it truly cannot, say so. Roadmap statements only with the owner's explicit approval, and without dates unless confirmed.
   • "Send me some information." "Happy to. So it's useful rather than a brochure, what would you want it to answer?"
4. Confirm. "Does that answer the concern, or is there more to it?" If not, go back to explore. Then propose the next step.
5. Draft the reply in the channel it arrived in.
   • Email: acknowledge in one line, ask about or answer the real concern, give the specific proof, one next step. Under 150 words.
   • Call: give the owner the exploring question and two or three talking points, not a script to read.
   • Draft for the owner's approval; never send without it unless a standing permission covers it.
6. Update the library. If this objection is new or your answer improved on the library's, add or edit the entry using references/objection-library.md.
   • Each entry: objection, type, what usually sits behind it, exploring questions, response, proof, what not to say, owner approval date.
   • Count how often each objection appears across deals (from CRM notes via execute_code if there is enough data) and rank the library by frequency.
   • Share updates with the team via brief_team once the owner approves the wording.

Worked example: a price objection by email

Buyer: "Thanks for the proposal. Honestly it's more than we expected."

Diagnosis: discovery notes show a clear pain (15 hours a week of re-planning across 3 sites) but the economic buyer has not seen the business case, and no other quote was mentioned. Most likely a value gap at the approval level, not a comparison.

Draft reply (for the owner's approval):

Thanks for being straight with me, Priya. Can I ask what you were expecting, and whether that's your view or how you think Dan will see it?

When we spoke, you put re-planning at about 15 hours a week across the three sites. At your figure for a planner's hourly cost, that's roughly a year, against for the recommended option. If it would help, I can put that on one page for Dan, with your numbers, so he can check the assumptions himself.

Why it works: it acknowledges without defending, asks what "more than expected" means and whose view it is, rebuilds value in their numbers, and offers to help the champion sell internally. It offers no discount.

Output

• For a live objection: the diagnosis (type and real concern, with the evidence), the reply draft, and the recommended next step.
• For a library request: a ranked library of the top 8 to 12 objections, each in the template format, marked "approved" or "draft".

Checks before you finish

• You know the real concern, or the draft asks for it; you did not answer the surface words.
• Every claim and proof point is true and approved; nothing invented.
• No discount, term, feature or date offered without the owner's approval.
• The reply ends with one clear next step.
• The tone is calm and respectful; no pressure tactics, false urgency or criticism of competitors.

Pitfalls

• Rebutting instantly. A fast counter-argument tells the buyer you were not listening. Ask first.
• Discounting as a reflex. It confirms the price was padded and invites more pushing.
• Winning the argument, losing the deal. The goal is a decision that is right for the buyer, not a debate win.
• Overpromising. "We can build that" or "that's on the roadmap" without approval creates a broken promise later.
• Treating conditions as objections. If the constraint is real, plan around it or step back.
• Library rot. Stale answers about old prices or features do damage. Date every entry and review quarterly.

See also: discovery-qualification, negotiation-prep, sales-follow-up.