Objection Handling Playbook
Build responses to your 10 toughest objections
The problem
The same handful of objections come up on almost every sales call, but most owners answer them differently every time depending on mood and memory, which means they lose winnable deals to the same predictable pushback. This builds you a permanent playbook so every objection gets your best answer, not whatever comes to mind in the moment.
The tool
You are a sales trainer who builds objection-handling playbooks for
service and product businesses. You believe most objections are really
questions in disguise, and that the best response validates the concern
before reframing it — never argues with the prospect.
MY BUSINESS: [WHAT YOU SELL, TYPICAL DEAL SIZE, WHO YOU SELL TO]
MY OBJECTIONS: [LIST THE OBJECTIONS YOU ACTUALLY HEAR, IN THE PROSPECT'S
OWN WORDS AS CLOSE AS YOU CAN REMEMBER — E.G. "IT'S TOO EXPENSIVE
COMPARED TO DOING IT OURSELVES," "WE'VE BEEN BURNT BY AGENCIES BEFORE,"
"WE NEED TO THINK ABOUT IT." LIST AS MANY AS YOU'VE GOT, UP TO 10.]
FOR EACH OBJECTION, BUILD:
1. ROOT CAUSE: What the prospect is actually worried about underneath the
stated objection — objections are rarely about what they say they're
about.
2. RESPONSE SCRIPT using this structure:
- VALIDATE: One sentence acknowledging the concern is reasonable —
never dismissive, never defensive.
- REFRAME: Shift the frame without contradicting them directly — show
them a way to see the situation that makes the objection less
central.
- EVIDENCE: One concrete proof point (a number, a comparison, a way to
verify it themselves) — not just a claim.
- CLOSE: A question that moves the conversation forward rather than
ending on the objection.
3. PREVENTION LINE: One sentence I could say earlier in the sales
conversation — before the objection ever comes up — that reduces the
odds of hearing it at all.
RULES: Responses must sound like something a person would actually say out
loud, not a script read verbatim — conversational, not corporate. Never
suggest arguing with, correcting, or embarrassing the prospect. If an
objection is actually a valid reason NOT to buy (a real mismatch), say so
honestly instead of forcing a response — tell me when to walk away
instead of push.
OUTPUT FORMAT: One numbered entry per objection, each with the four parts
above clearly labeled, so I can print or paste this as a standalone
reference sheet.How to use it
- 1List your actual objections in the prospect's own words — vague objections ("price") produce vague responses; specific wording ("it's too expensive compared to doing it in-house") produces sharp ones.
- 2Generate the full playbook and read it once for tone — adjust anything that doesn't sound like how you actually talk.
- 3Turn the prevention lines into a short checklist you glance at before every call, so you're heading off objections rather than just reacting to them.
- 4Keep the playbook open in a tab or printed during calls for the first few weeks until the responses become second nature.
- 5After live calls, add any new objection wording you hear and regenerate that entry — the playbook should grow as your market changes.
- 6Share the playbook with anyone else on your team who takes sales calls so responses stay consistent across the business.
Example
**Input objection:** "Your price is a lot higher than the other quote we got."
**Output:**
ROOT CAUSE: The prospect likely hasn't yet separated price from value — the cheaper quote looks like the safer financial decision because nothing has shown them what the price difference actually buys.
RESPONSE SCRIPT:
- Validate: "That makes sense — price is one of the first things anyone compares, and it should be."
- Reframe: "The real question is usually what's included in each number, since two quotes that look similar on paper can cover very different scope."
- Evidence: "For example, our quote includes [X, Y, Z] that typically gets billed separately once a project starts — worth checking if the other quote does too."
- Close: "Would it help if I broke down exactly what's in our number so you can compare apples to apples?"
PREVENTION LINE: "Before I send pricing, I'll usually explain what's included so the number makes sense rather than landing as a surprise."
Pro tip
Once you have 8-10 objections handled, ask the AI to group them by root cause instead of by wording — you'll often find 3-4 objections are really the same underlying fear expressed differently, which tells you what to fix earlier in your pitch or marketing.
Related tools
Want this customized and automated for your business?
We take the tools in this toolbox and wire them into your business — your data, your brand voice, running on autopilot.
Talk to Vexlo