How To Collect And Use Customer Objections

The reasons people do not buy from you are a short list. Usually five or six, repeated endlessly, in slightly different words.

Most businesses handle each one live, from scratch, every time. Which is expensive and inconsistent, and it means the objection is doing its damage before anybody gets to answer it.

Start by writing them down

One document. Every objection you have heard, in the words the customer used.

Pull them from: sales calls, email replies, the questions people ask before they ask the price, the reasons given when somebody said no, comments on your content, and the things people say right before they go quiet.

Then count them. The list will collapse into five or six real ones with variations.

For most service businesses they come out as some version of: it costs too much, I am not sure it will work for us, I do not have time for the onboarding, we tried something like this before, I need to talk to somebody else, and why you rather than the alternative.

Separate the real ones from the polite ones

"Send me some information" is not an objection, it is an exit.

The real objection is underneath it, and the only way to find out is to ask. "What would need to be true for this to be worth doing?" gets a straighter answer than "what are your concerns?", and the question set in the discovery call questions that matter is built for that.

Price is also usually not the objection. Price is the objection when the value is unclear, which is a different problem with a different fix, and it is why what a good offer actually looks like matters more than your rate card.

Answer each one properly, once

For every objection, write the best answer you have. Not a script to read, the actual argument, with the evidence attached.

The best answers have three parts: acknowledge the thing is reasonable, give the specific reason it does not apply here, and show the proof. Proof being a number, a named example, or a guarantee rather than a reassurance.

Our own answer to the biggest objection in marketing is a guarantee: a million views in six months or you do not pay until we do. It is not a clever line, it is a structure that removes the objection instead of arguing with it.

Then move the answers upstream

This is where the work pays off. Every objection answered on a sales call is an objection that should have been answered before the call.

On the service page, because somebody deciding whether to enquire is running the objections silently. That is part of how to write a service page.

In the FAQ, which is the most underrated page on most sites and the one AI search quotes from.

In your content, one post per objection, which gives you five or six posts that are guaranteed to be relevant.

In the proposal, so the answer is in the document rather than in the follow up call. The structure for that is how to write a proposal that closes.

In the follow up sequence, one objection per email, which is the most effective sequence most businesses never build, per the follow up sequence most businesses never build.

In the case studies, choosing examples that answer the objection rather than the ones you are proudest of. Which is what how to write a case study that sells is about.

Keep the list alive

New objections appear when the offer changes, when the market changes, and when you move upmarket.

So the list gets reviewed quarterly with the rest of it, in the same session as how to run a quarterly marketing review. Which objections disappeared, which are new, which answers stopped working.

The side effect nobody expects

A business that has written down its objections sells more consistently, because the answer no longer depends on who picked up the phone.

It also writes better copy, because objection answers are the most useful sentences in any piece of marketing. Everything persuasive you have ever read was answering something.

What this unlocks: a page and a sequence that handle the objections before a human has to, so the calls you take are with people who are already past them.