objection_handling v1.0.0

name: objection_handling description: Handle sales objections live without arguing: hear the real concern behind the words, separate price, timing, trust, fit, authority, and status quo objections, answer with matched and substantiated evidence, confirm the concern is actually resolved, and walk away cleanly when the fit is not there. Use when a prospect pushes back on a call, in email, or in a negotiation, when preparing talk tracks before a call, when reviewing a call where objections derailed the deal, or when running objection practice drills with scoring.

Objection Handling

Purpose

An objection is information, not a fight. The first words are rarely the whole concern, and answering the surface words with a rebuttal usually answers the wrong thing, fast.

This skill gives one live sequence that works across objection types, a map for each type so the response matches the real concern, an evidence rule that keeps claims honest, a clear walk away test, and a scored drill so reps practice against a rubric instead of against hope.

Two ideas sit underneath everything here:

• Sequence matters. Carew International teaches LAER: Listen, Acknowledge, Explore, Respond, in that order. Its LAER-B assessment work notes that using the steps out of order lands badly. Responding before acknowledging can feel like steamrolling the buyer before their concern is even fully stated.
• Prevention beats handling. In SPIN Selling, Neil Rackham argues that many objections are created by the seller: presenting solutions too early, and leading with features and advantages before a need is explicit, invites pushback. Developing the need first, with Problem, Implication, and Need-Payoff questions, prevents a large share of objections from forming at all.

Full maps by type: references/objection-maps.md. Worked talk tracks: references/talk-tracks.md. Drill scorer: scripts/objection_drill.py. Practice response template: assets/practice-response.md.

Workflow

1. Triage before you respond

Classify what just happened in the first few seconds. The right move differs completely.

• Brush-off: short, flat, no detail. Examples: "We are all set." "Send me something." "Not interested." Goal is exit or deferral, not information. Do not pitch into it. Ask one short sorting question, then honor the answer: "Is that the topic, or the timing?" If they will not engage, close cleanly and log it as no interest, not as an objection you handled.
• Concern: specific, tied to the deal, and the buyer stays engaged when you ask about it. Examples: worry about implementation time, security review, a past vendor failure. This is the only kind the full sequence below is built for.
• Condition: a hard blocker that no talk track removes. No budget holder exists, a contract locks them in until a stated date, a required capability is missing, a legal or compliance bar applies. Name it as a condition, agree what would have to change, set a dated check back or walk away. Arguing with a condition burns trust and time.

If you cannot tell which one it is, ask: "Help me sort this. Is this a concern we could work through, or is something fixed that blocks this either way?" Their answer routes the rest of the call.

2. Run LAER, in order, out loud

1. Listen. Let them finish. Do not interrupt, do not start building your counter while they talk, and leave a short pause after they stop. Take notes in their words.
2. Acknowledge. Play the concern back accurately and grant that it makes sense on their facts. "Implementation risk is a fair thing to pin down before anything else, given the last migration." Acknowledging is not agreeing that they are right about your product. It is proof that you heard the actual concern.
3. Explore. Ask open questions until you can state the real concern in one sentence and they confirm it. Useful stems are in the maps. Keep exploring while the answer is still a label ("too expensive") rather than a fact ("finance capped this line at half that, and I cannot move it until January").
4. Respond. Only now answer, and answer the confirmed concern, with evidence matched to that type (step 4 below). Reference what they said in Explore, tie it to the goal they stated earlier, then check: "Does that cover it, or is part of it still open?"

Skipping Explore is the most common failure. A price answer given to a trust concern, or a feature answer given to a timing concern, reads as not listening, because it is not listening.

3. Classify the concern and find the one underneath

Sort the confirmed concern into one primary type. Types overlap, so pick the one the buyer would pick.

• Price and value: the number versus what they believe they get for it.
• Budget and authority: money is not allocated, or the person who can allocate it is not in the room. Different problem from price. A discount does not fix either one.
• Timing: not now, next quarter, after another project. Often a priority ranking in disguise.
• Trust and risk: they do not yet believe it works, that your firm will deliver, or that switching is safe.
• Fit and need: they do not see a gap worth closing, or the product genuinely does not do what they need.
• Competition and status quo: an incumbent, an internal build, or doing nothing. Doing nothing is the competitor in most stalled deals.

Then run the isolation check before you invest in a long answer: "If we could sort this one out to your satisfaction, is there anything else that would stop you moving ahead?" A yes to moving ahead makes the concern real and worth working. A new concern surfacing means you had not found the real one yet. Explore the new one. Do not stack answers to three concerns at once.

4. Answer with evidence matched to the type

Match the proof to the concern. Relevance beats volume.

