Drip Campaign Examples: The 5 Email Sequences Every SaaS Needs

Search for drip campaign examples and you get stock screenshots of somebody else's welcome email and a definition recycled across forty blogs. What you rarely get is the actual machine: which event starts the sequence, how long the delays are, where it branches, and when it shuts up. That machine is what this article is about. We build email automation software, which means we spend our days inside these workflows, and nearly every SaaS lifecycle converges on the same five sequences. Here they are as blueprints, with the triggers, timing, and logic you can copy.

First, the thirty-second definition. A drip campaign is a pre-written series of emails sent automatically, one at a time, based on a schedule or a user's behavior. "Email sequence", "flow", and "lifecycle emails" all describe the same thing. The only distinction worth keeping: a classic drip runs on a fixed timer, while a behavioral sequence checks conditions along the way and branches. Everything below is the second kind, because for software products the timer alone is not enough.

The five sequences at a glance

Every one of them should be started by an event your product emits, applied as a tag the moment it happens. No CSV imports, no manual enrollment. If you take one structural idea from this article, take that one: drip campaigns should be triggered by product events, not by marketing calendars.

1. The signup nudge

In most self-serve products, a surprisingly large share of the people who create an account never start a trial. They signed up to look around, got distracted, and left. This sequence exists for exactly one reason: to ask them once, politely, to take the next step.

Trigger: account created, and no trial started after a waiting period. Structure: a single email. Subject line in the shape of "You signed up for [product]. Here is what you were probably looking for." Body restates the one core outcome, links straight to the action that starts the trial, and stops.

Keep this to one email on purpose. Someone who signed up and bounced is a cold lead, not a captive audience. A five-email nudge series to that group is how you earn spam complaints before anyone becomes a customer.

2. The trial activation sequence

This is the workhorse, and the most branched. Built properly it runs to fifteen or more steps in a sequence builder, of which only five are actual emails. The rest are delays and condition checks.

Trigger: trial started. The skeleton:

• Day 0, welcome. What to do first, one link, no feature tour. The job is a first small win, not a curriculum.
• Day 1 to 2, activation check. A condition looks at whether the user completed the product's key setup action. Not activated: the email removes the specific blocker ("takes 3 minutes, here is how"). Activated: skip ahead, no email. Sending "get started!" to someone who already started is how you teach people to ignore you.
• Day 4 to 5, value recap. What they have done so far and what stays behind if they leave. Honest, not fake urgency: the trial genuinely ends.
• Day 5 to 6, expiry warning. Branched on whether a payment method is on file. If yes, a quiet "your subscription starts on [date]" note. If no, the direct ask.
• Day 7, last day. Short, plain, one sentence and one button.

One gotcha that catches almost every team wiring that day 5 branch for the first time: with Stripe, a subscription stays in trialing status even after the user adds a card. The "became a paying customer" event only fires when the first charge succeeds at trial end. If your expiry emails check subscription status instead of card-on-file, you will send "your trial is ending, add a card!" to people who already did. Condition on the payment method event, not the subscription event.

3. The post-activation email

Trigger: the user completes the key setup action. Structure: wait 2 hours, then send one email with the single next step that leads to the product's core outcome.

The 2-hour delay is deliberate. Instant emails read as robotic and land while the user is still inside the app. A couple of hours later, the message arrives as a nudge back in. This sequence is one email long because the product should carry onboarding from here. Drip campaigns patch gaps, they should not become the product's second UI.

4. The win-back

Trigger: trial expired without a subscription. Structure: wait 24 hours, then one email giving a concrete reason to return, and a tag that marks it as sent so no future automation ever repeats it.

The 24-hour wait matters: day-of expiry emails collide with the expiry notice itself. The suppression tag matters more. Nothing burns trust like a "one-time offer" that shows up three times. What the reason to return should be is worth a careful choice: an extended trial, a recap of what they built, or an invitation to reply and talk all work, but never make it a predictable coupon, because a discount that reliably follows every expired trial trains your most price-sensitive users to let trials lapse on purpose. Expectations check: win-backs recover a trickle, not a flood. The sequence earns its slot because that trickle costs one email and zero ad spend.

5. The cancel save

Most cancel emails arrive after the subscription is already dead. If your billing has a notice period, the window between "user clicked cancel" and "access actually ends" is where a save is still possible.

Trigger: cancellation scheduled. Structure: wait a few hours, then a condition checks the cancellation is still pending (people un-cancel on their own; emailing them a save offer afterwards is embarrassing). Then it branches on the cancellation reason from the exit survey: a price objection earns a message about a cheaper plan or annual option, "missing feature" earns an honest note about whether it is coming. After the subscription actually ends, a separate one-line feedback ask goes out. The replies to that email will teach you more than any dashboard.

What to copy beyond the structures

Trigger on events and tag people out the moment the goal is met, so nobody gets an email asking for something they already did. One goal and one link per email. Plain text over designed templates for lifecycle mail, it reads like a person and renders everywhere. And judge sequences on clicks and conversions, never opens, because Apple Mail Privacy Protection inflates opens on autopilot.

Quick answers

Drip campaign vs. email sequence? Same thing in practice. Drip implies a fixed schedule, sequence implies branching logic. Every example above is technically a behavioral sequence.

How many emails should a drip campaign have? As few as complete the job. The biggest sequence above has five emails, and two of them skip when conditions say they are not needed. Volume is not the lever, timing is.

What software do you need? Any tool with event triggers, delays, condition branches, and tag-based exits can run everything in this article. The mainstream platforms do it with varying pain. We are building SendHeron because we wanted those primitives without the enterprise pricing; every sequence on this page can be assembled from the tags, delays, and branches it ships with.

SendHeron is in gated beta. Join the waitlist and we will help you stand up all five when your invite arrives.

Sequence structures current as of July 2026. Stripe trialing-status behavior per Stripe's subscription lifecycle documentation.