Optional analytics

With your permission, we use Google Analytics and Vercel Analytics to count visits and improve the website. We do not use this data for advertising or send form details. Cookie policy

Skip to content
Back to blog
Learning15 min read

Cold email templates: eight B2B examples by situation

Eight B2B cold email templates with placeholders, from the first email to the last, each with why it is built that way and when to leave it alone.

ByAsier Mugica· Founder of Ace Digital

Most lists of cold email templates are written to be copied whole, which is how the same email lands in inbox after inbox with only the first name changed. The templates below are built the other way round: a fixed frame, plus one slot that only you can fill, the reason you are writing to this person now. Each comes with a note on why it is built that way and when to leave it alone.

What makes a cold email template worth using?

A cold email template is worth using when it fixes the parts that never change, such as who you are, the ask and the opt-out, and leaves a clear slot for the part that must change every time: a true, specific reason to write to this person. A template that only swaps the name and company is a mass email.

This is more than a matter of style. Spamhaus, which runs widely used email blocklists, defines spam as unsolicited bulk email and bulk as a batch of messages with substantively identical content. In June 2025 it described the irrelevant cold email it sees rising as the same templates duplicated and sent at scale, often reworded by language models so that each copy reads differently. Merging a first name into the same paragraph does not change the content.

For one finished email taken apart line by line, see the annotated cold email example. This guide is about the frames: what stays fixed, what you fill in and when a frame is the wrong one.

What does every template need before it is sent?

Every template needs an honest sender, a subject that matches the body, a signature with your real name, company and postal address, and a plain way to stop further emails. In the US, the FTC's CAN-SPAM guide asks commercial email for those elements and says the law makes no exception for business-to-business messages.

  • Identification. The From, To and Reply-To lines and the routing information must be accurate and identify whoever sent the message, and the subject line must reflect what the message says.
  • An ad disclosure. The guide says commercial email has to be identified as an advertisement, clearly and conspicuously, and leaves room in how you do it.
  • A postal address. It can be a street address, a post office box registered with the US Postal Service or a private mailbox registered with a commercial mail receiving agency.
  • An opt-out. The email has to explain how to stop receiving messages from you. Requests must be honored within 10 business days, and the mechanism has to keep working for at least 30 days after you send, according to the FTC's compliance guide. You cannot charge for it or ask for more than an email address.

Every template below ends with a {{signature}} slot for your name, company and postal address, and a line that tells the reader how to stop further emails. That makes them a starting point, not a compliance check. Other countries start from different rules: Spain and New Zealand, for instance, start from the recipient's consent, as the section on the law in what cold email is explains. This is a summary of official sources, not legal advice: ask a lawyer to review your final text, list sources and opt-out process for each market.

How do placeholders work in a cold email template?

Placeholders are the slots in double curly braces, such as {{first_name}} or {{trigger}}, that a sending tool replaces with a column from your lead list. The name and the company are the easy ones. The slot that decides whether anyone reads the email is {{trigger}}: the specific, checkable reason you are writing now.

The placeholders used in the templates in this guide
PlaceholderWhat goes inWhere it comes from
{{first_name}}Their first name, as they sign their own emailsTheir profile or company site, checked by hand
{{company}}The company name, written the way they write itTheir website, not a database field in capitals
{{trigger}}One recent public fact: a job opening, a new office, a launch, an interviewThe page where you read it, saved next to the row
{{problem}}The problem that fact usually creates, in their wordsYour own sales conversations, not a feature list
{{offer}}What you do about that problem, in one lineYou, written once per campaign
{{topic}}The subject of the session, talk or questionYour own records or notes
{{colleague}}, {{event}}, {{contact}}A colleague who signed up, the event, a person who suggested you writeYour own records, and the contact's permission
{{detail}}, {{resource}}A new, specific point for the first follow-up; a useful page for the secondYour own knowledge of their market
{{signature}}Your name, company and postal addressYour own details

In sending tools, the placeholder names come from the columns of the file you upload. Instantly's help center explains that each CSV column is mapped to a built-in or custom variable, that custom variable names must match the column header exactly, capitals included, and that you should preview the email for a real lead before launching. Smartlead's help center describes variables the same way and also warns that they are case-sensitive. How the two tools differ beyond that is covered in Instantly vs Smartlead.

Two habits prevent most merge mistakes. Never send a row whose {{trigger}} is empty or generic: a fallback such as "your team" only hides the fact that you had nothing to say. And read every merged email in the first batch before it goes out, because a greeting to a legal entity name in capitals tells the reader exactly how the list was built. The sending domain needs to be ready too: Google's email sender guidelines ask everyone who sends to Gmail accounts to set up SPF or DKIM, and the guide to SPF, DKIM and DMARC explains the records.

How do you write a first email around a trigger?