• Price and value: the cost of the current problem in their numbers, scope options that change the price honestly, what is included that they assumed was extra. Never invent an ROI figure. If the return case rests on their numbers, do the math in front of them and label every assumption.
• Budget and authority: phased scope, a dated budget event, and material the buyer can use internally: a short summary of problem, cost of inaction, and proposed step, written for the person who is not in the room.
• Timing: the cost of waiting until their proposed date, a smaller first step that fits the current constraint, or agreement that later is genuinely right, with a dated reason to reopen.
• Trust and risk: verifiable proof. Named customers only where you have permission to name them, current certifications and security documents, a pilot with agreed success criteria, references the buyer can call, contract terms that share the risk. Per FTC guidance, testimonials are not substantiation, and you cannot make a claim through a testimonial that you could not substantiate directly. Treat a testimonial as a story that points to proof, never as the proof itself.
• Fit and need: a direct capability answer, including "it does not do that" when that is true, plus the workaround if one honestly exists and its limits.
• Competition and status quo: the specific difference that matters for their stated criteria, migration effort stated plainly, and the cost of the current setup in their terms. No disparagement and no invented competitor claims. If you do not know a competitor fact, say so and offer to check.

Evidence rules for every type: specific over vague, sourced over remembered, recent over old, and "I do not know, I will check and come back by [time]" over a confident guess. A claim you cannot back on request does not go in the response.

5. Confirm, then advance, park, or walk away

After your answer, confirm in words. Silence is not resolution. "Has that settled that concern, or is some of it still live?" If part is still live, return to Explore on that part only.

Then take exactly one of three exits:

• Advance: agree a specific next step with a date, an owner, and who else attends. "Next step" with no date is not an advance.
• Park: the concern is real and currently unresolvable, but a dated trigger could change it. Agree the trigger, the reopen date, and what you will send in between, if anything. Log it as parked with a reason, not as an open opportunity drifting.
• Walk away: apply the test in Operating Rules. Say it plainly, leave the door open without pretending, and log the real reason so marketing and product learn from it.

6. Log it the same day, in the buyer's words

Record for each objection: the exact words, the type you finally confirmed, whether it was a brush-off, concern, or condition, what evidence you used, whether it resolved, and the exit taken. Keep your inference on a separate line marked as inference.

Review the log monthly by type. A rising count in one type is a prevention problem, not a talk track problem. Price objections clustering usually means needs are being developed too thinly before pricing. Trust objections clustering usually means proof is arriving too late in the cycle. Feed the pattern back into discovery, not into longer rebuttal scripts.

7. Practice with scored drills

Use assets/practice-response.md for each drill round. The rep writes or records the full response to one objection from the maps, following LAER in order, with real evidence named and a confirm question at the end. Score it:

bash
python3 scripts/objection_drill.py assets/practice-response.md
python3 scripts/objection_drill.py --demo

The scorer checks sequence order, whether Explore contains a real question, whether evidence is named, whether a confirm step exists, response length, and whether banned pressure or invented-claim language appears. It scores mechanics only. A human or a reviewing agent still judges whether the answer is true and whether it matches the concern. Run three rounds per objection type, re-score after each rewrite, and keep the best-scoring true version in the team talk track file.

Output Contract

For a live or reviewed objection, produce:

• Objection record: buyer words verbatim, triage call (brush-off, concern, or condition), confirmed type, the real concern in one sentence, evidence used with its source, confirm result, and exit (advance with date, park with trigger and date, or walk away with reason).
• Talk track addition, only if the response worked and was verified true: the objection, the explore question that found the real concern, and the response in plain words, filed under its type in references/talk-tracks.md format.
• Drill result, when practicing: the scorer output plus a one line human judgment on truth and fit, and the score of the final round.
• Prevention note, when a pattern shows up: the type clustering, the earlier stage where it should be handled, and the discovery change proposed.

Operating Rules

• Never argue with the feeling, never interrupt, and never answer before Explore confirms what the concern actually is.
• Never reflexively discount. A price cut offered before the concern is confirmed teaches the buyer that the first price was not real, and it does nothing for budget, authority, timing, or trust concerns.
• Walk away when any of these hold: a required capability is missing with no honest workaround, no one with authority will engage after a genuine attempt to reach them, the budget condition cannot change on any date the buyer can name, the buyer asks you to misrepresent the product or the terms, or the same concern has been confirmed resolved twice and returns as a reason not to decide, with no new fact behind it. Walking away is a result, not a failure. Report it as one.
• Do not use pressure closes, artificial deadlines, or invented scarcity to push past an objection. If a deadline is real, state its source. If it is not, do not imply one.
• Cap live handling at the confirmed concerns the buyer will engage with. If a buyer raises a new objection each time one is resolved, name the pattern kindly and ask what would actually let them decide. If nothing would, take the walk away exit.
• Keep every claim substantiated and checkable. No invented numbers, customers, certifications, or competitor facts, and no guaranteed outcomes.
• Adapt the wording to the buyer and the channel. The sequence, the isolation check, and the confirm step do not change between a call, a video meeting, and email. In email, write the four LAER steps as separate short paragraphs so the buyer can see each one.