Stop Guessing at Email Sequences
Most SaaS teams have exactly one email sequence: the welcome series. And it usually stops at "Thanks for signing up!" followed by radio silence for 3 weeks until someone manually remembers to send a check-in.
Email sequences are revenue infrastructure. When built correctly, they run in the background and move people through your funnel without anyone on your team lifting a finger. Here are five sequences we've seen work, with exact timing, subject line frameworks, and the benchmarks you should hold them to.
1. Welcome Series
Trigger: User signs up or creates an account.
Goal: Drive activation — get the user to complete the core action that makes them likely to stick.
Benchmark: 50%+ open rate, 30%+ click rate on email 1.
The Sequence: 5 Emails Over 14 Days
Email 1 — Immediate (within 5 minutes)
- Subject framework: "Your [Product] account is ready — here's your first step"
- Content: Welcome, confirm what they signed up for, one single CTA to complete the first key action (import data, create first project, connect an integration). Don't overwhelm with features. One action.
Email 2 — Day 2
- Subject framework: "Did you get stuck? Here's help with [first action]"
- Content: Anticipate the most common blocker. Include a 60-second video walkthrough or 3-step guide. This email catches people who opened email 1 but didn't act.
Email 3 — Day 5
- Subject framework: "[Customer name] got [specific result] in their first week"
- Content: Social proof. One customer story showing a concrete outcome. Not a testimonial quote — a mini case study with numbers. End with CTA to replicate the same action.
Email 4 — Day 9
- Subject framework: "3 things most people miss in [Product]"
- Content: Feature education. Highlight three features that drive retention but aren't obvious from the onboarding flow. Quick descriptions with links to docs or demo videos.
Email 5 — Day 14
- Subject framework: "How's it going with [Product]?"
- Content: Direct ask for feedback. "Reply to this email with your biggest question." This catches users who are interested but confused. Replies feed your support and product team with real objections.
What to Watch
If your day-2 email has higher engagement than day-1, your welcome email is too complex. Simplify email 1 and move the extra content to email 2. If open rates drop below 30% by email 5, your sequence is too long or too generic — tighten the gap between emails 3 and 5.
2. Abandoned Trial
Trigger: User signed up for a free trial but didn't complete setup (no core action within 48 hours).
Goal: Re-engage and drive activation before the trial window closes.
Benchmark: 15-20% conversion from abandoned to active.
The Sequence: 3 Emails Over 7 Days
Email 1 — Day 3 (48 hours after signup, no activity)
- Subject framework: "You're 2 minutes away from [specific outcome]"
- Content: Acknowledge they're busy. Show exactly how little effort the first step requires. Include a single-click deep link that drops them directly into the setup flow — not the homepage, not the dashboard. The exact step they skipped.
Email 2 — Day 5
- Subject framework: "Most people get stuck here — quick fix"
- Content: Address the #1 reason people abandon setup. If it's data import, offer a done-for-you option or a sample dataset. If it's connecting integrations, link to a 90-second setup video. Remove the friction, don't just remind them it exists.
Email 3 — Day 7 (trial midpoint or near-end)
- Subject framework: "Your trial ends in [X] days — here's what you'll lose"
- Content: Loss aversion. Show what they've already set up (even if minimal) and what they'll lose when the trial expires. If they haven't set up anything, show what comparable users achieved in the same trial period. Include a CTA to extend the trial by 3 days if they complete setup today.
What to Watch
Track which step in your setup flow has the highest drop-off. That's what email 2 should address. If your abandoned trial conversion is below 10%, the problem isn't the emails — it's the setup flow itself. Fix the product experience first.
3. Re-Engagement
Trigger: Active user goes inactive for 30+ days (no logins, no feature usage).
Goal: Bring them back before they churn.
Benchmark: 5-10% reactivation rate.
The Sequence: 4 Emails Over 21 Days
Email 1 — Day 30 of inactivity
- Subject framework: "We noticed you've been away from [Product]"
- Content: No guilt. No "we miss you." State the facts: "You haven't logged in since [date]." Then share one new feature or improvement shipped since they left. Make it feel like they're missing out on something new, not being scolded for leaving.
Email 2 — Day 37
- Subject framework: "[Specific feature] just shipped — solves the problem you mentioned"
- Content: If you have feedback data from this user (support tickets, NPS comments, feature requests), reference it. "You asked about [X] — we built it." If no specific data, use the most-requested feature from the last quarter. Personalization matters most in re-engagement.
Email 3 — Day 44
- Subject framework: "Here's what your competitors are doing with [Product]"
- Content: Competitive angle. Share aggregate stats: "Companies in [their industry] using [Product] saw [X% improvement] in [metric]." No names needed. The implication is clear — others are getting ahead while they're inactive.
Email 4 — Day 51
- Subject framework: "Should we close your account?"
- Content: The breakup email. Ask directly: do you want to keep your account? Give two options: "Yes, I'll log back in" (link to dashboard) or "No, please close it" (link to cancel). This email consistently gets the highest reply rate in the sequence because it forces a decision.
What to Watch
If email 4 converts more than email 1, your re-engagement content (emails 1-3) isn't compelling enough. Users respond to the threat of loss, not the promise of value. That means your product's perceived value has dropped — a bigger problem than email copy can solve.
4. Upsell
Trigger: User approaches or hits their current plan's limits (storage, contacts, features, seats).
Goal: Upgrade to the next tier.
Benchmark: 3-5% upgrade rate.
The Sequence: 3 Emails Over 10 Days
Email 1 — At 80% of plan limit
- Subject framework: "You're almost at your [contacts/storage/sends] limit"
- Content: Inform, don't pressure. Show their current usage: "You've used 8,000 of your 10,000 contacts." Explain what happens when they hit the limit (features restricted? new contacts blocked?). Show the next plan tier with specific benefits relevant to their usage pattern.
Email 2 — At 95% of plan limit
- Subject framework: "You'll hit your limit this week — here's your best option"
- Content: Urgency without anxiety. Show a side-by-side comparison of their current plan vs. the next tier. Highlight the 2-3 features in the next tier that match their usage patterns. If possible, include a personalized ROI calculation: "Based on your usage, upgrading would give you [X] more [contacts/sends/storage] for $[difference]/month."
Email 3 — Limit reached
- Subject framework: "Your account has reached its limit — upgrade in 30 seconds"
- Content: Direct. The limit is hit. Here's exactly what's now restricted. One-click upgrade button. If they don't upgrade, let them know their data is safe but new actions are paused. Don't delete anything. Don't punish. Just gate new activity.
What to Watch
If users hit limits but don't upgrade, your tier gap is too wide — either in price or in features. Consider adding an intermediate tier. If users never approach limits, your free or base tier is too generous. Track the percentage of users who reach 80% of any limit within their first 90 days.
5. Win-Back
Trigger: User cancels their paid subscription.
Goal: Recover the customer within 30 days.
Benchmark: 2-5% return rate.
The Sequence: 3 Emails Over 30 Days
Email 1 — Immediately after cancellation
- Subject framework: "Your account is cancelled — here's what happens next"
- Content: Confirm the cancellation. Be gracious — no passive-aggressive copy. Tell them their data will be preserved for 30 days. Ask one question: "What was the main reason you cancelled?" with 4-5 clickable options (too expensive, missing features, switched to competitor, not using it enough, other). This data is worth more than the recovery.
Email 2 — Day 14
- Subject framework: "We fixed [the thing that made you leave]"
- Content: If they gave a cancellation reason, address it directly. Too expensive? Offer a discounted rate for 3 months. Missing feature? Show it's now on the roadmap (or shipped). Switched to competitor? Share a specific comparison point where you're stronger. If they didn't give a reason, lead with the biggest improvement you've shipped since they left.
Email 3 — Day 28
- Subject framework: "Your data will be deleted in 48 hours"
- Content: Final notice. Their data — contacts, history, configurations — will be permanently removed. One-click button to reactivate and preserve everything. This isn't a scare tactic if it's true. Data retention has costs, and 30 days is a reasonable window. The deadline creates genuine urgency.
What to Watch
Track cancellation reasons religiously. If "too expensive" is over 40% of responses, you have a pricing problem, not a retention problem. If "not using it enough" dominates, your activation and engagement sequences (see sequences 1-3) need work. Win-back emails treat the symptom. Cancellation reason data treats the cause.
The Infrastructure Behind All Five
These sequences require three things to work:
-
Event tracking. You need to know when someone signs up, goes inactive, hits a limit, or cancels. This means your product needs to emit events that your email tool can listen to.
-
Conditional logic. Each sequence has branching: if a user activates after email 2, stop sending the abandoned trial sequence. Your email tool needs to support suppression rules and conditional exits.
-
Metrics pipeline. Open rates, click rates, conversion rates per email, per sequence, per cohort. Review monthly. Kill underperforming emails. Test new subject lines quarterly.
Build one sequence at a time. Start with the welcome series — it has the highest volume and the most direct impact on activation. Get it running, measure it for 30 days, then build the next one. In 5 months, you'll have all five running automatically, and your revenue will reflect it.