What Is a Drip Sequence?
A drip sequence (also called an email automation or nurture sequence) is a series of pre-written emails sent automatically based on a trigger, signing up for a newsletter, starting a free trial, abandoning a cart, or going inactive.
Unlike a newsletter (which goes to everyone at once), a drip sequence meets each subscriber at their specific point in the customer journey. That context is what makes them convert.
The 3 Most Important Drip Sequence Types
Onboarding Sequence
Triggered when: user signs up or starts a free trial
Goal: get them to their first 'aha moment' before the trial ends
- →Email 1 (Day 0): Warm welcome + the one thing to do first
- →Email 2 (Day 2): Feature spotlight, the thing most users miss
- →Email 3 (Day 4): Social proof, what others achieve after 7 days
- →Email 4 (Day 6): Remove friction, FAQ, live demo, or support offer
- →Email 5 (Day 8): Upgrade nudge, what they unlock on paid
Sales / Nurture Sequence
Triggered when: lead downloads a resource or attends a webinar
Goal: move them from curious to convinced over 5–7 days
- →Email 1 (Day 0): Deliver the lead magnet + a strong first impression
- →Email 2 (Day 1): The problem, name their pain with specificity
- →Email 3 (Day 3): Your unique approach, why your solution is different
- →Email 4 (Day 5): Social proof, case study or testimonial
- →Email 5 (Day 7): The offer, make the ask with a clear reason to act now
Re-engagement Sequence
Triggered when: subscriber inactive for 60+ days
Goal: win them back or cleanly remove them from your list
- →Email 1: Acknowledge the silence honestly, 'We noticed you've been quiet'
- →Email 2 (3 days later): Remind them of value, what they've been missing
- →Email 3 (5 days later): Give them a reason to return, offer, new feature, or content
- →Email 4 (7 days later): The breakup email, 'We'll remove you unless you click here'
How to Write Each Email in the Sequence
Every email in a sequence has a single job. Before writing anything, answer: what is the one thing this email needs the reader to think, feel, or do? If you can't answer that in one sentence, you're not ready to write.
One job: get opened. Write 3 options. Pick the most specific and curious-making one. Under 50 characters.
Completes the subject line, not repeats it. 50–90 characters. The reader sees both before opening, make them work together.
No 'Hope this finds you well.' Start mid-thought or with a hook. The first line should pull them into line two.
One email, one idea. If you have two things to say, send two emails. Brevity signals respect.
One CTA per email. Hyperlink text that describes the action: 'Start your first project' beats 'Click here'.
Email Nurture Drip Sequence Timing: 3–4 Days Apart, Then Weekly
Short answer
Space the first three emails in a nurture drip sequence 3–4 days apart, then shift to a weekly cadence from Email 4 onward. This timing balances momentum with subscriber fatigue: too fast triggers unsubscribes, too slow loses warmth. The exact gap depends on industry, B2B leans toward 4 days, B2C and e-commerce toward 2–3 days.
| B2B SaaS | B2C / E-commerce | Purpose | |
|---|---|---|---|
| Email 1 | Day 0 (instant) | Day 0 (instant) | Welcome, deliver promised content |
| Email 2 | Day 3–4 | Day 1–2 | Value, educate |
| Email 3 | Day 7 | Day 4–5 | Social proof, case study |
| Email 4 | Day 14 (weekly) | Day 9 (weekly) | Offer, soft pitch |
| Email 5 | Day 21 (weekly) | Day 16 (weekly) | Urgency, breakup email |
Send too fast and you feel like spam. Send too slow and they forget who you are. The table above shows the two cadences that consistently produce highest open and click rates, B2B leans long, B2C/e-commerce leans tight.
Why the 3–4 day gap works for the first three emails: the subscriber is freshest right after signup, but bombarding them feels needy. Three days is long enough that each email feels independently considered, short enough that they still remember why they signed up. After Email 3, attention naturally decays, so weekly cadence becomes the sustainable rhythm without burning the list.
- ✓Always send the welcome email immediately, never delay Email 1.
- ✓Pause the sequence if someone converts. Nothing is worse than a sales email after they already bought.
- ✓Give at least 48 hours between each email, respect the inbox.
- ✓The highest-converting email in most sequences is the last one (urgency, scarcity, or the breakup).
Cadence Timeline: Visual Send Schedule
A linear view of when each email leaves the queue. Tight at the start, weekly after Email 3.
Welcome
Value
Social proof
Offer (weekly cadence starts)
Urgency / breakup
For e-commerce or B2C audiences, compress to Day 0 / Day 1 / Day 3 / Day 7 / Day 14. For B2B SaaS, follow the schedule above.
Full Sales Nurture Sequence (Word-for-Word, 5 Emails)
Templates feel abstract until you see one filled in. Below is a complete 5-email sales nurture sequence for a fictional B2B SaaS (project management tool for remote engineering teams). Every line is copy-paste ready, replace the bracketed sections with your specifics.
Day 0 — instant after lead magnet download
Subject: Your remote engineering checklist (and a quick tip)
Preview: The 3 mistakes most engineering managers make in week one →
Hey [first name], Here's the checklist you asked for: [link]. Quick tip while you're skimming it: the section on async standups (page 4) is the one most teams skip and then come back to after their first all-hands disaster. Read that one first. I'll send you 2 more deep-dive resources over the next two weeks. If you ever want to skip ahead, hit reply with "send everything" and I'll just dump the rest in your inbox. — [Your name]
Day 3 — value email
Subject: Why your standup is silently killing velocity
Preview: We measured this across 47 engineering teams. The pattern is brutal →
Hey [first name], A 2024 study of 47 engineering teams found that teams using sync standups shipped 23% fewer features per quarter than teams using async standups. Same headcount. Same backlog. The reason isn't time spent in the meeting. It's the context-switch cost: every developer pulled out of deep work, dropped back in, then needs ~20 minutes to recover focus. Three standups a week = 60 minutes of recovery time, per developer, per week. Three ways to fix this without dropping standups entirely: • Async first: standup posts via Slack/Loom, sync only when blocked • Cluster sync time: do standup right before lunch or end-of-day so the recovery window aligns with natural break time • Skip optional days: most teams don't actually need 5 standups a week [Product name] automates the async standup workflow so you don't have to build it. [Link to specific feature page] Want me to send a 2-min Loom showing how it works? Reply "send Loom" and I'll send. — [Your name]
Day 7 — social proof
Subject: How [similar company] cut standup time 80%
Preview: 47 engineers, 4 timezones, one async workflow →
Hey [first name], Sharing a story that might be familiar. [Similar company name] runs a 47-engineer team across 4 timezones. Their CTO told me last quarter: "We used to lose 5+ hours every week to async-sync friction. Engineers in Europe waiting for US sync calls, US engineers staying late for Asia handoffs. Just the cost of being distributed." They switched their standup workflow to [Product name] in February. Six weeks later: • Engineer's deep work hours: +6 per week per person • Velocity (story points / sprint): +18% • Meetings per engineer: -2 per week • Engineer satisfaction (internal survey): from 6.2 to 8.1 / 10 The interesting part: the change wasn't really about the tool. It was about giving the team permission to stop syncing for sync's sake. The tool just made it operationally easy. If your team is shipping less than you think it should, this is worth a 15-minute look. [Book a demo link] — [Your name]
Day 14 — the offer
Subject: A free 30-day [product name] trial (no card)
Preview: Set up your whole team in under 10 minutes →
Hey [first name], Quick recap of the last three emails: 1. The async standup checklist (your starting point) 2. Why sync standups silently kill velocity 3. How [similar company] cut their standup time 80% If any of that resonated and you'd like to try this on your team, here's a 30-day trial: [link]. No credit card. Set up your team in 10 minutes. What's in the trial: • Full async standup workflow (Slack + dashboard) • Async retro tool • 1:1 sync agenda builder • Engineering manager dashboard (velocity, satisfaction, blockers) If 30 days isn't enough, just reply and I'll extend it. We're trying to make this work for engineering teams, not pitch on a timer. — [Your name]
Day 21 — soft breakup
Subject: Should I stop emailing?
Preview: One reply will sort this out →
Hey [first name], I've sent you 4 emails over the past 3 weeks. If they've been useful, I'll keep going — there's a whole second series on async retros and engineering hiring I haven't sent yet. If they haven't been useful or this isn't the right time, no worries. Just reply with "stop" and I'll take you off this sequence permanently. No judgment, no follow-up. The only ask: just reply with "keep going" or "stop". The silence is harder to act on than either answer. — [Your name] P.S. The 30-day trial link is still active if you want to grab it: [link]
15 Subject Line Examples (Onboarding, Nurture, Re-engagement)
The subject line is the highest-leverage line in the whole sequence. Five examples for each main campaign type:
Onboarding (5)
- “Welcome — start here (60 seconds)”
- “The one feature most users miss in week 1”
- “How [user] hit their first win in 3 days”
- “Quick question, [first name]”
- “Your account is ready (here's what to do next)”
Sales Nurture (5)
- “The mistake we made before [product] (and how to avoid it)”
- “How [similar company] cut [pain] by 80%”
- “Should I send the case study?”
- “Two ways teams do this — only one scales”
- “Trying [product] this week? Here's a head start.”
Re-engagement (5)
- “We noticed you've been quiet, [first name]”
- “Quick — should I keep emailing?”
- “The 3 things you missed in [month]”
- “Last email (unless you click here)”
- “One reason to come back”
The 5 Biggest Drip Sequence Mistakes
Every email tries to sell
Most emails should provide value. Selling in every email trains readers to ignore you.
Generic subject lines
'Quick follow-up' and 'Just checking in' are ignored. Be specific: 'The feature 80% of users miss in week 1'.
No clear progression
Each email should move the relationship forward. If Email 3 could swap with Email 1, you don't have a sequence, you have random emails.
Writing to everyone
Segment. An abandoned cart email and an onboarding email should never read the same.
No re-engagement trigger
If someone opens 3 emails and doesn't click anything, your sequence should adapt, not blindly continue.