Answer every sales objection with evidence, and keep the list

What the Evidence move is

Evidence is the fourth move in The Salecopy Method. You log each objection the buyer raises, in their words, with the proof that answers it. Then you keep the list until every line is closed.

An objection is any reason the buyer gives for not going ahead, or not yet. It will take too long. Our team will not use it. We tried something like this before. The natural response is to answer on the spot, with confidence and a good story. The buyer nods, the call moves on, and everyone treats the matter as settled. Often it is not.

Log the objection in the buyer's words

Write down what the buyer said, as close to word for word as you can, and who said it. Put it on the deal record in your CRM (customer relationship management system, the place your deals are recorded), not in your own notebook.

Your summary is not good enough. Here is an invented example. A note that says 'concerned about implementation' tells the next reader nothing. A note that says 'our last rollout took nine months and the team still resents it' tells you exactly what proof is needed: a plan with dates, and someone who can describe what a rollout with you was like.

The buyer's words do three jobs. They show the real fear behind the polite version. They let you repeat the concern back accurately, which is how a person knows they were heard. And they let someone else on your team pick up the deal without guessing.

Record who raised it. The same objection from a daily user and from a finance lead needs different proof.

Match each objection to proof

For each line, ask what would settle this for a reasonable person. Send that, and note what you sent and when.

Enthusiasm is not proof. Neither is repeating the claim more firmly. If the only answer you have is that the buyer should trust you, the objection stays open. Proof comes in four kinds:

• A number. A calculation built from the buyer's own figures, with every input shown so they can check it.
• A reference. A conversation with one of your customers in a similar position, arranged with that customer's permission.
• A document. A security summary, a sample contract, a project plan with dates, an insurance certificate.
• A test. A trial, a pilot with one team, or a sample of the buyer's own data run through your process.

Say plainly what you cannot show

Sometimes you do not have the proof. You have no customer in their industry. You have never run at their volume. The integration they need is not built yet. Say so.

The line from the method is: That is a fair concern. Here is what I can show you, and here is what I cannot. It feels risky. It is the safer choice. A buyer who catches you stretching on one point has reason to doubt everything else you said. A buyer who hears you name a limit has more reason to believe the rest.

Then offer the closest thing you do have, and let the buyer judge it. No customer in their industry, but one with the same size team and the same problem. No history at their volume, but a pilot that would test it.

An objection you cannot close stays on the list as open, with a note. Later it may become a trade or a smaller first scope. It should not quietly disappear.

Why unanswered objections return at pricing

The mistake this move prevents is treating an objection as handled because the buyer stopped mentioning it. Silence is not agreement. A buyer who still doubts something has two choices: raise it again and seem difficult, or keep quiet and ask to pay less for the risk.

So the doubt comes back as a price request. The buyer who never believed your timeline asks for a discount. The buyer who is unsure their team will use it asks for a shorter contract or a way out. Any term like that is one to have your lawyer review. You think you are negotiating price. You are paying for an objection you never closed.

This is why the list is checked before the pricing call. If a line is still open, deal with it first. Sending a document costs you less than giving a discount. For the pricing conversation itself, see never concede, trade.

Where AI helps, and where it stops

If your calls are recorded and transcribed, an AI assistant can do the tedious part. It reads the transcript, pulls out each objection in the buyer's words, matches it to evidence you already have on file, and lists what is still open before the next call.

It prepares and checks. It does not decide which proof is good enough, and it does not send anything. Your rep reads the list, corrects it, chooses what to send and sends it. More on where that line sits in what AI should and should not do in a deal.

The assistant is only as good as your evidence library. Keep your references, documents and worked calculations in one place, each tagged with the objection it answers. Then matching takes minutes, for a person or for a machine.

Start with one deal

Pick the deal you most expect to close this month. Write down every objection you remember the buyer raising, and who raised it. Next to each one, write the evidence you sent. Not what you said, what you sent. The lines with nothing next to them are your work for this week.

What to add to your CRM

A prompt to try

You are helping me prepare for my next call with a B2B buyer. Do not contact anyone and do not write messages for sending. Your job is to find objections and check them against my evidence.

What I sell: [your product or service]
Call transcript or notes: [paste here]
Evidence I have available: [list your references, documents, calculations and tests]

Do this:
1. List every objection or doubt the buyer raised. Quote the buyer's exact words and name who said it.
2. For each one, name the item from my evidence list that best answers it, and say in one line why it fits.
3. If nothing on my evidence list answers it, write: no evidence available. Do not suggest that I claim something I cannot show.
4. List any objection that was raised and then dropped without a clear answer.
5. End with a list of what is missing: information you would need to do this job properly.

Use only the text I gave you. Do not invent quotes, customers, numbers or documents.