Cold email sequence template for B2B with steps, timing, channels and copy rules

A cold email sequence template is usually three to four emails spread across about two weeks, or, in Revenue Grid's figures, a multichannel cadence of 8 to 12 touches over 2 to 4 weeks that adds phone, LinkedIn and customer relationship management (CRM) tasks. Our template runs seven prospect touches and one research task, with an exit rule on every step, plus timing, copy rules and the sender and CAN-SPAM checks to clear before step one.

What a cold email sequence template looks like

A cold email sequence template comes in two common shapes. The email-only version is, in Instantly's words, "usually three to four emails spread across roughly two weeks." It opens with one cold email and follows with two or three follow-ups spaced several business days apart.

The multichannel version, usually called a sales cadence, is longer and mixes channels. Revenue Grid puts most effective B2B cadences at 8 to 12 touches over 2 to 4 weeks, combining email, phone, LinkedIn and CRM tasks. Cognism reports that Morgan J Ingram, previously its Creative Advisor, recommends a 17 to 21 day cadence. The same article quotes Florin Tatulea, Director of Sales at Barley, saying the best cadences contain 8 to 12 touchpoints.

The two shapes overlap more than the table suggests. Revenue Grid cites research that sequences with three email touchpoints reach reply rates of around 9.2%, with replies falling when email touches drop below three or rise above seven. In its reading, the email part of a cadence stays at three to four emails, with calls and social touches filling the rest. For cold outbound, it advises spacing touches 2 to 3 days apart.

A blank email-only skeleton

The block below is our own starting layout for the email-only shape. The day numbers are placeholders that fit inside two weeks. Adjust them to your own reply data.

SEQUENCE: segment name
Goal: one outcome, e.g. a reply or a booked call
Stop rule: end the sequence on any reply, yes or no

Day 1   Email 1  Opener      why them, why now, one-sentence offer, ask for interest
Day 4   Email 2  New angle   a resource or result relevant to their role
Day 8   Email 3  Direct ask  a specific next step and a time
Day 13  Email 4  Close-out   permission to stop, an easy way to say later or no

Per step, log: sends, replies, positive replies, meetings

Take the Market's view: start with the email-only shape when one person or a small team owns outbound and has no calling capacity. Move to the multichannel cadence once reps can work phone and LinkedIn tasks every day. To judge either shape, compare your reply rates against our cold email benchmarks.

The sequence template to copy, step by step

The table below is our template. Each row is one step, with a day, one channel, one job and one exit rule. That example puts a breakup email on Day 10 and a light re-engagement touch on Day 30.

Our version has seven prospect touches and one internal task. That sits inside the range Highspot gives for cold work, which usually includes 6-8 touchpoints across email, phone, and social.

How to use the exit rules

In our reading, every row needs its own exit rule because the sequencer cannot judge intent. Revenue Grid separates the two layers clearly: A cadence governs the sequence; a script governs what you say in each step. The table covers the sequence. The copy rules later in this piece cover the script.

Keep the call in step 5 short. Highspot's guidance for that touch is: "Keep it under 30 seconds. Leave a voicemail if there’s no answer."

Set the exit logic in your sequencing tool before the first send. A paste-ready version:

ON reply = positive        -> stop sequence, create meeting task, owner = rep
ON reply = not now         -> stop sequence, set re-contact date, tag "timing"
ON reply = wrong person    -> stop sequence, add referred contact at step 1
ON reply = unsubscribe     -> stop sequence, suppress domain contact
ON bounce                  -> stop sequence, flag record for data fix
ON call connected          -> stop sequence, log disposition
ON step 7 sent, no reply   -> pause until step 8
ON step 8 sent, no reply   -> move to nurture list

Worked check on volume

For example, load 200 contacts into the sequence. In this example, each contact receives up to seven touches, so the rep's maximum workload is 1,400 touches plus 200 research tasks. Every contact that exits early removes its remaining touches from that total.

Plan capacity on the maximum. Report on actual touches sent, so the reply rate per contact and the reply rate per touch stay separate in your dashboard.

How many follow-up emails to send and how far apart

Use three follow-ups after the first email, and widen the gap each time. Instantly describes the typical sequence as spread across roughly two weeks, and the cadence ranges cited earlier run longer than that once calls and LinkedIn touches are added. The email track can stay short while the full cadence runs longer.

Why fewer touches over a longer window

The reasoning is about the prospect's calendar, not yours. Cognism's guidance is that having fewer touchpoints in a longer cadence means you won’t be bombarding your prospects with requests. Florin Tatulea put it plainly: "You need to give people time to see your message and get back to you."

In our reading, a buyer who is traveling, closing a quarter or out sick for four days will miss a sequence that packs four emails into one week. The same four emails spread over two weeks reach that buyer at least once after they are back at their desk.