A first email around a trigger names one recent, checkable fact about the company, connects it to a problem that fact usually creates and asks one question that is easy to answer. The trigger is the only reason the email exists, so if you cannot fill that slot truthfully for a given person, do not send it.

  • Subject: {{trigger}}, in a few plain words
  • Hi {{first_name}}, I saw {{trigger}}.
  • Teams in that position often have to deal with {{problem}}. That is what we work on: {{offer}}.
  • Is that on your list for the next few months, or is it already covered?
  • {{signature}}. If you would rather not hear from me, reply and say so, and I will not write again.

Why it is built this way: the trigger answers the reader's first question, why me and why now, and they can tell in a second whether it is true. The offer gets one sentence because the reader decides on relevance, not features. The question has two easy answers, so replying costs little. For the subject, the patterns in cold email subject lines apply.

When not to use it: when the trigger has no link to what you sell, when it is old news, or when it is something the reader would not expect a stranger to know. A job posting or a press release is public. A guess about their internal problems dressed up as a fact is not a trigger.

What do you write when a colleague of theirs already knows you?

When a colleague of theirs already knows you, for example by signing up for your webinar or asking you a question, say so plainly and ask whether the topic matters to this person too. The template states the fact without inflating it: one person signing up does not mean the company is interested.

  • Subject: {{topic}} at {{company}}
  • Hi {{first_name}}, {{colleague}} on your team signed up for our session on {{topic}}, so I wondered whether it is on your desk as well.
  • If it is, I can send you the few points from the session that apply to a team like yours. No call needed.
  • Would that be useful?
  • {{signature}}. If you would rather not hear from me, reply and say so, and I will not write again.

Why it is built this way: the shared fact makes the email less cold, and the ask is to send something useful rather than to book a call, which is a smaller step for someone who has never spoken to you.

When not to use it: when the interaction is something the person did not knowingly share with you, such as a visit to your website picked up by a tracking tool. Mentioning it tells them they were watched. Leave the colleague's name out as well if using it could put them in an awkward spot with their manager.

What do you write after an event?

After an event, write about the conversation you actually had or the talk you actually heard, with one detail that proves it, and suggest a next step that matches how well you know each other. Shared context does the work that a trigger does in a first email, as long as it is real.

  • Subject: {{event}}, and {{topic}}
  • If you met: Hi {{first_name}}, we spoke briefly at {{event}} about {{topic}}.
  • If you only heard them speak: Hi {{first_name}}, I was at your talk at {{event}}, and your point about {{topic}} stayed with me.
  • You mentioned {{problem}}. That is the part we work on: {{offer}}.
  • Would a short call be useful, or would you rather I send a few notes by email first?
  • {{signature}}. If you would rather not hear from me, reply and say so, and I will not write again.

Why it is built this way: the detail from the conversation or the talk is what separates this email from the generic notes that follow most events. Offering notes by email as an alternative lets someone who is not ready for a call still reply.

When not to use it: when you did not meet or hear the person and your only link is an attendee list you bought or downloaded. Implying a meeting that did not happen is invented familiarity. In that case, use the first template with a real trigger instead.

How do you mention a mutual contact?

Mention a mutual contact in the first line, by name, together with the reason they thought you should talk, and only after that person has agreed to be named. The borrowed trust is the whole point of this template, so it fails the moment the reader checks with the contact and the story does not match.

  • Subject: {{contact}} suggested I write
  • Hi {{first_name}}, {{contact}} suggested I get in touch about {{topic}}, since it came up when we last spoke.
  • In short: {{offer}}.
  • If it is worth a conversation, a short call is the quickest way to see whether it fits. If not, just say so.
  • {{signature}}. If you would rather not hear from me, reply and say so, and I will not write again.

Why it is built this way: the contact's name and the reason go first because they are what the reader cares about. The ask stays light because the reader owes you nothing and should be able to say no without feeling rude to a friend.

When not to use it: when the contact did not actually suggest it, or when your only link is a shared connection on a social network. Better still, ask the contact to introduce you by email, copying both of you, and reply in that thread: then it is no longer a cold email at all.

How do you ask to be pointed to the right person?

To ask to be pointed to the right person, name the topic precisely, say in one line why you are asking and ask only who owns it. A request with one easy answer, a name, can get a reply or a forward even from someone who is not the buyer. Do not ask for a meeting in the same email.

  • Subject: who handles {{topic}} at {{company}}?
  • Hi {{first_name}}, I am trying to reach whoever is responsible for {{topic}} at {{company}}.
  • We {{offer}}, and I would rather write to the right person once than to the wrong one twice.
  • Is that you, or could you point me to the right colleague?
  • {{signature}}. If you would rather not hear from me, reply and say so, and I will not write again.

Why it is built this way: the reader only has to type a name or click forward. Keeping the single ask to a referral, with no meeting request attached, makes the email easy to answer.

When not to use it: when a few minutes on the company's website or team page would tell you who the right person is. Asking a busy executive to do your research spends goodwill you may need later. Do not send the same request to several people at the same company at once either: they compare notes.

What should the first follow-up say?

