You're 35 minutes into a discovery call. The prospect is leaning in. You've aligned on their problem, they've seen your demo, and they nod when you mention how this could save their team 10 hours a week. Then you say the price, and they go quiet. "That's more than we budgeted," they say. Or "We're not ready to implement until next quarter." Or "I'd have to check with our CFO first." Your stomach drops. You think you've lost them. So you do what every panicked salesperson does: you lower the price, you offer a "quick pilot," or you ask "is there any way we could make this work?" They sense desperation and ghost you. Wrong move. Here's what you don't know: *that objection wasn't a no. It was a yes with conditions.* You just didn't know how to hear it. This is the Aidxn pattern for the four objections that actually matter.
Why Most Salespeople Lose Deals at Objections
An objection happens when a buyer is interested enough to speak up—but hasn't been convinced enough to move forward. That's not failure; that's a pivot point. The problem: most salespeople either (1) argue back, (2) drop price, or (3) disappear. All three lose the deal. Arguing makes you defensive. Dropping price makes you desperate. Disappearing makes you seem uninterested. What you should do: probe the objection, rephrase it back to them, and offer a specific path forward. Objections are the closest you get to "I'm almost buying."
Here's the truth: if they didn't care, they wouldn't object. They'd just say "thanks, not interested" and hang up. Objections mean they see value but have a real (or imagined) barrier. Your job is to turn the barrier into a bridge. That requires understanding which of the four objections you're actually facing.
The Four Objections That Matter (And How to Handle Each)
Objection 1: Budget ("We Don't Have $X in the Budget")
This is the most common objection and the one salespeople screw up fastest. You hear "we don't have budget" and you panic-discount. Stop. Ask first.
"I hear you. What does your actual budget look like for a tool like this?" Wait. They might say a higher number than you thought. Or they might say "We could stretch to $Y if the ROI is clear." Or they might say "We literally have zero budget." The answer changes everything.
If their budget is lower than your price, you have three moves:
Move 1 (Tie discount to commitment): "I get it. Here's what I can do: if you commit to a yearly contract instead of monthly, I can lock you in at $X per year." You've just turned a price objection into a commitment question. Yearly contracts are worth the margin compression because you reduce churn and support load.
Move 2 (Add value instead of cutting price): "What if I throw in [extra feature / custom integration / dedicated success manager] if you're in by [date]?" Now they're not paying less—they're getting more. Their perceived value rises without you bleeding margin.
Move 3 (Reframe ROI): "You said this process costs your team 10 hours a week. That's about $3K in salary burned every week. Our tool is $500/month. So it pays for itself in a week and a half. What's the constraint—is it timing, or is budget the real issue?" Now you're speaking their language. They're mentally calculating payback. That's a buying signal.
The key: separate "we don't have budget" from "budget is a concern." The first is genuine scarcity. The second is "we're not convinced enough yet." If it's the second, you fix it with ROI clarity, not discounts.
Objection 2: Timing ("Not Right Now" / "Maybe Next Quarter")
This is the objection that sounds polite but kills deals because you follow up in six months and they've already moved on. Don't accept vague timing. Get specific.
"I understand. When you say 'next quarter,' what specifically needs to happen between now and then?" Listen for the real blocker. Is it internal (they need to finish another project)? External (a new budget cycle)? Genuine (they're waiting for board approval)? Or is it just politeness (they're not actually interested)?
If it's real, anchor to it: "Perfect. So if we lock in a contract today with a go-live date of [date], that works for you?" Now you've turned "maybe" into "yes, but later." You've also taken it off the back-burner by making it a real commitment with a date.
If they say "we're not sure what the timeline will be," that's a red flag. They're not actually ready. Probe: "Is the barrier on your end, or is there something about our solution that makes you hesitant?" If they can't name the blocker, they're not a buyer yet. Move on. Don't pretend urgency exists where it doesn't.
The move: "Let's do this: I'll send over a proposal locked to [their timeline]. If things move faster, you can pull the trigger early. If they slow down, we adjust. Sound good?" Now you're the flexible partner. They'll follow up because you're not pestering them—you're accommodating their real situation.
Objection 3: Authority ("I'd Need to Check with My Boss / CFO / CEO")
This is the decider-vs.-influencer objection. You're talking to someone who likes your product but doesn't own the decision. Most salespeople take this as a loss. Smart salespeople turn it into a team sell.
"Good call. Who specifically would need to sign off, and what do they care most about—budget, timeline, technical fit, or something else?" Now you know who you need to convince and what language resonates with them.
Next move: "How about this: I'll send over a summary of what we discussed today, plus a one-page ROI breakdown tailored to their priorities. You can loop them in, or if it's better, I can do a 20-minute call with both of you to walk through it. What works?" You've just made it easy for your current contact to advocate internally. You're also signalling that you understand the buying committee.
The key: get the influencer (the person you're on the call with) to champion your solution internally. Don't skip them and go straight to the decision-maker. That burns bridges. Instead, arm them with language and social proof so they can win the room. "Tell your CFO this is $500/month, saves 10 hours per week, and [competitor name] costs 3x more for half the features."
One last move: if they say "let me loop in my team," ask "When can you get them on a call?" Lock the calendar. The longer you wait, the colder the deal gets.
Objection 4: Need ("We Already Use [Competitor]" / "We Don't Think We Need This")
This objection is about perceived value, not actual need. They either don't see the gap in their current solution, or they don't believe you can fill it better. Two approaches:
Approach 1 (Find the gap): "I hear you. A few questions: with [competitor], how are you handling [specific workflow]? And what's the biggest pain with their approach?" Listen. Most people use Tool A but do part of their workflow in Tool B because Tool A doesn't cover it. That gap is your entry point. "What if you could do that inside one tool instead of three?" Now they're imagining efficiency.
Approach 2 (Acknowledge and reframe): "I totally respect [competitor]. We actually see them as a leader in that space. Here's where we're different: [specific advantage]. For teams that care about [that advantage], we're the better choice. Does that describe you?" You're not trash-talking. You're being honest about where you win. They'll respect the maturity. And if the competitor is actually better for them, admit it: "You know what, if you're happy with them, stick with them. No point switching if it's not broken." You've just become trustworthy. Referrals and future opportunities come from honesty.
The real move: don't assume they understand your value. Ask about their current solution so you can articulate the specific gap you fill. Generic pitch dies. Specific pitch (tied to their current tools) wins.
The Response Framework: One Move That Works for All Four
Here's the template for any objection:
Step 1: Affirm. "I get that. That's a real concern."
Step 2: Probe. "Tell me more. When you say [objection], what specifically worries you?"
Step 3: Rephrase. "So what I'm hearing is [restate their real blocker]. Is that right?"
Step 4: Offer three paths. "Here's what we can do: [move 1], [move 2], or [move 3]. What feels right to you?"
Step 5: Lock commitment. "Great. So we're doing [move]. Let me get that to you by [date], and I'll follow up on [date]."
The key: give them options, not ultimatums. "Here's what we can do" vs. "Here's what you need to do." One keeps them in the conversation; one makes them defensive.
When to Walk Away (And How to Do It Gracefully)
Not every prospect is a buyer. Sometimes the objection is real, and you're not the solution. Knowing when to walk separates pros from desperate amateurs.
Walk if they say: "We're using [competitor] and we're very happy" (your energy is wasted). "We're not looking to change vendors right now" (they'll ghost after you spend 10 hours on them). "We need to see a full self-serve demo before deciding" (no buying signal). "Can you discount 50%?" (they're shopping, not buying).
When you walk, do it with grace: "I don't think we're the right fit for where you are right now, but I think you're solving the right problem. If things change or you want a second opinion down the line, I'm here. No pressure. Keep crushing it." They'll remember you as the professional who didn't waste their time. Referrals and future deals come back.
Six FAQs on Objection Handling
What if they come back with a new objection after I've answered the first one?
That's not a new objection—that's a stalling tactic. They're testing whether you're serious. Answer it the same way: affirm, probe, rephrase, offer moves. If they do it three times, they're not a buyer. Be direct: "It sounds like you have concerns beyond what I can address today. What would need to be true for you to move forward?" Force clarity.
Should I ever drop price?
Only if they commit to something else in return: yearly contract, larger team/seats, beta feedback, case study. Never discount for nothing. You're training them to expect lower prices, and you're signalling weakness. Tie discounts to value-adds or commitment, and the conversation stays professional.
What if the objection is "Your product doesn't do [feature]"?
First, check if they're right. If yes: "You're right. That's on our roadmap for Q4. For now, here's how we handle it: [workaround]." If no: "Actually, we do. Let me show you." Then show it in their specific use case, not a generic demo. Specificity kills doubts.
How do I know if it's a real objection or just stalling?
Real objections come with specific language: "It's not in our budget," "We need CFO approval," "We use Tool X and it integrates directly with our workflow." Stalling sounds vague: "We'll think about it," "Let's revisit in a few months," "Sounds interesting." Stalling never converts. Probe until you get specificity, or walk.
Can I overcome an objection via email?
No. Objections require dialogue. You need tone, pace, and the ability to probe. An email objection response is a one-way pitch. They'll ignore it. If the objection came up on a call, handle it on the call. If it comes via email, reply: "Great question. This is easier to walk through on a call. You got 15 minutes tomorrow?" Lock it live.
What if my product is genuinely more expensive than competitors?
Own it. "We're not the cheapest option out there. What you get is [specific value: better support, faster implementation, deeper integrations]. For teams that care about those things, the ROI is there. Do you?" Now it's a values conversation, not a price conversation. Some buyers will say yes; some will shop. The yes-buyers are worth it.
The Bottom Line
Objections kill deals only if you panic. The four objections—budget, timing, authority, need—aren't rejections. They're conditional yeses. Your job is to understand which condition you're facing, probe until it's clear, rephrase it back to them, and offer a specific path forward. Most objections dissolve when you show you're listening. Most deals close when you're not desperate. Handle objections like a therapist, not a closer: ask good questions, validate their concern, and let them convince themselves. That's when they sign.
Want to dig deeper into objection handling on live calls? Check out the discovery call script where objection-handling lives in context. Or see how we price our own services — we use this exact framework with every prospect. Ready to talk?