Sales email sequence examples: what works and why

Deals stall between stages, not inside them. The sales email sequence examples below are built around the four moments where an opportunity most often goes cold: right after a discovery call, after a proposal lands, when a deal goes quiet, and months after a loss. Each one starts automatically when a rep moves the deal to a new stage in Opportunities, so nobody has to remember to send anything. You get a pipeline where every open deal has a next message already queued, and your reps spend their time on the conversations that reply.

Why sequences should follow the pipeline, not the calendar

Most teams build one long follow-up chain and start it when a lead arrives. That chain knows nothing about where the deal actually is. A prospect who has already seen a proposal gets an email introducing your services, and the credibility you built in the meeting leaks away.

Tying each sequence to a stage fixes that. The stage tells the platform what the buyer has seen, so the content can assume it. When the rep moves the deal forward, the old sequence stops and the right one starts.

Before you start

• A pipeline in Opportunities with stages that match how your deals really progress. Four to seven stages is enough for most firms.
• A rule that reps move deals the same day something changes. Stage-triggered email is only as accurate as the stage.
• Email sending set up and verified for your domain in Settings.
• Contacts linked to each opportunity, with a first name and a company name filled in.

Four sales email sequence examples by stage

After the discovery call

Goal: keep the momentum from the meeting and get the materials you need to scope the work. Three emails over about a week. The first, sent the same afternoon, recaps the problem in the buyer's words and lists what you need from them. The second, two days later, shares one relevant case outline or method note. The third asks a single question that moves the deal: who else needs to see the proposal.

After the proposal is sent

Goal: get a decision meeting booked, not a vague "we'll review it". The first email confirms the proposal arrived and offers a short walkthrough slot from your booking calendar. The second, three days later, addresses the objection your reps hear most often at this stage. The third asks plainly whether the timing still works.

Deal gone quiet

Goal: get an honest answer, even if it is no. This sequence fires when a deal sits in a stage longer than your normal cycle allows. Two short emails are enough. The last one gives the buyer an easy way out: reply "not now" and you will check back next quarter.

Closed-lost revisit

Goal: be the obvious call when the winning supplier disappoints. This starts when a deal moves to lost, waits several weeks, then sends one useful note per quarter. No pitch until the buyer replies.

How to set it up

1. In Opportunities, confirm each stage's entry rule with your reps.
2. In Marketing, Emails, Templates, create one template per message.
3. In Automation, create a workflow for the first stage you cover.
4. Add the Pipeline Stage Changed trigger.
5. Set In Pipeline and Pipeline Stage to the starting stage.
6. Add Send Email and pick the template from the dropdown.
7. Add Wait steps and the remaining emails.
8. Before each later email, add If / Else on the stage.
9. In the Settings tab, tick Stop on Response.
10. Use Test Workflow on a dummy contact, then publish.
11. Repeat for each remaining stage.

What this replaces and what it costs you each week

It replaces the rep's personal reminder system: sticky notes, calendar nudges and memory. In a 10 to 250 person firm with flat revenue, that system is usually where the leak is. Deals do not die from a bad pitch. They die from a fortnight of silence.

Running it takes about an hour a week once built. Someone reviews reply rates per sequence, reads a handful of replies, and edits the weakest email. Building the four sequences takes a day if your stages are already clean, longer if they are not.

When not to use stage-triggered sequences

Skip them for your largest deals with a single named buyer and a partner who talks to them weekly. An automated email there can cut across a live negotiation. Keep those deals in a separate pipeline with no workflows attached, and let the account owner write every message.

They also do not suit very short cycles, where a deal opens and closes inside a day. A single sales follow-up after the meeting does that job better.

Troubleshooting

The sequence keeps sending after the buyer replied

The reply exit is missing or watching the wrong channel. Add a condition that ends the workflow when an inbound email or SMS arrives from the contact, and test it with a real reply.

Two sequences run on the same contact

The contact sits on two opportunities, or a stage change did not remove them from the earlier workflow. Add a stage check before every send so each workflow stops itself when the deal moves.

Emails show blank names

Opportunity fields were used but the contact record holds the data, or the reverse. Check which record each field reads from and add a fallback value.

Nothing fires at all

The trigger filter names a different pipeline. Recheck the pipeline and stage in the trigger, then move a test deal again.

Related reading

For the mechanics of chaining messages and waits, read the guide to building an email sequence. The email workflow walkthrough covers triggers and conditions in more depth, and ideas for longer-term nurture suit the closed-lost revisit.

Frequently asked questions

How many emails should each stage sequence have?

Two to four. Each email needs a distinct job, such as a recap, a proof point or a direct question. If you cannot name the job, cut the email.

Should reps send these from their own address?

Yes. Set the sender to the opportunity owner so replies land with the person who knows the deal. A generic sales address reads as marketing and gets ignored.

Can I use the same sequence for every industry we serve?

Use one structure and swap the proof point. An agency buyer, a consultant, a mortgage broker and an estate agent each want a different example, but the stage logic stays the same.

What happens if a rep moves a deal backwards?

The sequence for the earlier stage starts again unless you prevent it. Add a filter that skips contacts who have already received that stage's sequence.

The journey this guide describes