Objection-to-Close Rebuttal Swipe File

60 rebuttals for the last mile of a deal

Format: buyer's objection (their words) → your response (verbatim, adjust names/numbers).

PRICE (15)

1. "It's more than we budgeted for." → "Fair — let's separate two things: more than you budgeted, or more than you expected? If it's the budget, let's look at what fits inside it. If it's expectation, let's revisit what's driving the number so it's not a surprise to whoever approves it."
2. "Can you throw in [X] for free?" → "I can look at including [X] if we adjust [term/timeline/payment] to make that work on our side — what could you move?"
3. "Your competitor is cheaper." → "What's actually included in their number? Let's compare scope line by line before we compare price alone."
4. "We could just build this ourselves." → "Totally an option — what's the fully-loaded cost of that, including the months before it's live and whoever's time gets pulled to build it? Let's put that next to this number."
5. "This needs to come down 15%." → "Help me understand what's driving 15% specifically — a budget ceiling, or a negotiating target? Those need different answers from me."
6. "We don't have budget for this right now." → "Is that a 'not this fiscal year' problem or a 'not approved yet' problem? If it's timing, let's talk about starting smaller now and scaling into next cycle's budget."
7. "Price is the only thing holding us back." → "If price were solved today, is everything else — timeline, stakeholders, technical fit — actually ready to go? Want to make sure price isn't standing in for something else."
8. "I need a number with more zeros knocked off." → "I want to get you a number that works — tell me what it needs to look like, and I'll tell you honestly what changes to get there, because it won't be the same deal at that number."
9. "Everyone else gives us a better deal." → "I believe that. What I can promise is this price reflects exactly what's in this proposal, no games. If you want a different price, let's change what's in scope, not pretend the number is soft."
10. "Just send your best and final." → "Happy to — let's get 15 minutes first so I understand what 'best' needs to solve for on your end. A number without that context usually isn't your best fit."
11. "We got quoted half this from another vendor." → "That's a big gap, worth understanding why. Sometimes it's support level, sometimes contract length, sometimes it's a lowball to raise later. Can we look at their proposal together?"
12. "This is a lot for what it does." → "Which part feels like it's not pulling its weight? Let's make sure the price maps to the value you actually need, not the value we assumed."
13. "Our finance team will never approve this." → "What number would finance approve, roughly? Let's see if we get there through scope or terms rather than guessing."
14. "Can we do month-to-month at this price?" → "Month-to-month changes the math for us — this price assumes a 12-month commitment. I can hold this number at 12 months, or requote month-to-month, which runs higher per month."
15. "We need this to fit inside what we paid last year." → "What changed in scope or usage since last year that's part of this number? Let's see what's driving the increase and whether we can offset part of it."

TIMING (15)

1. "We need more time to think about it." → "Of course — what specifically do you want to think through? Want to make sure I'm not leaving you to think through something I could just answer right now."
2. "Let's revisit this next quarter." → "What changes for you between now and next quarter that makes this a better time?"
3. "We're not ready to move yet." → "What would 'ready' look like — a specific milestone or approval you're waiting on?"
4. "This isn't a priority right now." → "Understood — what IS the top priority right now, and is there a connection between that and the problem we've been solving for?"
5. "Can we pick this back up in a few months?" → "We can — what's likely to be different in a few months that isn't true today?"
6. "I need to finish [other project] first." → "Makes sense — does that actually block this, or are they running in parallel for your team?"
7. "Let's slow down, this is moving fast." → "Fair — what pace would feel right? I want to match your process, not rush it."
8. "We just started this evaluation, no rush." → "What does your timeline usually look like for a decision like this, so I can plan around it with you?"
9. "Our fiscal year just started/ended." → "Does that change your budget cycle for this, or just the internal approval timing?"
10. "I'm out for the next two weeks." → "No problem — who can keep this moving while you're out, or should we pick a date right after you're back?"
11. "We have too much on our plate right now." → "What's competing for the team's attention? Want to understand if this gets deprioritized or just delayed."
12. "Let's wait until after the holidays/conference." → "Got it — is there anything that could move forward in parallel, like the technical review, so we're not starting from zero after?"
13. "We need to see how [other initiative] plays out first." → "What's the connection between that and this decision? Sometimes they're more independent than they look."
14. "There's no urgency on our end." → "What would create urgency? Want to understand if there's a cost to waiting that isn't obvious yet."
15. "Let's just pause for now." → "Before we do — what's the one thing that would need to be true for this NOT to pause? Let's see if we can solve that first."