Region changes the count.

A worked spacing plan

This is our own schedule for the email track. The gaps grow so that each email lands after the previous one has had time to be read.

Each step needs its own content. Instantly's rule is to give every follow-up a fresh reason to reply. For the last email, Cognism suggests that a good idea is to ask the prospect for feedback on your outreach, which gives a non-buyer an easy way to reply.

The stop rule

STOP RULES (apply to every contact)
1. Any reply (positive, negative, neutral) -> remove from sequence, route to owner
2. Meeting booked -> remove from all sequences
3. "Not the right person" + referral -> remove, start new contact on referral
4. Unsubscribe or "stop" -> suppress across all sequences
5. Hard bounce -> remove, flag record for data review
6. Out-of-office reply -> pause, resume after return date

What each email in the sequence should say

Inbox time is already contested. Salesforce reported that 25% of desk workers and 43% of executives say they spend too much time on email. Every email in the sequence has to earn its read in the subject line and the first sentence.

Subject line: accurate and short

The subject line should describe what the body actually says. A subject that promises one thing and delivers another costs you the reply and the next open.

Opening: tied to the prospect

The first line is about them, not you. Salesforce suggests you reference relevant blog posts, mutual connections, or recent achievements, and it reported that open rates jump 29% higher when cold emails are personalized. Cut stock openers such as "I hope this email finds you well."

One call to action per email

Give each email one ask, so the prospect has one decision to make. The sources disagree on the first ask. Salesforce says to avoid a direct meeting request in the first message, while Instantly opens its meeting request sequence with a direct ask for a prospect who knows your name but hasn't engaged. In our reading, the deciding factor is familiarity: a soft ask for strangers, a direct one for prospects who already recognize you.

Follow-ups: new material each time

As covered above, each follow-up needs its own reason to reply. Instantly names three options: a follow-up might introduce a different angle, share a relevant result or resource, or simply make the next step easier.

Two checks before you hit send

First, count pronouns. Salesforce puts the target ratio of "I" and "my" to "you" and "your" at 1-to-2.

Second, check reading level. Salesforce recommends writing at an eighth-grade reading level. Short sentences and plain verbs get you there. Paste the draft into any readability checker before it goes into the sequence.

Prospects who finish the sequence without replying can move into the lead nurturing playbook.

Sender and opt-out requirements to meet before step one

Run these checks on the sending domain before step one goes out. The cadence and copy from earlier sections only matter if the mail is accepted.

Gmail's rules cover personal accounts, meaning an account that ends in @gmail.com or @googlemail.com. Google states that the Email sender guidelines don’t apply to messages sent to Google Workspace accounts. In our reading, most business-to-business prospect lists still include some personal addresses, so treat the baseline as mandatory.

The baseline for every sender

Starting February 1, 2024, all email senders who send email to Gmail accounts must meet the requirements below:

• Complaints: keep spam rates reported in Postmaster Tools below 0.3%. MailReach advises a stricter working target: below 0.1% and never let it reach 0.3%.

The bulk-sender tier

Google defines a bulk sender as one that sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period. The count is domain-wide: messages sent from the same primary domain count toward the 5,000 limit. The status does not reset. Senders who meet the above criteria at least once are permanently considered bulk senders.

Separating cold outreach onto its own primary domain keeps the two counts apart.

The opt-out rule also applies: marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body. Google lists unsubscribe requests aren’t honored within 48 hours as a violation. In practice, your CRM suppression list has to sync faster than that.

Stricter enforcement

Starting November 2025, Gmail is ramping up its enforcement on non-compliant traffic. Google says failing messages will experience disruptions, including temporary and permanent rejections. A setup that previously drew soft deferrals can now produce hard bounces. Recheck each item on a schedule, not only at launch. The full setup is covered in our outbound email deliverability guide.

What every cold email must include under CAN-SPAM and UK and EU rules

The opt-out mechanics are covered in the previous section. This one is the content checklist the Federal Trade Commission (FTC) sets for each commercial email. This is a description of the rules, not legal advice.

The first point for business-to-business teams: the law makes no exception for business-to-business email. Cold outreach to a VP of finance is covered.

The CAN-SPAM checklist for every step

Timing is set by the same guide. An opt-out mechanism must be able to process opt-out requests for at least 30 days after sending, and you must honor a recipient's opt-out request within 10 business days. An outsourced sender does not shift the duty: you can't contract away your legal responsibility.

Why the per-email penalty matters for sequences

Each separate email in violation can carry a penalty of up to $53,088. A sequence multiplies sends. Read that as the scale of the exposure, not a forecast of any fine.

Primary purpose

For mixed content, the FTC says the primary purpose is the deciding factor. If the subject line would lead the reader to think it is commercial, it's a commercial message for CAN-SPAM purposes. A prospecting email almost always is.

