TL;DR
Don't rewrite your sales scripts just because prospects say no — often, the real issue is pitching without a decision-maker present or letting calls end without a next step. Objection handlers are meant to support your sales sequence, not lead your pitch or replace discovery. Use these 5 B2B objection scripts to isolate the real blocker (value vs. cost) and bridge to a concrete calendar hold or pilot engagement.
What Are Sales Objections Scripts?
Sales objections scripts are predefined responses used to handle prospect pushback during a call or in a follow-up email.
When to use them: Use a sales objections and responses template to keep the conversation moving and isolate the real blocker (e.g., budget, authority, timing) after you've listened to the prospect's concern.
When not to use them: Do not use them to preempt objections before they are raised or to act like a "corrective consultant." They should support your sales sequence, not replace genuine discovery.
It happens constantly: a founder wraps up their third product demo of the week, and once again, the prospect ends it with, "I need to discuss this with my boss." The founder immediately pauses outreach and spends the next three days rewriting their email sequences and creating a new sales objections and responses template.
But the script was never the main problem. The real mistake was outsourcing their learning to a script too early. They were selling without the actual decision-maker in the room and repeatedly letting the call end without a committed next step. You need to do enough manual sales calls to know which objections are real. As HubSpot notes, handling objections requires active listening first. If you use scripts like a "corrective consultant" trying to prove your prospect wrong, you will fail, because nobody wants to pay to be told they are wrong. Sales is simply an equation of perceived value versus perceived cost and complexity.
Summary: Top 5 B2B Sales Objections
Objection | Real Blocker | Script Goal | Next Step |
|---|---|---|---|
"I need to think about it." | Value, cost, or timing | Isolate the true hesitation | Concrete calendar hold |
"I need to talk to my boss." | Authority | Multi-thread the deal | Direct meeting with decision-maker |
"It's too expensive." | Cost and risk | Offer a structured pilot | Review a pilot scope |
"We use a competitor." | Value and trust | Return to original intent | Targeted test addressing a gap |
"This is not a priority." | Timing and value | Align with top priority | Firm future date or immediate pivot |
5 Sales Objection Handling Examples (Swipe File)
Below are the five most common early-stage B2B sales objections, along with copy-paste script cards. Every response is designed to clarify the objection, reframe it around the buyer's goal, and enforce an "objection-to-next-step check" to keep the sequence moving.
1. "I need to think about it."
When a buyer needs to think, do not leave the conversation in limbo. You need to isolate whether they are concerned about the value, the cost, or the timeline.
Say this on the call:
"Absolutely, it's a big decision. Just so I'm clear on where we stand—is the hesitation around whether this fits into your current roadmap, or is it more about the pricing structure? Let's put a brief 20-minute sync on the calendar for Thursday so you have time to review."
Send this after:
"Hi [Name], great talking today. As discussed, I’ll leave you to review the workflow we mapped out. I’ve sent over a calendar invite for Thursday at [Time] to catch up on any questions about how this fits your roadmap or pricing. Let me know if you need any documentation before then."
Do not say: "Sure, I'll follow up next week." (This is a passive release that kills momentum).
Ask for this next: A concrete calendar hold while the buying impulse is alive.
Objection-to-next-step check:
Objection | Real Blocker | Script Goal | Next Step |
|---|---|---|---|
"I need to think about it." | Budget or strategic fit | Isolate true hesitation | Thursday calendar hold |
2. "I need to talk to my boss / team / partner."
This usually means the decision-maker was not on the call.
Say this on the call:
"That makes complete sense; you definitely need [Boss's Role] on board. Usually, when teams take this to leadership, the biggest question is how it impacts [Specific Metric/Goal]. Let’s do this: let's put 15 minutes on the calendar for next Tuesday with you and [Boss's Name] so I can answer their technical questions directly."
Send this after:
"Hi [Name], attaching the one-pager on how we impact [Metric] for your conversation with [Boss's Name]. I’ve also sent a placeholder for Tuesday to review this together so I can take the burden of answering technical questions off your plate."
Do not say: "Okay, let me know what they say."
Ask for this next: A multi-threaded meeting with the actual decision-maker.
Objection-to-next-step check:
Objection | Real Blocker | Script Goal | Next Step |
|---|---|---|---|
"I need to talk to my boss." | Authority | Multi-thread the deal | Direct access to decision-maker |
3. "It’s too expensive."
When pricing is the stated blocker, you need to either lower the perceived risk or clarify the perceived value. If they are interested but risk-sensitive, this is the time to introduce a pilot. As Steve Blank's customer development methodology suggests, reducing customer risk through iterative testing is often more effective than simply discounting.
Say this on the call:
"I hear you. If budget is the primary blocker right now, what if we structure this as a low-risk pilot? We can define a very specific scope for the next 30 days to prove out the ROI on [Specific Pain Point]. If it works, we discuss a full contract. If not, we part ways. Does a scoped test make it easier to start?"
Send this after:
"Hi [Name], following up on our chat. Since managing upfront cost is critical for you right now, I’d like to propose bringing you on as a design partner.
The scope: We will run a 30-day pilot focused strictly on [Specific Goal].
The ask: Weekly 15-minute feedback loops with your team.
The timeline: We can spin this up by Monday.
Let me know if you're open to reviewing a pilot agreement."(For more details on structuring this, see our design partner pilot email template).
Do not say: "Actually, doing this manually is costing you a lot of time and money compared to our software." (This is corrective consulting and creates friction).
Ask for this next: A structured, low-risk pilot engagement.
Objection-to-next-step check:
Objection | Real Blocker | Script Goal | Next Step |
|---|---|---|---|
"It's too expensive." | Cost and risk | Offer low-risk pilot | Reviewing a pilot scope |
4. "We already use a competitor / built this internally."
Use this to return to discovery. Find out why they booked the call in the first place instead of feature-dumping.
Say this on the call:
"Makes total sense, [Competitor/Internal Tool] is a great setup. I'm curious though—what was the main reason you originally signed up for our call today? Was there a specific gap or workflow you were hoping to fill?"
Send this after:
"Hi [Name], really appreciate your transparency about using [Competitor]. Based on what you shared about struggling with [Specific Gap they mentioned], I’ve attached a quick breakdown of how we handle that specific workflow differently. Let’s keep our tentative hold for Friday to see if running a parallel test makes sense."
Do not say: "We're actually much better than [Competitor] because we have X, Y, and Z features."
Ask for this next: A parallel test or a follow-up call focused strictly on their unmet need.
Objection-to-next-step check:
Objection | Real Blocker | Script Goal | Next Step |
|---|---|---|---|
"We use a competitor." | Value and trust | Return to discovery | Targeted test for the gap |
5. "This is not a priority right now."
Reframe this objection around their existing strategy and goals.
Say this on the call:
"I completely understand; everyone's bandwidth is maxed out. You mentioned earlier that accelerating your Q3 launch was the top priority. How does keeping the current manual process impact that timeline? If we can save you [Time/Money] on that specific goal, is it worth 15 minutes next week to explore a limited test?"
Send this after:
"Hi [Name], I know this isn't top of the priority list this quarter. I'm taking a step back until you're ready, but since you mentioned the Q3 launch is critical, I wanted to leave you with this quick case study on how we accelerated a similar launch for [Company]. Let's touch base in [Month]."
Do not say: "But implementing this will actually save you time right now!"
Ask for this next: A defined timeline for reconnection, or a pivot to how you serve their immediate top priority.
Objection-to-next-step check:
Objection | Real Blocker | Script Goal | Next Step |
|---|---|---|---|
"This is not a priority." | Timing and value | Reframe around goals | Firm future date or pivot |
Tactical Checklist: The Pre-Flight Check
Before using any of these scripts, you need a process for diagnosing the real pushback. Run through this mental checklist before and during the call:
Confirm buyer role: Are you talking to the decision-maker or an evaluator?
Identify the pain: Do you know exactly why they booked the call?
Understand current workaround: What are they currently using to solve this problem?
Define the decision process: How does their team actually buy software?
Secure the next meeting: Never leave the call without a calendar hold or a signed pilot.
The core flow to remember on a live call is:
Objection → Clarify why they took the call → Reframe around their goal → Ask for the pilot/next step
FAQ
What are sales objections scripts?
They are prepared responses used by founders and sales teams to effectively handle common prospect pushbacks (like "it's too expensive" or "I need to think about it").
What is a sales objections and responses template?
It is a swipe file or structured guide containing specific phrases, follow-up emails, and action items that help you navigate rejections and secure a concrete next step.
Should we build sales objections scripts into the front of the pitch so we preempt every objection?
No. Objection handlers are support material, not your lead message. Do not lead your pitch with "You might be thinking this is too expensive, but..." Start by finding out why the buyer booked the call in the first place, do proper discovery, and then use an objection handler only when their specific concern appears. Do not make the script sound like corrective consulting, because prospects do not want to pay to be told they are wrong.
How do you handle 'I need to think about it'?
Do not let the call end without a concrete next step. Ask clarifying questions to isolate if the concern is about value, cost, or timing, and secure a calendar hold for a brief sync later in the week.
When should an objection become a pilot offer?
When a prospect is clearly interested but states that pricing is the main blocker. A trial or pilot works as a great objection handler by reducing risk, supporting your sequence rather than replacing discovery.
