Practical objection handling lessons from the Sales Micro Learning archive, organized so you can find a useful move before your next sales conversation.
A buyer spends 30 minutes reviewing your solution, then says, “We’re happy with our current vendor.” Yet something made this conversation worth taking. Surface that reason without attacking the incumbent: “That makes sense. Given things are working, what made this conversation worth having now?” Their answer may reveal a missing capability, upcoming change, or concern they haven’t named. Now you can discuss why they explored—not force a comparison they never asked for. 🎯 Try this today: Paste that question into the notes for one deal where an incumbent could become the default choice.
A buyer closes the proposal and says, “This looks useful, but switching sounds painful.” The word “switching” may hide one specific concern. Make the burden concrete before answering: “When you picture the switch, which part feels hardest—moving data, getting internal buy-in, or getting the team productive?” Once they choose, you can address the real objection instead of promising that everything will be easy. 🎯 Try this today: Write that question into the notes for one deal where change effort could stall the decision.
Use the Budget Bridge when a buyer says, “We don’t have budget.” Most reps hear a dead end. Better reps find out whether it’s a money problem, a priority problem, or a timing problem. 1. Label it: “Sounds like budget is the main concern right now.” 2. Isolate it: “If budget were available, would this be something you’d want to solve?” 3. Reconnect to impact: “What is the current issue costing the team each month it stays unsolved?” 4. Map the path: “How do unplanned priorities usually get funded here?” 5. Set a checkpoint: “When should we revisit this based on planning or the next trigger?” Budget objections are often priority objections wearing a finance costume. 🎯 Try this today: Find one deal marked “no budget” and ask one question that separates money, priority, and timing.
When a buyer says, “I need to run this by my boss,” don’t hear it as a brush-off or a yes. Hear it as a coaching moment. Your real job is to find out whether they can explain the pain, impact, and recommendation when you’re not in the room. 🎯 Try this today: Ask one buyer, “When you bring this up internally, what part do you think will get the most pushback?”
When a buyer says “we already use X,” don’t attack the incumbent. That just makes them defend their decision. Use the Incumbent Wedge: 1. Label: “Sounds like you’ve already got something in place.” 2. Respect: “Makes sense — switching for the sake of switching is rarely worth it.” 3. Probe for strain: “Where does it work well, and where do teams still create workarounds?” 4. Quantify: “How often does that happen, and who feels it most?” 5. Earn comparison: “If that gap is worth solving, would it be useful to compare how others handle it?” This borrows from Never Split the Difference: lower resistance before asking for the truth. 🎯 Try this today: Write your 5-line response to “we already use a vendor” and include one question about workarounds.
When a buyer says “not a priority,” don’t try to make your product sound more exciting. Treat it like a stack-rank problem: “Totally fair — what’s sitting above it right now?” Their answer tells you whether to reframe, nurture, or walk away cleanly. 🎯 Try this today: Write a two-line response to “not a priority” that acknowledges it, then asks what initiative is getting the attention right now.
“Send me info” is usually not a next step. It’s a polite exit unless you attach it to a reason and a follow-up. Use the Door Crack framework: 1. Acknowledge: “Happy to.” 2. Narrow: “So I don’t send a generic deck, what’s most relevant: pipeline, rep productivity, or forecasting?” 3. Trade: “I’ll send the 2-minute version on that.” 4. Advance: “If it looks relevant, should we compare notes Thursday at 10?” You’re not refusing. You’re turning a brush-off into a real signal. 🎯 Try this today: Write your 4-line response to “send me info” and use it before sending any deck or one-pager.
When a prospect says, “We already have a vendor,” don’t attack the vendor. That makes them defend a decision they probably helped make. Instead, respect the incumbent and question the fit against today’s reality: “Makes sense. What’s changed in the business since you picked them?” 🎯 Try this today: Write a one-line response to your “we already use ___” objection that starts with agreement, then asks what has changed.
Most reps answer objections too early. Use the 3-Beat Objection Reset before you defend anything: 1. Cushion: “That’s a fair concern.” 2. Clarify: “When you say implementation risk, do you mean timeline, IT bandwidth, or adoption?” 3. Convert: “If we could show a low-lift rollout plan, would that address the concern—or is there another blocker?” Objections get easier when you stop reacting to the headline and uncover the real fear underneath. 🎯 Try this today: Take one common objection you hear and write your Cushion → Clarify → Convert response in three lines.
When a prospect says, “We’re not prioritizing this right now,” don’t rush to prove ROI. That often sounds like you didn’t hear them. Use a Chris Voss-style label first: “Sounds like this feels important, but not urgent enough to displace what’s already on your plate.” 🎯 Try this today: Write one label for your most common objection, then use it on your next call before asking any follow-up question.
PEARL — a 5-step loop that keeps you composed when tension spikes 1. Pause: the instant you feel heat, stop talking mid-sentence if needed. Silence buys you control. 2. Exhale: one slow 4-count breath lowers cortisol and buys your brain oxygen. 3. Acknowledge: name the emotion in neutral words (“Sounds like you’re frustrated about the delay”). Labeling defuses it (see: Never Split the Difference). 4. Reframe: shift from blame to joint problem (“Let’s figure out how to hit the date without burning the team”). 5. Listen: give them 30 seconds of uninterrupted airtime—your curiosity signals respect and gathers data. 🎯 Try this today: In your next charged moment—email or meeting—run PEARL in order. Notice which step feels hardest; practice that one twice more before close of business.
When someone knocks your idea in a meeting, turn defense into data: pause, nod, and say, “Interesting—can you walk me through what you’re seeing that I might have missed?” Their brain shifts from attack to explanation, you get intel, and everyone sees you stay unflappable. 🎯 Try this today: In your next discussion, the moment you feel the urge to rebut, deploy that sentence verbatim and stay silent for one deep breath while they respond.
SOAP Answer — four lines that keep exec Q&A under 30 seconds 1. Statement: give the straight answer first (“Yes, we can ship by 6/30.”) 2. Outcome: name the metric or risk at stake (“Hits FY churn target—saves ~$140k.”) 3. Approach: one sentence on how you’ll make it true (“Pulling two contractors onto QA, nightly regression kicks off Monday.”) 4. Proof: a concrete data point or precedent (“Same swap cut bug backlog 23 % last quarter.”) 🎯 Try this today: Pick one hard question you expect in your next leadership meeting—draft its four-line SOAP Answer and rehearse it once before you log on.
Executives don’t fear your idea’s cost—they fear being stuck with it. Add an explicit rollback clause: “If churn isn’t down 2 % in four weeks, we revert in under 30 minutes with zero customer impact.” You’ve turned a one-way door into a swing gate, and risk-averse brains relax enough to say yes. 🎯 Try this today: Draft one ask you’ll make today and append a single sentence that names the success metric, the deadline, and the exact reset step.
C.A.L.M. Loop — the 4-step reset when a conversation turns tense 1. Center: inhale 4, exhale 6, silently label your feeling (“frustrated”). Naming emotion lowers its grip (Kross, Ethan). 2. Acknowledge: voice their emotion in one line (“Sounds like this delay is stressing you”)—a “label” in Never Split the Difference that melts resistance. 3. Listen: give them 30 silent seconds after one prompt (“Tell me more about the impact”). No nodding at Slack, just ears. 4. Move: suggest a single concrete next step you can both live with (“Let’s list two fixes and pick by 3 p.m.”). 🎯 Try this today: When the next micro-friction flares (late spec, blunt email), run C.A.L.M.—watch the room cool and the path forward appear in under a minute.
M.I.N.T. — a four-step snap check for turning “I’ll think about it” into “Deal.” 1. Motive — open with how it advances THEIR goal (“Cuts your ticket backlog 25%”). 2. Impedance — remove the friction (“My team handles the rollout; you just review the doc”). 3. Norms — show peers already on board (“Ops and Legal signed off yesterday”). 4. Tradeback — offer a give they value (“You’ll get first dibs on the beta metrics”). 🎯 Try this today: Draft your next ask as four bullets labeled M, I, N, T. If one feels thin, bolster it before you hit send or speak.
A short, practical lesson on prospecting, discovery, objection handling, or closing - delivered to your inbox each morning. Free to start.