UK and EU contacts

Tag UK and EU records in the CRM and route them to whoever owns compliance before enrollment.

Worked example for an invented product, with testing and the traps

Ledgerline is an invented product used only for this example. It matches bank transactions to the general ledger every night so finance teams review exceptions instead of ticking every line. The target role is the controller at a mid-market company. In this example, the list holds 1,000 verified contacts, and the sequence runs four emails on days 1, 4, 9 and 16.

The four emails, ready to paste

EMAIL 1 (Day 1)
Subject: Month-end close at {Company}

Hi {FirstName},

{Company} posted two senior accountant roles this quarter, which often
means the close is stretching. Ledgerline matches bank lines to your
general ledger each night, so your team reviews exceptions instead of
checking every line by hand.

I wrote a one-page breakdown of where close time goes in teams your
size. Want me to send it?

{Signature}
{Postal address} | Reply "stop" and I will not email again

EMAIL 2 (Day 4)
Subject: Audit evidence for reconciliations

Hi {FirstName},

A different angle from my last note. When auditors ask for match
evidence, teams often rebuild it from spreadsheets the week before
fieldwork. Ledgerline records who approved each match and when, so the
evidence exports as one file.

If audit prep costs you more time than the close, reply "audit" and I
will send a sample export.

{Signature}
{Postal address} | Reply "stop" and I will not email again

EMAIL 3 (Day 9)
Subject: 20 minutes on your reconciliations

Hi {FirstName},

If the close or audit prep is on your list this quarter, a 20-minute
screen share would show Ledgerline running on a sample of your own bank
data. You would see which lines it matches, which it flags, and what
your team would still review.

Would Tuesday or Thursday next week work for a short call?

{Signature}
{Postal address} | Reply "stop" and I will not email again

EMAIL 4 (Day 16)
Subject: Right person?

Hi {FirstName},

I have written three times about bank reconciliation and may have the
wrong person. If someone else at {Company} owns the close or the
reconciliation process, a name would help me stop filling your inbox.

Who should I speak with about reconciliation?

{Signature}
{Postal address} | Reply "stop" and I will not email again

Email 1 holds back the meeting request. That follows Salesforce's advice to avoid a direct request for a meeting in the first message. The meeting ask arrives in email 3.

The A/B test and how to read it

Salesforce describes a split where you create two versions of the same email and send to 20% of your audience. In this example, on 1,000 contacts that is 200, so 100 get each version. Change one variable only.

Result in this example: A drew 6 replies per 100, B drew 3 per 100. Three replies is too few to call a winner. A two-proportion check shows it:

p_A = 6/100 = 0.06    p_B = 3/100 = 0.03
pooled p = 9/200 = 0.045
SE = sqrt(0.045 x 0.955 x (1/100 + 1/100)) = 0.0293
z = (0.06 - 0.03) / 0.0293 = 1.02
Need z >= 1.96 for 95% confidence. 1.02 is not there.

Sample needed to detect 6% vs 3% (95% confidence, 80% power):
about 750 delivered contacts per variant, 1,500 in total.

That is more than this list holds. In this example, treat A as the working default, keep testing it on later batches, and pool results until each arm passes 750. Compute reply and meeting rates on delivered emails. Suppose 94 of A's 100 delivered: the reply rate is then 6/94, or 6.4%. Suppose 2 of those replies book meetings: the meeting rate is then 2/94. Compare both against the cold email benchmarks, then run the meeting count through the reverse funnel calculator to see what list size your pipeline target needs.

The traps, each with the fix

1. No DMARC record. Publishing a DMARC policy record is now a requirement for sending domains targeting Yahoo and Gmail users. Fix: publish it, then confirm it with a TXT record lookup.
2. A meeting ask in email 1. Fix: offer something useful first and save the calendar ask for email 3.
3. Tracking links and images. Mailercloud lists excessive use of links or images among spam-like traits. Fix: send plain text with no images and at most one link.
4. Follow-ups that reuse one angle. Fix: give each step new content. In this sequence that means close time, then audit evidence, then a demo on the prospect's own data, then a referral.
5. Counting sent instead of delivered. Fix: subtract bounces before you compute any rate.

Monday checklist

• DMARC, SPF and DKIM confirmed by TXT lookup
• Four emails loaded, one ask each, no images
• 200-contact split set as in the worked example, one variable changed
• Reply and meeting rates computed on delivered emails

What this page does not cover

This page does not cover UK and EU consent rules in detail beyond tagging those contacts and routing them to your compliance owner before enrollment, and it leaves the full domain setup to our outbound email deliverability guide. The CAN-SPAM and Gmail sections describe the rules as written and are not legal advice.