sales-objection-handling

{
  "skill_name": "sales-objection-handling",
  "evals": [
    {
      "id": 1,
      "prompt": "I sell Palewright, warehouse inventory software, about $42k a year, to ops directors at mid-market 3PLs. Had a demo Tuesday with the ops director at Norhall Logistics. We booked the call Monday and I demoed Tuesday morning - I didn't really dig into how they run receiving today, I just walked her through the product because she seemed keen. Proposal went out Wednesday. This morning she replied: 'We like it, but honestly it's too expensive for where we are right now.' I've got a follow-up call Thursday. What do I say? We don't have a case study in her vertical and no ROI study of our own yet.",
      "expected_output": "A triage of the price objection into value gap vs genuine budget constraint, a note that the demo preceded need development, and a single rebuttal entry in the seven-field output shape with no invented proof.",
      "files": [],
      "expectations": [
        "Splits 'too expensive' into a value gap and a genuine budget constraint before drafting any script, and states the two need opposite responses",
        "Supplies a triage question asking whether the number doesn't fit this year's budget or whether she is not sure it's worth that number",
        "Flags that the demo preceded any need development and names that as a likely manufactured cause of the price objection",
        "Attributes the finding that sellers create objections, or that features presented early raise price sensitivity, to Rackham or the Huthwaite research",
        "Points the user at the discovery-questions skill (sales-discovery-questions) to fix the upstream gap",
        "Keeps the prevention check to one pass and still answers Thursday's objection rather than converting the reply into a discovery exercise",
        "Delivers a rebuttal entry containing all seven fields: the verbatim objection, what it usually means, the diagnostic question, the response script, the proof point, the hand-back question, and what a repeat means",
        "The response script is between two and five sentences and uses contractions",
        "Invents no case study, customer name, benchmark or savings figure, and states plainly that no proof asset exists for this objection",
        "Uses no Feel-Felt-Found construction anywhere in the scripts",
        "Adds no deadline, price increase, or scarcity claim that the user did not state",
        "On the value-gap branch, instructs the rep to weigh the price against a goal or cost the buyer states in her own words, rather than defending product features"
      ]
    },
    {
      "id": 2,
      "prompt": "Deal at Kestrel Foods, $58k a year. They've cleared security review and legal is done. Their procurement lead emailed this morning: 'We're ready to go but I need 20% off to get this signed this quarter.' I want to keep the deal. One constraint: I can't put a pilot, an opt-out clause or any kind of money-back guarantee on the table without my VP of Sales approving it, and she's on leave until the 30th. Give me my options and what I actually say on the call.",
      "expected_output": "An options set with de-risking removed entirely rather than ranked last, trading at the top, every reduction paired with a reciprocal get, and concession-order planning handed off.",
      "files": [],
      "expectations": [
        "Removes de-risking - pilot, opt-out, guarantee - from the options entirely rather than listing it as a lower-ranked or conditional choice",
        "States why a de-risk option merely ranked last is dangerous: it resurfaces mid-call as a promise the rep is not authorized to make",
        "Puts trading at the top of the remaining options",
        "Pairs every proposed price reduction with a specific reciprocal get such as a longer term, a case study, a reference or intro, or a committed signature date",
        "Never concedes a discount unilaterally",
        "Names at least two costs of discounting beyond the immediate margin, from: it sets the account's floor, it signals the original number was padded, the precedent carries into renewal",
        "Notes a discount still requires deal-desk or internal approval",
        "Hands planning of the full concession order to negotiation-concession-planner rather than improvising a concession ladder in this answer",
        "Includes one diagnostic question that tests what the 20% ask actually stands for before any counter is made",
        "Produces a spoken script with contractions that the rep can say out loud, not an email draft"
      ]
    },
    {
      "id": 3,
      "prompt": "I run a 6-person SDR team selling a payroll tool to HR leads at 50-300 person companies. Most calls die in the first fifteen seconds with 'not interested' or 'just send me something by email'. Two of my reps are eight weeks in and they crumble. Our VP wants me to write a card that makes reps try five separate rebuttals before they're allowed to let a prospect go, and he wants it on the wall by Monday. Write the card.",
      "expected_output": "A refusal to build the five-attempt quota, a reflex-mode card built on the pause and a ledge or agree-disarm-redirect turnaround, capped at one or two attempts, with a graceful exit.",
      "files": [],
      "expectations": [
        "Refuses to build the five-attempt rule and states plainly that a rebuttal quota is off-limits",
        "Gives the reason: a scorecard rewarding pushing past a no creates compliance exposure in consumer channels and can make the script itself the violation",
        "Caps turnaround attempts at one, two at the most",
        "Classifies 'not interested' and 'just send me something' as reflex brush-offs rather than considered objections",
        "States that arguing with a reflex converts it into a real objection",
        "Opens with a ledge - a pre-memorized neutral line - attributed to Jeb Blount, or uses the agree-disarm-redirect shape of the Mr. Miyagi Method",
        "States the goal of the turnaround is the meeting or the next thirty seconds, not the sale",
        "Does not have the rep interrogate the brush-off with a diagnostic question; the response itself is the test",
        "Ranks poke-the-bear below the ledge and the Mr. Miyagi approach for these two eight-week reps, giving the reason that it depends on product knowledge a new rep does not yet have",
        "Includes a graceful-exit line for taking the no",
        "States that a 'take me off your list' or 'stop calling me' ends the conversation with no further angle",
        "Notes the ledge and the Mr. Miyagi approach are equivalent in rehearsal cost and arena, and are chosen on the rep's temperament rather than on merit",
        "Mentions the pause - the magic quarter of a second - before the rep reacts"
      ]
    },
    {
      "id": 4,
      "prompt": "Deal at Vantara Health, $120k ARR, 11 weeks in. The VP of Ops agreed on the value in week 4 and again in week 7. Since then all I get is 'this all looks good, I just need time to think it over' - that's the third time now. My plan for Friday: send three more case studies plus a side-by-side against our two competitors, tell him our list price goes up January 1st (it might, nobody's actually decided), and then just close him again and ask what it's going to take to get this signed. Sanity check my plan?",
      "expected_output": "A re-diagnosis as indecision, rejection of the extra proof, the fake price increase and the re-close, replaced by one recommendation, contained exploration, and a concrete risk-reversal move.",
      "files": [],
      "expectations": [
        "Diagnoses indecision - fear of getting it wrong - rather than a status-quo preference or a hidden competitor",
        "Attributes the indecision finding to The JOLT Effect, or to Dixon and McKenna",
        "States that adding more value, urgency or FOMO makes indecision worse, and rejects the three extra case studies and the comparison matrix on that basis",
        "Rejects the January 1st price increase outright as manufactured urgency because the user said it is not decided",
        "Rejects closing again without answering the stall, naming the deflect-and-close loop as a pressure device rather than a diagnostic one",
        "Replaces the menu of options with one clear, confident recommendation",
        "Limits the exploration by reassuring the buyer he already has enough information to decide",
        "Takes risk off the table with a concrete de-risking move: an opt-out, a guarantee, a phased rollout, or a smaller first commitment",
        "Asserts no specific win-rate percentage for risk-reversal language as an established fact, treating any such figure as directional and correlational",
        "Supplies the confidence question - what he would need to see to feel confident this is the right call - and reads indecision from the shape of the answer rather than its content",
        "States that a fourth 'I need to think about it' calls for shrinking the commitment further or time-boxing it, never more information",
        "The recommendation script is spoken language with contractions, two to five sentences, and carries no marketing adjectives"
      ]
    },
    {
      "id": 5,
      "prompt": "Prospect at Crowmarsh Retail told me: 'We're already on Beacontrail and we're all set.' I've got a battlecard a teammate put together in March that says Beacontrail charges $1,900 per seat per year and has no API. I want to open with that - 'you're overpaying and they'll never integrate with your WMS' - then pivot to us. We do have one customer, Tulloch Grocers, who moved off Beacontrail last year and said so on a recorded reference call. Draft me the response.",
      "expected_output": "An incumbent-objection entry that refuses the trashing opener, marks the unverifiable competitor claims, flags the battlecard as stale, and attaches the single real proof asset.",
      "files": [],
      "expectations": [
        "Names the possible meanings of the incumbent objection rather than answering it directly: genuinely satisfied, satisfied by default because nothing was ever compared, or frustrated but dreading the switching cost",
        "Refuses the competitor-trashing opener and replaces it with a question about how the incumbent is performing in one specific area",
        "Does not assert the $1,900 seat price or the no-API claim as fact, and marks every competitor claim 'verify before use' because current public pricing and packaging cannot be checked here",
        "Flags the March battlecard as stale and states that competitor and pricing entries need refreshing monthly",
        "States that a battlecard carrying stale competitor pricing is worse than none because reps stop trusting the whole library",
        "Uses the Tulloch Grocers switch as the proof point because it is a real named asset the user supplied",
        "Attaches exactly one proof point to the response, and states that stacking several weak proofs reads as desperation",
        "Gives a hand-back question asking how the current setup is working, or what one thing they would change about it",
        "States that a genuinely satisfied and verified incumbent user is a disqualification for now, with a re-entry trigger set on the renewal date",
        "Does not tell the prospect to rip out the incumbent, framing the ask as a short look the buyer judges",
        "Produces the full seven-field rebuttal entry, including what a repeat of the objection means"
      ]
    },
    {
      "id": 6,
      "prompt": "Need three strong rebuttals for a stuck deal so I can keep it in the forecast. Fenwick Marine, about $30k. My contact Dale is a systems analyst, he loves the product and has built the internal case himself. Problem: their fiscal budget was set in June with no line item for anything like this, the CFO froze new software spend until the fiscal year ends next June, and Dale has never met the VP who'd have to carry it upstairs. Nothing is forcing a decision - their current process works badly but it works. Give me the three rebuttals.",
      "expected_output": "A refusal to supply rebuttals, a disqualification with the terms ladder worked through and ruled out, plus a graceful exit script, a re-entry condition and a CRM follow-up date.",
      "files": [],
      "expectations": [
        "Declines to supply the three rebuttals and names the situation as a disqualifying constraint: no budget exists, no path to authority, no compelling event",
        "States explicitly that disqualifying is a valid output rather than a failure, and that a skill which always produces a comeback teaches reps to push dead deals",
        "Works through the budget-constraint terms - phased start, smaller scope, later start date, champion enablement - and explains why each one fails here before landing on disqualification",
        "Notes that a later start date only moves the problem rather than solving it",
        "Notes that champion enablement costs about a week of the rep's own time building someone else's business case, and that Dale has no path to the VP",
        "Produces a graceful exit script",
        "Produces a named re-entry condition tied to an observable change, such as the next fiscal budget cycle or the spend freeze lifting",
        "Produces a specific follow-up date to put in the CRM",
        "Invents no compelling event, deadline or urgency to force the decision",
        "Says plainly that the deal should come out of the active forecast rather than be worked with a script"
      ]
    },
    {
      "id": 7,
      "prompt": "I'm head of enablement at Sarrow, a data quality platform. Average deal is $85k and we have 14 AEs. Two things drive this: procurement is in the room on nearly every deal from the proposal stage onward, and no-decision losses were 41% of everything we closed-lost last quarter, by far the biggest bucket. I want an objection playbook the whole team drills in our Thursday sessions, not a one-off script for someone's live deal. Which frameworks should they actually learn, in what order, and how will I tell whether it's working?",
      "expected_output": "A ranked learning order re-ranked for a compounding team mandate, with the high-effort moves deliberately promoted on the stated conditions, plus an ordered measurement set and library maintenance rules.",
      "files": [],
      "expectations": [
        "Presents the frameworks as an explicitly stated ranked learning order rather than an unordered list",
        "Promotes tactical empathy above its default efficiency rank, citing procurement or an adversarial economic buyer in the room",
        "Promotes the full JOLT play above its default rank, citing no-decision already being the largest loss category",
        "States the general rule that the highest-value, highest-effort moves lose every efficiency round and must be promoted deliberately when the conditions fire",
        "Promotes LAARC, the Sandler up-front contract and JOLT on the grounds this is a compounding team mandate, and states these three pay only once a team drills them",
        "States the up-front contract costs about a week of habit across the whole team and is not worth it for a single call",
        "States that tactical empathy must sequence a label and silence before any calibrated question, because a calibrated question fired first lands as an attack",
        "Orders the measurement set: diagnostic-question rate first, objections-per-call by rep second, no-decision loss rate third, ordered by how fast each returns a signal",
        "States the no-decision loss rate needs roughly a quarter of closed deals before it means anything",
        "States that if the best closers hear materially fewer objections, the fix is upstream sequencing rather than more rebuttal drilling",
        "Gives library maintenance rules: date every entry, source responses from real winning calls rather than invention, refresh competitor and pricing entries monthly",
        "Builds no rebuttal quota or minimum-attempts rule into the drill scorecard"
      ]
    },
    {
      "id": 8,
      "prompt": "In-home solar sales, I run a team of 9 closers in Arizona. The standard stall at the end of the appointment, when only one spouse is home, is 'I need to run it by my wife before we do anything.' Right now my guys say: 'I get it - but I can guarantee you're saving at least $180 a month from day one, and the utility's raising rates next month, so if we lock the paperwork in tonight you're protected.' Then they push for the signature. Tighten this script up for me.",
      "expected_output": "A rewritten script stripping the guaranteed savings and the unverified rate rise, removing the lone-signature push, substituting a written summary and a scheduled two-party conversation, with the compliance-review requirement stated.",
      "files": [],
      "expectations": [
        "Rejects the guaranteed $180 a month savings line as an unsubstantiated savings or guaranteed-return claim that is off-limits in this category",
        "Rejects the 'utility's raising rates next month' line as manufactured urgency unless the increase is published and substantiated",
        "Warns against any wording implying affiliation with the utility or a government program",
        "Names energy or utilities as a regulated category and states explicitly in the output that every script must go through the firm's own compliance review before anyone speaks it",
        "Does not attempt to enumerate the applicable consumer-protection or energy regulations itself, leaving that to the firm's compliance team",
        "Removes the push for a signature from the lone spouse present",
        "States that pressuring one partner to sign alone is the exact pattern consumer-protection rules target",
        "Replaces the close with a written one-page summary of the price and options left behind, plus a scheduled time when both partners are available",
        "Supplies a diagnostic question asking what the absent partner will want to know that has not been covered",
        "Treats the objection as most often a genuinely shared decision rather than assuming it is a brush-off or a relocated price concern",
        "Classifies in-home high-ticket consumer selling as sitting between B2B and B2C: a single household with committee-like dynamics",
        "States what a repeat means: without a scheduled two-party conversation, treat it as a polite no"
      ]
    },
    {
      "id": 9,
      "prompt": "I manage a 4-store furniture chain. New staff freeze when a customer says 'just looking, thanks' - most of the time they nod, walk away, and we lose the sale. I want a three-step rebuttal they can run every single time someone says it, and I'm going to make it a rule that they ask for the sale within 60 seconds of greeting anyone on the floor. Write me the three steps.",
      "expected_output": "A refusal to treat 'just looking' as an objection, a low-pressure non-sales opener instead of a rebuttal sequence, and a rejection of the 60-second rule.",
      "files": [],
      "expectations": [
        "Declines to treat 'just looking' as an objection and states it is a predictable step of a retail visit",
        "Attributes that position to Harry Friedman's retail work",
        "Rejects the rule to ask for the sale within 60 seconds, and states the sale starts later in the visit",
        "Supplies a low-pressure, non-sales opener that lets the browsing continue",
        "Produces no three-step rebuttal sequence as requested",
        "Does not tell staff to argue with or press the customer after the brush-off",
        "Notes that B2C decisions usually sit with one decision-maker, with price and trust dominant and a larger reflex or emotional share than B2B",
        "States that the diagnose-before-you-script rule is identical in B2C and B2B",
        "Writes the opener in spoken language with contractions, short enough to say on a shop floor",
        "Sets no minimum number of approaches or rebuttal attempts per customer"
      ]
    },
    {
      "id": 10,
      "prompt": "Deal at Hollowick Bank, $70k. Week 3 the VP said 'the timing's bad, we're mid-migration'. I offered a Q1 start and he said 'we'd need SOC 2 anyway'. We're SOC 2 Type II so I sent the report. Now he says 'I'd really want to see it work with our ticketing system'. We do not have a native integration with the one they run - realistically it'd be a webhook plus a nightly CSV job. Write me a strong answer for the ticketing question so we can get this moving again.",
      "expected_output": "A re-diagnosis of the shifting objections as a smokescreen, the if-solved test, an honest capability answer naming the webhook-and-CSV reality, and LAARC's guardrails promoted.",
      "files": [],
      "expectations": [
        "Does not answer only the ticketing question, and names the pattern of shifting objections as a smokescreen",
        "States that winning the stated objection leaves the deal dead when the real objection is unaddressed",
        "Supplies the if-solved test - asking whether he would move forward if the ticketing gap were solved - and explains that a 'no' exposes the smokescreen",
        "Classifies the ticketing question as a capability objection rather than a value objection, and prescribes an honest scope answer",
        "States the honest answer includes conceding there is no native integration and describing the webhook plus nightly CSV job as what actually exists",
        "Refuses to bluff or imply a native integration exists, noting the prospect verifies during evaluation and the trust loss outlives the deal",
        "Attributes the value-versus-capability distinction to Rackham",
        "Promotes LAARC over LAER here because an objection the rep declared handled has come back, naming Assess and Confirm as the two added guardrails",
        "Requires an explore or assess step before responding, rather than answering in the same breath the objection lands",
        "States what a third shift means: stop rebutting, re-diagnose, or disqualify",
        "Treats the objections as possibly proxying an absent stakeholder's concern and scripts for the champion's internal case - a one-pager or talking points for his boss - not only the live call"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "prospect says we're too expensive, what do I say on the follow-up call", "should_trigger": true },
    { "query": "how should my reps respond to 'not interested' in the first ten seconds", "should_trigger": true },
    { "query": "they keep telling me they need to think about it, third time now", "should_trigger": true },
    { "query": "build an objection handling playbook for my AE team", "should_trigger": true },
    { "query": "they asked for a discount to sign - should I give it or is there something better to offer", "should_trigger": true },
    { "query": "customer told me they already use a competitor and they're all set", "should_trigger": true },
    { "query": "rebuttal for 'we have no budget this year'", "should_trigger": true },
    { "query": "someone on the phone said 'just send me some info' - how do I turn that around", "should_trigger": true },
    { "query": "write me scripts for the five objections my SDRs hear most", "should_trigger": true },
    { "query": "my deal stalled at 'I need to run it past my wife'", "should_trigger": true },
    { "query": "how do I handle price pushback without discounting", "should_trigger": true },
    { "query": "he said the timing isn't right - is that real or is he blowing me off", "should_trigger": true },
    { "query": "what should I say back when they compare us to a cheaper tool", "should_trigger": true },
    { "query": "objection library for our sales team", "should_trigger": true },
    { "query": "how do I stop losing deals to no decision", "should_trigger": true },
    { "query": "shopper says just looking and my staff freeze", "should_trigger": true },
    { "query": "buyer went quiet after the proposal and now says it's not a priority", "should_trigger": true },
    { "query": "I need a comeback for 'send me a proposal and I'll circulate it'", "should_trigger": true },
    { "query": "help me answer 'we're happy with our current vendor'", "should_trigger": true },
    { "query": "what's the right response when someone says your product is overpriced", "should_trigger": true },
    { "query": "script for the stall at the end of an in-home sales appointment", "should_trigger": true },
    { "query": "how do I know if what they told me is the real reason or a cover story", "should_trigger": true },
    { "query": "prospect raised security concerns that don't match anything else in the deal", "should_trigger": true },
    { "query": "my rep keeps arguing with people who brush him off on the phone", "should_trigger": true },
    { "query": "what do I do when the same objection comes back a second time", "should_trigger": true },
    { "query": "how do I answer a capability question when the honest answer is we can't do it", "should_trigger": true },
    { "query": "we lose deals at the last step, buyer always says they need more time", "should_trigger": true },
    { "query": "help me write what to say when they push back on the price", "should_trigger": true },
    { "query": "coach me through the pushback I'm going to get on Thursday's call", "should_trigger": true },
    { "query": "our closers need better answers for the 'I have to talk to my partner' stall", "should_trigger": true },
    { "query": "how should I respond to 'we already built something internally'", "should_trigger": true },
    { "query": "give me a question to ask before I answer whatever they throw at me", "should_trigger": true },
    { "query": "what do I say when someone says they're not interested", "should_trigger": true },
    { "query": "procurement just said our price is way out of line, what do I say back", "should_trigger": true },
    { "query": "the buyer keeps asking for more information and never decides", "should_trigger": true },
    { "query": "I want a card on the wall with what to say to common brush-offs", "should_trigger": true },
    { "query": "how do I respond when a customer says it costs too much", "should_trigger": true },
    { "query": "what's a good way to handle 'call me back next quarter'", "should_trigger": true },
    { "query": "my team caves on price every time someone pushes", "should_trigger": true },
    { "query": "when do I stop pushing back and just walk away from the deal", "should_trigger": true },
    { "query": "prospect says our competitor is 30% cheaper, what do I say", "should_trigger": true },
    { "query": "how do I keep a cold call alive after the first no", "should_trigger": true },
    { "query": "buyer says they like it but can't get it approved internally", "should_trigger": true },
    { "query": "what do I say when they ask why we cost more than the alternative", "should_trigger": true },
    { "query": "is there a framework for responding to pushback on sales calls", "should_trigger": true },
    { "query": "we've been told no three times, is there a way back in", "should_trigger": true },
    { "query": "help me answer the 'we'll revisit in six months' brush-off", "should_trigger": true },
    { "query": "write the words my rep can actually say when the buyer says it's too much money", "should_trigger": true },
    { "query": "what do I do when someone says they're happy with what they've got", "should_trigger": true },
    { "query": "guy on the phone shut me down in twenty seconds, what now", "should_trigger": true },
    { "query": "write the first 10 seconds of my cold call opener", "should_trigger": false },
    { "query": "opener for cold calling CFOs at manufacturing companies", "should_trigger": false },
    { "query": "what discovery questions should I ask on a first call", "should_trigger": false },
    { "query": "build me a discovery question set for a 30 minute qualification call", "should_trigger": false },
    { "query": "plan which concessions I give and in what order before the procurement negotiation", "should_trigger": false },
    { "query": "build a concession ladder with cost to us versus value to them", "should_trigger": false },
    { "query": "what's my walk-away point and BATNA for this renewal", "should_trigger": false },
    { "query": "build the ROI business case for this deal", "should_trigger": false },
    { "query": "calculate the payback period the CFO will want to see", "should_trigger": false },
    { "query": "score this opportunity against MEDDPICC", "should_trigger": false },
    { "query": "which MEDDPICC elements are still unknown on this deal", "should_trigger": false },
    { "query": "review this call transcript and score how the rep did", "should_trigger": false },
    { "query": "grade my AE's objection handling on this recorded call against our rubric", "should_trigger": false },
    { "query": "turn my call notes into a recap email with next steps", "should_trigger": false },
    { "query": "write the mutual action plan items from yesterday's meeting", "should_trigger": false },
    { "query": "test these five subject lines and tell me which to send", "should_trigger": false },
    { "query": "why are my cold emails landing in spam", "should_trigger": false },
    { "query": "check my SPF and DMARC setup before we start sending", "should_trigger": false },
    { "query": "read these CRM notes and flag the qualification red flags", "should_trigger": false },
    { "query": "who is the actual champion on this deal", "should_trigger": false },
    { "query": "map the buying committee from these email threads", "should_trigger": false },
    { "query": "design the commission plan for our new AE seats", "should_trigger": false },
    { "query": "set next year's quotas for the team", "should_trigger": false },
    { "query": "should we run pods or an assembly line structure", "should_trigger": false },
    { "query": "are we product-led or sales-led and how do we transition", "should_trigger": false },
    { "query": "define our ideal customer profile from closed-won data", "should_trigger": false },
    { "query": "where should the tier cutoffs sit for our named accounts", "should_trigger": false },
    { "query": "build the account segmentation model and the fit score behind it", "should_trigger": false },
    { "query": "estimate the TAM and SAM for the mid-market segment", "should_trigger": false },
    { "query": "how much pipeline coverage do we need to hit the number", "should_trigger": false },
    { "query": "design the touch cadence for a 21 day outbound sequence", "should_trigger": false },
    { "query": "find me personalization angles for this prospect list", "should_trigger": false },
    { "query": "build the interview loop and scorecard for hiring SDRs", "should_trigger": false },
    { "query": "how do I get promoted from SDR to AE", "should_trigger": false },
    { "query": "which sales podcasts and newsletters should I follow", "should_trigger": false },
    { "query": "I'm starting a new sales project, where should I begin", "should_trigger": false },
    { "query": "de-escalation script for angry customers in our support queue", "should_trigger": false },
    { "query": "how do I respond to a one-star app store review", "should_trigger": false },
    { "query": "write counter-arguments for my debate club motion", "should_trigger": false },
    { "query": "handle investor objections during our seed pitch", "should_trigger": false },
    { "query": "my manager pushed back on my roadmap, how do I respond", "should_trigger": false },
    { "query": "how do I object to a question during a deposition", "should_trigger": false },
    { "query": "write the rebuttal to reviewer two on my conference paper", "should_trigger": false },
    { "query": "write the FAQ section for our pricing page", "should_trigger": false },
    { "query": "how do I push back on scope creep from a client on this project plan", "should_trigger": false },
    { "query": "answer the security questionnaire section of this RFP", "should_trigger": false },
    { "query": "customer wants a refund, what's our policy response", "should_trigger": false },
    { "query": "negotiate my salary offer with the hiring manager", "should_trigger": false },
    { "query": "write the renewal reminder sequence for accounts up in 60 days", "should_trigger": false },
    { "query": "draft the win-loss interview questions for deals we lost", "should_trigger": false }
  ]
}

# Response frameworks - what to learn first

Read this while drafting scripts, to pull the exact steps of the mode chosen in SKILL.md. Attribution matters in this field and much of it is folklore; every framework below is verifiably sourced. Treat any objection framework not listed here as unverified, and don't cite it as established.

The order below answers "which one do I memorise before tomorrow's calls", not "which ones exist". Effort here is rehearsal time, the live-call composure the move demands, and how badly it fails in unskilled hands; a framework that is powerful for an expert and damaging for a novice is high-effort, not high-value. Cost and effort are one axis here: nothing on this ladder is bought, only learned.

- efficiency: pause > split > LAER > ledge == Miyagi > gap > LAARC > contract > JOLT > Voss
- value: JOLT > Voss > LAER == LAARC > gap > ledge == Miyagi > contract > split > pause
- effort: Voss > JOLT > contract > LAARC > gap > LAER > ledge == Miyagi > split == pause

Ties, argued:

- `ledge == Miyagi`: same arena (the first thirty seconds), same rehearsal cost (two or three memorised lines), same failure mode (a second attempt reads as pressure); they differ only in the rep's temperament.
- `LAER == LAARC` on value: LAARC buys the same resolved objection, with two extra checks against declaring victory early; the difference sits in effort, not in what either buys.
- `split == pause` on effort: both are learned once in a sitting and then cost nothing per call.

Default rung: the pause plus LAER. Move up to LAARC the first time an objection reps declared handled comes back.

What this order starves: tactical empathy and the full JOLT play are the two highest-value entries and lose every efficiency round, because a quarter of rehearsal buries them. Promote both when:

- a single deal is worth a large share of the number
- procurement or an adversarial economic buyer is in the room
- no-decision is already the largest loss reason on the board

At that point the quarter is cheap.

The order is a default, not a law; it shifts with context and with who executes it. Re-rank against what you already know about the user:

- a team already drilled in one methodology starts from that methodology's spine instead of LAER
- a solo founder selling their own product takes pause, split and gap and skips the rungs that only pay once a team drills them
- a transactional high-velocity motion promotes the ledge to first and may never need JOLT
- a complex six-figure deal inverts that

Not on the ladder, deliberately:

- MEDDICC - a qualification framework, not a live-call move; no rep can say it out loud. A late price or authority objection is often a symptom of weak decision-criteria and economic-buyer work upstream, and that scoring belongs to mbfinotti/sales-skills@meddpicc-scorecard.
- Concession ladders - which trade to make in what order is mbfinotti/sales-skills@negotiation-concession-planner's job; improvising one mid-call is how a discount floor gets set by accident.
- Feel-Felt-Found, the deflect-and-close loop, rebuttal quotas - ruled out by SKILL.md's ethics gate, not ranked last. See Anti-patterns below, which exist so they're recognized, never chosen.

## Table of Contents

- [The shared loop](#the-shared-loop)
- [1. The pause, then one diagnostic question - Jeb Blount, "Objections" (2018)](#1-the-pause-then-one-diagnostic-question---jeb-blount-objections-2018)
- [2. Value vs. capability split - Neil Rackham, SPIN / Huthwaite research](#2-value-vs-capability-split---neil-rackham-spin--huthwaite-research)
- [3. LAER - Listen, Acknowledge, Explore, Respond](#3-laer---listen-acknowledge-explore-respond)
- [4. The ledge, disrupt, ask - Blount == Mr. Miyagi Method - 30 Minutes to President's Club](#4-the-ledge-disrupt-ask---blount--mr-miyagi-method---30-minutes-to-presidents-club)
- [5. Gap re-anchor - Keenan, Gap Selling](#5-gap-re-anchor---keenan-gap-selling)
- [6. LAARC - Listen, Acknowledge, Assess, Respond, Confirm](#6-laarc---listen-acknowledge-assess-respond-confirm)
- [7. Up-front contract - Sandler (David Sandler, 1967)](#7-up-front-contract---sandler-david-sandler-1967)
- [8. The JOLT play - Matthew Dixon and Ted McKenna, "The JOLT Effect" (2022)](#8-the-jolt-play---matthew-dixon-and-ted-mckenna-the-jolt-effect-2022)
- [9. Tactical empathy - Chris Voss (Black Swan Group)](#9-tactical-empathy---chris-voss-black-swan-group)
- [Scope-gated, not ranked - Harry Friedman, retail (B2C)](#scope-gated-not-ranked---harry-friedman-retail-b2c)
- [Anti-patterns - named so they're recognized, never used](#anti-patterns---named-so-theyre-recognized-never-used)

## The shared loop

Every credible framework is a variation of the same loop: stop; listen fully; acknowledge; diagnose the real concern; respond; confirm. The differences are which steps get guardrails, and that is what the rungs below price.

## 1. The pause, then one diagnostic question - Jeb Blount, "Objections" (2018)

The magic quarter of a second: pause before reacting. Emotional control precedes any technique. Then one question - "Can I ask what's behind that?" - before any response.

Blount's wider model: four objection types, each getting a different play.

- prospecting brush-offs
- red herrings
- micro-commitment
- buying-commitment

**Cost and value:**

- Costs near-zero: one habit, learned in a sitting. The composure demand is real but small; saying nothing is easier than saying the right thing.
- Buys the correct diagnosis, which every other rung depends on. Fails safely in unskilled hands: the worst case is a slightly long silence.

## 2. Value vs. capability split - Neil Rackham, SPIN / Huthwaite research

The strongest empirical work in the field, and it cuts against rebuttal culture. Objections are more often created by the seller than the buyer; prevention beats rebuttal. Presenting features early increases price sensitivity, so a late price objection is often the bill for an early feature dump. Split what lands:

- a value objection (unconvinced it's worth it) needs need-development
- a capability objection (can-you-do-X) needs an honest scope answer, including "we don't do that"

**Cost and value:**

- Costs near-zero: a distinction learned once, no rehearsal, no composure demand.
- Buys the two most expensive mis-answers avoided - pitching value at a capability question, and bluffing a scope answer the prospect verifies during evaluation.

## 3. LAER - Listen, Acknowledge, Explore, Respond

Carew International, branded "LAER: The Bonding Process". The load-bearing step is Explore: the model forbids responding immediately and requires an open question to find the root concern. Default spine for a considered objection.

- Costs an hour to learn and about a week of calls before a rep stops answering in the same breath the objection lands.
- Buys structure on every considered objection, in any arena - the widest coverage per hour on this ladder.

## 4. The ledge, disrupt, ask - Blount == Mr. Miyagi Method - 30 Minutes to President's Club

The ledge is a pre-memorized neutral line that buys the rational brain recovery time during a reflex objection; the full turnaround is ledge, then disrupt (say something unexpected that breaks the prospect's script), then ask for the meeting without hesitating. Fits reflexive brush-offs only; explicitly not a reasoned late-stage price objection.

Nick Cegelski and Armand Farrokh's Mr. Miyagi Method covers the same first thirty seconds from the other side: agree with and absorb the objection instead of fighting it, disarm, then redirect to selling the meeting - not the product. Their three cold-call buckets each keep the agree-disarm-redirect shape with a different redirect:

- dismissive ("not interested")
- situational ("no budget right now")
- existing-solution ("we already use something")

**Cost and value:**

- Cost an hour each: two or three lines memorised, then said the same way every time.
- Buy meetings out of brush-offs, which is the only outcome available in that arena. Damage in unskilled hands is low, and the one-turnaround cap contains it.

## 5. Gap re-anchor - Keenan, Gap Selling

Objections are a symptom of poor discovery. Don't defend the product; make the buyer weigh the objection against their own stated future state: "You said X was critical. Help me understand how the price outweighs getting there." Re-anchor price objections on the quantified gap between current and desired state.

- Costs an hour to rehearse and is worthless without discovery notes; it depends on a future state the buyer actually stated, so its real cost is whatever the discovery call cost.
- Buys price objections answered in the buyer's own words rather than the seller's, which is what stops a value argument turning into a price argument.

## 6. LAARC - Listen, Acknowledge, Assess, Respond, Confirm

From the academic professional-selling textbook line (Ingram, LaForge, Avila, Williams). Two guardrails beyond LAER:

- Assess asks "is this the real objection, and how much does it actually matter?" before any response
- Confirm asks "is it genuinely resolved?" before moving on

**Cost and value:**

- Costs an hour on top of LAER, and slows the rep down twice per objection.
- Buys smokescreens caught and false resolutions caught. That extra hour only pays where smokescreens are common or reps tend to declare victory early; otherwise it buys the same outcome LAER already bought.

## 7. Up-front contract - Sandler (David Sandler, 1967)

Mutual agreement, set at the start of every meeting, on what the meeting will decide. Pre-empts vague stalls ("let me think about it") because what happens at the end was agreed at the start. Sandler treats "no" as an acceptable, even desirable outcome - the origin of disqualification as a professional discipline.

Its high-damage variant, negative reverse selling ("Sounds like this might not be a fit. Should we stop here?"), puts the burden back on the buyer. Used sincerely it is powerful; used as a trick it reads as manipulation, so price it with Voss rather than here.

- Costs a week: it changes how every meeting opens, so a team adopts it together or it reads as odd. Compounding - worth the week only if the team drills it, never for one call.
- Buys stalls that never happen, which is cheaper than any stall handled well.

## 8. The JOLT play - Matthew Dixon and Ted McKenna, "The JOLT Effect" (2022)

Late-stage stalls are often indecision - fear of getting it wrong - not preference for the status quo, and more value, urgency, or FOMO makes indecision worse. The supporting numbers come from the authors' own call datasets, so treat magnitudes as directional. The four behaviors:

1. Judge the indecision - assess its source and severity early.
2. Offer a recommendation - one confident option, not a menu.
3. Limit the exploration - reassure the buyer they have enough information; contain the research loop.
4. Take risk off the table - opt-outs, guarantees, phased or smaller first commitments.

- Costs a quarter: behaviors 1-3 are a week of coaching, but behavior 4 needs standing authority to offer opt-outs and guarantees, and getting those terms approved is a standing job for legal and finance, not a rehearsal.
- Buys back no-decision losses, the largest single loss category in most late-stage pipelines - the highest-value entry here, and the reason to promote it past its rank as soon as the board shows the losses.

## 9. Tactical empathy - Chris Voss (Black Swan Group)

Tools:

- Labels: "It seems like...", "It sounds like..." - name the emotion or position, then stop talking.
- Mirrors: repeat the last one to three words as a question, then silence.
- Calibrated questions: open "how"/"what" questions ("How am I supposed to do that?") that make the buyer solve the problem with you.
- Dynamic silence: four-plus seconds after a label or key statement. Let it work.
- Accusation audit: voice their worst objections about you before they do.

Sequencing rule: empathy and labeling first, calibrated question second. A calibrated question fired before empathy lands as an attack.

- Costs a quarter and the most composure of anything on this ladder. Damaging in unskilled hands: a label delivered as technique is heard as technique, and the sequencing error turns the whole move hostile. That damage is why it ranks last on efficiency despite ranking second on value.
- Buys adversarial pushback survived - procurement pressure, a hard no, an angry buyer. Overkill for routine low-friction objections. Evidence base is hostage-negotiation case experience, not controlled sales trials.

## Scope-gated, not ranked - Harry Friedman, retail (B2C)

"No Thanks, I'm Just Looking" (1989): "just looking" is a predictable step of a retail visit, not an objection. Disarm it with a low-pressure, non-sales opener and let the browsing continue; the sale starts later in the visit. Near-zero to learn and it applies on a retail floor and nowhere else, so it sits outside the ladder rather than competing with it.

## Anti-patterns - named so they're recognized, never used

- Feel-Felt-Found: "I know how you feel, others felt the same, they found..." Popularized by Zig Ziglar (the invention claim is untraceable folklore). Today it's formulaic, instantly detected, and dishonest whenever the "others" are invented.
- The deflect-and-close loop: dodge the first objection without answering it, close again, repeat. The underlying observation - a first objection is often a smokescreen - is sound and widely shared; the loop built on it is a high-pressure persuasion device, not a diagnostic one, and a compliance risk in consumer channels.
- Rebuttal quotas: a script or scorecard rewarding N rebuttal attempts before accepting a no. See the ethics section of SKILL.md; in consumer telemarketing, that scorecard can make the script itself the violation.

# Worked examples - rebuttal sets

Each entry follows the output shape defined in SKILL.md. The scripts are deliberately spoken language - short sentences, contractions, no marketing adjectives. Keep them that way when tailoring.

The last entry is a negative example: what a bad rebuttal looks like and why each part fails.

## Example 1"It's too expensive" (B2B, post-demo)

Context: mid-market compliance platform, about $30k/year, sold to an operations director. Demo done, proposal sent.

- Objection: "We like it, but honestly it's too expensive."
- What it usually means: a value gap (the ROI story didn't land), a genuine budget ceiling, or the opening move of a negotiation.
- Diagnostic question: "Help me understand - is it that thirty grand doesn't fit this year's budget, or that you're not sure it's worth thirty grand?"
- Response script (value-gap branch): "That's fair. Can we go back to something you said earlier? You told me audit prep eats about three weeks of your team's time, twice a year. If that number's right, the problem costs you more than the fix does. What am I missing?"
- Proof point: the case study showing audit-prep time cut at a similar-size customer - only if it exists in the interview inputs.
- Hand-back question: "If the math held up, would you want this in place before the next audit cycle?"
- If it repeats: a second "too expensive" after the value math holds usually means a real budget ceiling or a missing stakeholder. Stop re-selling value. Move to terms - phased start, smaller scope - or ask who else has to sign off.

## Example 2"Not interested" (cold call, reflex - identical in B2B and B2C)

Context: outbound cold call, first twenty seconds. The product barely matters; the timing is the diagnosis.

- Objection: "Not interested."
- What it usually means: nothing yet. It's a reflex to being interrupted, not a judgment of the offer.
- Diagnostic question: none out loud - interrogating a reflex sounds like an interrogation. The response itself is the test: if the same words come back after one turnaround, treat it as real.
- Response script: "Totally fair - you weren't expecting this call. Can I take twenty seconds to say why I called you specifically, and then you tell me if it's a bad fit?"
- Proof point: none at this stage. Proof on a cold call belongs to the meeting pitch, not the brush-off.
- Hand-back question: "Worst case you've lost twenty seconds - fair?"
- If it repeats: take the no. "No problem - thanks for being straight with me." One turnaround, two at most. A second push is where compliance risk starts on consumer calls.

## Example 3"We already use [incumbent]" (B2B discovery)

Context: the prospect names their current vendor and closes the door politely.

- Objection: "We're already on [incumbent]. We're all set."
- What it usually means: genuinely satisfied (possibly disqualifying), satisfied by default because nothing was ever compared, or frustrated but dreading the switching cost.
- Diagnostic question: "That makes sense - most teams I talk to have something in place. How's it handling [the one area where you're demonstrably stronger]?"
- Response script (frustration surfaced): "Yeah, that's what I hear a lot. Teams that moved to us from [incumbent] mostly did it for exactly that. I'm not going to tell you to rip anything out - would twenty minutes be worth it to see how we handle it differently, and you judge?"
- Proof point: a reference customer who switched from that specific incumbent. Verify the incumbent's current public pricing and packaging before any comparison claim if web browsing is available; otherwise mark each competitor claim "verify before use".
- Hand-back question: "If you could change one thing about the current setup, what would it be?"
- If it repeats: satisfied and verified means disqualify for now. Leave one well-placed question behind ("worth asking them what happens to your data at renewal"), set a re-entry trigger on the renewal date, and exit gracefully.

## Example 4"I need to think about it" (late stage, indecision)

Context: B2B or consumer high-ticket. Value agreed weeks ago; this is the third "thinking about it".

- Objection: "This all looks good. I just need some time to think it over."
- What it usually means: at this stage, usually fear of getting it wrong - not a status-quo preference, and usually not a hidden competitor.
- Diagnostic question: "Totally get it. What would you want to be sure of before saying yes?" A specific answer is a true objection; a vague or ever-growing list is indecision.
- Response script (indecision confirmed): "Can I make a recommendation? Based on everything you've told me, I'd start with the smaller rollout - one team, ninety days. If it doesn't do what I've said, you walk away and you've lost nothing. You already have what you need to make this call."
- Proof point: the opt-out or guarantee terms themselves - the de-risking is the proof.
- Hand-back question: "Does starting small like that take the pressure off?"
- If it repeats: more information will not close an indecisive buyer. Shrink the commitment again, or time-box it yourself: "I don't want to keep taking your time if the honest answer's no - and no is fine."

## Example 5"I have to talk to my partner" (B2C high-ticket, authority)

Context: home-improvement quote, in-home visit, one partner present.

- Objection: "I have to run it by my wife first." / "I have to run it by my husband first."
- What it usually means: a genuinely shared decision (most of the time), a polite exit, or a price concern relocated onto the absent partner.
- Diagnostic question: "Of course. What do you think they'll want to know that we haven't covered?"
- Response script: "Makes sense - I'd want the same. Rather than you re-explaining all this from memory, how about I leave a one-page summary with the price and the options, and we pick a time this week when you're both free for ten minutes?"
- Proof point: the written summary itself. In-home high-ticket selling often falls under cooling-off and doorstep rules, so the paper trail is also the compliance-safe move.
- Hand-back question: "Which evening are you usually both home?"
- If it repeats: without a scheduled two-party conversation, treat it as a polite no. Never pressure a lone partner into signing - in several jurisdictions that exact pattern is what consumer-protection rules target.

## Negative example - the same objection, handled badly

Objection, same as Example 1: "We like it, but honestly it's too expensive."

Bad response: "I completely understand how you feel. A lot of our customers felt exactly the same way, but once they saw the value, they found it was the best investment they ever made. And look - I can do fifteen percent off, but only if you sign by Friday."

Why every part fails:

- Feel-Felt-Found is formulaic and instantly recognized - and the "customers who felt the same" are invented, so it's also a lie.
- It skips diagnosis entirely. No attempt to learn whether this is a value gap, a budget ceiling, or a negotiation move, so the response can't possibly match.
- The unilateral discount answers a question nobody asked, drops the price floor for the whole account, and signals the original number was padded.
- The fake Friday deadline is manufactured urgency - an ethics-line violation, and if the buyer is indecisive, pressure makes the odds worse, not better.
- Nothing hands the conversation back. The prospect's easiest next move is to leave.

---
name: sales-objection-handling
description: Diagnoses what a sales objection really means and writes rebuttal scripts a rep can say out loud, or calls the deal dead when the objection is a real constraint. Covers price/budget, timing, competitor/incumbent, authority, status-quo, and trust objections for B2B and B2C, with price-specific guidance on value gap vs genuine budget limit and trading instead of discounting. Use whenever the user mentions a price objection, "too expensive", "not interested", "send me some info", "we already use a competitor", stalling, or an objection library, even without the word objection. Do NOT use for discount trade planning (mbfinotti/sales-skills@negotiation-concession-planner) or ROI math (mbfinotti/sales-skills@deal-value-calc).
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.2.8"
---

# Objection Handling

Diagnose what a sales objection really means, then produce spoken-language response scripts - or say plainly that the deal should be disqualified. Works for B2B and B2C, from cold call through negotiation, with dedicated price-objection sequencing.

## The prevention check (run it first)

The strongest research in this field (Neil Rackham's Huthwaite studies) found that objections are more often created by the seller than the buyer, and that preventing them beats rebutting them. Pitching before the need is developed, or leading with features, manufactures price sensitivity.

1. Once the interview tells you where the objection landed, ask what discovery happened before it.
2. If the honest answer is "we pitched before we understood the problem", say so, and recommend mbfinotti/sales-skills@sales-discovery-questions to fix the upstream gap.
3. Then continue - the rep still has to answer the objection in front of them. One check; don't turn this into a discovery session.

## Interview

Ask one question per message. Offer multiple-choice options wherever possible - the user is often answering from a phone between calls. Gather:

1. What are you selling, and to whom? (product, rough price point, buyer persona)
2. B2B, B2C, or consumer high-ticket (auto, solar, home improvement)?
3. Where did the objection land: cold call / discovery / demo / proposal or negotiation / retail or inbound?
4. The prospect's exact words. Verbatim matters - "that's a lot of money" and "we have no budget" are different objections.
5. What has the rep already tried in response?
6. Which proof assets exist: case study, benchmark, reference customer, guarantee, trial? Never invent one.
7. Do you sell in a regulated category - securities, insurance, lending, health/pharma, energy/utilities? (See Ethics and compliance.)
8. By when does this have to land - the call tomorrow, this quarter's pipeline, or next year's team enablement?
9. One-off win or compounding asset: scripts for one rep's live deal, or a framework the whole team adopts and drills?
10. What's the effort ceiling - rehearsal hours available before the next call, and can the rep offer an opt-out, guarantee, or phased start without sign-off?

Re-rank the framework ladder on those answers, and say which answer moved what:

- A call tomorrow promotes the pause, the value/capability split and the ledge, and drops everything costing a quarter of rehearsal.
- A compounding mandate promotes LAARC, the up-front contract and the JOLT play - all three only pay once a team drills them, and all three are wasted on a single deal.
- No authority to offer de-risking deletes the de-risk move from the discount menu below and leaves trading at the top.

## Workflow

1. Run the interview, then the prevention check.
2. Diagnose the objection (next section). Never script before diagnosing.
3. Pick the response mode that matches the diagnosis.
4. Draft the rebuttal set in the output shape below. Apply the price sequencing section to any price objection. For competitor objections: if you can browse the web, verify the competitor's current public pricing and packaging before writing a comparison claim; if you can't, mark every competitor claim "verify before use".
5. Apply the ethics and compliance gate.
6. Run every script through your preferred humanizer skill - mandatory, this is language meant to be spoken. If no humanizer skill is available, do a manual pass: read each line aloud, add contractions, cut anything a person wouldn't actually say on a call.
7. Deliver. If the user is building a reusable library, add the maintenance notes below.

## Diagnose before you script

The stated objection is often not the real one. The same words need opposite responses depending on what's underneath, and a rebuttal aimed at the surface words wastes the rep's turn. Classify first:

| Diagnosis                | What it is                                                         | Tell-tale signs                                                                                                    | Mode                    |
| ------------------------ | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | ----------------------- |
| Reflex brush-off         | Automatic response to being interrupted, not a considered position | Cold call or shop floor, first 30 seconds, generic wording ("not interested", "send me some info", "just looking") | Reflex                  |
| Smokescreen              | A stated objection concealing the real one                         | Vague, shifts when probed, doesn't match the deal's facts                                                          | Probe, then re-diagnose |
| True objection           | A real, specific concern that must be resolved to progress         | Specific, consistent, tied to facts ("your API doesn't cover X", "the CFO capped spend at Y")                      | Considered              |
| Indecision               | Fear of getting it wrong, not preference for the status quo        | Late stage, agrees on value, keeps asking for more information, options, or stakeholders                           | Indecision              |
| Disqualifying constraint | A constraint no script can move                                    | No budget exists at all, no path to authority, no compelling event, hard regulatory bar                            | Disqualify              |

Make the rep ask one diagnostic question before responding. All four cost the same near-zero breath, so the ordering is pure value:

`"what's behind that?" > the price triage > the if-solved test > the confidence question`

- "Can I ask what's behind that?" - opens up almost any objection, and needs no guess about which arena you're in.
- "Is it that the number doesn't fit the budget, or that you're not sure it's worth it?" - the price triage. Splits the single most common objection into its two opposite responses, but only once you know it's about price.
- "If [stated objection] were solved, would you move forward?" - a "no" exposes a smokescreen. Needs a stated objection specific enough to name back.
- "What would you need to see to feel confident this is the right call?" - a specific answer is a true objection; an endless list signals indecision. Slowest to interpret: the tell is in the shape of the answer, not its content.

Before any of that, the magic quarter of a second (Jeb Blount): pause before reacting. The first instinct is to defend, and defending is almost always wrong.

## Response modes

The diagnosis picks the mode, so the four modes are deliberately not ranked against each other - a ranking there would be false precision. The choice of framework _inside_ a mode is ranked, and that ordering is what a rep with limited rehearsal time needs.

Learn the frameworks in this order - value bought per hour of rehearsal:

`pause > value/capability split > LAER > ledge == Mr. Miyagi > gap re-anchor > LAARC > up-front contract > JOLT play > tactical empathy`

Steps, originators, what each costs to learn and what each buys are in [./references/response-frameworks.md](./references/response-frameworks.md) - read it when drafting. Effort there is rehearsal time, live-call composure, and how badly the move fails in unskilled hands; nothing on the ladder is bought, only learned.

What that order starves: tactical empathy and the full JOLT play are the two highest-value entries and lose every round, because each costs a quarter of rehearsal. Promote both when:

- a single deal is worth a large share of the number
- procurement or an adversarial economic buyer is in the room
- no-decision is already the top loss reason

The order is a default, not a law - it shifts with context and with who executes it. Re-rank it against what you already know:

- a team already drilled in one methodology starts from that spine instead of LAER
- a solo founder skips the rungs that only pay once a team drills them
- a transactional motion promotes the ledge to first
- a complex six-figure deal inverts that

### Reflex mode (cold call and retail brush-offs - identical in B2B and B2C)

The goal is the next 30 seconds and the meeting, not the sale. Never argue with a reflex - arguing upgrades it into a real objection.

`ledge, disrupt, ask == Mr. Miyagi > poke the bear`

1. Open with a ledge (Jeb Blount): a pre-memorized neutral line that buys the rep's rational brain recovery time. Blount's full turnaround is ledge, disrupt, ask. An hour to memorise; buys a beat the rep would otherwise spend defending.
2. Or agree and redirect instead of fighting - the Mr. Miyagi Method (30 Minutes to President's Club): absorb the objection, disarm, redirect to selling the meeting, not the product. Their three cold-call buckets - dismissive, situational, existing-solution - each keep that shape with a different redirect. Tied with the ledge: same arena, same rehearsal cost, same failure mode; pick on the rep's temperament, not on merit.
3. Then poke the bear (Josh Braun): "'I'm not interested' isn't an objection." Ask one question that surfaces a problem the prospect may not know they have, instead of pushing. Same hour to learn, but the question only lands with product knowledge a new rep doesn't have yet - that dependency is what ranks it third, not the move itself.
4. One turnaround attempt, at most two. Then take the no gracefully - see Ethics and compliance.

### Considered mode (discovery, demo, proposal)

`LAER > LAARC > up-front contract > tactical empathy`

- LAER - Listen, Acknowledge, Explore, Respond (Carew International). The default spine: an hour to learn, a week of calls before the rep stops answering in the same breath, and it covers every considered objection in any arena.
- LAARC - Listen, Acknowledge, Assess, Respond, Confirm (from the academic professional-selling textbook line). One extra hour on top of LAER for two guardrails: Assess forces "is this the real objection?" before responding, Confirm forces "is it actually resolved?" before moving on. That hour pays only where smokescreens are common or reps declare victory early; elsewhere it buys what LAER already bought.
- Sandler's up-front contract - agree the meeting's outcome up front, and vague stalls never form. Costs a week of habit across the whole team, so it earns its place only under a compounding mandate, never for one call.
- Tactical empathy (Chris Voss / Black Swan Group) - a label and dynamic silence first, a calibrated how/what question second. Sequencing matters: a calibrated question fired before empathy lands as an attack. Last here because it costs a quarter and misfires badly in unskilled hands, first on value when the pushback is adversarial - that's the promotion condition above.

Whichever spine is in play:

- Never respond in the same breath the objection lands. The explore/assess step is what catches smokescreens.
- Attach exactly one proof point per response, matched to the specific concern. Three weak proofs read as desperation.
- Distinguish value objections (buyer unconvinced it's worth it - rebuild the need) from capability objections (can-you-do-X - answer honestly, including "we don't do that") per Neil Rackham's research. Near-zero to learn, which is why it sits second on the ladder.

### Indecision mode (late-stage stalls)

Per The JOLT Effect (Dixon and McKenna, 2022), a large share of lost deals die to buyer indecision - fear of getting it wrong - not preference for the status quo. Adding more value, urgency, or FOMO makes indecision worse. When the diagnosis is indecision, switch modes:

1. Give one clear, confident recommendation - not more options.
2. Limit the exploration: reassure the buyer they already have enough information; stop feeding the research loop.
3. Take risk off the table: opt-out, guarantee, phased rollout, smaller first commitment. De-risk because it answers the actual fear - the win-rate statistics attached to risk-reversal language are vendor-published and correlational, so treat them as a hint, not a law.

### Disqualify (a valid output, not a failure)

When the diagnosis is a real constraint (no budget at all, no path to authority, no compelling event, a hard regulatory bar), say so and stop rebutting. A skill that always produces a comeback teaches reps to push on dead deals.

Output instead:

- a graceful exit script
- a re-entry condition ("when X changes")
- a follow-up date to put in the CRM

## Price objections

Price gets its own treatment because "too expensive" is the most common objection and the most misdiagnosed.

Triage first - the two meanings need opposite responses:

- Value gap: the buyer doesn't yet see enough value to justify the number. Fix the value story, not the price. Use the buyer's own stated goal against the objection (Keenan's Gap Selling): "You said cutting audit prep was the priority this quarter - help me understand how the price outweighs that." Quantifying the gap is mbfinotti/sales-skills@deal-value-calc's job.
- Genuine budget constraint: the money truly isn't available this cycle. No value pitch fixes this. Change the terms, ranked by what each costs the rep against what it recovers: `phased start > smaller scope > later start date > champion enablement > disqualify with a re-entry date`. A phased start needs no new approval and keeps the deal this quarter; a smaller scope shrinks it permanently; a later start date only moves the problem; champion enablement costs a week of the rep's time building someone else's business case; disqualifying is last because it recovers nothing this cycle - but it is the honest answer once none of the four above fit.

Split them with: "Is it that the number doesn't fit this year's budget, or that you're not sure it'd be worth it at that number?"

When price comes up before value is established:

- Don't stonewall. Refusing the number reads as evasive and stacks a trust objection on top of the price one.
- Give an honest range or anchor, then earn the right to add context: "It runs between X and Y depending on scope - can I ask two quick questions so I can tell you where you'd land?"
- The transferable principle from conversation-intelligence research (vendor-published, correlational - treat as a heuristic): discuss price on the first call, after value. Not never, and not in the opening minute.

When they push for a discount, three moves compete. The axes disagree, so read all four lines:

- efficiency: `de-risk > trade > discount` when opt-out or guarantee terms already exist; `trade > de-risk > discount` when they don't, because getting terms approved is a standing job, not a call-prep task
- value: `de-risk > trade > discount`
- effort: `de-risk > trade > discount`
- compliance cost: `de-risk > discount > trade`

- De-risk - an opt-out, guarantee, or smaller first commitment often resolves the fear the discount ask stands in for, and it costs no margin. Highest effort of the three: the terms have to exist and be approved before the call, and a guarantee is a contract term that needs legal sign-off and is hard to withdraw once offered. Deleted from the menu entirely if the interview said the rep can't offer one without sign-off - a de-risk move parked at the bottom reappears mid-call as an unauthorized promise.
- Trade - every reduction gets something back: a longer term, a case study, an intro, a signature date. An hour of rehearsal and the composure to ask; needs only the customer's own permission, so no review is triggered. The default when de-risking isn't available.
- Discount - never conceded unilaterally, and last on efficiency and value. It ranks lowest on effort only in the trivial sense that saying a smaller number takes no rehearsal; it buys a smaller deal, sets the account's floor, and signals the original number was padded. It still needs deal-desk approval, and the precedent carries into the next renewal.

Planning which concessions to trade, and in what order, ahead of a negotiation belongs to mbfinotti/sales-skills@negotiation-concession-planner - hand off rather than improvising a concession ladder here.

Remember the prevention finding: features presented early increase price sensitivity (Rackham). A late "too expensive" is often the bill for a rushed pitch. Weak decision-criteria and economic-buyer work earlier in the deal is the usual root cause - MEDDICC's economic-buyer lens is cost, completion, confidence - and mbfinotti/sales-skills@meddpicc-scorecard scores that; this skill supplies the words in the meantime.

## B2B vs B2C

- B2B: objections often come from a buying committee, so the words the rep hears may be a proxy for an absent stakeholder's concern. "I need sign-off" and "not this quarter" frequently mean "I can't get this through my process", not "I don't want it" - script for the champion's internal battle (a one-pager, talking points for their boss), not just the live call.
- B2C: usually one decision-maker, shorter deliberation, price and trust dominate, and the reflex/emotional share is larger. In retail, "just looking" is a predictable step of the visit, not an objection (Harry Friedman's retail work) - disarm it with a low-pressure opener and let the visit continue.
- Consumer high-ticket (auto, solar, home improvement) sits between the two: a single household with committee-like dynamics ("I need to talk to my partner") and heavy consumer-protection regulation.
- Identical in both, explicitly: the diagnose-before-you-script rule, the reflex brush-off response, and the trade-don't-cave rule on discounts.

## Output shape

Produce a rebuttal set: one entry per objection, each containing:

1. The objection - verbatim, as the prospect says it.
2. What it usually means - the concerns underneath, and which diagnosis each points to.
3. The diagnostic question - the one question that tests which meaning is in play.
4. The response script - spoken language, two to five sentences, contractions, no marketing adjectives.
5. The proof point - which real asset from the interview backs it. Never invented.
6. The hand-back question - the question that returns the conversation to the prospect.
7. If it repeats - what a second occurrence of the same objection means, and what to do (usually: stop rebutting, re-diagnose, or disqualify).

Read [./references/worked-examples.md](./references/worked-examples.md) before writing your first set - including the negative example.

## Ethics and compliance

Hard rules, not style preferences:

- Never manufacture urgency (fake deadlines, fake scarcity), invent social proof, or make any claim the rep can't substantiate. A script with an invented proof point is a lie with better formatting.
- Never build a rebuttal quota - any rule or scorecard requiring N rebuttal attempts before accepting a no. Consumer telemarketing rules require honoring a request to stop; a script that rewards pushing past it makes the script itself the violation.
- A clear "stop calling me" or "take me off your list" ends the conversation. Script the graceful exit, not another angle.
- If the user sells in a regulated category, whole categories of claim are off-limits. Route every script through the firm's compliance review before anyone speaks it, and state that requirement explicitly in the output. Don't enumerate the rules yourself - that is their compliance team's job, not this skill's.
  - Regulated categories: securities, insurance, lending, pharma/health, energy/utilities, a consumer-duty regime.
  - Off-limits claims: guaranteed or predicted returns, unsubstantiated savings figures, implied affiliation with a utility or government body, off-label claims.

## If the output becomes a library

- Date every entry.
- Source responses from real winning calls (call recordings, win/loss notes) instead of invention as soon as any exist.
- Refresh monthly for competitor and pricing entries. A battlecard carrying stale competitor pricing is worse than none - reps stop trusting the whole library.
- If your harness has persistent memory, store the product, personas, proof assets, and diagnosed patterns so later sessions can skip the interview; otherwise tell the user to keep the library in a dated file they own.

Owning and maintaining the library org-wide is beyond this skill's scope - keep this note short in the output.

## Measuring whether it works

`diagnostic-question rate > objections-per-call by rep > no-decision loss rate` - ordered by how fast each one can tell you anything.

- On scored calls, check whether the rep asked a diagnostic question before responding - visible on the next call you score, and the leading indicator that this skill's core habit stuck.
- Track objections-per-call by rep. If the best closers hear materially fewer objections, the problem is upstream sequencing, not rebuttal skill - invest there. Needs a few weeks of calls before the spread means anything.
- Track the no-decision loss rate. A falling rate is the signal the indecision mode is landing, but it needs a quarter of closed deals to move - the most valuable number here and the slowest to arrive.

## Failure modes

- Rebutting a reflex as if it were reasoned. Argument converts a brush-off into a real objection. Ledge, then a question.
- Answering the surface words of a smokescreen. You win the stated objection and the deal still dies. Probe first.
- Adding value, urgency, or FOMO for an indecisive buyer. It reliably makes indecision worse. Switch to indecision mode.
- Feel-Felt-Found ("I know how you feel, others felt the same, they found..."). Formulaic, instantly recognized, and dishonest whenever the "others" are invented. Don't use it.
- The deflect-and-close loop: dodging the first objection without answering, closing again, repeating. A pressure device, not a diagnostic one - and a compliance risk in consumer channels.
- Trashing the competitor. Ask how the incumbent is working instead; a well-placed question beats badmouthing.
- Bluffing a technical or capability answer. The prospect verifies during evaluation, and the trust loss outlives the deal.
- Shipping first-draft scripts. If it reads like an email, nobody can say it. The humanizer pass is not optional.

## References

- mbfinotti/sales-skills@cold-call-opener - the opener itself; this skill starts once pushback lands.
- mbfinotti/sales-skills@sales-discovery-questions - when the prevention check shows discovery was thin.
- mbfinotti/sales-skills@meddpicc-scorecard - deal qualification scoring.
- mbfinotti/sales-skills@deal-value-calc - quantifying the ROI/business case behind a value-gap rebuttal.
- mbfinotti/sales-skills@negotiation-concession-planner - planning concession trades ahead of a negotiation.
- mbfinotti/sales-skills@sales-call-review - scoring a recorded call, including how objections were handled.
- [./references/response-frameworks.md](./references/response-frameworks.md) - named frameworks: steps, originators, and when each fits.
- [./references/worked-examples.md](./references/worked-examples.md) - filled-in rebuttal sets, positive and negative.