Writing for the Buying Committee, Not the Buyer

A B2B purchase is almost never one person's decision. The person who replies to your email has to sell it internally to people you will never speak to, against objections you never hear. That changes what a cold email is for: it is not trying to close the reader, it is trying to arm them. Most outbound copy is written as though the reader decides alone, and that is why it stalls after a positive reply.

The Reader Is Not the Buyer

Almost all cold email advice, including most of ours, is written around a single recipient: catch their attention, establish relevance, earn a reply. That is the right frame for getting a response and the wrong frame for getting a deal.

The person who replies to a good cold email is usually an operator. They feel the problem daily, which is exactly why your message resonated. What they typically do not have is unilateral authority to spend money on it. Somewhere between their interest and a signature sit a manager who owns the budget, a finance function that owns the process, occasionally security or legal, and one or two peers whose workflow would change.

None of those people read your email. They hear a summary of it, secondhand, from someone with less context than you and less time to make the case. Every stalled deal that started with genuine enthusiasm failed somewhere in that translation.

So the useful question is not "will this person be persuaded?" It is "can this person repeat my argument accurately to someone more sceptical than they are?"

Who Is Actually in the Room

Four roles show up in most B2B purchases, and they want different things:

Your champion has to satisfy all four with material you gave them. The operator you are writing to is one column out of four.

Write the Sentence They Will Repeat

This is the single most practical change to make.

Somewhere in your email there should be one sentence that your reader could say out loud, from memory, to their manager, and have it land. Not a paragraph. One sentence, containing what the problem costs and what changes.

Test it directly: read your email and ask what your reader would say if their boss asked "what's this about?" If the honest answer is a vague gesture at efficiency or growth, the email has no repeatable sentence in it and the deal will die in a corridor conversation you never witness.

Concrete beats comprehensive here. "We are spending most of two days a week rebuilding lists by hand" travels. "A platform that streamlines and optimises our go-to-market motion" does not survive the walk to the next desk. The first is specific enough that a manager can picture it; the second requires the manager to take it on faith from someone who is themselves paraphrasing.

This is the same discipline as writing a good subject line, applied one level deeper: subject line formulas and how to judge them.

Make It Forwardable

The most useful thing you can send a warm prospect is something they can forward without editing.

Most sales material fails this test because it is addressed to the recipient. "As we discussed" and "following our call" are dead weight the moment the message is passed to someone who was not on the call. Your champion then has to write an introduction, provide context, and summarise, which is work, and work is where momentum goes to die.

What travels well:

• One page, self-contained. Readable by someone with no prior context, including who you are and why this conversation started.

• The problem stated in their terms, not your category's terms.

• The objection the budget owner will raise, answered before it is asked. Usually cost, usually timing, occasionally "why not just do this internally".

• A next step small enough to approve without a process. A thirty-minute call is approvable. A pilot with a scope document is a project.

If you send only one thing after a positive reply, send this rather than a proposal.

Address the Blocker Before the Blocker Appears

Deals do not usually die on the merits. They die because someone with a narrow remit and a veto asked a question nobody had answered.

The pattern is predictable enough to pre-empt. Whoever owns risk in the organisation will ask where data goes, what the contract term is, and what happens if it does not work. Whoever owns the systems will ask what it touches. None of those people are hostile; they simply have no incentive to absorb an unknown.

You can hand your champion the answers in advance, in a single short block, without turning your email into a security questionnaire. Doing so changes the internal conversation from "let me find out" to "already covered", and the second one keeps its momentum.

This is also the honest argument for a small, reversible first step. A pilot that can be stopped is easier to approve than a commitment that cannot, because it lets the blocker say yes without owning the downside.

What This Means for Targeting

If the reader is not the buyer, the obvious conclusion is to target the buyer instead. That is usually wrong.

Senior budget owners reply to cold outreach at lower rates, and when they do reply the conversation often has less substance, because they feel the problem less directly. The operator who lives with the problem gives you a real conversation and a credible internal advocate. The right approach is generally to earn the operator's reply and then equip them, rather than to skip them.

Where seniority does matter is that the message has to be written for the level you are contacting, and a message aimed at a C-level reader is a genuinely different artefact: writing cold outreach C-level executives actually read.

What does change is qualification. Asking "who else would need to be comfortable with this?" early tells you whether a decision path exists at all, and it is the question that predicts stalling better than budget or authority questions do. More on that pattern in why prospects go quiet after they said yes.

A Practical Checklist

1. Find the repeatable sentence in your email. If there is not one, the email is not finished.

2. Ask whether the value would survive being paraphrased by someone with less context than you.

3. Name the specific cost or friction, not the category of benefit.

4. Write the follow-up material so it needs no introduction to be understood.

5. Pre-answer the risk question before someone with a veto asks it.

6. Make the next step small enough that approving it is not itself a decision.

7. Ask who else needs to be comfortable, in the first exchange, not the fourth.

FAQ

Should I try to reach every stakeholder directly? Generally no, at the cold stage. Multi-threading is valuable once a deal is live and a champion can introduce you. Cold outreach to four people at one company in the same week reads as a campaign rather than a conversation, and it can undermine the champion you already have.

How do I know who the real decision-maker is? Ask, but indirectly. "Who else would need to be comfortable with this?" gets a truthful answer where "are you the decision-maker?" gets a defensive one.

Does this mean cold emails should be longer, to cover more stakeholders? No, the opposite. The cold email targets one reader and needs one repeatable sentence. The stakeholder material comes after a positive reply, as a separate forwardable document.

What if my champion will not name anyone else? Treat that as information. Either they have not thought about the internal path, which means you should help them map it, or they are not in a position to move it, which changes how much you invest.

Is a case study the right forwardable document? Sometimes, if it matches their situation closely enough to be recognisable. A generic case study is worse than a plain one-page description of the problem and the proposed first step, because it invites the objection that their situation is different.

How does this change follow-up? It changes what you send. A follow-up that adds a fact your champion can use is progress. A follow-up asking whether they have had a chance to discuss internally adds nothing and puts the work back on them.

Want outreach written for the conversation that happens after the reply, not just for the reply? Lidgen builds human-reviewed messaging around real buyer context, so interest arrives with something behind it. Book a demo.