Email Marketing Automation Examples
Practical examples of lifecycle email automations for ecommerce, SaaS and B2B companies.
What email marketing automations should every business have?
Email marketing automations are the flows that run continuously in the background, responding to customer behaviour without manual intervention. The automations that matter most are determined by your business model, but certain categories — welcome, onboarding, recovery, retention and win-back — are universal. The difference between a basic email program and a high-performing one is usually the depth and quality of these automations.
This guide provides practical examples of automations across ecommerce, SaaS and B2B. Each example explains the trigger, the purpose, the typical flow structure and what makes it effective. These are frameworks, not templates — the specific messaging and timing should be calibrated to your audience and business model.
AppLabx designs and builds these automations as part of lifecycle system engagements. Each automation is connected to the broader customer lifecycle rather than treated as an isolated flow.
Ecommerce automation examples
Welcome series (triggered by newsletter signup or account creation). Purpose: set expectations, deliver promised value, introduce the brand and drive first purchase. A typical welcome series runs 3-5 emails over 7-14 days. The first email delivers the signup incentive immediately. Subsequent emails introduce brand story, product range, social proof and a time-limited offer. The sequence should feel like the beginning of a relationship, not a sales pitch.
Cart recovery (triggered by cart abandonment). Purpose: recapture revenue from shoppers who added items to cart but didn't complete purchase. The first email should send within 1-2 hours. A typical sequence runs 2-3 emails over 24-72 hours. The first email is a simple reminder. The second addresses common objections (shipping, returns, trust). The third may include a modest incentive. Timing and messaging should be calibrated to cart value and product type.
Post-purchase (triggered by order confirmation). Purpose: drive repeat purchase, build loyalty and reduce returns. The sequence should begin with order confirmation and shipping updates, then transition to usage tips, complementary product recommendations and review requests. For consumable products, trigger a replenishment reminder based on typical usage cycles.
Win-back (triggered by inactivity — e.g., no purchase in 90-180 days). Purpose: re-engage lapsed customers before they're permanently lost. The sequence should acknowledge the absence, highlight what's new, offer a reason to return and provide a clear path back. If there's no response after 2-3 attempts, suppress the subscriber to protect deliverability.
SaaS automation examples
Welcome and onboarding (triggered by signup or trial start). Purpose: guide new users to their first success with the product. The sequence should cover account setup, core feature introduction, quick wins and support resources. Each email should drive a specific action that moves the user closer to activation. The goal is not to explain everything — it's to get the user to experience value quickly.
Trial expiry (triggered by approaching trial end date). Purpose: convert trial users to paid subscribers before the trial ends. The sequence should start 5-7 days before expiry, highlighting what the user has accomplished during the trial, what they'll lose access to and what the paid plan includes. The final email should be sent on the last day of the trial.
Feature adoption (triggered by product usage data). Purpose: drive adoption of features that correlate with retention. If data shows that users who use Feature X are 3x more likely to retain, trigger an email when the user has not yet used Feature X. The email should explain the feature's value in the context of the user's existing usage.
Churn prevention (triggered by declining engagement or usage). Purpose: re-engage users before they cancel. Triggered when product usage drops below a defined threshold. The sequence should acknowledge the decline, offer help, highlight unused features and provide a path to re-engagement. The final email before cancellation should be direct and helpful.
B2B automation examples
Lead nurture (triggered by content download, webinar registration or demo request). Purpose: move opted-in leads through the buying cycle with stage-appropriate content. The sequence should be triggered by the specific content the lead engaged with, not a generic nurture track. Early-stage leads receive educational content. Mid-stage leads receive comparison and evaluation content. Late-stage leads receive case studies and implementation details.
Post-demo follow-up (triggered by demo completion). Purpose: reinforce the value demonstrated, address unanswered questions and move the lead toward the next step. The first email should send within 24 hours while the demo is fresh. It should reference specific topics discussed and provide relevant resources.
Re-engagement (triggered by extended inactivity — e.g., no email engagement in 60-90 days). Purpose: re-activate dormant leads before they're lost. The sequence should acknowledge the absence, provide fresh value (new content, industry insights) and offer a clear path to re-engagement. If there's no response, suppress the lead to maintain list quality.
Post-sale onboarding (triggered by deal close). Purpose: transition the new client from sales to success, set expectations and drive adoption. The sequence should cover account setup, key contacts, implementation timeline, success criteria and support resources. This is often overlooked but critical for retention.
Frequently asked questions
How many email automations should we start with?
Start with the automations that address the highest-value gaps in your current program. For most companies, that's welcome, cart/trial recovery and post-purchase/onboarding. Don't try to build every automation at once. Build the fundamentals well, measure results, then expand.
What's the difference between an automation and a campaign?
Automations run continuously in the background, triggered by specific customer behaviours. Campaigns are one-time sends planned around your marketing calendar. Automations generate revenue passively. Campaigns require ongoing production effort. Both are necessary; automations typically generate more revenue per effort.
How long should automation sequences be?
There's no universal answer. Welcome sequences typically run 3-5 emails. Recovery sequences run 2-3 emails. Retention sequences are ongoing. The right length depends on the complexity of the decision, the buying cycle and the value of the customer. Test and optimise based on results, not arbitrary rules.
Can we use the same automation for ecommerce, SaaS and B2B?
The categories are similar (welcome, recovery, retention) but the triggers, messaging, timing and goals differ significantly. An ecommerce cart recovery email is not the same as a SaaS trial expiry email. Build automations specific to your business model and audience behaviour.
Start with a complimentary diagnostic
A brief, no-obligation directional review of your current email program — not a lengthy audit.
Prefer email? hello@applabx.com