What is lifecycle marketing? A field guide for operators starting from zero

Picture two marketing teams running the same product. Team A schedules everything: Tuesday newsletter at 10am, sale email on the 1st, product update when the launch date arrives. Same calendar, same audience, identical email landing in everyone's inbox at the same moment regardless of what each user did yesterday. Team B sends a welcome message twenty seconds after a user signs up — not because it's Tuesday, but because someone just joined. They send a cart-recovery email four hours after a basket sits abandoned. They send nothing at all to a user who hasn't opened anything in six months, because that user has clearly left and another email won't change it.

Team B is doing lifecycle marketing — sending messages triggered by what each individual user just did, rather than by what the calendar says. Team A is running batch sends to everyone at once, on a schedule. That single shift, from calendar-driven to behaviour-driven, is the whole field in one sentence.

Every other definition you'll read — "multichannel nurture", "behavioural CRM" (Customer Relationship Management — the systems and discipline of managing communication with users over time), "personalisation done properly" — is a longer way of saying the same thing. The useful shift, the one that separates lifecycle from everything that came before it, is what fires the trigger. Old marketing fires off a calendar. Lifecycle fires off the user's state. Once you see that, the rest of the field falls into place.

Most newcomers arrive with three tangled definitions in their head. Worth separating them.

Batch-and-blast— the same email sent to your whole list at the same time, on a schedule someone picked in advance — is what most brands do before they build a lifecycle practice. Tuesday newsletter, sale email, product launch — same shape every time. Nothing wrong with batch as a tool. It's a real channel. But it treats the audience as a single monolith and can't react to what any individual user did, because it isn't listening.

Acquisition marketing sits at the other end of the funnel. Paid ads, SEO, affiliate, partnerships — work aimed at turning a stranger into a user. The job stops the moment they sign up. Lifecycle starts where acquisition stops: once a stranger becomes a user, lifecycle owns the relationship from there.

Lifecycleis the bit in the middle — post-signup, pre-churn — and reacts to the individual user's state. A user who installed the app three days ago but hasn't opened it gets a different message than a user who's using it daily. Someone who bought yesterday gets a different message than a three-year subscriber. A user who hasn't opened an email for six months gets a different message than one who opens every send. That's the whole job.

And the one thing it actually is: a sub-discipline of CRM. CRM is the broader umbrella covering every system and process that manages user communication after signup. Inside that umbrella, lifecycle is the part that ships actual messages. If your team has a CRM lead, lifecycle is most of what they spend their time on.

Before the programs, the tools, and the metrics, there's a way of thinking about every lifecycle decision that makes the rest of the field cohere. Three layers, in order. Skip the order and you end up writing a great email for the wrong people at the wrong time — which describes most of the bad lifecycle work you see in the wild.

