Objections: Label, Align, and Pivot
An objection is information. It tells you what the other person needs in order to move forward — what risk they’re managing, what comparison they’re making, what gap they see between what you’re offering and what they need. Treat it as data and it becomes the most useful thing in the conversation. Treat it as an attack and you’ve started a negotiation you’re likely to lose.
Most objection handling fails for one of two reasons: the responder dismisses the objection too quickly (“I hear you, but actually…”), which makes the person feel unheard; or the responder agrees with the objection and then stops talking, which stalls the conversation. The pattern below threads between these two failure modes.
Who it’s for
Anyone who receives pushback — in a sales context, in an internal pitch, in a performance review, in a job negotiation, or in any situation where your proposal is meeting resistance and you need to understand that resistance clearly before you can address it.
The pattern: LAP
Label — Name what you’re hearing as specifically as you can, in their terms.
Align — Find the version of their concern that you genuinely endorse, and say so.
Pivot — Ask one narrow, diagnostic question that helps you understand what they’d actually need to move forward.
The key is that all three steps happen in sequence, without interruption or defense between them.
Step 1: Label
Labeling is naming the emotional reality or practical concern underneath the objection. Not “I hear you” — that phrase has been so overused it means nothing. A real label identifies the specific tension:
“Sounds like you’re weighing [what you’re offering] against [what they already have or know].”
“It seems like the real concern is less about the cost and more about whether this will create work for your team.”
“If I’m reading this right, you need confidence that this will actually get used before you can justify the budget.”
A good label makes the person feel seen before you’ve said a single thing in defense of your position. When people feel seen, they become less defensive. When they become less defensive, they give you more information.
What to listen for to build the label: the specific nouns they used (“the team,” “the timeline,” “the last time we tried this”), the emotion under the words (frustration, skepticism, risk-aversion), and the unstated comparison (what alternative they might be weighing this against).
Step 2: Align
This is not the same as agreeing that your thing is bad. It’s finding the legitimate version of their concern and endorsing it.
Almost every objection has a version that’s completely reasonable. If someone says “it’s too expensive,” the legitimate underlying concern might be: “I don’t have confidence the return is clear enough to justify the cost at this stage.” That concern is completely valid. Say so.
“That makes sense — if the payback period isn’t clear, it’s hard to justify this over other uses of that budget.”
“You’re right to be cautious. Teams that have bought something in this category before and had to clean it up are understandably more skeptical.”
“Honestly, that’s a fair read. If I were in your position with the same information I’ve given you so far, I’d want more evidence too.”
The last example is particularly powerful because it’s completely honest — and honesty at this moment is extremely rare in a sales conversation, which is exactly why it’s disarming.
Alignment is not a technique for tricking someone into lowering their guard. It’s a signal that you’re in the room to help them make a good decision, not to close a deal regardless of fit.
Step 3: Pivot
The pivot is a single, narrow, diagnostic question. Not “so how can we move forward?” — that puts the burden on them. Not a restatement of your pitch. A question that helps you understand specifically what they’d need to feel differently.
“Is the hesitation primarily about the budget, the timing, or the confidence that it’ll work for your specific situation?”
“If the cost were the same and the only difference was [specific thing they mentioned], would that change anything?”
“What would you need to see in a pilot to know whether this is worth the full investment?”
The purpose of the pivot is not to argue them out of their objection. It’s to understand which version of their objection is real — because often the stated objection is a proxy for a deeper concern, and addressing the proxy without addressing the underlying concern doesn’t move anything.
Common objection types with worked responses
“We need to think about it.”
Label: “Sounds like you’re not ready to commit until you’ve had a chance to pressure-test this internally.” Align: “Makes sense — you shouldn’t commit to something this size without your team having a chance to poke at it.” Pivot: “What specifically would make you feel ready? Is there something I haven’t addressed that’s still open?”
(See also: the dedicated article on handling “we need to think about it”.)
“It’s too expensive.”
Label: “It sounds like the concern is whether the return is clear enough to justify the cost given what else is competing for that budget.” Align: “That’s a fair position — the ROI case I’ve made is based on our other customers, not your specific numbers.” Pivot: “If we could quantify the impact specifically for your situation, would that change the calculus? Or is it genuinely a budget availability issue right now?”
“We’re already using [competitor/internal solution].”
Label: “It sounds like switching costs are a real factor here — not just the price but the disruption of moving off something that’s working at some level.” Align: “That’s the right way to think about it. Switching always has a hidden cost.” Pivot: “When you say it’s working — what’s it not doing that has you even taking this meeting?”
“We’ve tried something like this before and it didn’t work.”
Label: “It sounds like you’ve been burned by this before, and trusting that this time would be different requires evidence you don’t have yet.” Align: “That’s completely fair. If I’d spent time and money on something that didn’t deliver, I’d be skeptical of the next version too.” Pivot: “Would it help to understand specifically where the previous attempt failed? I’d either tell you we have the same problem, or tell you where we’re genuinely different.”
“Send me more information.”
Label: “It sounds like you want to evaluate this on your own terms before deciding whether a follow-up conversation is worth your time.” Align: “Reasonable — you shouldn’t have to take another meeting to decide if this is relevant.” Pivot: “So I send the right thing: what’s the specific question you’re trying to answer? I’d rather send three pages of the right content than a twenty-page deck.”
What not to do
Counter immediately. If your first instinct after hearing an objection is to explain why they’re wrong, suppress it. Even if you’re right, being right is not the same as being persuasive. Wait until you’ve completed the Label and Align before saying anything that defends your position.
Use their nouns, not yours. When you label, use the exact words they used. “You’re concerned about the implementation timeline” lands differently than “you’re concerned about how long it’ll take.” They said “timeline” — use “timeline.” This signals that you heard the specific thing they said, not a summary of it.
Winning on Slack. Objections that arrive over text after the meeting are almost impossible to resolve over text. A written response to a written objection produces more writing, not more clarity. When you get a written objection, reply in writing once — briefly, with a label and an offer to talk — and then wait.
Practice prompt
Write down the three objections you most expect in your next high-stakes conversation. For each one, write a LAP response: the label (in their language), the align (a version of their concern you genuinely endorse), and the pivot (one narrow diagnostic question). Read each response aloud. If it sounds like a sales script, rewrite it in the language you’d use with a friend who was raising the same concern. That’s the register you want.
Related reading
- Discovery without interrogation — surface objections early by asking the right questions
- “We need to think about it” — a deep dive on the most common deflection
- The pricing conversation — the specific case where cost is the objection