When a prospect replies, “We already have a provider,” you know something about their current setup. You still don’t know whether they’re satisfied, how much your offer overlaps with that provider, or whether they’re considering a change. A short question can help you work out whether there’s anything useful to discuss.
Sales objection handling means understanding a buyer’s concern and responding with information that helps them decide what to do next. Over email, that often means asking for clarification before offering an explanation.
Below are seven common B2B replies, with templates you can adapt to the conversation and a worksheet for recording concerns and agreed next steps.
What counts as a sales objection?
A sales objection is a concern that could prevent a buyer from moving forward. It might relate to price, timing, an existing supplier, or whether the solution addresses a worthwhile problem. Other replies, such as requests for information or referrals, call for a different response.
| Buyer’s reply | What you know |
|---|---|
| “It’s too expensive.” | The buyer has a concern about the cost or perceived value. |
| “Contact me next quarter.” | The buyer has suggested a later conversation. |
| “Send me more information.” | The buyer wants information before deciding whether to continue. |
| “I’m not the right person.” | You need to check ownership of the problem or purchasing decision. |
| “Please stop contacting me.” | You should stop the outreach and record the request. |
A request for information or a referral isn’t automatically an objection, and an objection alone doesn’t establish buying intent. Read the reply in context before deciding how to respond.
How to handle sales objections over email
Read the full thread before choosing a template. A reply to an unsolicited introduction needs a different response from a concern raised after a demo and proposal.
Acknowledge what the buyer said, clarify anything that would change your answer, and provide relevant information. Asking questions before attempting to resolve the concern is also central to Highspot’s objection-handling guidance.
Keep the next step proportionate to the conversation. Someone asking for a pricing breakdown should receive that breakdown. Someone who has explicitly ruled out the project should not receive another meeting request.
Before sending, check:
- Does the response address the buyer’s actual concern?
- Are the product details, pricing, and supporting claims accurate?
- Is the question necessary to understand the situation?
- Does the proposed next step match what the buyer has agreed to?
The templates below are starting points. Replace the brackets with verified details and remove anything that doesn’t fit the thread.
1. “We already use another solution.”
An existing provider may cover everything the buyer needs or only part of the workflow. Don’t assume they’re dissatisfied or criticize a competitor you haven’t evaluated in that account.
Hi [First name],
Thanks for letting me know. Does your current setup also cover [specific task relevant to your offer]?
I reached out because [brief, verified reason this task may matter to their team]. If it’s already covered, I’ll leave it there.
[Your name]
The question should identify a real distinction. For example, a team may already have a contact database while still researching account activity manually.
If the prospect confirms that their current setup meets their needs, acknowledge it and close the conversation. A hypothetical gap isn’t a reason to keep pushing.
2. “We don’t have the budget.”
A lack of budget can mean funding is unavailable, the project isn’t a priority, or the buyer hasn’t established a reason to spend. Use what you already know about the conversation. If they clearly say there’s no project or interest, thank them and stop. If a relevant project has been delayed, you could ask about a later check-in.
Hi [First name],
Thanks for the update. I’ll pause the conversation for now.
You mentioned [confirmed project or priority] earlier. Would you like me to check back in [month], or would you prefer to get in touch if funding becomes available?
[Your name]
This version assumes you’ve had a meaningful discussion about a project. For a cold prospect who says they have no budget, a short acknowledgment may be enough. Record any agreed follow-up date and pause the original outreach sequence until then.
3. “It’s too expensive.”
This concern usually comes after the buyer has seen a price. Before defending the quote or offering a discount, find out what they’re comparing it with. They might be concerned about affordability, the proposed scope, an unexpected fee, or whether the value justifies the cost.
Hi [First name],
Thanks for being direct. Is the concern that the total exceeds your available budget, or that the proposed scope doesn’t justify the cost?
The quote includes [accurate summary of the main inclusions]. I can send an itemized breakdown so you can review what you would be paying for.
[Your name]
Let their answer guide the response. Explain what’s included if scope is the issue. If they have a firm spending limit, be honest about whether you can meet it.
Offer a smaller package or different terms only if those options are available and approved. Any value calculation should use the buyer’s inputs and clearly stated assumptions.
4. “Contact me next quarter.”
The buyer has suggested a possible next step. Agree on a time without adding another pitch to the reply.
Hi [First name],
Thanks. Would [week or date] be a suitable time for me to check back?
I’ll pause outreach until then. When we reconnect, we can revisit [topic already discussed] and check whether the timing has changed.
[Your name]
A date gives both sides a shared expectation, but it isn’t a commitment to buy or attend a meeting. When you follow up, briefly reference the earlier exchange and ask whether the topic is still relevant. Don’t restart the conversation as if the buyer has never heard from you.
5. “We handle this internally.”
The internal team may be doing the work successfully. If there’s a task where outside support could help, explain how your offer would fit without suggesting the buyer’s employees need replacing.
Hi [First name],
Thanks for clarifying. Which part of [workflow] does your team currently spend the most time on?
Our role is to help with [specific task your offering supports]. If that task is already working well internally, there may be little reason to change it.
[Your name]
Ask this only when the buyer has shown some willingness to discuss the workflow. If their message is a clear decline, acknowledge it instead.
If they describe a problem you can address, explain the relevant capability and its limits. Use an example to show how the work would fit into their existing process.
6. “Send me more information.”
Send something the buyer can evaluate that matches their question or the issue discussed in the thread. Requiring a meeting before providing basic information adds unnecessary friction.
Hi [First name],
Of course. Here’s [resource link], which covers [specific topic].
The part most relevant to your question is [short, factual explanation]. It also explains [important requirement or limitation].
If you have questions after reading it, I’m happy to answer them here.
[Your name]
Include a brief answer or summary so the email is useful even if they don’t open the link. A product overview, pricing page, technical explanation, or relevant case study may fit. Avoid sending several attachments and leaving the buyer to find the answer.
If you want permission to follow up, ask plainly. Sending information doesn’t establish an agreement to receive an ongoing sequence.
7. “I’m not the right person.”
Check who owns the responsibility you’re asking about. The recipient may understand the topic without being responsible for it, or they may be telling you the outreach is misplaced.
Hi [First name],
Thanks for letting me know. I’m trying to reach whoever oversees [specific responsibility] at [Company].
If you’re comfortable pointing me to the relevant team or person, I’d appreciate it. Otherwise, no problem.
[Your name]
Be specific about the responsibility. “Who handles sales?” is harder to answer than “Who owns outbound account research?”
A referral helps you find the right contact; it doesn’t mean the original recipient endorses your offer. Describe the introduction accurately when approaching the new contact.
A sales objection handling worksheet
Copy this table into a spreadsheet or your existing sales notes to keep the context behind each reply.
| Field | What to record |
|---|---|
| Account and contact | Company, contact, role, and conversation owner |
| Exact buyer reply | Their original wording |
| Conversation stage | Initial outreach, discovery, demo, or proposal |
| Confirmed concern | What the buyer explicitly told you |
| Missing information | What you still need to understand |
| Supporting information | Approved pricing, product details, or relevant resources |
| Response sent | The reply used in this conversation |
| Agreed next action | Action, owner, and date, if agreed |
| Contact status | Active conversation, paused, closed, or do not contact |
For example, imagine a buyer replies after a proposal: “We can’t fund this until January.” The confirmed concern is funding timing, and January is a possible follow-up period. Record whether they agreed to a check-in and anything you still need to clarify.
Don’t record “will buy in January.” That’s an assumption that could mislead the next person handling the account.
When to stop handling an objection
Stop outreach when someone asks you to stop or unsubscribe. Record the request through your team’s process so another campaign doesn’t restart contact.
Be willing to close a conversation when the buyer has no relevant need, your offering cannot meet an essential requirement, or there’s no workable commercial fit. Repeating an argument after the buyer has answered it rarely gives them useful information.
Using AI for sales objection handling
An AI-generated response needs accurate product information and enough context to interpret the buyer’s message. “We don’t have the budget” shouldn’t trigger an invented discount, and a question about an unsupported integration shouldn’t receive a confident promise.
Alisha, Floworks’ AI SDR supports personalized email outreach, objection handling, and meeting scheduling.
When evaluating it for your team, bring anonymized examples of the replies your salespeople receive. Ask to see how those situations are handled, especially when the answer depends on pricing, technical requirements, or a buyer’s request to end the conversation.
Book a Floworks demo to discuss how Alisha could fit your outreach and reply-handling workflow.
Frequently asked questions
What is sales objection handling?
Sales objection handling means understanding a buyer’s concern and responding with relevant information. The outcome may be a further conversation, an agreed follow-up, or a decision to close the opportunity.
Should you respond to an objection with a question?
Ask a question when the answer would change your response. If the buyer has already explained the concern clearly, address it directly.
What is the difference between a sales objection and a rejection?
An objection raises a concern that may need discussion. A rejection communicates that the buyer does not want to proceed. Respect a clear rejection, particularly when it includes a request to stop contact.
Can you reuse the same objection handling template?
You can reuse the structure, but check it against each conversation. The buyer’s wording, the sales stage, and any previous commitments should determine what you send.
