Objection handling documents

What an objection handling document is

An objection handling document lists the reasons your buyers give for not going ahead, and gives each one a written answer a salesperson can use: the evidence, the words to say, and the proof to send afterwards. Most businesses hear the same seven or eight objections, in slightly different clothes, and lose deals to them one at a time because each salesperson improvises.

It is not a battlecard, which covers one named competitor in detail. An objection document covers the whole set of reasons for no, of which "we are talking to someone else" is only one. It is also not a script. Nobody reads a script convincingly, so each answer is written as an argument with a short spoken version, and the salesperson makes it their own.

Who this is for

A business with more than one person selling, where the best salesperson has answers the others do not, and nobody has written them down. It suits a firm losing deals at the same point in every conversation, or a firm that can see the price objection coming and has never settled what to say about it. It also suits an owner hiring a first salesperson, who cannot spend the year it took to learn the answers themselves.

It is not for a business that has not yet had enough sales conversations to know its objections; the document is built from real ones, and inventing them produces answers to questions nobody asks. If you are at that stage, a set of customer interviews with people who bought will surface what they nearly said no to, and that is where to begin.

What goes in it

The document is built from evidence, then written. The evidence comes from four places: recordings or notes of sales calls, the emails buyers send when they decline, short interviews with your salespeople, and short interviews with two or three customers who hesitated and bought anyway. From that I list every objection heard, group the ones that are the same objection in different words, and rank them by how often they appear and how often they end the conversation.

Each objection in the final list gets the same five-part treatment.

• The objection as the buyer says it. In their words, not yours. "This is more than we budgeted" is a different objection from "I do not see the value", and they get different answers.
• What it usually means. The concern underneath, which is often not the one stated. A price objection from a buyer who has not asked what is included is a value question.
• The answer. Two or three sentences of argument, with the evidence that supports it: an approved client figure, a comparison, a fact about how the service runs.
• The talk track. The spoken version, one or two sentences, written to be said rather than read.
• What to send. The case study, page or document that backs the answer up, so the follow-up email writes itself.

Where an objection is simply true, the document says so and says what to offer instead. An honest answer to a fair objection keeps the conversation; a clever one ends it.

What you get

The objection document. Six to twelve pages in an editable file, one section per objection, seven to ten objections, in rank order. Written to be read in twenty minutes before a call and searched during one.

The one-page summary. Each objection and its talk track on a single sheet, for the desk or the car.

The evidence list. A short spreadsheet of every objection recorded during the research, where it came from, and how it was grouped, so that when a new objection appears next year your team can add it the same way.

A worked example

An illustration, not a client. A commercial HVAC maintenance company with three salespeople sells annual service contracts to property managers. Reading 40 declined-proposal emails and listening to eight recorded calls produces 23 distinct objections, which group into seven. The top three by frequency: "our current contractor is fine", "we only call someone when something breaks", and "the board will not approve a new line item".

The first is answered not by criticising the incumbent but with the two things a property manager cannot know about them until something fails, and a short case study of a building that switched after a failed inspection. The second is answered with the company's own records, described in aggregate, of what an emergency call costs against a contract year. The third gets a one-page board summary the property manager can forward, which is the real answer to that objection. The document is nine pages. The newest salesperson reads it in a lunch hour and stops answering "our contractor is fine" with a discount.

How it runs

1. A half-hour call. What you sell, who sells it, and where conversations stall. No charge.
2. A fixed price in writing. The number of objections and the research sources agreed before anything starts.
3. Gathering. Two weeks. You send declined emails and any recordings; I interview each salesperson for 30 minutes and two or three customers if you are willing to introduce me.
4. The ranked list. One page: every objection, grouped and ranked. You confirm it matches what you hear before anything is answered.
5. The draft. Within ten working days of approval. Your best salesperson reads it and marks anything they would not say.
6. Delivery. The document, the one-page summary and the evidence list, with a 45-minute session for the sales team.

Three to four weeks from first call to final document is typical.

What it costs

Objection handling documents are not a published band on the pricing page, so each is quoted as a fixed price in CAD after the half-hour call. The price depends on the number of salespeople to interview, whether call recordings exist, and whether the proof each answer needs already exists or has to be written. A team of three with recorded calls and two case studies on file is the simplest version.

What happens next

Some answers need proof that does not exist yet, so a case study is the usual next piece. If one competitor's name comes up in most conversations, a battlecard gives it the detail an objection document cannot. And the objections a buyer raises in a meeting are the ones a stranger raises silently on the website, so the public answers usually belong on an FAQ page too.