Day 20 · Phase D

Objections Aren't Rejection: They're Trying Your Offer On

Topic: objections as information · four-way triage · agree first·4 moves · 1 triage table
The hardest deal to save is never the one who says "too expensive." It's the one who nods all the way through, calls you impressive, and finishes with "let us discuss it internally."
Anyone who can raise a specific objection has already run your offer through their own budget, their own calendar and their own colleagues. Nobody invents a line like "who's going to import our messy member spreadsheet?" without having tried the thing on in their head. So an objection is a receipt for effort, not a rejection letter — and what you actually have to handle is never the sentence itself, but the risk sitting behind it that hasn't been said out loud.
MOVE 01

A specific objection is a receipt. Politeness is the bad news A specific objection is a receipt; politeness is the bad news

ambiguity aversionno-decisionbuying signal
An objection doesn't mean "I don't want this." It means "I haven't worked out the risk of this step yet." If they'll say the risk out loud, you have something to work with; the risks they won't say turn into "let me think about it," and then they think about it forever.
"Beware 'Yes' — Master 'No'." — Chris Voss, Never Split the Difference (2016), chapter title
Three buyer reactions — don't rank them by how polite they sound 1 · Specific pushback "Our member sheet is a mess — who imports it?" → Already used it in their head Give a plan, not a promise 2 · Vague hesitation "Looks good, let me think." "We'll discuss internally." → Risk exists, unspoken Your job: turn it into 1 3 · Pure praise "Really professional — we'll be in touch." → Usually a polite exit Keep it out of the forecast Closer to a deal Further from a deal People afraid of choosing wrong never say "no" — they say "let me look again" Rank follow-ups by how concrete the pushback was, not by how warm the person was.
Setting: you sell gym membership software. Two demos in one week — owner A frowned and picked three holes in it, owner B nodded throughout and called you impressive. Next week you only have time for one.
✗ Chase the one who was nicest

"B was so pleasant." So you chase for three weeks: send materials, book a second demo, send a case study. The replies get slower, then stop. Meanwhile you answered none of A's three holes, so A assumes you had no answer.
—— You read warmth as intent. Warmth is a social lubricant; it carries no information about buying.

✓ Chase the one who pushed back hardest

To A: treat the three holes as a checklist and answer them on the spot — a method where you have one ("I'll do the import myself, just send me the raw export, two working days"), a straight no where you don't ("multi-site permissions aren't there yet, October at the earliest").
To B, send one message: "You didn't raise a single concern last time, which actually worries me — is there a piece you can't sign off on, or is this just not the moment? If it's not the moment, say so and I'll stop chasing."
—— That last clause is the whole message: make saying no cheap and people tell you the truth. Either answer pays: a real objection, or three weeks back.

Why it works

Mechanism: a specific objection means they've already simulated your offer inside their own constraints. And "risk I can't put a number on" is an expensive state for a brain to sit in — people would rather not move than accept an outcome whose odds they can't even estimate. What blocks the deal is usually not "you aren't good enough" but "I can't calculate what happens if this goes wrong."

  • Hard evidence · ambiguity repels more than risk: Ellsberg (1961, QJE) and his classic paradox — people prefer a gamble with known odds over one with unknown odds, even when the unknown one is the better bet. Not fear of losing; fear of not being able to compute.
  • Hard evidence · ambiguity has its own circuitry: Hsu, Bhatt, Adolphs, Tranel & Camerer (2005, Science) used fMRI to contrast risk (known probabilities) with ambiguity (missing information): under ambiguity, the amygdala and orbitofrontal cortex showed heightened activity while striatal activity tracked expected reward, and patients with orbitofrontal lesions were largely insensitive to ambiguity. Every time you skip "who does this step, and how long it takes," you're loading the other person's amygdala. (cross-ref neuroscience)
  • Industry data · your biggest competitor is no-decision: Dixon & McKenna, The JOLT Effect (2022), analysed millions of recorded sales calls: a large share of qualified opportunities neither lose to a rival nor stay with the status quo — they die of the buyer's fear of getting it wrong, and the fix is taking the downside off the table (narrow the options, give a clear recommendation, absorb part of the risk). Strength: vendor-owned data, not peer-reviewed — use it as a hypothesis.

Two boundaries. One, more objections ≠ better deal: the signal is in specificity, not volume. Two, some people genuinely don't need it — reading every "no" as "I under-sold it" will burn half a quarter on someone who was never going to buy. The next move is how you tell those apart.

MOVE 02

