RUN THE PROGRAM · Chapter 5
The four lifecycle flows that produce the revenue.
Lifecycle email automation is a set of trigger-based flows that fire on something a contact did (or did not do), without a human sending each message. The four flows that produce almost all the revenue a B2B SMB email program earns are welcome (on signup), lead nurture (on a research-stage action), re-engagement (on 90 days of silence), and win-back (on a longer gap for former customers). This chapter covers the trigger, length, and purpose of each.
KEY TAKEAWAYS
- Welcome series: three to five emails over seven to ten days, firing within one hour of confirmation.
- Lead nurture: five to eight emails over four to six weeks, each tied to a specific stage of the buying question.
- Re-engagement: two to three emails over ten to fourteen days, fired at 90 days of silence. Last email asks explicitly to confirm or unsubscribe.
- Win-back: three emails over three weeks, each offering a specific reason to return. Not a generic discount.
The four flows, side by side
| Flow | Trigger | Length | What it achieves |
|---|---|---|---|
| Welcome series | A new contact confirms their subscription or completes a signup form. Fires once, within an hour of confirmation. | Three to five emails over seven to ten days. Shorter if the first email already answers the subscriber's main question. | Sets expectation for cadence and content. Captures first-touch engagement data (opens, clicks, segment self-identification). Hands warm contacts to sales. |
| Lead nurture | A contact downloads a resource, attends a webinar, or hits a specific page threshold without becoming a lead yet. | Five to eight emails over four to six weeks, each tied to a specific stage of the buying question, not a generic drip. | Moves a research-stage contact toward a sales conversation by answering progressively deeper questions. Qualifies them in or out through content choice. |
| Re-engagement | A contact has not opened or clicked anything for 90 days. Fires once per contact, with a cooldown so it does not loop. | Two to three emails over ten to fourteen days. The last email asks explicitly whether they still want to be on the list. | Separates genuinely interested contacts from dead weight. Removing dead contacts improves deliverability more than any technical fix does. |
| Win-back | A former customer has had no account activity for a defined period (90, 180, or 365 days depending on the sales cycle). | Three emails over three weeks. Each one offers a specific reason to return, not a generic discount. | Reopens a conversation with a customer who already knows the product. Win-back revenue costs a fraction of new-customer acquisition when it works. |
Building the welcome series
The welcome series is the single highest-return automation in a B2B SMB email program. Open rates on the first welcome email run between 50 and 70 percent, roughly three to four times the rate of any other send the business will ever ship. The time to earn the subscriber's trust is in that first week; after that, the message competes with every other newsletter already in their inbox.
The practical five-email structure, over seven to ten days:
- Email 1 (within 1 hour of signup): From the founder's address. States who the business serves, what the subscriber will receive, how often. Asks one open question the subscriber can reply to.
- Email 2 (day 2): The single most useful resource the business has produced for someone at the subscriber's stage. One link, no sales pitch.
- Email 3 (day 4): A short case study showing the specific result a similar customer achieved. Names the customer, names the number.
- Email 4 (day 7): An offer to talk, if useful. If not useful, two more resources the subscriber can read on their own.
- Email 5 (day 10): A segmentation question. "Which of these three topics is most relevant to you right now?" The reply (or click) tags the subscriber for the right future broadcast segment.
Building the lead nurture
The lead nurture is the flow that moves a research-stage contact closer to a sales conversation. The trigger is a specific research-stage action: downloading a resource, attending a webinar, or hitting a page-view threshold on the pricing or services pages without yet contacting sales. The content walks the subscriber through progressively deeper questions a buyer asks on the way to a purchase decision.
A six-email nurture over four weeks, for a B2B SMB with a 60 to 90 day sales cycle:
- Day 1: Deliver the resource that triggered the enrollment. Thank the subscriber and set expectations for the next few emails.
- Day 4: The second question a buyer at this stage asks, with the business's genuine answer. No sales pitch.
- Day 9: A side-by-side comparison of two options a buyer at this stage is weighing. Fair to both sides.
- Day 14: A customer story relevant to the subscriber's industry or role, with specific numbers.
- Day 21: The question a buyer asks when they are close to a decision: pricing, implementation, risk. Direct answer.
- Day 28: An offer to talk. If not interested, the subscriber returns to the regular broadcast list.
Building the re-engagement flow
The re-engagement flow protects deliverability by removing dead subscribers before mailbox providers notice them. The trigger is 90 days of no opens or clicks on any send. The flow does one thing: ask the subscriber to confirm they still want to receive mail, and remove them if they do not.
- Day 1: "We noticed you haven't opened anything in a while. Here's what you'll get if you stay." One link to a recent high-value resource.
- Day 7: "Still useful?" One click to confirm. A paragraph summarizing what the subscriber is on the list for.
- Day 14: "This is the last email unless you confirm you still want to be on the list." Explicit confirmation link. If no click within 7 days, the subscriber is removed from the active broadcast list.
Confirmation rate on a healthy re-engagement flow runs between 15 and 35 percent. The other 65 to 85 percent of the enrolled contacts were already gone; removing them improves open rate for the remaining list by between 10 and 30 percentage points within one send.
Building the win-back campaign
The win-back is distinct from the re-engagement flow. Re-engagement runs on any subscriber who went silent. Win-back runs on a former customer specifically: someone who paid for the service, then stopped. The sales cycle to re-sign a former customer is a fraction of the cycle to acquire a new one, because the trust is already built.
The three-email structure, triggered on a customer-defined churn event (contract end, subscription cancellation, 180 days of no account activity):
- Day 1: A specific thing the business has changed since the customer left, written by the account owner who worked with them. Not a template.
- Day 10: A customer story from a similar account that returned, with the result they got. Names the customer, names the number.
- Day 21: An invitation to a 20-minute call to look at whether a return would make sense. Not a sales demo.
The win-back is personal, not automated, past the trigger. A generic discount email to a former customer who left for a specific reason earns no replies. The business's win-back revenue typically runs between 10 and 25 percent of former-customer accounts enrolled, when the sales owner follows up on replies within 48 hours.
- Companies that already send one broadcast newsletter consistently and are ready to layer in automation. The broadcast is the editorial muscle; automation extends it.
- Programs with CRM-to-email-platform integration, so lifecycle stage changes in the CRM fire the right flow automatically.
- Founders willing to write the welcome series in their own voice. The welcome is the one flow where personal voice drives most of the lift.
- The team enrolls contacts in three or more overlapping flows at once, so one subscriber receives six emails per week and unsubscribes.
- AI drafts are shipped without a human finishing pass. Lifecycle emails are the most personal messages the business sends; a template-sounding welcome is worse than no welcome.
- The business sets up flows and never reviews them. Content dates fast; a six-month-old welcome often names a product the company no longer offers.
- Each flow has exactly one enrollment trigger, with branching inside the flow for different segments. Simplifies debugging.
- An exclusion rule prevents a subscriber from receiving more than three automated emails in any seven-day window.
- The sales owner is notified when a nurture or win-back subscriber replies, with a 48-hour SLA on the response.
Common questions.
What are the four lifecycle email flows an SMB should build first?
+
The four lifecycle email flows an SMB should build first are the welcome series (fired on signup), the lead nurture (fired on a research-stage action), the re-engagement flow (fired on 90 days of inactivity), and the win-back campaign (fired on 90 to 365 days of customer inactivity). Together these four flows produce the majority of the revenue email generates for a B2B SMB. Broadcast newsletters support them by keeping the brand in the inbox between flows, but they do not substitute for the automated sequences, because broadcast cadence does not match an individual contact's timing the way a trigger-based flow does.
How long should a welcome email series be?
+
A welcome email series should be three to five emails over seven to ten days. Shorter is fine if the first email already answers the subscriber's main question (what the business does, what they will receive, when the next email comes). Longer than five emails inside two weeks starts to feel like a sales sequence rather than a welcome, and reply rate drops. The first email should land within one hour of signup, from a real person's address, and set expectations for cadence. Email two to five each answer a specific question the business knows a new subscriber has.
What is the right trigger for a re-engagement flow?
+
The right trigger for a re-engagement flow is 90 days of no opens or clicks on any send. 60 days is too aggressive and fires on subscribers who are seasonally active. 180 days is too late because the inbox provider has usually already started routing the business's mail to Promotions by then. A 90-day inactivity trigger with a cooldown period (the flow cannot re-fire for the same contact more than once in six months) catches most of the drift before deliverability is affected, without annoying real subscribers who skipped a few sends.
What should a win-back email offer that a nurture email should not?
+
A win-back email should offer a specific reason the former customer should return, rooted in what has changed since they left: a new feature they asked about, a problem they ran into that the product now solves, a change in pricing or service that matches their earlier objection. A nurture email, by contrast, answers a research-stage question that applies to any buyer at that stage. The win-back is customer-specific; the nurture is stage-specific. Mixing them produces nurture emails that sound presumptuous to new leads and win-backs that sound generic to former customers.
How do I trigger an email automation from a HubSpot workflow?
+
HubSpot workflow triggers run on contact-based rules: a form submission, a lifecycle stage change, a specific property value, or a page view that meets a threshold. The practical rule for a 10 to 50 person B2B company is to trigger each lifecycle flow on exactly one event, with branching inside the flow for different segments. One trigger simplifies debugging when a subscriber reports not receiving the email, because the audit log has a single entry point rather than six overlapping enrollment conditions. HubSpot's Workflows documentation (knowledge.hubspot.com) covers the specific setup for each flow type.
Should I use AI to write lifecycle emails?
+
AI should draft lifecycle emails, not finish them. The welcome series and the nurture flow are the two most personal, trust-building touches in the whole program. An AI draft gives the writer a starting structure in minutes rather than hours, which is worth the investment. The finishing pass (replacing generic claims with specific examples, rewriting the opening and closing in the founder's voice, deleting the AI-pattern phrases that leak through) is what makes the difference between an automation subscribers delete and one they reply to. A lifecycle flow with no human finishing pass earns the lowest reply rate of any email the business sends.
What percentage of email revenue typically comes from automation versus broadcasts?
+
For a well-run B2B SMB email program, lifecycle automation typically produces 60 to 80 percent of the attributed email revenue, while broadcast newsletters produce the remaining 20 to 40 percent, by every working consultant's field data (specific vendor-published numbers tend to be higher but include e-commerce, which inflates the automation share). The practical implication is that time spent improving the four automated flows produces more revenue per hour than time spent on the next broadcast send, in most SMB programs that have been running broadcasts for six months or longer.
How often should I update the content of an automated flow?
+
Automated flow content should be reviewed every six months, with a lighter check every quarter to catch dated references. The welcome series dates fastest because it references the company's current positioning and offerings; a six-month-old welcome often references a product the company no longer sells or a feature it has since renamed. The nurture flow dates more slowly because it answers evergreen research-stage questions. The re-engagement flow should almost never change, because its job is unambiguous and new copy adds variance without lift. Set a calendar reminder for the biannual review; nobody rediscovers an automation on their own.
NEXT CHAPTER
Proving the whole program is paying back.
The final chapter covers the five numbers an owner should actually watch, and how to tie email to pipeline in the CRM. See the Measurement and ROI chapter.
Official sources
- Government of Canada: Canada's Anti-Spam Legislation (CASL) overview
- CRTC: CASL compliance and enforcement
- Google: Email sender guidelines for bulk senders (2024 enforcement)
- Yahoo: Sender best practices and bulk sender requirements
- Microsoft: Strengthening the Outlook email ecosystem (2025 requirements for high-volume senders)
- IETF RFC 7489: DMARC specification
- IETF RFC 7208: Sender Policy Framework (SPF)
- IETF RFC 6376: DomainKeys Identified Mail (DKIM)
- M3AAWG: Sender Best Common Practices
- Schema.org: EmailMessage