Customer objection response script template
An objection is only useful if it changes your next action. This worksheet runs three moves in a fixed order — classify the blocker, match proof or scope to it, ask for exactly one decision — so the reply you send is aimed at what is actually blocking the buyer rather than at the sentence they happened to say.
Published Updated Published by The Foundable team
Overview
The common failure is answering the stated objection at face value. Someone says the price is high; the real blocker is that they have never seen the thing work. Classification comes first and is not optional: write down which of the nine blockers this reply represents before you draft a word.
Quick answers
What should an objection response contain?
One named blocker, one instrument matched to it — a proof point, a sample, a screenshot, a smaller scope, a risk reducer or a willingness-to-pay question — and one closing ask. Not three asks, and not a paragraph of reassurance.
How should the script handle price pushback?
Acknowledge the concern, restate the paid outcome, clarify scope or reduce risk, offer a smaller test where that makes sense, then ask what result or price would make it worth trying. Reflexive discounting removes the signal you were trying to collect.
Is silence an objection?
Treat it as a classifiable reply category. Silence after a specific ask usually carries information about timing, authority or fit, and it belongs in the log next to the spoken objections.
What counts as a good outcome?
A decision. A clear no that you can log is a successful outcome of this script — it frees the follow-up slot and tells you something about the audience. A polite maybe is the outcome to avoid.
Classify the blocker
Paste the buyer's reply in their exact words and name the category before drafting. Keeping the wording intact matters: the phrases people choose are the diagnostic material, and paraphrasing loses them.
- The nine categories: price, timing, trust, proof, scope, authority, fit, referral, silence.
- The phrase in their reply that made you choose that category — quote it.
- The second-most-likely category, if you are not sure. Uncertainty is a legitimate entry.
Before pasting a real reply anywhere — here or into an assistant — remove names, phone numbers and company identifiers. A customer did not consent to being processed.
Match proof and scope
Pick one instrument that fits the diagnosis. A proof gap needs the single most relevant example, not five. A scope mismatch needs a smaller first step, not a lower price. A risk concern needs a risk reducer — a shorter commitment, a defined exit, a milestone payment.
- The instrument: proof point, sample, screenshot, smaller scope, risk reducer, or a willingness-to-pay question.
- The one artefact you will actually attach or link.
- What you will not do: the discount, the extra feature, or the free trial you were tempted to offer.
Ask for one decision
Close with exactly one next step and a follow-up date. Then write down the decision rule: what this reply, and replies like it, would change about audience, price, package, proof asset, follow-up timing or the paid ask.
- The closing ask: a clarifying answer, an example review, a referral, a short call, a smaller paid test, or a clear no that can be logged.
- The follow-up date, written now rather than remembered later.
- The decision rule: what changes if this blocker appears three times.
Fill the template here
Redact names and numbers before pasting a real reply. Fill the classification before you draft the response — that order is the whole method.
Do this step for me
The classification and the draft you typed travel with you. Foundable's page sends a fixed prompt and none of your text; this carries the real content, and nothing leaves your browser until you press it.
- Buyer reply, verbatim
- Blocker category
- Proof or scope instrument
- The single closing ask
- Follow-up date
- Decision rule
What you leave with
- A classified blocker with the buyer's own phrase attached
- One matched response instrument and the artefact behind it
- A single closing ask with a follow-up date
- A decision rule for what a repeated blocker changes
- A Markdown export you can paste into your own notes
Workflow
- 01
Paste the exact reply
Keep the buyer's words, strip their identifying details. The wording is the diagnostic input.
- 02
Classify before drafting
Name the blocker and quote the phrase that made you choose it. Drafting first biases the diagnosis.
- 03
Match one instrument
Proof, smaller scope, risk reducer, follow-up date, referral ask, or a willingness-to-pay question — one of them.
- 04
Log the decision
Record what the reply changes: audience, price, package, proof asset, follow-up timing or the paid ask.
Limitations and corrections
- No script produces a yes. This one is built to produce a decision, and a clear no counts as one.
- A price objection is data, not a verdict on your price. One buyer saying it is expensive tells you about that buyer; three saying it for the same reason tells you about the offer.
- The nine blocker categories are a working taxonomy from common sales practice, not a validated model. Two of them will overlap on real replies.
- Do not paste a customer's name, phone number or company details into any assistant, including ours. Redact first.
- Drafts stay in this browser and are cleared with site data.
Corrected in public: tell us what is wrong at /contact and the change is dated on this page.
Frequently asked questions
Rarely. Two answers give the buyer two things to weigh and usually produce silence. Answer the one you classified and offer the second only if they raise it again.
That is the authority category, and the right instrument is a referral ask, not proof. Asking who else would need to be in the conversation is a small, easy yes.
Start free with Ted.
Bring the messy version of the idea. Ted turns it into a first move, something real, and a way to see what people actually do — free to start, no card.
AI output needs your review. No income is promised or guaranteed.