# Lifecycle Email Course > A three lesson course that takes you from a blank lifecycle map to a shipped sequence, with exercises, event schemas and copy templates at every step. Source: https://saas-marketing.net/courses/saas-lifecycle-email/ Topic: SaaS Email Marketing Type: course-index Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/courses/saas-lifecycle-email/ ## Short answer This is a three lesson build sprint, roughly two hours per lesson, that ends with one live product triggered sequence in your own ESP. Lesson one maps lifecycle stages to product events. Lesson two builds segments from those events. Lesson three writes, ships and measures the sequence. You need admin access to an ESP and one engineer who can emit events. The first exercise is deleting emails, not writing them. ## Key takeaways - The course ends with a shipped sequence in your production ESP, not a slide deck or a certificate of completion. - Lesson one forces an audit that typically retires 30 to 60 percent of an existing automation library before anything new gets written. - You need product events flowing into your ESP before lesson two, which is the prerequisite most teams underestimate. - Budget six hours total across three sessions, plus two to three hours of engineering time for event instrumentation. - Every lesson ships one artefact: a lifecycle map, a segment spec, then live copy with a measurement plan attached. --- Most lifecycle email courses hand you a theory of the funnel and leave you with a notebook. This one ends with a sequence running in your production account, firing off a product event, with a holdout group attached so you can prove it worked. Three lessons. About six hours. Here's the position I'll defend for the whole course: before you write a single new email, you will delete some. Probably a lot of them. Teams that skip the audit end up layering good messages on top of a bad send schedule, and the new work gets blamed for the old fatigue. ## Who this course is for, and what you need before lesson one It's for the person who owns lifecycle email at a SaaS company between roughly 500 and 50,000 active accounts, whether that's a growth marketer, a lifecycle specialist or the founder still doing it at 11pm. If you're evaluating platforms rather than building sequences, start with [SaaS Email Marketing Platforms Compared](/guides/saas-email-marketing-platforms/) instead and come back after you've picked one. Two prerequisites, and both are hard gates. The first is admin access to an ESP you can actually publish from. Not a sandbox, not a request ticket into a marketing ops queue. If approval to send takes four days at your company, the course will stall in lesson three. The second is one engineer who can emit product events. You need somebody who will add `project_created`, `invite_sent` and `integration_connected` to your event stream inside a week. Two to three hours of their time covers it. Without those events, lesson two collapses into day-based drips, which is the pattern the whole course exists to replace. Open your ESP and count active automations. If that number is above twelve and nobody can name what each one does, you have an audit problem, not a copywriting problem. Lesson one is built for exactly that situation. ## The three lessons and what each one ships Each lesson produces one artefact. No lesson is finished until the artefact exists, and the exercises are structured so you cannot fake it. Lesson one is the audit and the map. You'll list every automated send, tag each one with the lifecycle stage it claims to serve, then check whether that stage has a product event behind it. Most teams discover two or three stages with six emails each and one stage, usually the second week of the trial, with none. The deeper reasoning behind stage definitions lives in [SaaS Email Marketing Strategy](/guides/saas-email-marketing-strategy/). - Lesson two is where the course earns its keep. You'll convert the map into segments built on behaviour rather than signup date, using the methods in [Lifecycle Email Segmentation With Product Data](/guides/lifecycle-email-segmentation/). A user who created a project on day one and a user who hasn't logged in since signup are on the same day-three drip in most accounts. That's the defect we fix. Lesson three ships. You write the copy, set the holdout at 10 percent, publish, then build the dashboard. One sequence only. ## What's included, and what you'll bring yourself The templates are deliberately unglamorous. You get an event schema sheet with 14 pre-named SaaS events and the properties each one needs, a segment spec template, six copy skeletons covering welcome, activation nudge, feature adoption, trial expiry, dormancy and win-back, and a measurement sheet that calculates activation lift against your holdout. What you bring: your product, your event stream, and an honest view of your current numbers. The course asks you to record baseline activation rate in lesson one so lesson three has something to compare against. Teams that skip that step end up with a shipped sequence and no way to argue it worked. **~6 hours** Total focused time across three lessons, excluding engineering instrumentation If you want to size the revenue opportunity before committing the time, run your numbers through the [SaaS Email Revenue Calculator](/calculators/email-revenue/) first. At 2,000 signups a month and a 4 point activation lift, the arithmetic usually justifies six hours without much debate. ## The honest time estimate, and what the course will not do Two hours per lesson is real if you've done the prerequisites. It is not two hours if you spend the first session chasing ESP credentials or arguing about who owns email. Add a week of calendar time at the front for access and instrumentation. The course will not fix deliverability. If your domain reputation is damaged, better segmentation helps at the margin but you need the technical work first, and [SaaS Email Marketing Mistakes](/guides/saas-email-marketing-mistakes/) covers the failure modes that cause it. It also will not pick your platform. If you're between vendors, the [HubSpot vs Customer.io](/comparisons/hubspot-vs-customer-io/) breakdown is the faster read, and teams running self-hosted should look at [Mautic for SaaS](/guides/mautic-for-saas/) before starting lesson two, because Mautic's segment refresh behaviour changes how you write entry conditions. Somebody completes all three lessons, then immediately builds four more sequences in week two. Engagement drops, unsubscribes climb, and the lifecycle programme gets blamed. Ship one. Measure for 30 days. Then build the second. ## How this fits the rest of the library The course is the practical layer. The reference layer sits in [SaaS Email Marketing](/saas-email-marketing/), which covers the strategy, platform and deliverability material in more depth than three sessions allow. When you want to know whether your post-course numbers are good or merely better, [SaaS Email Benchmarks](/research/saas-email-benchmarks/) has open, click and activation ranges segmented by ACV band and motion. ## Start with lesson one this week Block two hours, open your ESP, and list every active automation before you read another word of theory. The audit is unpleasant and it's also the single most influential hour in the course. Lesson one begins with that list. ## Frequently asked questions ### How long does the lifecycle email course take? Roughly two hours per lesson across three lessons, so six hours of focused work. Add two to three hours of engineering time to instrument product events before lesson two. Most teams run it across three weeks, one session per week, which leaves room for the exercises between sessions. Compressing it into two days works if your events already fire. ### Do I need an engineer to take this course? For lesson two and three, yes. You need someone who can emit product events such as project_created or invite_sent into your ESP or CDP. Without event data you can still complete lesson one and build the map, but the segments in lesson two degrade into time based drips, which is the exact pattern the course is designed to replace. ### Which email platform does the course use? The exercises are written to be platform neutral and tested against Customer.io, Braze, HubSpot and Mautic. Event names, segment logic and copy transfer directly. Screenshots reference Customer.io because its segment builder maps most cleanly to the concepts, but nothing in the course depends on it. ### Why does the course start by deleting emails? Because most SaaS email programmes are an archaeological record of old campaigns rather than a designed system. Sending fewer, better timed messages usually lifts engagement inside a month and protects domain reputation. The lesson one audit sorts every active automation into keep, rewrite or retire, and retire is normally the biggest pile. ### Is this course useful if we already have onboarding emails? Yes, and those teams tend to get more from it than teams starting from zero. Existing sequences give you baseline open, click and activation numbers to measure against. The course reframes those emails around product behaviour instead of signup date, which is usually where the lift comes from. ### What counts as finished at the end of lesson three? One sequence live in production, triggered by a product event, with a defined holdout group and a dashboard showing activation rate for treated versus held out users. If you cannot point at that dashboard, you have not finished, and the course explicitly tells you not to move on to a second sequence.