COMPETITOR (15)

1. "We're also looking at [competitor]." → "Good — what's standing out to you about them so far? I'd rather know now than find out later."
2. "[Competitor] does [feature] and you don't." → "Tell me more about how you'd use that — sometimes there's a different way we solve the same underlying need."
3. "We've used [competitor] before and liked them." → "What worked well? Want to make sure we're not asking you to give up something that mattered."
4. "Why should we switch from what we have?" → "Fair question — what's not working with what you have today? If nothing is, we probably shouldn't be having this conversation."
5. "[Competitor] is the market leader." → "They are well known — what specifically made you take this meeting if they're already the obvious choice?"
6. "Your competitor's rep said [claim about your product]." → "I want to make sure you have accurate information — can you tell me exactly what was said so I can respond directly?"
7. "We're doing a bake-off between vendors." → "Good — what does the evaluation criteria look like, and who's scoring it?"
8. "[Competitor] gave us a free trial." → "We can talk about a pilot too — what would you want to prove out before committing?"
9. "We already have a relationship with [competitor]." → "That's valuable — what would it take for us to earn that same level of trust?"
10. "Their integration with [tool] is better." → "Tell me more about that — is it a must-have or a nice-to-have for your workflow?"
11. "We're not sure you're big/established enough." → "Fair concern — what would you need to see to feel confident in our stability and support?"
12. "[Competitor] has more customers our size." → "Who specifically, if you don't mind — I might be able to connect you with a similar customer of ours."
13. "Your pricing model is different, hard to compare." → "Let's normalize both to the same unit — cost per [seat/deal/outcome] — so it's a fair comparison."
14. "We liked their demo better." → "What stood out in theirs? Want to make sure I'm showing the parts of ours that are actually relevant to what you care about."
15. "We're worried about switching costs from our current vendor." → "What does switching actually involve on your end? Let's map it out concretely instead of estimating."

"NEED TO CHECK" / STAKEHOLDER (15)

1. "I need to check with my boss." → "Makes sense — what do you think their first question will be? Let's make sure you have a strong answer, or better, get 15 minutes with them together."
2. "I need to run this by the team." → "Good idea — what do you expect their reaction to be? Anything I should prepare for that conversation?"
3. "Legal needs to review this." → "Of course — is there anything in the contract you already expect them to flag, so we get ahead of it?"
4. "I'm not the final decision-maker." → "Understood — who else needs to be part of this, and can we get them on a call before this goes further?"
5. "My partner/co-founder needs to weigh in." → "Fair — would it help to have them on a short call so they hear the reasoning firsthand, rather than secondhand?"
6. "Procurement owns this process." → "Got it — what does procurement typically need from us at this stage?"
7. "I need buy-in from the other department." → "What's their usual concern when something like this comes up?"
8. "Let me check internally and get back to you." → "Sounds good — what's a fair date for you to have an answer, so I follow up at the right time?"
9. "IT/security needs to sign off." → "Makes sense — do you know their typical review timeline, and is there anything we can send proactively?"
10. "I need approval above a certain dollar amount." → "Is there a way to structure this so it fits under that threshold, or should we plan for that approval step now?"
11. "My manager wasn't in the room for the demo." → "Would it help to do a shorter recap demo just for them, so they're not hearing this secondhand?"
12. "The board needs to approve budget like this." → "Good to know — when does the board meet next, and is there anything I can provide to support that conversation?"
13. "I need to check if this conflicts with another vendor contract." → "Makes sense — anything specific you're worried might conflict?"
14. "I'll loop in the right people and circle back." → "Appreciate that — who besides you needs to be convinced, and what matters most to them?"
15. "This needs committee approval." → "Understood — what does the committee usually weigh most heavily, so we make sure that's front and center?"