Best Lifecycle Email Marketing Software for SaaS
Customer.io is the best pick in this guide for SaaS teams whose lifecycle email depends on product and billing events. The reason is structural: its workflows start from a single user event, such as a trial start, a usage limit or a failed payment, and its segments update as profile data changes. Its Essentials plan is listed at $100 a month billed monthly, and the 10,000-profile tier is $145 a month. Prices in this guide are the figures each vendor shows on its pricing page as of 7 October 2026.
How SaaS Lifecycle Email Differs From Other Email
A subscription product creates email moments that a newsletter never has. A trial has a clock: it starts on a known date, it ends on a known date, and the messages that matter most sit on either side of that end date. A paying customer has a billing state that changes outside your application. A card can fail overnight, a plan can be downgraded from the billing portal, and a cancellation can be scheduled for the end of the month without any login at all. If your lifecycle tool only sees what happens inside your product, it misses the events that most directly affect revenue.
Accounts add a second layer. Many SaaS products sell to a company but are used by several people inside it. An admin who manages billing needs a different message from an end user who has never logged in twice. A team that adds its fifth member is a different expansion signal from one person who keeps hitting a usage limit. Tools differ a lot in whether they model users and accounts separately, and that difference becomes expensive to fix once a year of campaigns is built on the wrong identity.
Payment recovery is a time-critical flow with its own rules. A dunning sequence is only useful if it fires when the payment fails, reaches the right person, links to a card-update page, and stops the moment the card is updated. If the lifecycle tool learns about a failed payment a day late, or cannot stop the sequence once the customer pays, the flow causes harm: people receive a warning after they have already fixed the problem. The same risk applies to trial conversion emails that keep arriving after the user has converted.
Consent and suppression also work differently across transactional and lifecycle mail. A password reset or an invoice is part of the service. A message about a new feature is marketing. Your lifecycle tool should keep those streams apart, so that an unsubscribe from marketing does not silence required account messages, and so that a bounce or complaint is respected everywhere it matters. For SaaS, this is a selection criterion rather than an afterthought.
Deliverability sits underneath all of this. Sending to addresses that have gone stale, or that were collected without a clear consent source, damages sender reputation for every stream a company sends. List verification services such as ZeroBounce, NeverBounce and Kickbox check addresses before you import them and can flag risky ones before they reach a trial or payment flow. They do not replace a lifecycle tool, but they reduce the bounce rate that lifecycle tools have to absorb. Check each verification vendor's pricing page directly, since this guide does not list their prices.
The rest of this guide evaluates ten platforms against those realities. It covers where each one fits, what it costs at realistic list sizes as each vendor lists them, where it falls short, and how to move your flows into it without losing suppression history or breaking billing-triggered sequences. You can also compare the wider set of email tools for SaaS on the main comparison page.
Lifecycle Email Platforms Compared
| Tool | Best for | Entry price (plan and billing) | Key limitation |
|---|---|---|---|
| Customer.io | Lifecycle emails triggered by product and billing events | Essentials from $100/mo, billed monthly; $145/mo at 10,000 profiles | No annual price listed for Essentials; cost rises with profile count |
| Drip | Workflow-led email for growing lists with unlimited sends | $39/mo for 1 to 2,500 people, billed monthly | No ongoing free plan; 14-day trial only |
| ActiveCampaign | Teams that want email, automation and a CRM in one product | Starter from $15/mo at 1,000 contacts (same monthly and annual figure) | Prices scale with contacts; advanced segmentation starts at Pro |
| HubSpot Marketing Hub | Companies already running their CRM in HubSpot | Free tools; Starter from $7/mo; Professional from $800/mo | Large jump between tiers; per-seat model |
| Klaviyo | Profile-rich lifecycle programs with predictive features | Free for 250 active profiles; email plan from $20/mo for 500 profiles | Some defaults assume retail patterns; SMS is priced separately |
| Loops | Early-stage teams that want lifecycle and transactional mail in one tool | Free for up to 4,000 sends in a rolling 30 days; Growing Audience at $99/mo | Free plan carries a Loops footer and reaches only the 1,000 newest contacts |
| Userlist | B2B SaaS where journeys run at company level | Basic at $149/mo for up to 10,000 users; Professional at $349/mo at the same size | Starts high for small teams; little value for consumer products |
| Intercom | Support conversations and lifecycle messages in one inbox | Essential at $19 per seat/mo, billed annually | Email is one part of a wider suite; AI outcome charges are usage-based |
| Braze | Enterprise programs that need real-time orchestration | Pricing on request; free trial available | No public price; implementation takes significant effort |
| Iterable | Large-volume enterprise lifecycle programs | Pricing on request through a demo; no free plan | Demo-led buying; more platform than an early-stage team needs |
Map Your Events Before You Compare Tools
Most lifecycle email projects go wrong before the first email is written, because the events that should trigger them were never defined. Write the event list first, give each event one owner, and name one system as its source of truth. Only then compare platforms. The right tool is the one that receives the events you already produce, in the form you already produce them, without a rebuild on your side.
For a typical subscription SaaS product, the event list falls into five groups. Each group feeds a flow you will eventually build, and each group usually comes from a different system.
- Acquisition and signup: account_created, email_verified, source_campaign_set, invite_accepted. These drive welcome sequences and first-session flows. They almost always come from the application.
- Activation: setup_step_completed, core_action_performed, integration_connected, teammate_invited. These decide whether a user moves from onboarding into engagement content. They also come from the application, and they are the events most likely to change when the product changes.
- Trial and conversion: trial_started, trial_ending_in_7_days, pricing_page_viewed, plan_limit_reached, subscription_started. These drive trial conversion and expansion. Trial dates usually come from billing, while page views come from the site.
- Billing: payment_failed, payment_recovered, plan_changed, invoice_paid, subscription_cancelled. These drive dunning, plan-change confirmations and win-back. They should come from the billing system, never from a guess based on product usage.
- Engagement risk: no_login_for_14_days, feature_usage_dropped, support_ticket_opened, cancellation_page_viewed. These drive retention and re-activation. They combine product data with support or billing data, which is why identity matters so much.
Billing events deserve special attention because they often come from a different system than product events. Stripe processes card payments and subscriptions and emits events about them. Its standard card processing is priced per transaction, with no monthly platform fee on the standard pricing page. Paddle works as a merchant of record and is also priced per transaction, with no monthly platform fee. Neither is a lifecycle email tool, but both are common sources of the events that dunning and trial flows depend on. Decide early which system owns each billing state, so that the email tool never disagrees with billing about whether a customer is paying.
Identity is the other decision. A user ID from your application and a customer ID from billing are not automatically the same thing, and an account ID may group several users. Write down which identifier each event carries, and confirm that your lifecycle tool can join them. If it cannot, you will end up sending a dunning email to someone who is not the billing contact for the account, and that mistake is hard to undo once it has reached a customer's inbox.
Finally, decide what counts as a state change. A trial that is extended by a sales conversation is not the same event as a trial that expires. A plan that is downgraded at the end of a period is not the same as a plan that is cancelled immediately. These distinctions should be explicit in your event names, because a lifecycle flow that treats them as the same will send the wrong message at the most sensitive point in the relationship.
Each Platform for SaaS Lifecycle Email
What each tool does well for SaaS teams, where it falls short, what it costs as listed, and where to find its pricing page.
Customer.io
Best pick for product-event lifecycle emails
Customer.io is built around the idea that a customer's behavior in your product should decide which message comes next. For SaaS, that matters most in onboarding and trial conversion. A user who creates a first project, invites a teammate or hits a usage limit can enter a workflow at that moment, and the workflow can branch on what the user does next. The profile is the unit of work, and segments update as attributes and events change. That consistency is the product's central strength.
The Essentials plan is listed with a visual workflow builder, email and community support, and basic data integrations, which covers what most teams need to build onboarding, trial, expansion and recovery flows. The AI Agent core skills are part of the same plan, while higher agent limits and premium support belong to the Premium tier. A team should treat the AI features as an extra to evaluate after the basic flows work. The core requirement is still a well-defined event schema, because a clean schema makes every later workflow easier to trust.
Where it falls short: the Essentials price is listed monthly only, with no annual figure on the pricing page, and the profile count that goes with the $100 base price is not stated. The profile-based tiers are the numbers to plan around. They start at $145 a month for 10,000 profiles, then rise to $235 at 20,000, $325 at 30,000, $415 at 40,000 and $505 or more at 50,000 and above. A list that grows quickly will push the bill up in steps, so model growth before you commit. Customer.io is also not a CRM. If your sales team needs deal pipelines in the same system, you will need another tool alongside it.
Pricing: Essentials from $100 a month billed monthly, with profile tiers from $145 a month at 10,000 profiles. Premium is priced on custom profile volume. Eligible early-stage companies that have raised under $10 million can receive 12 months free through the Startup Program, subject to the program's rules. Pricing page: customer.io/pricing.
Drip
Best for workflow-led email with a predictable monthly cost
Drip prices by the number of people on your list, and the listed tiers from 1 to 40,000 people include unlimited email sends up to the middle of the range. For a SaaS team with a steady list and frequent campaigns, that arrangement is practical: the cost is set by audience size, and sending more does not add to the bill on those tiers. The product includes dynamic segments, onsite campaigns and workflows, which covers the common SaaS need for onboarding branches and trial reminders.
Drip's limits are specific. The listed tiers allow up to 50 workflows, so a team that builds a separate flow for every segment and every plan will reach that ceiling. Plan a naming and consolidation scheme from the start. The jump between people-based tiers is also large at the upper end. The 37,501 to 40,000 tier is listed at $609 a month with 480,000 email sends, and the 45,001 to 50,000 tier at $699 with 600,000 sends. At those sizes, check the included sends against your real volume, because the unlimited-send promise does not apply to every tier.
Drip suits a team whose events are simple and reliable. Trial start, activation milestone, plan change and cancellation translate neatly into tags and events. If your flows depend on dozens of granular product events that change every week, consider whether a more event-native tool will be less work to maintain. The 14-day trial requires no credit card, but there is no ongoing free plan on the pricing page, so budget for a paid tier from the start.
Pricing: $39 a month for 1 to 2,500 people, $49 for 2,501 to 3,000, $89 for 4,501 to 5,000, $154 for 9,001 to 10,000, and $369 for 22,501 to 25,000, all billed monthly with unlimited email sends on those tiers. Pricing page: drip.com/pricing.
ActiveCampaign
Best for teams that want email, automation and a CRM in one place
ActiveCampaign fits when lifecycle marketing and sales follow-up are the same job. A trial user who needs a personal call, a free account that has gone quiet for a month, and a paying customer who may expand all sit in one contact record. The Starter plan includes email marketing, marketing automation and standard CRM and ecommerce integrations. That is enough to run onboarding and trial sequences without a separate CRM.
The higher tiers add segmentation depth, which matters for SaaS expansion. Plus adds standard segmentation and landing pages, Pro adds advanced segmentation, and Enterprise adds premium segmentation and a dedicated account team. If your expansion emails depend on combining product usage with pipeline stage or deal value, plan on Pro or above.
Where it falls short: prices are set by contact count, and the listed starting prices apply at 1,000 contacts. The listing does not show figures at larger sizes, so a team with 5,000 or more contacts will need the pricing page or a quote. ActiveCampaign also has a learning curve. Its strength is that many features sit in one place, and that is also why new users can find the builder crowded. A free trial is available, but the listing does not state how long it runs.
Pricing: Starter from $15 a month, Plus from $49, Pro from $79 and Enterprise from $145, each starting at 1,000 contacts, with the same monthly and annual figure listed. Pricing page: activecampaign.com/pricing.
HubSpot Marketing Hub
Best for companies already running their CRM in HubSpot
HubSpot's main advantage for lifecycle email is the shared contact record. Form submissions, email interactions, deal changes, support tickets and page visits attach to one contact, so a lifecycle workflow can respond to what sales and support have already done. A workflow can hold a nurture email for a contact with an open deal, and a retention email can refer to a recent support case. For a SaaS company whose sales team works trials by hand, that shared history is the reason to choose HubSpot.
The Marketing Hub has a free set of tools, so a team can start without a paid plan. The paid tiers are far apart: Starter is listed at $7 a month, Professional at $800 a month and Enterprise at $3,600 a month, under a per-seat model. Model the Professional jump explicitly before you commit, because the move from Starter to Professional is a change of scale, not a small upgrade. Advanced workflow features are where most teams hit that step.
HubSpot also brings complexity. A combined CRM, service and marketing suite has more settings than a dedicated lifecycle email tool, and most of the value depends on the CRM being used consistently across the whole team. If sales and marketing do not share a process, the shared record becomes a source of conflicting data rather than a benefit.
Pricing: free Marketing Hub tools, Starter from $7 a month, Professional from $800 a month and Enterprise from $3,600 a month. Pricing page: hubspot.com/pricing/marketing.
Klaviyo
Best for data-heavy lifecycle programs that use predictive signals
Klaviyo was built for profile-rich marketing, and that model carries over to SaaS when your team wants product events, billing data and predictive signals on one profile. Flows can be triggered by profile properties, events and segment membership. The product's predictive features are described by the vendor as forecasts for metrics such as churn risk and purchase likelihood. For a SaaS team with a large event stream and someone who can maintain the data model, that depth can pay off.
The free plan covers 250 active profiles and 500 email sends a month, with $5 of mobile messages included. That is workable for prototyping flows against a real list. The paid email plan is listed at $20 a month for 500 profiles, $30 for 1,000, $60 for 2,500, $100 for 5,000, $150 for 10,000 and $400 for 25,000. SMS plans are priced separately, and those figures should be taken from the pricing page.
Where it falls short: the product has a retail heritage, and some defaults assume e-commerce patterns such as product catalogs and purchase events. A SaaS team may need to rewrite templates and flows to fit subscription events. Costs also track active profiles, so a broad list of trial sign-ups who never activate will push the bill up. Clean out dormant profiles on a schedule, and keep the trial-to-active rule explicit so the count stays honest.
Pricing: free plan for 250 active profiles and 500 sends a month; email plan from $20 a month for 500 profiles, rising to $400 a month for 25,000 profiles, as listed monthly. Pricing page: klaviyo.com/pricing.
Loops
Best for early-stage teams that want lifecycle and transactional sending in one tool
Loops is a lean option for a small SaaS team that needs onboarding emails, product updates and transactional messages without a large platform. The free plan includes unlimited contacts, with up to 4,000 sends in any rolling 30 days to the 1,000 newest contacts, and a rate of 10 emails per second. The paid Growing Audience plan, listed at $99 a month, includes unlimited sends to subscribers and transactional sends to users outside your audience. For a product that sends account mail to people who are not on the marketing list, that combination matters.
The free plan has clear limits. It adds a Loops footer to emails, caps the rolling send volume, and reaches only the 1,000 newest contacts. A team with more than 1,000 active contacts will hit those limits quickly, so the free plan is a starting point for a new product rather than a long-term home. Loops also offers a smaller set of workflow features than the enterprise tools in this guide. That suits a team that wants a few well-built flows rather than a large canvas.
Setup is short when your events are simple. Send signup, trial and plan events from your application and a billing webhook, build onboarding and trial flows, and add a dunning flow once the product takes real subscription payments. Keep transactional templates in a separate place from marketing templates, so that a marketing unsubscribe is never applied to account mail by mistake.
Pricing: free plan with up to 4,000 sends in a rolling 30 days; Growing Audience plan at $99 a month with unlimited sends to subscribers and transactional sends to users outside your audience. Pricing page: loops.so/pricing.
Userlist
Best for B2B SaaS where journeys run at company level
Userlist is built for B2B products where the buyer is a company and the user is one of several people inside it. Its segments cover both users and companies, so a lifecycle flow can respond to an account-level signal, such as a team reaching a seat threshold, while another flow responds to one person's onboarding progress. For a team selling to organizations, that two-level model matches the way accounts actually grow.
The Basic plan includes marketing and lifecycle email, in-app messages, and segments for users and companies. The Professional plan adds A/B split testing, conversion goals and advanced workflow features. The Enterprise plan has custom message limits. Role-based messaging, such as separate emails for billing admins and for end users, is a practical use case, and it is the kind of routing a B2B team often builds by hand elsewhere.
Where it falls short: paid plans start high for a small team. The listing gives $149 a month for Basic and $349 a month for Professional, each at up to 10,000 users. If you sell to individuals rather than companies, the account-level features add complexity without adding value, and a consumer or prosumer product is usually better served by a per-profile tool.
Pricing: Basic at $149 a month and Professional at $349 a month, each for up to 10,000 users; Enterprise on request. Pricing page: userlist.com/pricing.
Intercom
Best for teams that want support and lifecycle messages in one inbox
Intercom combines a messenger, a shared inbox, help content and automated messaging. For a SaaS company, the advantage is that lifecycle messages and support conversations share context. A user who opened a ticket about an integration can receive a different onboarding path than a user who did not, and a support agent can see which message the user last received. This matters most when support volume is high and the same people write in during onboarding.
The plans are listed per seat, billed annually. Essential is $19 per seat and includes live chat, a shared inbox and ticketing, pre-built reports, a public help center and basic automation. Advanced is $85 per seat and adds a workflow automation builder, multiple team inboxes and round robin assignment, with 20 free Lite seats. Expert is $132 per seat and adds SSO, HIPAA support, SLAs, multibrand Messenger and Help Center, with 50 free Lite seats. A 14-day trial is available without a credit card.
Where it falls short: Intercom is a messaging suite first and an email tool second. If you need the deepest email-specific controls, a dedicated lifecycle email platform will usually offer more. Usage-based AI outcomes and messaging are charged on top of the seat price, so the total depends on volume as well as headcount. Seat pricing also means a larger team pays more even when the contact list is small.
Pricing: Essential from $19 per seat a month, Advanced from $85 and Expert from $132, each billed annually, plus usage-based AI and messaging charges. Pricing page: intercom.com/pricing.
Braze
Best for enterprise programs that need real-time orchestration
Braze is designed for large customer engagement programs that need decisions made on live user state, across several channels, with a data model that brings together product, billing and third-party data. Its Canvas journey builder supports branching on current attributes and experiment paths. It suits organizations with dedicated lifecycle, data and engineering teams.
For a growing SaaS company, the main question is whether that scale is needed. Braze offers a free trial but no public price, and its pricing page directs buyers to a sales conversation. Implementation takes significant effort: the data model, the event pipeline and the team's workflow all need design before the first campaign. A small team that needs onboarding and dunning running in a few weeks will usually get there faster with a simpler tool.
Pricing: free trial available; pricing on request. Pricing page: braze.com/pricing.
Iterable
Best for large-volume enterprise lifecycle programs
Iterable is aimed at organizations that send large volumes across email and other channels and want one platform for journeys, experiments and messaging. Its positioning is enterprise-scale programs with dedicated operations staff, and buying is handled through a demo rather than a self-serve checkout.
For a SaaS team in the early or growth stage, the trade-off is clear. There is no free plan, no public price, and a setup process that assumes a larger team. Consider Iterable when your lifecycle program is already large, has its own operations function, and needs experimentation and channel features at volume. Before that point, a per-profile or flat-tier tool will almost always cost less to run and maintain.
Pricing: on request through a demo; no free plan listed. Pricing page: iterable.com/pricing.
What Each Platform Costs at Three List Sizes
The figures below are the monthly prices each vendor lists for the plan named, at three list sizes. Where a vendor does not list a price at that size, the cell says so and points to the pricing page. Confirm current figures before you budget.
| Tool and plan basis | 5,000 contacts | 10,000 contacts | 25,000 contacts |
|---|---|---|---|
| Customer.io (Essentials, profile tiers, billed monthly) | Not listed at this size; the 10,000-profile tier starts at $145/mo | $145/mo (Essentials, 10,000 profiles) | Between $235/mo (20,000 profiles) and $325/mo (30,000 profiles); no 25,000 tier listed |
| Drip (people tiers, billed monthly) | $89/mo (4,501 to 5,000 people) | $154/mo (9,001 to 10,000 people) | $369/mo (22,501 to 25,000 people) |
| ActiveCampaign (contact-based plans) | Not listed at this size; see pricing page | Not listed at this size; see pricing page | Not listed at this size; see pricing page |
| Klaviyo (email plan, active profiles, listed monthly) | $100/mo (5,000 profiles) | $150/mo (10,000 profiles) | $400/mo (25,000 profiles) |
| Loops (Growing Audience plan) | $99/mo | $99/mo | $99/mo; check contact limits on the pricing page |
| Userlist (Basic and Professional) | Not listed at this size | $149/mo Basic; $349/mo Professional (up to 10,000 users) | Not listed at this size |
| HubSpot Marketing Hub | Not contact-based on the listing; Starter $7/mo, Professional $800/mo | Same listed tiers | Same listed tiers |
| Intercom (per seat, billed annually) | Depends on seats, not contacts: Essential $19 per seat | Advanced $85 per seat | Expert $132 per seat |
| Braze and Iterable | Pricing on request | Pricing on request | Pricing on request |
Intercom and HubSpot are not priced by list size, so their costs follow the team and the plan instead. Intercom's per-seat prices mean that a team of five on Advanced pays $85 for each seat, billed annually, before any usage-based AI or messaging charges. HubSpot's listed Starter and Professional tiers are the same at any contact count on the listing.
For a list of 10,000 people, Drip's $154 a month and Customer.io's $145 a month for 10,000 profiles are close, while Klaviyo's $150 a month at 10,000 profiles is similar in size. The gap widens at 25,000 contacts, where Drip is listed at $369 and Klaviyo at $400. Those differences matter less than whether a tool models your flows well, but they do matter for budget planning. Calculate the figure for your own list growth over twelve months, not for today's count.
Where the cost is a sum rather than a single price, show the arithmetic. For example, a team that runs Drip's 9,001 to 10,000 tier at $154 a month pays 12 × $154 = $1,848 a year, while the same team on Customer.io's 10,000-profile tier at $145 a month pays 12 × $145 = $1,740 a year. Those are the listed figures only; add any add-ons your flows need before comparing totals.
How to Choose a Lifecycle Email Platform for SaaS
Work through these questions in order. Each one narrows the list before you look at price.
First, decide where the trigger events come from. If most of your lifecycle logic depends on product usage, pick a tool that accepts high-volume event data cleanly and lets you build workflows on individual events. If most of it depends on billing, choose a tool with a clean subscription model and confirm how it receives payment and plan changes. If most of it depends on sales activity, a CRM-connected tool will save more time than any feature list.
Second, decide whether accounts matter more than users. A B2B product where the admin pays and a team uses the product needs company-level segments and role-based routing. A consumer or prosumer product can work with per-person profiles. Choosing the wrong model is expensive, because re-keying a year of journeys from person to account is slow and error-prone.
Third, decide how much of the list is active. Per-profile tools cost more when inactive trial users stay in the list. Clean dormant profiles on a schedule, and confirm that the tool can exclude people who have churned or never activated from paid sends. Flat-tier tools reward a list that is mostly active, but a large dormant list can still push you into a higher tier.
Fourth, decide whether you need transactional and lifecycle sends from one vendor. Loops includes transactional sends to users outside your audience on its paid plan, which suits a team that wants fewer vendors. Keep the streams separate even inside one tool, so a marketing opt-out never stops required account messages.
Fifth, decide how much build effort you can afford. A visual builder with a small set of well-tested flows is faster to launch than a platform that needs an engineer for every branch. Enterprise tools such as Braze and Iterable can repay that effort at high volume, but they are rarely the shortest path for a team of a few people.
Sixth, decide how you will check deliverability before sending. Run candidate lists through a verification service, check the bounce and complaint rates of the first flows, and set a rule for removing addresses that hard-bounce. A lifecycle tool cannot fix a list that was never clean, and a trial flow sent to bad addresses damages the reputation that your password reset and invoice mail depend on.
| If you need | Pick | Because | Starting price as listed |
|---|---|---|---|
| Lifecycle emails fired by product and billing events | Customer.io | Event-triggered workflows and profile segments are the core of the product | $100/mo Essentials, billed monthly |
| Predictable monthly cost with unlimited sends | Drip | Fixed people-based tiers, with unlimited sends on the listed tiers | $39/mo for 1 to 2,500 people |
| Email, automation and a CRM in one tool | ActiveCampaign | Contact records, automations and sales follow-up share one system | $15/mo Starter at 1,000 contacts |
| A CRM you already run in HubSpot | HubSpot Marketing Hub | Workflows can react to deals, tickets and page visits on the same contact | $7/mo Starter |
| Data-rich flows with predictive signals | Klaviyo | Profile data and predictive features are central to the product | Free for 250 active profiles; $20/mo at 500 profiles |
| Early-stage lifecycle plus transactional mail | Loops | Free plan to start, and transactional sends included on the paid plan | Free for up to 4,000 sends in 30 days |
| Journeys that run at company level | Userlist | Company and user segments with role-based routing | $149/mo Basic at up to 10,000 users |
| Support conversations and lifecycle messages in one inbox | Intercom | Messages and tickets share context about the same customer | $19 per seat/mo, billed annually |
| Real-time orchestration at enterprise scale | Braze or Iterable | Built for large programs with dedicated operations teams | Pricing on request |
Setup and Migration Checklist
If you are moving from a spreadsheet, a newsletter tool or an older lifecycle platform, work through these steps in order. Skipping the suppression step is the most common reason a migration causes complaints.
| Step | What to do | Finished when |
|---|---|---|
| 1. Define lifecycle states | Write six to eight states, from visitor to win-back, with one owner per state | Every active user maps to exactly one state |
| 2. List the events | Name each event that moves a user between states, with its payload fields | Each event has a named source system and an identifier |
| 3. Assign event sources | Decide whether product, billing or CRM events own each state. Use a webhook, a native connector or a pipeline tool where the email platform lacks one. Make's Core plan is listed at $10.59 a month billed monthly, or $9 billed annually, for 10,000 credits | Billing owns subscription state, and the product owns usage state |
| 4. Map identities | Join user IDs, account IDs and billing customer IDs in one table | Every billing event resolves to the right person or account |
| 5. Verify the list | Run the addresses through a verification service and remove invalid and high-risk ones | Known-bad addresses are removed before the first send |
| 6. Export suppression data | Export unsubscribes, bounces and complaints with dates and sources from the old system | The suppression file is complete and reviewed |
| 7. Import with consent | Import only contacts with a consent source. Tag each one with that source and import date | No suppressed address is active in the new tool |
| 8. Build three core flows | Onboarding, trial conversion and payment recovery, in that order | Each flow has a trigger, an exit and a stop rule for paying customers |
| 9. Cut over | Pause old sends, switch triggers to the new tool, and keep the old system read-only for a short period | No contact can be in an old flow and a new flow at the same time |
Payment recovery needs its own check during cutover. A customer in a dunning sequence in the old system should not start a new dunning sequence in the new one. Export the state of every open payment failure, import it as a single status, and confirm that the new flow stops when a payment succeeds. This is the part of a migration that is easiest to get wrong and most visible to customers.
Trial flows need the same care. Import trial start and end dates rather than only a status field, so that the new tool can time its messages correctly. A trial that started nine days ago should not receive a "your trial starts now" message after the move. Test the timing rules on a small internal segment before you turn them on for everyone.
Plan the cutover around the calendar as well. Avoid switching during a billing run or a product launch, because a surge of events can make a half-migrated flow visible to customers. Keep a short written log of what was moved, when, and by whom, so that any complaint can be traced to a specific step.
Building Flows That Stay Correct
The difference between a lifecycle program that works and one that annoys customers is usually in the stop rules, not the copy.
Every flow needs an exit condition written in the event language of your system. An onboarding sequence should exit when the core action happens, not when a timer runs out. A trial conversion sequence should exit when a subscription starts. A dunning sequence should exit when a payment succeeds or the subscription ends. If you cannot state the exit in one sentence, the flow is not ready to launch.
Build a priority order between flows. A user who is mid-onboarding should not receive an upgrade offer, and a user in a payment recovery sequence should not receive a promotional email. Set these rules once, at the account level, rather than inside each flow, so that a new campaign cannot quietly break an existing one.
Check frequency across streams. Transactional mail, lifecycle mail and product announcements all reach the same inbox. A cap on marketing sends per person per week protects the rest. Decide the cap with the product team, and document it where the people building campaigns can see it.
Review flows on a schedule. A workflow that was accurate at launch can drift as the product changes. Renamed events, new plan names and changed trial lengths all break triggers quietly. A monthly check of event volumes per flow will catch most of these problems before a customer does.
Keep copy honest about the product. Lifecycle messages that promise features the product does not have, or that cite results without a source, cause refunds and complaints. Link claims to documentation, and remove any line you cannot support from a public page.
Common Mistakes to Avoid
Building expansion before onboarding works
Expansion emails need reliable usage data and a user who has reached value. If activation is weak, upgrade messages land on people who have not yet understood the product, and they tend to unsubscribe. Fix the first flow before adding the fourth.
Letting per-profile costs grow unchecked
Per-profile tools charge for every contact they hold. A free-trial list that grows every week without a cleanup rule can double the bill within a year. Set an archive rule for people who have not activated or logged in for a long period, and apply it before the tier changes.
Mixing marketing and account mail
A password reset that is caught by a marketing opt-out is a support ticket waiting to happen. Keep account messages on a separate sending path with their own rules, even when one vendor handles both.
Choosing an enterprise platform too early
Real-time orchestration and experiment paths are valuable when a team has the data, the operations staff and the volume to use them. Before that point, the implementation effort tends to outweigh the benefit, and the flows that matter most still need to be built first.
Lifecycle Email Marketing FAQ
Common questions about lifecycle email, billing triggers and migration for SaaS teams.
Which lifecycle emails should a SaaS team build first?
Start with the three flows that touch revenue most directly: onboarding up to the first meaningful action, trial conversion before the trial ends, and payment recovery when a card fails. Each one has a clear trigger (a signup event, a trial end date, a failed payment event from your billing system) and a clear exit (the user activates, converts, or updates the card). Add retention and win-back once those three are running and you can see which events they depend on. Expansion emails come last, because they need reliable usage data to be useful.
Do I need a billing integration to run lifecycle email for a subscription product?
You need subscription events from somewhere, and your billing system is the most reliable source. Trial start, conversion, plan change, failed payment and cancellation all happen in billing first. You can send these to an email tool through a native connector, a webhook, or an intermediate pipeline. Without them, your trial and payment flows depend on guesses from product usage, which is less accurate for the moments that matter most.
Is Customer.io free for early-stage companies?
Customer.io lists a Startup Program under which eligible early-stage companies that have raised under $10 million can receive 12 months free. Eligibility is set by the program rules on the pricing page, so read those before you plan around it. After a free period ends, the Essentials plan is listed at $100 a month billed monthly, and profile-based tiers start at $145 a month for 10,000 profiles.
How do I choose between a per-contact tool and a flat-tier tool?
Per-contact pricing grows with the number of people you message, including people who never open anything. Flat tiers with unlimited sends are easier to forecast once your list stops changing much, but the jump between tiers can be large. Model your list at the size you expect in 12 months, not today. For a list of 9,001 to 10,000 people, Drip lists $154 a month, while Customer.io lists $145 a month for 10,000 profiles. At that size the difference is small, so the choice should turn on how each tool models your flows.
Can one tool handle both transactional and lifecycle email?
Some can, and some are built only for marketing sends. Loops lists transactional sends to users outside your audience as included on its paid Growing Audience plan, which is useful if you want one vendor for product notifications and lifecycle campaigns. Keep the two streams separate in your setup even when one tool sends both: transactional mail should not depend on marketing consent, and a marketing unsubscribe should never stop a password reset or an invoice.
What does a per-seat tool like Intercom cost compared with per-profile tools?
Intercom lists its plans per seat per month, billed annually: Essential at $19, Advanced at $85 and Expert at $132 per seat. The cost therefore follows the size of your support and marketing team rather than your contact list. That is the opposite of profile-based tools such as Customer.io or Klaviyo, where list size drives the price. A small team with a large list can find a seat-based plan cheaper; a large team with a modest list can find the reverse. Intercom also lists usage-based AI outcome and messaging charges on top of the seat price, so budget for those separately.
How should I handle unsubscribed contacts when I migrate to a new lifecycle tool?
Export suppression lists from the old tool and import them before you send anything from the new one. Include unsubscribes, hard bounces and spam complaints, and keep the reason and date where the export allows. Do not import unsubscribed people as active contacts, even if the new tool offers a way to do it. Tag contacts by consent source so that a future audit can show where each address came from. Run the old and new systems in parallel only for a short cutover window, and make sure a person cannot receive the same flow from both.