List everyone who can say no before you negotiate

What the List move is

List is the third move in The Salecopy Method. Before you negotiate, you write down each person who can approve, block or delay the deal, what each one needs to see, and who on your side is talking to them.

The reason is simple. The person you talk to every week is rarely the only person who decides. Someone holds the budget. Someone reads the contract. Someone has to use the thing you sell. Any of them can say no, and a no from a person you never met is the hardest one to answer, because you hear it late and secondhand.

The mistake this move prevents is agreeing terms with a champion who cannot sign. A champion is the person inside the buyer's company who wants your deal to happen. They matter a great deal. They are not the whole list.

Four roles to fill on every deal

The method names four buying roles. In a small company one person can hold two of them. In a larger one, a role can be a whole team. Either way, each role gets a name next to it.

• Decision maker. The person who says yes or no at the end. Needs to see that the problem is real, what it costs to leave it alone, and that choosing you is a small risk.
• Budget holder. The person whose money it is. Needs to see the total cost, when it is paid, and what it is being compared with.
• User. The people who will work with what you sell every day. They need to see that their day gets easier, and what changes for them in the first weeks.
• Legal or procurement. Procurement is the team that manages buying from suppliers. They need your contract, your security or insurance documents, and time. They rarely say no outright. They delay.

Write down what each person needs to see

A name alone is not enough. Next to each person, write one line: what they need to see before they can say yes. Then write who on your side is talking to them, and when you last did.

That one line changes how you prepare. A finance lead who cares about payment terms does not want another product demo. A user who fears extra data entry does not care about your discount. If you cannot write the line, you do not know yet, and that is your next question.

Mark anyone who is likely to be against the deal. A person who chose the current supplier, or built the process you are replacing, has a reason to slow things down. Better to hear their concern now and answer it with proof than to meet it at the pricing stage. That is the next move, covered in answer objections with evidence.

How to ask without annoying your champion

Reps avoid this question because it can sound like going over someone's head. Asked badly, it does. So do not ask who the real decision maker is. Ask about the process, and make it about helping your champion look prepared.

Ask early, in discovery, when it is an ordinary question. Asked for the first time in the week of the pricing call, it sounds like panic. If your champion offers to carry the message for you, accept, and still ask for a short introduction. Your champion is good at their own job. Selling your product to their finance lead is not their job.

Lines a rep can use:

• Who else will look at this before it is signed, and what will each of them want to know?
• When your company last bought something like this, what were the steps between yes and a signature?
• I want to make this easy for you to take upstairs. What will your finance lead ask you that I can answer now?
• Would it help if I wrote a one-page summary for each person, covering only what they care about?

Talk to more than one person

Sales teams call this multi-threading: having a working conversation with several people at the buyer, not just one. The reason is practical. People change jobs, go on leave and get pulled onto other projects. If your only contact goes quiet, the deal goes quiet with them.

Match people on your side to people on theirs. Your founder writes to their decision maker. Your technical lead talks to their users. Your finance person answers their finance person. Each conversation is short and about that person's line on the list.

Tell your champion about every one of these before it happens. Multi-threading done behind someone's back costs you the one person who wanted the deal.

Keep the list on the deal record

The list belongs in your CRM (customer relationship management system, the place your deals and contacts are recorded), on the deal itself, not in a notebook. Each role has a contact attached and a last-contacted date. A manager can then open any deal and see which roles are empty.

An AI assistant is useful here. It can compare the contacts on the deal with the four roles and flag the gaps, for example a deal in negotiation with no budget holder attached. It flags. Your rep decides who to call, and makes the call.

If your pipeline (the stages a deal moves through) has rules for leaving each stage, add one: a deal does not enter negotiation with an empty decision maker or budget holder. More on that in pipeline stages with exit criteria.

What to do this week

Open your five largest open deals. For each one, fill in the four roles from memory, with a name and the date you last spoke. Count the blanks. Each blank is a question for your next call with that buyer, and you now have the words to ask it.

What to add to your CRM

A prompt to try

You are helping me prepare for a B2B negotiation. Do not contact anyone and do not write messages for sending. Your job is to check my list of people and tell me what is missing.

What I sell: [your product or service]
The buyer: [company, size, sector]
Deal stage: [stage]
People I have spoken to, with job title and what each said: [paste notes]

Do this:
1. Sort each person into one of four roles: Decision maker, Budget holder, User, Legal or procurement. If you are unsure, say so and say why.
2. List the roles that have no named person.
3. For each person, write one line on what they probably need to see before they can say yes. Mark each line as a guess for me to confirm.
4. Give me three questions I can ask my main contact to fill the gaps without going over their head.

Use only what is in my notes. If something is not there, list it as missing. Do not invent names, titles or facts.