Triage before you answer: no need / no trust / no hurry / too expensive Triage first: no need, no trust, no hurry, too expensive

status quo biaspresent biasobjection classes
The four have completely different causes, so one stock answer only works when you guess right: "no need" sends you back to discovery, "no trust" needs proof, "no hurry" needs a date, "too expensive" needs a comparison. Pick the wrong cell and the harder you try, the more you sound like a salesperson.
"Every sale has five basic obstacles: no need, no money, no hurry, no desire, no trust." — attributed to Zig Ziglar (widely repeated; a practitioner's taxonomy, not a research finding)
One sentence, four different diseases NO NEED · we're fine as we are Subtext: changing hurts more than staying Ask: "When did this last go wrong?" No answer → drop it; an answer → price that day Don't: pitch more features, harder NO TRUST · believes the problem, not you Subtext: if you can't deliver, I carry it Ask: "What would you need to see?" → Same-size case, pilot, downside off the table Don't: repeat how reliable you are NO HURRY · agreed, but ranked seventh Subtext: nobody yells at me if I skip it Ask: "And if it's the same in 3 months?" → Hook it to a date already in their calendar Don't: invent a fake deadline TOO EXPENSIVE · half the time a proxy Subtext: not worth it / not my budget Ask: "Compared to what?" + "Price solved = yes?" "Yes" → talk structure, not discount; else look again Don't: discount by reflex Triage takes one move: when you hear an objection, don't answer — ask the diagnostic question first.
Setting: you've quoted, and they say "that's a bit over budget." Same sentence, potentially four different causes.
✗ Treat every "expensive" as a price problem

"Let me ask — I can probably do 10% off."
—— Three things happen at once: you've admitted the list price was fiction, you've dragged the conversation from value back to numbers, and if what they were really stuck on was "can this actually be made to work," they still won't sign at 10% off — only now you've spent your card.

✓ Two sentences of triage first

First: "Over by how much? Over compared to other quotes, or over what you'd set aside for this?"
Second (isolate the objection): "Suppose we could sort the price out — would everything else be fine?"
· "Yes, basically" → a genuine price problem. Talk structure (instalments, one site first, part of the fee tied to the result), not discounts.
· "Well, I'd still want to see how the import goes" → the disease is no trust, and discounting is medicine for the wrong illness.
—— The second sentence is the valuable one: five seconds to split "expensive" into a real price objection and a disguise. If you still can't tell which cell you're in, just ask: "Is this something we didn't explain well, or something that just isn't on your list this year?"

Why it works

Mechanism: four different mechanics. "No need" is the gravity of the status quo — not moving is the default and changing carries a one-off cost. "No hurry" is temporal discounting — the same task shrinks automatically once it's in the future. "No trust" is risk ownership — if the purchase fails, they carry it alone. "Too expensive" is usually the most dignified exit from the other three.

  • Hard evidence · the status quo is itself a force: Samuelson & Zeckhauser (1988, Journal of Risk and Uncertainty) combined experiments with real health-plan and retirement-allocation data to show that merely labelling an option as the status quo substantially raises how often it's chosen, with inertia growing as the option set grows. Your competitor is usually not a rival vendor but the "change nothing" default — and offering more options helps it, not you.
  • Hard evidence · procrastination isn't laziness, it's discounting: O'Donoghue & Rabin (1999, American Economic Review) modelled present bias — near-term costs are magnified and future benefits shrunk, so "worth doing but not urgent" gets deferred indefinitely. Ariely & Wertenbroch (2002, Psychological Science) supply the antidote: groups working to deadlines clearly outperformed those with none. The cure for "no hurry" is a date you both agree on.
  • Weaker evidence · the four-way split itself: this taxonomy descends from Ziglar's practitioner lore and has no controlled studies behind it. Its value isn't scientific; it's that the categories are roughly exclusive and exhaustive, so you can label a call in three seconds.

Boundary: the answers to diagnostic questions aren't necessarily true. "Compared to what?" can produce a rival quote invented on the spot. What the questions really do is move the conversation from "you convince me" to "let me tell you" — and the Mom Test rule (ask about specific past behaviour, not future intent) applies here too. Also, don't use "suppose we could sort the price out" on someone who's offended or in a hurry: it carries a transactional smell and reads like a trap.

MOVE 03

Agree first: argue, and they start defending their own sentence Agree first: the moment you argue, they start defending their own sentence

reactanceaffect labelingautonomy
Right after someone voices an objection, what they care about isn't your offer — it's not looking stupid for having said that. The harder you push to prove them wrong, the harder they hold on. Let them confirm that you understood and that you aren't going to force them, and only then do they have the capacity to re-run the numbers.
"People are generally better persuaded by the reasons which they have themselves discovered than by those which have come into the mind of others." — Blaise Pascal, Pensées (1670)
They say: "Our spreadsheet works fine for us." The rebuttal route The agreement route "Spreadsheets have three fatal flaws…" (possibly all true) What they hear: you chose badly Autonomy threatened → reactance They start listing what the sheet does well Position now firmer than before "If it works, don't switch — is it the hassle?" (label + concede what's true) "Totally your call — I'm not pushing." Choice handed back → reactance drops "One question: what about shift swaps?" They name the gap themselves The fork isn't in the content — it's in whether they felt the choice being taken away Naming a feeling tracks with reduced amygdala activity (Lieberman et al., 2007); "totally your call" has meta-analytic support (Carpenter, 2013). The right-hand route still ends in a question, not a feature — you point at the gap, they draw the conclusion.
Setting: the customer says "we've done rostering in a spreadsheet for six years and it's fine." You know spreadsheets break on shift swaps and multi-site sync.
✗ Win on facts

"Spreadsheets have three fatal problems: version conflicts, no permissions, and every change means messaging everyone…"
—— Every point is correct and every point is useless. You said "that method has problems"; they heard "your judgement for six years was wrong." From here they stop evaluating the product and start defending themselves: "we're small, it's enough for us."

✓ Concede → label → hand back the choice → ask one narrow question

"Six years and it still works, so it's probably genuinely a good fit — I don't think you should replace something just because it's replaceable. (concede the fact)
Sounds like the real cost here is having to go through a migration — is that fair? (label the concern, and leave room to be corrected — a correction is a win too)
Whether you switch is entirely your call; I'm not going to push it today. (hand the choice back explicitly)
Just one question: when somebody swaps a shift at short notice, who edits the sheet, and how do the other two sites find out?" (one narrow gap)
—— The first three lines never mention your product. On the fourth, they either say "yeah, that does get messy" or "we have a group chat." Either way the gap came out of their mouth, not yours — and those two things weigh completely differently.

Why it works

Mechanism: rebuttal steps on two mines at once. First, autonomy — the moment people sense a freedom being removed, they generate a drive to take it back, and the cheapest way to take it back is to hold their sentence harder. Second, an unnamed worry sits as diffuse tension, and nobody can be tense and do arithmetic at the same time. So the order has to be: cool it down, then reason.

  • Hard evidence · reactance is measurable: Brehm (1966) introduced reactance theory; Dillard & Shen (2005, Communication Monographs) showed experimentally that it decomposes into anger and counter-arguing, intertwined — the more forceful and freedom-threatening the message, the higher both run and the further attitudes move the wrong way. Which explains the counterintuitive part: the more thoroughly you argue, the firmer they sometimes get.
  • Hard evidence · "but you are free to refuse" buys compliance: Guéguen & Pascual (2000) asked strangers in the street for bus fare; simply appending "but you are free to accept or refuse" lifted compliance from roughly one in ten to nearly half. Carpenter (2013, Communication Studies) meta-analysed 42 studies and confirmed the effect is reliable but small (r ≈ 0.17). What it adds isn't pressure — it's autonomy.
  • Hard evidence · naming a feeling cools it: Lieberman et al. (2007, Psychological Science) had participants label emotional faces rather than merely view them: amygdala activity dropped markedly while right ventrolateral prefrontal cortex activity rose, the two inversely related — labelling is itself a form of implicit emotion regulation (Torre & Lieberman, 2018, Emotion Review). Honest note on the extrapolation: in the study people labelled emotions they saw, not a salesperson labelling a customer's. It supports the mechanism "putting it into words cools it," not the claim that labelling scripts raise close rates — that rests mainly on Voss-style field experience, which is weaker evidence. (cross-ref neuroscience)

Three boundaries. One, concede the fact, never the conclusion: faking agreement and then adding "but" is heard within a second and damages trust more than open disagreement. Two, "totally your call" has to be true: saying it and then chasing three more times is lying to someone's face. Three, leave room to be corrected — "sounds like…, is that fair?" not "I know you're just worried about the hassle." The second one delivers a verdict on their behalf, which is a fresh offence of its own.

Restate → label → hand back → ask

· Restate the fact: "You're saying ___, and it's never caused a real problem."

· Label the concern (leave room): "Sounds like it's mostly not wanting a migration — is that fair?"

· Hand back the choice: "Whether you switch is entirely your call; I'm not pushing today."

· Ask one narrow question: "Just one question: when ___ happens, how is it handled now?"

· No "but" anywhere. If you need a turn, use a full stop instead of a conjunction.

MOVE 04

Move objections earlier: intel before the quote, siege after it Move objections earlier: intel before the quote, crisis after it

inoculation theoryobjection preventiontwo-sided messages
The same "too expensive" is ground you have to defend when it arrives after your quote, and free intelligence when it arrives before. The best objection handling is not letting it wait until the last minute — invite it to the table yourself and it can no longer function as a reason to say no.
"An ounce of prevention is worth a pound of cure." — attributed to Benjamin Franklin (proverbial)
Inoculation in three steps: weak version + resolve it on the spot + hand back the judgement

· List your three standing objections (go through the last ten stalled conversations — they repeat).

· Raise them yourself during discovery, in a weakened form: "the first two weeks of data migration are genuinely annoying, other customers have said so."

· Resolve it there and then: "which is why I do the import; you just send me the raw export."

· Hand the judgement back: "whether those two weeks are worth it, decide after you've seen the pilot."

· Before quoting, run the rehearsal question: "when you take this to your team, which line are you most likely to get stuck on?" That line is what kills the deal in the room you're not in.

Setting: you're about 30% more expensive than the competition, and they will definitely go and compare.
✗ Hide it and hope

Don't mention it, trust that service will win them over. Then they get the rival quote and open with "they're 30% cheaper" — and now every explanation you give sounds like backfilling. The number they saw first became the anchor, and everything you say afterwards is arguing with an anchor.

✓ Say it first, and hand them the comparison method

"One thing up front: we're roughly 30% more expensive than the cheap end of the market, and that gap is real. It buys two things — we do the migration, and someone picks up the phone within two hours when something breaks.
If you are comparing, I'd compare three things: who does the import, who you call when it breaks, and whether year-two renewal goes up. If you compare and decide it isn't worth it, choosing them is a perfectly reasonable call."
—— "Expensive" goes from something you got caught on to something you flagged; the criteria for comparison are set by you; and that last sentence stops the whole thing sounding like a pitch. By the time they hold the cheaper quote, they're holding your checklist too.

Why it works

Mechanism: exactly like a vaccine — give a weakened, controlled version of the attack and people spontaneously generate reasons against it. When they later meet the strong version (a rival's quote, a colleague's "isn't that expensive?"), the ammunition is already theirs, and self-made ammunition lasts. Bonus: volunteering a weakness raises credibility, because advertising never admits its own faults.

  • Hard evidence · inoculation theory: McGuire & Papageorgis (1961) found in the original experiments that people pre-exposed to weakened counter-arguments, and given refutations, held their position far better under a subsequent strong attack than people given only supportive arguments. Banas & Rains (2010, Communication Monographs) meta-analysed the literature and confirmed inoculation confers resistance, with a small but reliable effect.
  • Fairly strong evidence · admitting a flaw raises credibility: Eisend (2006, International Journal of Research in Marketing) meta-analysed two-sided messages and found a consistent advantage on credibility, with the net effect depending on how heavy and how relevant the negative is. The flaw you admit has to be one they were going to hit anyway — not a core defect that would justify walking away. Admitting that isn't candour; it means you shouldn't be selling it.
  • Industry data · skilled sellers receive fewer objections: Rackham, SPIN Selling (1988), drawing on Huthwaite's observation of some thirty-five thousand sales calls, reached a counterintuitive conclusion: a large share of objections are created by the seller — piling on features and advantages early measurably increases price objections. Strength: vendor-owned research, not peer-reviewed, raw data unpublished, but pointing the same way as the two findings above.

Boundary: inoculation has a dose. Too heavy ("we're often late") isn't inoculation, it's suicide; too light ("if I had to name a flaw, we care too much") carries no threat, produces no resistance, and sounds oily. One test only: is this a pothole they will definitely hit after go-live? If yes, say it now — you've moved their discovery of it from "furious" to "prepared." If no, don't invent one to look candid. Also, inoculation is for people already leaning your way; with someone who disagrees to begin with, voicing the counter-argument first just hands your rival a microphone.

Your Day 20 Action

No new scripts today. Just turn the objections you've already heard into a table you can look things up in.

One (20 minutes): go through your last 10 stalled or dead conversations and write down what the other person actually said — their words, not your paraphrase. Paraphrase flatters automatically.

Two (10 minutes): tag each line: no need / no trust / no hurry / too expensive. Put the ones that won't tag in a separate pile — that pile is usually the valuable one. Count which cell is biggest. That cell is your actual bottleneck, and it's probably not the one you assumed.

Three (15 minutes): write exactly two sentences for the biggest cell: one diagnostic question, one line of agreement to open with. Don't write a third — you won't remember any of them live.

Four (next call): practise one move only — when you hear an objection, restate it and ask a question back, and never once defend. Afterwards note whether they loosened or hardened.

Five (this week): take the most frequent objection and move it into the opening of your next discovery call — weakened version, resolved on the spot.

Boundary: triage, labelling and handing back the choice are all tools for making the truth easier to say. They are not switches that turn "no" into "yes." Some "we don't need it" really means they don't need it, and some "too expensive" really means they can't afford it — spotting those and letting go cleanly sends the time you save to someone who does need you.
Think It Through
1. When they say "let me think about it," should I chase? How many times before it's harassment?
First separate two things that get lumped together: "I don't want it" and "I'm scared of choosing wrong." The first is a demand problem and chasing is waste; the second is an uncertainty problem, and chasing correctly is exactly what helps — and it's more common than people assume, because someone afraid of choosing wrong almost never says no, they say "let me think."

Open your next call by splitting the two with one line: "Since last time — is this just not on the list, or is there a piece you can't quite sign off on? Say it straight, I won't hound you." That second clause is mandatory; it drops the cost of honesty to zero. If the answer is "not on the list," stop pitching and just agree a restart point tied to a hard date they already have (before the new site opens, before the audit, before peak season) — then genuinely let go. If the answer is "I can't sign off on X," the objection has surfaced; go back to triage.

As for how many times: the count isn't the point, what you bring each time is. "Just checking where you landed" is extraction, and three of those is harassment. Bring something usable each time — how a same-sized customer handled that exact pothole, a one-pager they can take to their boss — and five is fine. Hard line: chasing after an explicit "no thanks" is harassment, no exceptions. And if you said "totally your call," you have to actually stop; the entire value of that sentence is that it was true.
2. Won't constant agreeing make me look spineless? When should I just say they're wrong?
It will — if what you're agreeing with is the conclusion. The distinction: concede facts, never conclusions. "Six years without a serious failure" is a fact; agree with it sincerely. "So we don't need to change" is a conclusion; you don't have to echo it or rebut it — just ask a specific question. Faking agreement and adding "but" is the worst of both: it's heard instantly, you don't look decisive, and you've spent your sincerity.

Three situations demand a straight answer. One, a factual error that would make them buy wrong — "this integrates with our old system, right?" If it doesn't, say so on the spot; vagueness here costs a hundred times more than the awkwardness. Two, what they want to buy isn't what they need — "from what you've described, you shouldn't be buying this from us." It loses the deal and it is the highest-return sentence in the job. Three, they're comparing on an obviously wrong criterion (first-year price with no view of renewal) — but give the criteria before the verdict: "I'd compare these three things" beats "you're comparing it wrong."

The rule of thumb: be hard on facts and soft on posture. Soft means "I'm not forcing you and I don't think you're foolish." Hard means "that number is wrong, and we can't do that." Most people have it exactly backwards.
3. Labelling, giving freedom, inoculating — where's the line against manipulation?
One line you can apply in the moment: are you reducing their uncertainty, or manufacturing it? The first is persuasion, the second is manipulation.

Side by side it's obvious. "The migration is genuinely annoying for two weeks, and I'll do it" reduces uncertainty; "this price is only good until tonight" manufactures it. "What would you need to see before you'd be comfortable?" hands them back their own criteria; "if you keep hesitating a competitor will get there first" borrows their loss-sensitivity to bypass their judgement — the same line the scarcity-and-urgency issue drew: real scarcity can be stated, manufactured scarcity can't.

Three finer checks. One, is "totally your call" true? Say it and keep chasing, and it stops being respect and becomes a technique. Two, is the labelling for understanding or for control? "Sounds like it's the hassle — is that fair?" leaves room to be corrected; "I know you're just afraid of the trouble" delivers a verdict. One is a question, the other a sentence. Three, is the flaw you inoculate with real? Picking a harmless fake weakness to look candid isn't a two-sided message, it's theatre.

And in the end, the same ruler: if they later learned the whole truth, would they feel helped or conned? When you can't answer that, you usually already know the answer.