Nurture Sequence Strategies: Triggers, Exits, Tools
How to design a nurture sequence: entry rules, behavior branching, exit rules, flow collisions, and which tools run each strategy, with USD prices.
A nurture sequence is a set of emails plus the rules that decide who enters, what moves each lead forward, and when the lead stops, built for people who are interested but not ready to buy. The strategy lives in those rules rather than in the copy. You pick an engine (a fixed time-based drip, behavior-triggered steps, or a score), you give every flow an exit, and you stop your nurture flows from colliding with your trial, onboarding and sales flows. Below are the trade-offs of each choice, two complete sequence maps, how to decide a lead is done, a way to measure the flow with counts, and which tools support which strategy, with USD list prices at 5,000, 10,000 and 25,000 contacts.
This page is about the rules that govern any lead flow. The trial window has its own page in trial conversion sequences, the flow after signup is in onboarding email sequences, the first few emails are in welcome sequence best practices, and outbound to cold prospects is in sales email sequences.
Entry rules: who belongs in the flow and who must be kept out
An entry rule has three parts, and most flows are written with only the first. The trigger is the thing the lead did, such as downloading a guide, attending a webinar, starting a signup and not finishing it, or letting a trial lapse without paying. The inclusion test is what must be true about the person at that moment, for example that consent is recorded and the address has not bounced. The exclusion list is everyone who must not enter even though they fired the trigger.
The exclusion list is where flows go wrong. At a minimum keep out current customers, anyone in an active trial (that flow takes priority), anyone a sales rep is already working, anyone who unsubscribed, and anyone who entered this same track recently. Decide re-entry explicitly: a lead who finishes the track and downloads a second guide a few months later is either a new entry into a different track or a person who waits out a re-entry window you chose in advance. If you leave it undecided, your tool will pick a default for you and you will find out from a complaint.
Give each major topic its own track instead of pouring every lead into one general flow. The guide someone downloaded tells you what problem they have, and a track that continues that subject is the cheapest personalization available. Write the entry reason into a field on the contact at the moment of entry, because you will need it later to split your measurements by source.
Time-based, behavior-triggered or score-triggered: choosing the engine
The engine is the rule that moves a lead from one email to the next. There are three, and each one fails in a particular way.
| Engine | What moves a lead forward | Works when | Fails when |
|---|---|---|---|
| Time-based drip | A fixed wait after the previous email | The content is a course that must be read in order, or you have no signals beyond the signup | The lead is ready on day 3 and still receives the day-10 lesson, or has already bought and keeps receiving mail |
| Behavior-triggered | An action (a visit to a pricing page, a click on a product link, a product event) or the absence of one after a wait | You can capture the behavior reliably and match it to the right person | Events arrive late, twice or under the wrong identity, or so few leads trigger anything that the branch never fires |
| Score-triggered | Points add up across behaviors, and a threshold changes the track or alerts a person | Several weak signals must be combined and a sales team needs a short list to call | The weights were guessed, nothing decays, and the threshold is never checked against real buyers |
Most teams should build in this order. Start with a time-based spine, because it is simple and every tool can do it. Then add behavior as skips and exits: skip the email that explains a feature the lead already used, and exit when the lead books a call. Add a score last, and only to decide when to alert a human.
Be selective about which behavior you branch on. Email opens are a poor trigger because some mail clients load images automatically, so an open may not be a person. Clicks on your own links, visits to your own pages, product events and replies are better, because each is an action you can name. A branch on "visited the pricing page in the last seven days" is explainable to a colleague in one sentence; a branch on "engagement score above 40" is not, until someone shows where 40 came from.
If you build a score, derive it from your own past. Take the leads who became customers and list what they did before buying: which pages, which emails, how many replies. Weight the behaviors that show up before purchases, make points expire after a period of inactivity, and write down the threshold with the date you set it. A score without decay turns every old lead into a hot one, and a threshold nobody has revisited drifts away from how people buy.
Content jobs by stage
Each email in a nurture flow should have one job that matches what the lead currently believes. A useful test is to name the job in a few words before writing; if you cannot, the email is a newsletter item that happens to be in a flow.
| Where the lead is | Job of the email | What to leave out |
|---|---|---|
| Knows the problem, not the fix | Help them see the cost of the status quo and the shape of a solution, with a worked example from their own role | Your product name in the headline, and feature lists |
| Comparing approaches | Lay out the options honestly, including doing nothing or building in-house, and say who each option suits | Claims about competitors you cannot source |
| Considering your product | Answer the objection that stops most people: price, effort to switch, security review, who else on the team must agree | Urgency with no date behind it |
| Gone quiet | Ask what changed, or offer one useful link and a way to say "not now" | A guilt-trip subject line |
Worked map 1: a behavior-branched track for people who downloaded a guide
The scenario is a B2B software company that gives away a guide in exchange for an address and wants to find the minority of downloaders who are evaluating tools. The track has a time spine of about three weeks, one behavior branch and three ways out. The delays are starting points to adjust to your audience, not tested values.
| Step | Trigger or delay | Content job | Exit rule |
|---|---|---|---|
| 1. Delivery | Immediately on form submit, if consent is recorded and the contact is not a customer or in a trial | Deliver the guide and ask one question in plain text: what are you trying to solve? Replies go to a real inbox | Becomes a customer, unsubscribes, or replies (a person takes over and the flow pauses) |
| 2. Second look | 2 days after step 1, only if the guide link was not clicked | Resend the guide with a different promise in the subject; if the link was clicked, skip to step 3 | As step 1 |
| 3. One idea applied | 5 days after step 1 | Take the guide's main idea and apply it to a worked example in the lead's role | As step 1 |
| 4. Branch check | 7 days after step 1: has the contact visited the pricing page or clicked a product link since entry? | No email. Yes goes to step 5a, no goes to step 5b | None |
| 5a. Fit and next step | Immediately after the branch, for the yes group | Say which plan or setup fits their situation, what switching takes, and offer a call | Books a call, so the lead is handed to sales and the track ends |
| 5b. Comparison | 3 days after the branch, for the no group | Lay out the ways teams solve this problem, with the trade-offs of each, and where your product sits | Clicks any product link, so the lead moves to step 5a |
| 6. Objection | 10 days after the branch, if still in the track | Answer the question that most often stops a switch, using what your replies in step 1 told you | As step 1 |
| 7. Choose a lane | 7 days after step 6 | Two links: talk to someone, or "not now, send me occasional updates" | The first link hands off to sales; the second, or no click after 7 days, moves the lead to map 2 |
Step 4 is where this track pays off or does not, so test it first. Send a test contact through a pricing-page visit and through none, and confirm both paths. Then check the step 5b exit by clicking a product link from inside the email; people forget that the exit conditions need testing as much as the entry.
Worked map 2: a long-cycle track for leads who are not ready yet
Many leads will not decide in three weeks, and some have a budget cycle that runs for months. A long-cycle track is slow on purpose, so the cadence is a promise to the lead: one email a month, stated in the first message. Because each email arrives after the lead has forgotten you, it must carry its own context instead of assuming they remember the last one.
| Step | Trigger or delay | Content job | Exit rule |
|---|---|---|---|
| 1. Reset | On entry from map 1, or when a contact has had no activity for a window you set | Say what they will get (one email a month) and how to stop; tag the topic they cared about earlier | Unsubscribes, becomes a customer, or starts a trial |
| 2. Teach | 30 days after step 1 | A piece on their topic that is useful without your product | As step 1 |
| 3. Ask | 30 days later | A short question: what changed on your side, such as team size, tools or budget? A person reads every reply | A reply that shows buying intent hands the lead to sales |
| 4. Relevant news | 30 days later | A product update, sent only to leads whose topic tag matches it | As step 1 |
| 5. Teach again | 30 days later | A checklist or comparison on their topic | As step 1 |
| Pull-back | At any point: the lead visits the pricing page or clicks a product link | Pause this track and re-enter map 1 at step 5a | The lead leaves map 2 while map 1 runs |
| 6. Stay or go | 30 days after step 5, if no activity since step 1 | One question: do you want to keep hearing from us? One link to stay | No click within 14 days sets the status to dormant and ends the track |
Cadence: let attention set the spacing, and spend it where the signal is
There is no cadence that suits every audience, so set it from two observations: how fast your own leads tend to act after a first touch, and how many of your recent sends went unopened and unclicked. Map 1 is dense at the start because a fresh lead is paying attention, and it widens as attention fades. Map 2 is monthly because the goal is to stay known, not to persuade.
Two cadence rules prevent most problems. First, bind the spacing to the engine: in a behavior-triggered flow a click should speed the next step up, while silence should slow it down, never the reverse. Second, cap the total across flows rather than per flow, because a lead who is in two tracks feels the sum of both. That cap is part of the collision rules further down, and it matters more than the interval inside any single sequence.
Re-engagement is a separate flow with its own entry rule
Nurture is for leads who have not bought. Re-engagement is for people who used to respond and stopped: subscribers who have not clicked for a long stretch, trial users who vanished, or customers who went inactive. Keep it out of the nurture track, because the question it asks is different. Nurture asks "are you ready?"; re-engagement asks "are you still here?"
Define the entry as a window with no clicks, no visits and no product activity, and make the window at least as long as several of your normal sends, otherwise you will chase people who are only on a slow cadence. A short flow is enough: an honest check-in with one useful link, a preference message that lets the person choose a topic or a lower frequency, and a final notice that you will stop sending unless they click. Any click returns the contact to the active segment. No click after the final notice ends marketing mail to that address.
This flow has a cost reason as well as a courtesy one. In tools that bill by contacts, subscribers or profiles, people who left long ago still count against your plan, and they dilute every count you report. Sunsetting them keeps both the bill and the measurements honest.
When two flows want the same lead: collisions and suppression
The first nurture flow you build works alone. The third one collides with the others, and the lead notices before you do. A person can be a downloader in map 1, a trial user, the contact on an open deal and a dormant subscriber at once, and each flow believes it owns them. The fix is a priority order that every flow checks, backed by one status field that all flows read and write.
| Situation | Rule |
|---|---|
| A nurture lead starts a trial | Exit nurture. The trial flow owns the contact. If the trial ends unpaid, enter the long-cycle track, not map 1 again |
| A nurture lead pays | Exit every nurture track at once, and re-test "is this a customer?" immediately before each send, not only at entry |
| A rep opens a deal or conversation | Suppress nurture while the deal is open. If it closes lost, wait out a period you chose, then enter the long-cycle track |
| The lead fires a second track's trigger | Keep one active track. Record the new interest as a tag so the next email can use it, and do not start a second sequence in parallel |
| The contact is in re-engagement | Pause every other marketing flow until the contact clicks or the final notice passes |
| Billing, security or account notices | Never suppressed by a nurture cap, never counted toward it, and kept apart from marketing unsubscribes |
Implement the order with a lifecycle status field such as lead, nurture, long-cycle, trial, customer, sales-owned and dormant. Changing the field is how a flow ends, and every flow's entry rule reads it. For the global cap, store a "last marketing email sent" date on the contact and add a condition ahead of each send: if it is more recent than your minimum gap, wait. Some tools offer this natively; for example, Brevo's help center lists marketing pressure management among its Professional plan features. Elsewhere the date field does the same job.
How to decide a lead is done
A flow that never ends is a newsletter with extra steps. Define the ways out before you build, and record each one on the contact with a reason and a date.
- Converted. The lead started a trial or paid. This is an exit from nurture and an entry into the next flow.
- Handed to sales. A person accepted the lead. Count a handoff only after the rep takes it; a score crossing a threshold is an alert, not an acceptance.
- Disqualified. The lead is a student, a competitor or the wrong size of company. Mark them so no track picks them up again.
- Opted out. The lead unsubscribed. This outranks every other state.
- Dormant. The lead went through the long-cycle track and ignored the stay-or-go email. Keep the record, stop the marketing mail.
Finishing the last email of a track is not an end state. A lead who completes map 1 without acting is moved to map 2, and one who completes map 2 without acting becomes dormant. Treat "completed with no action" as a status you can count, since a large number there tells you the content or the entry rule needs work.
Marking leads done also affects what you pay. Customer.io's billing documentation says a profile that exists at any point in a billing period counts toward that month's bill even if you delete it, so a clean-up in the middle of a month does not lower that month's invoice.
Measure the flow with counts you can define
You do not need a benchmark from anyone else to know whether a flow works. You need a few counts defined precisely enough that two people would get the same number, tracked per entry cohort (everyone who entered in March, for example) so a slow lead is not credited to the wrong month.
| Count | Definition | What a surprise tells you |
|---|---|---|
| Entered | Contacts that passed the entry rule in the period, split by the entry-reason field | A sudden jump or drop usually means the trigger or the exclusion list changed, not demand |
| Exited by reason | Converted, handed to sales, disqualified, opted out, dormant, suppressed by another flow, completed with no action | Many exits "suppressed by another flow" mean two flows are competing for the same people |
| Still active | Contacts inside the flow today | Entered should equal the sum of exits plus still active; if it does not, some contacts are leaking out with no recorded reason |
| Converted | Entered contacts that reached your conversion event within a window you set before looking at results | Compare cohorts that had the same window; a recent cohort will look worse only because it has had less time |
| Time to exit | Median days from entry to each exit reason | If converted leads exit long after the last email, the flow is not what moved them |
Two cautions keep these numbers honest. Leads who were already keen will convert with or without your emails, so a rising converted count alone does not prove the flow caused it. If you have enough volume, withhold a random slice of entrants from the flow, fix its size before you start, and compare converted counts between the two groups; if you do not, say plainly that your count is a trend and not a measured effect. And change one thing at a time, such as a delay, a branch condition or one email's job, so a movement can be traced to a change.
Which tools support which strategy, with prices at 5,000, 10,000 and 25,000 contacts
Group tools by what they know about a lead. Event-driven tools know what a person did in your product, so behavior branches and product-event exits are natural. CRM-linked tools know where the lead sits in a sales pipeline, so handoffs and score alerts are natural. List-based tools know subscribers, tags and email clicks, which is enough for time-based and click-based tracks. Prices below were read from each vendor's pricing page on 7 October 2026; the billing units differ (subscribers, profiles, users, contacts, emails sent), so compare them only after counting your own list in the same unit.
| Tool | Type | 5,000 contacts | 10,000 contacts | 25,000 contacts |
|---|---|---|---|---|
| Loops (subscribers) | Event-driven | $48/mo at 4,788 subscribers | $99/mo at 9,998 subscribers | $198/mo at 24,339 subscribers |
| Customer.io Essentials (profiles) | Event-driven | $100/mo, billed monthly | $145/mo, billed monthly | Not listed; $235/mo at 20,000 and $325/mo at 30,000 |
| Userlist Basic (users) | Event-driven | $149/mo (tier covers up to 10,000 users) | $149/mo | Not listed; $229/mo up to 18,000 users and $369/mo up to 32,000 |
| Encharge Growth (subscribers) | Event-driven | $179/mo | $249/mo | $389/mo |
| ActiveCampaign Plus (contacts) | CRM-linked | $145/mo | $189/mo | $389/mo |
| HubSpot Marketing Hub (seats) | CRM-linked | Priced per seat rather than per contact: Starter from $7/mo, Professional from $800/mo, Enterprise from $3,600/mo | ||
| MailerLite Comfort (subscribers) | List-based | $49/mo | $89/mo | $179/mo |
| Kit Creator (subscribers) | List-based | $75/mo | $116/mo | $166/mo |
| Brevo (emails sent) | List-based | Priced by monthly emails, not contacts: Standard starts at $18/mo for 5,000 emails a month | ||
Event-driven: Customer.io, Loops, Userlist, Encharge
Customer.io's Essentials plan includes a visual workflow builder, and its documentation lists custom events among the data you can send in. The cost to plan for is that every lead is a profile, including the ones that have gone dormant, so build the sunset step from map 2 into the flow rather than leaving it for later.
Loops starts a flow from four trigger types: contact added, contact updated, contact added to a list, or an event received through its API, an integration or a form. Its branching docs say each branch is an audience filter on contact properties, and a contact who matches no filter leaves the workflow, which is handy for exits but means every condition you branch on must exist as a contact property. Loops' free plan sends to the 1,000 newest contacts only (up to 4,000 sends in any rolling 30 days), so a long-cycle track that reaches older leads needs a paid plan.
Userlist segments both users and companies, which suits a B2B nurture where the buyer is a team. Its Basic plan lists 20 custom events and Professional lists unlimited, and Professional also adds A/B split testing and conversion goals, at $349 a month for up to 10,000 users. Conversion goals are a ready-made version of the "converted" exit in the measurement section. See Userlist vs Customer.io for a direct comparison.
Encharge's pricing page lists behavior-based emails, API events with event-based segmentation, and lead scoring. Its Premium plan, which also adds HubSpot, Salesforce and transactional email, lists $399 a month for up to 10,000 subscribers.
CRM-linked: ActiveCampaign and HubSpot
ActiveCampaign's pricing page lists a standard CRM and marketing automation from Starter, and limits Starter to 5 actions per automation. Map 1 has seven emails and a branch, so it cannot fit in five actions, which puts it on Plus at $189 a month for 10,000 contacts. ActiveCampaign states its starting prices as billed annually.
HubSpot's Marketing Hub page lists email automation as 1 automated action on Free, up to 10 on Starter and unlimited on Professional, and ties up to 1,000 workflows with behavioral events and predictive lead scoring to Enterprise. If you want a score to trigger a handoff to a rep inside HubSpot, that is a purchase at Enterprise's $3,600 a month starting price, not a feature of the cheaper tiers.
List-based: Brevo, MailerLite and Kit
Brevo's help center says the Free plan includes marketing automation for up to 2,000 contacts, while Standard, which starts at $18 a month, has automation for unlimited contacts. Brevo prices by emails sent, so the arithmetic is sends rather than leads: 1,000 leads in map 1 at up to 4 emails each in a month is 4,000 sends, inside the 5,000-email tier that the starting price covers. Contact scoring appears on its $499-a-month Professional plan.
MailerLite's Free plan allows up to 250 subscribers and 2,500 emails a month. At up to 10K subscribers its page lists Comfort at $89 and Power at $129 a month, and Comfort's allowance is 10 times the ceiling of your subscriber tier: 10,000 subscribers x 10 = 100,000 emails a month, enough for 10,000 leads each receiving seven emails (70,000 sends).
Kit's Free plan covers up to 10,000 subscribers with broadcasts, tagging and segmentation, but visual automations and sequences begin on the Creator plan, which lists $116 a month at 10,000 subscribers. Kit describes the visual automation builder as building funnels on subscriber behavior with split paths.
Which to choose
- Choose Loops if a small team drives the flow from product and form events and the branches can be expressed as contact properties.
- Choose Customer.io if events are the backbone of the whole lifecycle and several flows must coexist under one status model.
- Choose Userlist if the unit of nurture is the account and you need company-level segments.
- Choose Encharge if you want behavior emails and lead scoring in one SaaS-focused tool with Stripe and CRM integrations.
- Choose ActiveCampaign Plus if a sales team needs the CRM and deal stages next to the sequence.
- Choose HubSpot if your CRM and sales team already work there; budget for Professional or Enterprise before building score-based handoffs.
- Choose Brevo, MailerLite or Kit if the nurture is content-led and moves on time and clicks, such as map 2 and the re-engagement flow.
The best pick for the reader this page targets (a small SaaS team with product events and a list near 10,000) is Loops. It supports the triggers and property-based branches that maps 1 and 2 need, and its table price of $99 a month at 9,998 subscribers is the lowest in the event-driven group at that size. Before committing to it or any other tool, rebuild the hardest branch (the pricing-page check at step 4 of map 1) in a free trial; if it needs data your tool cannot hold, move one row down the list. Our tool guide for SaaS teams doing lead nurturing goes further into that shortlist.
Frequently asked questions
How long should a nurture sequence run before a lead counts as done?
Run the active track for as long as the lead keeps doing something: clicking, visiting, replying. Then move quiet leads to a slow monthly track, and end that track with an email that asks them to confirm they want to stay. A lead who ignores that last message becomes dormant and leaves your marketing flows. Write the rule down as a number of emails with no click and no visit, and review it after one full cycle.
Do I need lead scoring to run a behavior-based nurture?
No. Two or three plain behaviors, such as a pricing-page visit, a click on a product link or a reply, cover most of what a score would tell you, and they are easier to debug. Add a score only when several weak signals have to be combined before a person at your company is told to act. If you do, check the points against the people who actually bought before trusting the threshold.
Can a list-based tool like Brevo, MailerLite or Kit run these strategies?
Yes for the time-based and click-based parts, which cover the long-cycle track and re-engagement. The gap appears when a branch depends on something that happens in your product or your CRM, because those tools mostly know about subscribers, tags and email clicks. Test your hardest branch before you buy, and if it needs product events, look at the event-driven group.
How is a nurture sequence different from a newsletter?
A newsletter goes to everyone on a schedule you set, and a lead never finishes it. A nurture sequence starts from a specific entry event, changes with what the lead does, and has exit rules that remove the lead when they buy, hand off to sales, or go quiet. Many teams run both and move a lead from the sequence into the newsletter only once the lead has chosen it.