AI playbook examples for handling B2B objections
Train your AI SDR to handle B2B objections with a structured sales playbook. Get concrete examples for price, timing, and competition rebuttals.
Get startedShort answer
To handle objections, replace vague AI instructions with a structured sales playbook. Give the AI specific triggers, rebuttals, and questions to pivot a conversation back toward booking a meeting.
Start with the objections you actually hear
Before you write a playbook, read the replies you already have. Open your LinkedIn inbox and copy the last twenty replies that ended in no meeting. You are looking for repeated sentences. Clever one-offs do not help. A prospect who says 'we do not have budget' and a prospect who says 'this is not a priority' are in different buckets.
Group the replies by what the person is protecting. Some are protecting time. Some are protecting a budget line. Some are protecting a tool they already bought. Some are protecting against looking foolish in front of their team. The bucket tells you what question to ask next.
Do not build a library for every sentence. You need four or five buckets, each with one validation line and one pivot question. If a reply does not fit, it goes to you, not to the AI.
Not interested
- Objection bucket
- Do not argue. Ask what they are using now.
- What the AI should do
- What made you look at this problem in the first place?
Too busy
- Objection bucket
- Lower the ask to a short call.
- What the AI should do
- Would a 10 minute call next week be easier than a full demo?
Already have a solution
- Objection bucket
- Ask about one edge case.
- What the AI should do
- How does your current tool handle [specific workflow]?
Price or budget
- Objection bucket
- Ask about the cost of the current workaround.
- What the AI should do
- Are you paying a person or another tool to handle this today?
Write the rebuttal in three moves
A rebuttal on LinkedIn has one job: keep the conversation alive long enough to ask for a short call. It does not need to prove the product is better. Long paragraphs give the prospect more to ignore.
Use three moves. Validate the concern in one sentence. Ask one question about how they handle it today. Ask for a short call only after they answer. The AI can follow that order. It cannot follow 'be persuasive'.
Keep each message under three sentences. If the prospect writes one line, reply with one or two lines. Matching length is one of the simplest ways to sound human.
- 1
Name the trigger
Write the exact phrases you see: 'no budget', 'not a priority', 'we already use X', 'send me info'. Put them in the playbook as triggers.
- 2
Write the validation line
Use their words. 'That makes sense, budget is tight' works. 'I understand your concern' sounds like a template.
- 3
Add one pivot question
Ask about the current workaround, timing, or what their team would need to see. One question only.
- 4
Set the ask
Ask for a 10 minute call or a specific time. Do not ask for 'a quick chat' because that is not a decision.
- 5
Set the fallback
If the reply includes security, legal, custom pricing or a request for a proposal, stop and hand off.
A price objection is not a request for a discount
When someone says 'too expensive', they often mean 'I do not see enough value yet' or 'this is not in my budget this quarter'. If the AI offers a discount, it teaches the prospect that the first price was fake. It also answers a question you did not hear.
Ask what they are comparing the price to. A manual process, a freelancer, an intern, or another tool. That comparison is the real objection. Once you know it, you can talk about the cost of the current workaround.
Do not defend the price in the first reply. Agree that the number matters, then ask one question. The goal is to get a call where you can show the cost of doing nothing.
Example
- Prospect
This is too expensive for us right now.
- Suggested reply
That makes sense. Are you comparing it to a budget line you already have, or to the cost of handling this manually?
- Prospect
We have someone doing it manually.
- Suggested reply
Got it. Then the question is whether that person is the best use of the time. Do you have 10 minutes Thursday to walk through what that manual work costs you?
- Prospect
Maybe. Send times.
Paste this job
When the prospect says [price objection], do not offer a discount. Reply in this order: 1. Acknowledge the number. 2. Ask what they are comparing it to. 3. Ask for a 10 minute call to walk through the current cost. If they ask for a discount twice, hand off.
Timing objections are usually priority objections
When someone says 'not right now', ask what changes next month or next quarter. Sometimes the answer is a real budget cycle. Sometimes the answer is 'I do not want to deal with this'. You need to know which one.
If the timing is real, book a follow-up for the date they name. Do not keep sending messages every week. If the timing is vague, ask what would make it a priority this month. That question separates a polite no from a real future buyer.
The AI should not promise to check back in six months and then vanish. It should ask for a specific month or a short call now. If the prospect gives a date, set a reminder and stop.
A 'not right now' without a date is a no. Ask for the date before you agree to follow up.
Competition and 'we already use something'
Do not run down the competitor. The prospect chose them for a reason, and attacking that choice makes the prospect defend it. Ask how the current tool handles the one workflow where your product is different.
If they name a competitor, ask what happens when that tool hits the edge case. If they do not know, that is your opening. If they say it works fine, ask for a call to compare notes. You may not win, but you will learn what the market believes.
A useful line is: 'I am not asking you to switch. I am asking whether the current setup handles [specific case].' That line works because it does not ask the prospect to admit a mistake.
Weak reply
- 'We are better than [competitor] and cheaper too.'
- 'Our customers switch because we have more features.'
Strong reply
- 'That tool is solid for [use case]. How does it handle [edge case] today?'
- 'If it handles that well, you probably do not need a call. If it does not, is it worth 10 minutes to compare?'
Know when the AI should stop
An AI SDR should not handle every reply. Some replies need a human: security review, legal terms, custom pricing, a request for a proposal, or a message that mentions a personal problem. The AI can keep the conversation warm, but it should not invent answers.
Set a stop list in your playbook. When a reply includes one of those triggers, the AI should send one short holding message and hand the conversation to you. The holding message should not promise anything. 'Good question. I am pulling in [name] who handles that' is enough.
If the AI gets a reply it cannot classify, do not let it guess. Guessing is how you get a message that sounds confident and wrong. A short handoff is better than a clever reply that loses the deal.
- Security or data questions
- Legal or contract language
- Custom pricing or a discount request
- A request for a proposal or an RFP
- Any message that mentions a personal or sensitive situation
Doing this with Kinlead
Kinlead writes messages and follow-ups from the campaign's goal, tone and an optional sales playbook, which is your own sales script. You can put the triggers, validation lines and pivot questions from this guide into that playbook.
Each campaign chooses how replies are handled: hand the conversation to you at the first reply, let the AI reply until there is real interest, or let the AI reply until a meeting is booked using your scheduling link. Queued messages can be read and edited on the Actions page before they send, and every reply lands in one inbox sorted by intent. See AI LinkedIn outreach.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? AI playbook examples for handling B2B objections.md