Stage. Where is this user in their relationship with the product? The canonical stages — broad buckets every lifecycle team works with — are: new (just signed up, hasn't taken a meaningful first action yet), activating (signed up, taken a first step, not yet a habit), active (regular user, the main population), at-risk (engagement declining, not yet gone), lapsed(effectively gone, no recent activity). A user's stage determines the broad program they're eligible for. New users get welcome flows, lapsed users get win-back flows, and nobody gets both at once.

Moment. Inside a stage, what just happened? A new user who signed up twenty seconds ago is in a different moment than one who signed up yesterday. An active user who just made their first purchase is in a different moment than one who viewed their cart twice without buying. Moments are the specific triggers — the events — that start a specific sequence inside the right program.

Message.Given the stage and the moment, what does the message actually say? Wording is the last decision, not the first. When teams skip stage and moment thinking and jump straight to "let's write a great email", they end up with prose that's great in isolation and useless in context. Stage picks the program, moment picks the trigger, and only then do you write the words.

This stacking — stage, moment, message — is the backbone of every Orbit skill for lifecycle design. The Lifecycle Program Design skill walks through it formally.

Almost every lifecycle stack anywhere — B2B SaaS, consumer app, ecommerce, marketplace — is built from some combination of five programs. Learn these and you know roughly 80% of what a lifecycle team ships in a year.

Welcome / onboarding. The first 7–14 days after signup. Goal: move new users to their first meaningful action — what the industry calls activation (the moment a new user does the thing that predicts they'll stick around). Shape: a short sequence, branched on whether the user has activated yet. How to build the welcome sequence

Cart / browse abandonment. A specific user action — viewed a product, added to cart, browsed a category — didn't convert into a purchase. Goal: recover the intent before it goes cold. Shape: 1–3 emails over 24–48 hours, stopping the moment the user converts or re-engages. More than two emails hits diminishing returns fast. Cart flow mechanics

Post-purchase. A user just bought something. Goal: turn a one-off buyer into a repeat one. Shape: order confirmation, then delivery transactional, then review request, then "you might also like", then either a replenishment cadence (if the product has a natural reorder cycle, like coffee or contact lenses) or back into normal lifecycle rhythm. Post-purchase playbook

Win-back / reactivation. A user hasn't engaged for some defined period — typically 30, 60, or 90 days, depending on the category. Goal: reactivate them, or conclusively sunset them (stop sending). Shape: 2–3 increasingly sharp messages, then a hard "stop sending" decision. The crucial principle: trying forever to "save" users who have clearly left poisons your sender reputation — your standing with mailbox providers like Gmail and Outlook, who use it to decide whether your future emails go to inbox or spam. Win-back mechanics

Transactional. Not strictly a marketing program, but lifecycle teams usually own the templates. Receipts, shipping updates, password resets, account notifications. These are the highest-open-rate emails in the system, often double or triple the rate of marketing sends, which makes them the most valuable surface in the system for subtle nudges (a one-line "might also like", a link to the help centre). Transactional template craft

The argument that gets a CFO to actually fund a lifecycle team isn't about better emails. It's about how the maths compounds. Imagine you improve 90-day retention — the share of users still active 90 days after signup — by two percentage points this quarter. The effect doesn't just show up in this quarter's revenue. Every future cohort (every future group of new signups) inherits the improvement. Six quarters later, you're still collecting on the work you did today, stacked on top of every other improvement in between. Retention gains compound.

Acquisition doesn't behave that way. A dollar spent on paid social this month bought you some users this month. Next month, you spend another dollar to buy another batch. Those two dollars don't compound. They're independent.

This is why lifecycle economics almost always beat acquisition economics past a certain size — and why companies that cross that threshold invest heavily in lifecycle while those that don't stay stuck on the acquisition treadmill, raising the next round to fund the next month's ad spend. The retention economics guide walks through the maths in detail.

Three honest questions to ask of your current setup. Any "no" means you're running batch-and-blast in lifecycle clothing.

Can your emails fire off user behaviour, not just off time?If every send starts with someone clicking "Schedule campaign" on a date picker, you don't have lifecycle — you have a newsletter programme. Real lifecycle requires an ESP — Email Service Provider, the platform that sends your emails — or a CRM that can listen to events ("user signed up", "cart abandoned", "no activity 30 days") and fire sequences from them automatically.

Do different users get different messages based on their state? If every subscriber receives the same email, that's batch. Lifecycle means a user three days into onboarding gets something different than a power user of two years. The mechanism that makes this possible is segmentation — splitting your audience into groups based on attributes or behaviour. Segmentation basics

Do you measure programs, not just campaigns?A campaign is one send. A program is the end-to-end flow — the full welcome sequence, the full cart-abandonment series, the full win-back. Measuring the campaign tells you if a single email was well written. Measuring the program tells you if the whole thing actually moves the business. Without program-level measurement, you're optimising content, not outcomes — and the gap between those two things is where most lifecycle programs quietly fail.

If this is the "what even is this" stage, treat the guide above as the frame. The rest of the Beginner course gives you the foundations to actually run a program. Start with retention economics for why any of this matters in financial terms. Then read segmentation beyond RFM for how to actually slice the audience, and the welcome email sequence for your first program in detail. Subject line anatomy covers the smallest unit of craft, email deliverability covers why your emails might not arrive, and the cadence question covers how often to send, done properly.

Once you're running real programs and want to deepen the craft, move to the Intermediate course. When you're managing deliverability infrastructure and causal measurement (proving your program caused the revenue rather than just correlating with it), the Advanced course is the destination.

One last thing. If you take nothing else from this guide: stage, then moment, then message. Build the audience logic before the words. Most bad lifecycle work is great copy fired at the wrong person. Get the triggers right and average copy will outperform brilliant copy sent on a Tuesday.