Cold email guide
How to Write a B2B Cold Email: A Practical Framework
A useful cold email is not a compressed sales brochure. It gives one relevant buyer a credible reason to consider one business problem and makes the next step easy to decline or accept. This guide shows how to build that message from the brief up.
Key takeaways
- Start with a commercial problem the recipient may reasonably recognise.
- Use one verified signal rather than shallow personalisation.
- Keep the first message focused on one idea and one question.
- Review every factual statement before the email is used.
1. Write the brief before the email
The quality of a cold email is normally decided before the first sentence is written. If the sender cannot clearly describe the buyer, the offer and the reason the problem matters now, the message usually falls back on generic benefits.
A practical brief should separate what is known from what is assumed. The buyer's role, a public company event and the sender's approved proof may be known. The buyer's internal process, priorities and dissatisfaction are usually assumptions until confirmed.
- Buyer: the role responsible for the outcome, not simply the broad industry.
- Problem: the cost, delay, risk or missed opportunity worth discussing.
- Trigger: a verified change that may make the problem more timely.
- Offer: the specific way the seller can help investigate or improve the situation.
- Proof: an approved result, credential or relevant experience that can be substantiated.
2. Use a simple four-part structure
The email should move logically from relevance to a small next step. It does not need to explain every feature, objection and implementation detail.
A dependable structure is: context, problem, relevance and question. Context shows why the message is being sent. The problem makes the commercial issue specific. Relevance explains how the sender can help. The question gives the recipient a simple way to respond.
Example structure
Subject: Workflow handoffs Hi Sarah, Growing service teams often add systems while approvals and customer updates still move through inboxes and spreadsheets. That can make response times and ownership harder to see as volume increases. We help operations leaders identify the handoffs creating the most avoidable delay. Would a short workflow review be useful?
The message identifies one operational issue and asks one low-friction question. It does not claim to know that Sarah's team definitely has the problem.
3. Personalise with evidence, not decoration
Personalisation should change the reason for contacting the recipient. Mentioning a hobby, a generic compliment or an unconnected social post may prove that research occurred, but it rarely improves the business relevance of the message.
Prefer a signal connected to the offer: a vacancy, expansion, new service, leadership appointment, regulatory deadline, system rollout or clearly stated strategic priority. State only what can be verified and do not imply access to private information.
- Useful: linking a public hiring plan to the operational capacity your offer addresses.
- Weak: opening with a broad compliment that could be sent to any company.
- Risky: asserting an internal problem or financial result without evidence.
- Misleading: suggesting a prior relationship or familiarity that does not exist.
4. Make the subject line easy to understand
A subject line should help the recipient recognise the topic without pretending the message is an internal reply. Clear subjects such as ‘Month-end capacity’, ‘Customer onboarding handoffs’ or ‘Technical hiring calibration’ set an honest expectation.
Avoid false urgency, fake reply prefixes and exaggerated claims. The subject and message should describe the same topic so the recipient does not feel misled after opening it.
5. Ask for the smallest useful next step
The first email rarely needs to close the sale. It needs to establish whether the problem is relevant enough for a conversation. A short diagnostic question, permission to send a useful outline or a focused review is usually easier to evaluate than a large commitment.
Use one call to action. Multiple questions, calendar links and requests for detailed information increase the amount of work required from someone who has not yet agreed that the topic matters.
Low-friction questions
Would a short workflow review be useful? Is improving shortlist quality relevant this quarter? Would it help if I sent the one-page review outline?
6. Review the draft before sending
Generation can accelerate drafting, but the sender remains responsible for accuracy, targeting and appropriate use. Read the message aloud, remove unnecessary claims and confirm that the recipient can understand the reason for contact without additional context.
- Is every company, role and event accurate?
- Does the email focus on one commercial issue?
- Can every claim and proof point be supported?
- Is the language natural for the person sending it?
- Is there one clear question and an easy way to decline?
- Will the outreach respect applicable rules, suppression lists and contact preferences?