The first follow-up should add one new thing, such as a detail, a risk or a different angle on the same trigger, and go as a reply in the same thread so the first email sits right below it. It should never be a bare "just checking in", which asks the reader to do the work of remembering you.

  • Subject: the same thread, so it reads Re: plus your original subject
  • Hi {{first_name}}, one detail I left out last time: {{detail}}.
  • If {{problem}} is not a priority right now, a one-word reply is enough and I will stop here.
  • {{signature}}. If you would rather not hear from me, reply and say so, and I will not write again.

Why it is built this way: the new detail gives the reader a reason to look again, and offering an easy no makes replying cheap either way. A reply in your own thread is a real reply, so the Re: is honest; Google's sender guidelines only rule out Re: and Fwd: on messages that are not actual replies or forwards. The {{detail}} slot follows the same rule as {{trigger}}: specific and true, or not at all.

When not to use it: when the first email bounced, when you got an out-of-office reply with a return date, or when the person replied in any way, including a no. A reply ends the automated sequence; a person answers it.

What should the second follow-up add?

The second follow-up should give the reader something useful they can use without talking to you, such as a checklist, a short note or a public page about their problem, and ask for nothing. It shows how you think and leaves the door open without adding pressure.

  • Subject: the same thread
  • Hi {{first_name}}, no need to reply to this one.
  • In case it helps with {{problem}}, this covers how to approach it: {{resource}}.
  • If it raises a question, I am happy to answer it by email.
  • {{signature}}. If you would rather not hear from me, reply and say so, and I will not write again.

Why it is built this way: by the third email, another request feels like nagging. Something useful with no strings attached is the one message a busy reader is unlikely to resent, and it is easy to forward to a colleague.

When not to use it: when you have nothing genuinely useful to send. A gated download that asks for their details, a generic company brochure or an attachment from a stranger are not resources. If the {{resource}} slot would hold one of those, skip this step and go to the last email.

How do you close a cold email sequence?

Close a cold email sequence with a short, polite last email that says you will stop writing about this topic, leaves a way back if things change and then actually stops. No guilt, no fake deadline and no question designed to provoke a reply. The silence was an answer, and this email respects it.

  • Subject: the same thread
  • Hi {{first_name}}, I have not heard back, so I will take it that {{topic}} is not a priority at {{company}} right now, and this is my last email about it.
  • If that changes, or if someone else on your team owns it, a reply here will reach me.
  • {{signature}}

Why it is built this way: saying the sequence is over removes the pressure and gives a reader who was interested but busy a clear moment to answer. Pointing to someone else on the team gives a second easy way to reply.

When not to use it: when the person already replied, and never as a trick. If you write that it is your last email, it has to be: remove the address from every sequence in every tool, not just this one.

How do you know whether a template works?

A template works if it brings replies from the right people and meetings that actually happen, so judge it on positive replies and meetings held per hundred delivered emails, not on opens. Change one slot or one line at a time, keep the list and the sender the same, and write down every result.

The method is the same as for testing subject lines, set out in the guide to cold email subject lines: two random halves of the same list, one difference between them and a decision made before you start on what counts as a win. With small B2B lists a difference of one or two replies is noise, so read results over several weeks, not one send.

When is a template the wrong tool?

A template is the wrong tool when the list is short and each buyer is worth a lot, because then every email deserves to be written from scratch around that company. Use templates as a checklist of the parts an email needs, and write the specific part, the reason, by hand for every person.

That writing takes time, and it is the part that cannot be automated well. If you would rather hand over the list, the writing and the replies, a cold email agency does that work. Ace Digital is one option: through our booked meetings service every email opens with something true about that one company, and when there is nothing real to say, we do not send it.

Frequently asked questions

What is the difference between a cold email template and a cold email example?

A template is a frame with slots you fill for each person; an example is one finished email written for one reader. Templates keep the fixed parts right and save time. Examples show what a finished email sounds like. Read both, but send neither without rewriting the specific part for the person who will receive it.

Can I send the same template to my whole list?

Not if only the name and company change. Spamhaus defines bulk email as a batch with substantively identical content and treats unsolicited bulk email as spam, as it explains in its post on cold emailing. Each email needs a reason that applies to that person, and rows without one should be left out.

How long should a cold email be?

There is no independent standard. The word counts that circulate come from tool vendors' analyses of their own customers' emails, which you cannot check. A practical test works better: the whole email, signature included, should fit on a phone screen without scrolling, and every sentence should help the reader decide whether to reply.

Should a cold email include a link or an attachment?

Keep the first email plain, with no attachments and ideally no links, so the reader can judge it in a few seconds and it reads like one person writing to another. A link fits better in a later follow-up, when it points to something useful the reader can open without filling in a form.

Can I use AI to fill in the placeholders?

AI can speed up the research behind each slot, but a person should check every fact before sending, because a wrong trigger does more harm than none. Spamhaus also lists language models rewording one basic message among the habits of the irrelevant cold email it sees growing. Decide the reason yourself, then write it.

Sources