Every business already has a customer lifecycle. The question is how much of it is designed.
In most systems we look at, automation is heavy at the front and thin everywhere else. Plenty of effort goes into turning a stranger into a buyer. After that, the system goes quiet, or keeps treating the new customer as a prospect. A software client signs an annual contract at the start of the month and, a week later, gets the next email in the prospect nurture inviting them to book a demo. The closed deal lived in the CRM; the nurture lived in the marketing platform; no rule connected the two.
Lifecycle automation is the work of making every stage explicit: who is in it, how they got there, what should happen while they’re there, and what moves them on.
What is lifecycle automation?
Lifecycle automation is automation organized around customer states rather than campaigns. Instead of asking “what emails should we send this month?”, it asks “what should happen when someone becomes a first-time buyer, stops engaging, or reaches their renewal window?”
That makes it broader than email. A stage change might trigger an email, but it might also assign an account manager, create a task, update a segment, pause ads, or suppress someone from a promotion. The messages are the visible part. The state logic underneath decides whether the right person gets them.
The eight stages
Not every business uses all eight, and the boundaries differ between a SaaS company, a service firm and an online store. These are the stages we design for, and what each one needs to get right.
Acquire
The person isn’t in your system yet. Automation here is mostly about making sure the first touch is captured properly: UTM and source data passed through forms, ad audiences synced, and existing customers excluded from acquisition campaigns so you aren’t paying to reach people you already have.
Capture
Someone gives you an email address or fills in a form. The record is created, deduplicated against existing contacts, tagged with a source and placed in the right starting state. Get this wrong and every later stage inherits the error.
Nurture
Not ready to buy yet. Nurture should respond to what the person does, such as pages viewed, products browsed or content downloaded, rather than drip the same five emails to everyone. It also needs an exit: when someone converts or goes cold, nurture stops.
Convert
The moment intent becomes action. For B2B that might be a demo request routed to the right rep within minutes. For ecommerce it’s cart, checkout and browse abandonment, with rules that stop discount-hunters from learning that abandoning a cart earns a coupon.
Onboard
The stage most often missing. A new customer needs a different message than a prospect: how to get started, what to expect, who to contact. For a service business it may be a kickoff checklist and account manager assignment. For a store it’s order confirmation, shipping updates and a first-use guide, with promotional sends held back for a few days.
Retain
Keeping customers active. Replenishment reminders, usage nudges, check-ins before renewal, and the less obvious part: detecting early signs that someone is drifting, such as fewer logins, a longer gap between orders or an unanswered survey.
Expand
Cross-sell, upsell and referral, triggered by fit rather than by calendar. A customer who bought a starter kit and reordered twice is a reasonable candidate for the next tier. Someone with an open support complaint isn’t.
Reactivate
Win-back for customers who’ve lapsed, and re-engagement for subscribers who’ve stopped opening. This stage has a second job: deciding when to stop sending. Contacts who don’t respond to a sunset sequence should be suppressed, which also protects deliverability.
The logic that gets lost
The failures we’re called in for usually trace back to rules nobody wrote down, the ones that sit between flows and decide who belongs where.
- Eligibility. Who qualifies for this stage, based on which data?
- Exclusion. Who should never receive this, even if they technically qualify?
- Priority. If someone is in two journeys at once, which wins?
- Timing. How long after an event, and what happens on weekends, holidays or during a sale?
- Exit. What removes someone, and what happens to messages already queued?
On Klaviyo, much of this lives in trigger filters, flow filters, segment definitions and the metrics coming from your store. On HubSpot, it sits in lifecycle stages, lists, workflow enrollment and suppression settings. We document it outside the platform as well, so the logic survives the next person who edits a flow.
Not sure which stages you're missing?
We'll map your current journeys against these eight stages and show where customers fall into silence or get the wrong message.
Where we usually start
Rarely with all eight. We map the current lifecycle first: the states your data can actually identify, the events your systems send, and the journeys already running. That usually reveals one or two stages doing most of the damage. Often it’s onboarding (nothing happens after purchase) or reactivation (nobody is ever removed from the list).
From there, the build follows the same path as any of our projects. Define states and rules, implement in the platform, test with real scenarios including people who belong in two journeys at once, then measure and adjust. If the underlying data is unreliable, we’ll say so before building on it, and a CRM audit may be the better first step.
For ecommerce brands, our ecommerce solution page and Klaviyo page go into platform detail. For B2B and service businesses, see B2B CRM. Detailed email program design is covered under email marketing automation.
Pricing
Lifecycle automation starts from $2,500. That typically covers mapping the current lifecycle and building or rebuilding the journeys for a small number of priority stages on one platform.
Scope grows with the number of stages, how many platforms share the journey (a CRM, a marketing platform and a store, for example), the condition of the event data, and how much existing automation has to be untangled first. See pricing for all services.
How is lifecycle automation different from email marketing automation?
Lifecycle automation defines the states and rules that move customers through their relationship with you. Email automation is one of the outputs. A lifecycle change might send an email, but it might also assign an owner, update a segment or stop a campaign. We often do both together.
Do we need all eight stages automated?
No. A business with one-off purchases may have little to do at the expansion stage. A service firm may not need browse abandonment. We build the stages that match how you make and keep customers.
What if our data can’t tell which stage someone is in?
Then that’s the first job. If the store never sends a refund event, or the CRM has no reliable renewal date, a retention or win-back journey would be guessing. We’d fix the event or field first, sometimes through an integration, and build the journey once the system can see the state change.
How do you measure whether it’s working?
Each stage gets a measure tied to its job: onboarding by first meaningful action, retention by repeat purchase or renewal, reactivation by returning customers rather than opens. We agree these before building.