The lifecycle email playbook: which flows to build, in what order

Most lifecycle advice hands you a diagram with fourteen boxes. The useful version is a build order, because you will only ever have time to build the next one.

Every business has the same five moments where an automated email earns its keep. What differs is which of them has the most money attached, and that is the only question that should decide what you build first. This playbook maps each moment to a flow, gives you the full copy for every flow through the templates, and shows how the order changes by business model — then how to fit it to the automation allowance on your plan.

The five moments, and the flow for each

Campaigns — launches, sales, newsletters, events — sit on top of this rather than inside it. They are scheduled by you; lifecycle flows are triggered by the customer. A programme with good campaigns and no lifecycle flows is working harder than it needs to, because every result depends on you remembering to send something.

The build order, by business model

The rule is simple: build first whichever flow sits on the moment with the most revenue attached, then the moment that protects the rest. Applied to the three common models:

• Online store — 1. Abandoned cart. 2. Welcome series. 3. Post-purchase. Cart recovery reaches people with active purchase intent and pays back in its first week; post-purchase starts from an order confirmation you are already sending. Then re-engagement once the list is a year old.
• Subscription or SaaS — 1. Failed payment. 2. Free trial. 3. Welcome series. Failed-payment recovery comes first because it returns money you have already earned, from customers who wanted to stay. The trial sequence decides conversion; the welcome series is for the people who join a list without starting a trial.
• Publisher, creator or service business — 1. Welcome series. 2. Re-engagement. 3. Whichever moment has money in it: post-purchase if you sell anything, a trial flow if you sell a paid tier. With no cart and no subscription billing, the relationship is the product, so the flows that protect it come first. Your newsletter runs alongside as a campaign rather than taking a flow slot.

Where flows collide, and the exit rules that stop it

Every flow you add can put a second email in front of the same person on the same day. The collisions are predictable, so the exit conditions can be too:

The last one is the one that gets skipped, because it feels like losing contacts. It is the opposite: sustained non-engagement is a signal mailbox providers use against your whole list, and Gmail expects bulk senders to keep complaints under 0.3%. The deliverability guide covers why.

Fitting the playbook to your Bluey plan

On most platforms the constraint on a lifecycle programme is time. On Bluey it is also the automation allowance, which is the one limit that should shape your build order rather than your budget.

• Spark — 3 automations. Exactly enough for the first three flows in whichever build order above fits your business. Choose them deliberately; the fourth flow is the signal to move up, not a reason to merge two flows into one.
• Grow — 25 automations. Room for the full lifecycle plus variants: separate post-purchase paths for first-time and repeat buyers, a failed-payment variant for 3D Secure declines, a re-engagement flow per segment. Grow also adds A/B testing and send-time optimisation, which is when testing timing inside a flow becomes worth doing.
• Business — unlimited. For programmes where each product line, market or brand runs its own set of flows.
• No cap on steps or branches inside a flow on any plan, so the exit conditions above never cost you anything.
• Every one of these needs its event source connected first — no event, no trigger. Shopify is live today. The WooCommerce and Stripe connectors are coming soon, so until they ship route those events in through webhooks, Zapier or viaSocket via the API. Connect before you build.

Lifecycle FAQ

Related