Outbound Sequence Templates: 5 Examples You Can Adapt

An outbound sequence template works when it pairs a real trigger with a short, day-numbered run of steps across email and one social touch. The five sequences below each start from a different real trigger: a new sales hire, a funding round, a trade show, an SDR hiring wave, and a thread that went cold. Copy the shape, then replace every {{variable}} with your own research before sending.

Four steps, one trigger, one ask per step.

Day 1

Email 1: the trigger

Names the new role and the month it happened, then one soft question.

Day 4

LinkedIn touch

A short congrats note, no pitch, no second ask.

Day 8

Email 2: the proof

One proof point, one new question, nothing repeated from email 1.

Day 14

Email 3: the soft close

Names the real reason for silence, leaves one door open.

What makes a sequence template worth copying?

Four rules decide whether a sequence gets replies, the same four rules that make one cold email structure work on its own. First, never open with "I hope this email finds you well": it says nothing about the reader and signals a template nobody adapted. Second, no fake personalization: a first-name merge field is not a reason to write, a real trigger is. Third, one ask per email: two asks in the same message gets neither answered. Fourth, the ask is a soft question, never a demand; "worth comparing notes on this?" earns replies that "let's book a call" does not.

The five sequences below hold these four rules on every step, across email and the one LinkedIn touch each one uses.

Template 1: a new head of sales just got hired

Day 1, email 1 (the trigger):

Subject: {{FirstName}}, congrats on the new role at {{Company}}

Saw you stepped into {{Role}} at {{Company}} this month.

Most new sales leaders inherit a pipeline someone else built.

Worth 15 minutes to compare what you're inheriting against what actually works?

Why it works: the trigger names a real month and a real event, not a title match pulled from a database.

Day 4, LinkedIn touch: a short connection note: "Congrats on the move to {{Company}}. No pitch, just wanted to connect before your first board update."

Why it works: one soft line, no ask, no second request stacked on top of the first.

Day 8, email 2 (the proof):

Subject: What usually breaks in month one

Most new heads of sales spend month one auditing a pipeline they did not build.

{{ProofPoint}} once that audit found the real gap.

Would a 20-minute audit of your current list help before next month's number?

Why it works: one proof point, not a client logo wall, and the ask stays a single yes-or-no question.

Day 14, email 3 (the soft close):

Subject: Last note from me

No reply yet, which is fine, your first month is full.

I'll stop here unless you want the short audit above.

Reply any day this still interests you.

Why it works: the close names the real, likely reason for silence instead of guessing, and leaves one door open without repeating the ask.

Template 2: the company just raised a funding round

Day 1, email 1:

Subject: Congrats on the {{RoundStage}} round

Congrats on closing the {{RoundStage}} round this quarter.

A new round usually means new hires before new process.

Worth a quick look at what breaks first once the team doubles?

Why it works: the trigger is named by stage, never by amount, and the problem is the one every funded team actually hits first.

Day 5, LinkedIn touch: a comment on the funding announcement, then a short note: "Following the news, curious how the next few months look for the team."

Why it works: the touch references the same public trigger as the email, so both channels tell one story.

Day 9, email 2 (the proof):

Subject: What usually breaks first after a round

{{ProofPoint}} for one team that scaled right after its round.

The pattern repeats: the list grows before the process does.

Want the two-question check we use for a team in that spot?

Why it works: one proof point stands in for a case study link, and the ask offers something specific instead of a generic call.

Day 16, email 3 (the soft close):

Subject: Closing the loop

I'll leave this here unless timing changes once the round settles.

If the hiring plan shifts next quarter, just reply.

Why it works: it names the real reason to come back later instead of a vague "just checking in."

Template 3: a trade show is six weeks away

Day 1, email 1:

Subject: Saw {{Company}} is exhibiting at {{TradeShow}}

Saw {{Company}} is exhibiting at {{TradeShow}} in six weeks.

Booths usually fill the calendar the week before, not during.

Worth locking 15 minutes now, before that week disappears?

