Updated · 10 min read
What is lifecycle marketing? A field guide for operators starting from zero
Most intros to lifecycle marketing either define it by listing the tools (Braze, Iterable, HubSpot...) or by reciting the email types (welcome, cart, win-back...). Neither builds the mental model an operator needs. Lifecycle is one simple idea — send the right message at the moment it's most useful — executed across a small set of canonical programs. This guide is the version of the definition I wish I'd been handed when I started.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
The one-sentence definition
Lifecycle marketing is the practice of sending the right message at the moment it's most useful — based on where each user is in their relationship with the product, not on what the marketing calendar happens to say this week.
Every other definition you'll read — "multichannel nurture", "behavioural CRM", "one-to-one at scale" — is a longer way of saying the same thing. The useful shift, the one that separates lifecycle from everything that came before it, is the source of the trigger. In a traditional marketing calendar, the trigger is time: Tuesday at 10am, we send the newsletter; the campaign launches on the 1st. In lifecycle, the trigger is the user's state: someone just signed up, so they enter the welcome program; someone abandoned a cart, so they enter the cart program; someone hasn't opened anything for 90 days, so they enter the win-back program.
That inversion — from calendar-driven to state-driven — is the whole idea. Everything else is craft on top of it.
How it differs from batch-and-blast (and from acquisition)
Batch-and-blastis what most brands do before they build a lifecycle practice. One message, same for everyone, same day, different week. The newsletter. The sale email. The product launch. There's nothing wrong with it — batch messaging is a real channel — but it treats the audience as a single monolith. It can't react to what any individual user did, because it's not listening.
Acquisition marketingsits at the other end. Paid ads, SEO, affiliate, partnerships — work aimed at turning a stranger into a user. The job stops once they've signed up. Lifecycle starts where acquisition stops: the moment a stranger becomes a user, lifecycle owns the relationship.
Lifecycleis the bit in the middle: the post-signup, pre-churn span. It reacts to the individual user's state. The user who installed the app but hasn't opened it in three days gets a different message than the user who's using it daily. The user who bought something yesterday gets a different message than the user who's been a subscriber for three years. The user who hasn't opened an email for six months gets a different message than the user who opens every one.
The mental model: stage → moment → message
Every lifecycle decision lives on three layers. Getting them in the right order is most of the craft.
Stage. Where is this user in their relationship with the product? The canonical stages are: new (just signed up, hasn't activated), 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.
Moment. Inside a stage, what just happened? A new user who signed up 20 seconds ago is in a different moment than a new user who signed up yesterday. An active user who just made their first purchase is in a different moment than one who just viewed their cart twice. Moments are the specific triggers that start a specific sequence.
Message.Given the stage and the moment, what should the message say? The message is the last decision, not the first. When teams skip the stage and moment thinking and jump straight to "let's write a great email", they end up with a great email that's sent to the wrong people at the wrong time.
This stacking — stage, then moment, then message — is the backbone of every Orbit skill for lifecycle design. The Lifecycle Program Design skill walks through it formally.
The five canonical programs
Almost every lifecycle stack anywhere is built from some combination of these five programs. If you know these, you know 80% of what a lifecycle team does.
1. Welcome / onboarding. The first 7–14 days after signup. Goal: move new users to their first meaningful action ("activation"). Shape: a short sequence, conditional on whether the user has taken the activation action yet. How to build the welcome sequence
2. Cart / browse abandonment. A specific user action (viewed cart, added to cart, browsed category) didn't convert. Goal: recover intent. 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
3. Post-purchase. The user bought. Goal: turn a one-off buyer into a repeat one. Shape: order confirmation → delivery transactional → review request → "you might also like", then either into a replenishment cadence (if the product suits one) or into normal lifecycle rhythm. Post-purchase playbook
4. Win-back / reactivation. User hasn't engaged for a defined period (30 / 60 / 90 days depending on the category). Goal: reactivate or conclusively sunset them. Shape: 2–3 increasingly sharp messages, then a "stop sending" decision. A crucial principle: trying forever to "save" users who have clearly left poisons your sender reputation. Win-back mechanics
5. Transactional. Not a marketing program — but the lifecycle team usually owns the templates. Receipts, shipping updates, password resets, account notifications. These are the highest-open-rate emails in the system, which makes them the highest-leverage surface for subtle lifecycle nudges (a one-line "might also like", a link to the help centre). Transactional template craft
Why lifecycle compounds (and acquisition doesn't)
Every percentage point of retention you add today keeps paying off for every future cohort. Every dollar of acquisition you spend today is one dollar.
The economic argument for lifecycle that makes senior leaders actually care is the compounding one. When you improve 90-day retention by 2 percentage points this quarter, the effect doesn't just show up in this quarter's revenue. Every future cohort you acquire also benefits from the improved retention. Six quarters later, you're still collecting on the improvement you made today — stacked on top of every other improvement in between.
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 user. The two dollars do not compound; they're independent.
This is why lifecycle economics almost always beat acquisition economics past a certain scale — and why the companies that cross that scale invest heavily in lifecycle while the ones that don't stay stuck on the acquisition treadmill. The retention economics guide walks through the maths in detail.
How to tell if you're actually doing lifecycle
Three honest questions to ask your current setup. If the answer to any of them is no, you have batch-and-blast with lifecycle cosplay, not a lifecycle program.
1. Can your emails trigger 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 / CRM that can listen to events ("user signed up", "cart abandoned", "no activity 30 days") and fire sequences from them.
2. Do different users get different messages based on their state? If every subscriber gets the same email, that's batch. Lifecycle means a user three days into onboarding gets a different message than a user who's been a power user for two years. Segmentation is the thing that makes this possible. Segmentation basics
3. Do you measure programs, not just campaigns?A campaign is a single send. A program is the end-to-end flow (welcome, cart, win-back, etc.). Measuring the campaign tells you if the email was well written. Measuring the program tells you if the program actually moves the business. Without program-level measurement, you're optimising content, not outcomes.
Where to go next in this library
If you're still at the "what even is this" stage, this guide is the frame. The rest of the Beginner course gives you the foundations:
1. Retention economics — why any of this matters in financial terms.
2. Segmentation beyond RFM — how to actually slice the audience.
3. The welcome email sequence — your first program, in detail.
4. Subject line anatomy — the smallest unit of craft.
5. Email deliverability — why your emails might not arrive.
6. The cadence question — how often to send, done properly.
When you're running actual programs and want to level up, move to the Intermediate course. When you're managing deliverability infrastructure and causal measurement, the Advanced course is the destination.
Frequently asked questions
- Is lifecycle marketing the same as email marketing?
- Email is the most common channel for lifecycle, but not the only one. Push, SMS, in-app, and web push are all lifecycle channels. What makes it lifecycle isn't the channel — it's that sends are triggered by user state, not by a calendar. A triggered push on signup is lifecycle; a Tuesday promo email is batch.
- Do I need a CDP to do lifecycle?
- No. You need an ESP or CRM that can listen to events and fire sequences. Most modern ESPs (Braze, Iterable, Customer.io, HubSpot) can do this without a separate CDP. CDPs become useful when you're unifying data across many sources and building sophisticated audiences — which is an intermediate / advanced problem, not a starter one.
- How much data do I need before lifecycle is worth doing?
- Enough users that 'new', 'active', and 'lapsed' cohorts exist as meaningfully different groups. For most products that's a few thousand users. Below that, you're better off focused on acquisition and product — lifecycle has diminishing returns when the audience is too small for cohort-based sends to reach meaningful volumes.
- Where does lifecycle end and customer success / support begin?
- Lifecycle owns automated, scalable messaging triggered by state. Customer success and support own high-touch, one-to-one interactions. In practice the boundary is porous — a lifecycle system might trigger a CS outreach for users showing churn signals, and a support interaction might enrol a user into a targeted lifecycle sequence. Treat them as collaborating teams, not separate silos.
- Is lifecycle marketing dead because of AI / predictive / [latest buzzword]?
- No. The tools have changed — AI personalisation, predictive sends, dynamic content — but the core idea (message someone based on where they are, not when the calendar says) is exactly what AI tools exist to do at higher fidelity. The craft underneath doesn't change; the precision of execution does.
This guide is backed by an Orbit skill
Related guides
Browse allChoosing which lifecycle programs to build first
New lifecycle lead, empty Braze account, a laundry list of programs you could build. The question nobody trains you for is which to build first. This is the selection framework — by business type, by team size, by data maturity, and the programs I'd actively wait on.
Lifecycle marketing for flat products
The standard lifecycle playbook assumes weekly engagement and neat stage progression. Most real products aren't shaped like that. This is how to design lifecycle for products used once a year, once a quarter, or whenever the user happens to need you — where the textbook quietly makes things worse.
The cadence question: how often should you email?
Everyone asks how often to email. Almost nobody answers it properly, because it's the wrong question. Cadence isn't a single number — it's a consequence of five other decisions you probably haven't made yet. Here's the version of the debate that resolves.
Retention economics: proving lifecycle ROI to finance
Lifecycle programs get deprioritised when they can't defend their impact in dollars. The four models that keep the budget — LTV, payback, cohort retention, incrementality — and the four-slide pattern that wins a CFO room.
Abandoned cart emails: what actually works
Cart abandonment is the easiest program to get wrong because the defaults work well enough to hide the problem. Here's the structure that actually moves incremental revenue — timing, sequencing, and the discount policy most teams have backwards.
Segmentation strategy: beyond RFM
RFM is the floor of audience segmentation, not the ceiling. Every program that stops there ends up describing what users already did without ever predicting what they'll do next. Here's the segmentation stack that actually drives lifecycle decisions — and how to build it in Braze without ending up with 400 segments nobody understands.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 54 lifecycle methodologies, 55 MCP tools, native Braze integration. Pay what it's worth.