Why it works: the trigger carries a real date, six weeks out, and names the actual constraint, not just the event's name.

Day 6, LinkedIn touch: a comment on their exhibitor announcement: "Looking forward to seeing the booth at {{TradeShow}}."

Why it works: it stays visible without adding a second ask before the first one gets answered.

Day 12, email 2 (the proof):

Subject: Before the floor gets busy

{{ProofPoint}} for a team that booked meetings before the show, not during it.

Two slots are still open the week before {{TradeShow}}.

Which one works, Tuesday or Wednesday?

Why it works: the ask is two fixed options, the lowest-friction version of a calendar request.

Day 20, email 3 (the soft close, near the show date):

Subject: See you at {{TradeShow}}?

No pressure if the calendar's already full before the show.

If a gap opens at the booth, I'll be around.

Why it works: it closes the sequence without a hard sell and leaves room for an in-person follow-up at the event itself.

Template 4: the company is hiring SDRs

Day 1, email 1:

Subject: Saw the SDR roles open at {{Company}}

Saw {{Company}} is hiring {{Number}} SDRs this quarter.

New reps usually take a full quarter before they carry a number.

Worth seeing what fills that gap while they ramp?

Why it works: the trigger is one specific job posting, not an assumption about company size.

Day 5, LinkedIn touch: a comment on the job post: "Saw the SDR openings, good sign the pipeline's growing."

Why it works: it shows the research came from the actual posting, not a generic "saw you're hiring" line.

Day 10, email 2 (the proof):

Subject: What fills the ramp-up gap

{{ProofPoint}} while a new SDR team was still ramping up.

The gap usually costs a full quarter of pipeline, not headcount.

Want the short list of what we'd check first?

Why it works: the proof point names a specific cost, a quarter of pipeline, instead of a vague efficiency claim.

Day 16, email 3 (the soft close):

Subject: One more note

I'll stop here unless the ramp-up gap is still a live problem.

If it is, a short reply is all it takes.

Why it works: it restates the one problem from email one instead of introducing a new angle at the last step.

Template 5: following up after no reply

Day 1, email 1 (a new angle, not "just checking in"):

Subject: Different angle this time

Last time I wrote about {{OldAngle}}, which clearly wasn't the right moment.

{{NewTrigger}} changed since then, worth a second look?

One question: still worth 15 minutes, or should I close the file?

Why it works: it names the old angle honestly instead of pretending the first email never happened, then earns a second chance with something new.

Day 7, LinkedIn touch: a short note: "No worries if the timing's still off, just wanted to flag {{NewTrigger}} in case it changes things."

Why it works: it repeats the same new reason across channels instead of inventing a second excuse to reach out.

Day 14, email 2 (the final attempt):

Subject: Last look before I close the file

{{ProofPoint}} for a team in a similar spot that waited past this point.

I'll close the file after this unless something's changed.

Why it works: it gives the reader a real deadline, the file closing, instead of an empty "following up" with no stakes attached.

How to adapt these templates without losing the trigger

Each sequence above works only once the {{variables}} carry something true this month, for this one account. A list built from a title search gives a name and a title, nothing to write about; the research itself has to supply the trigger, which is why how to run B2B outbound covers the full build: the list, the offer per segment, and the infrastructure behind it. Keep the spacing between steps, a few days each time, and keep the one-ask rule even once a second channel joins the sequence. A LinkedIn touch that pitches while the email next to it just informs confuses the reader on both channels at once.

Common mistakes

1. Leaving the brackets visible. {{FirstName}} sent as literal text reads as mass-sent and costs the reply before the first line is read.
2. Stacking two asks across two channels. A LinkedIn message pitching the same call as the email confuses the reader, and a confused reader answers neither.
3. Opening the breakup email with "just checking in." It repeats the first message with less information and costs the second chance.
4. Running the same five steps on every account regardless of the trigger. A template without a real trigger reads the same to everyone, the exact failure these sequences are built to avoid.
5. Skipping the social touch because it feels like extra work. One light LinkedIn note between two emails keeps the sender visible without adding a second ask.

FAQ