SaaS Drip Campaigns: How to Build Them and Which Platform to Use
How to design SaaS drip campaigns for trials, onboarding, expansion, payment recovery and win-back, and how Drip and Close compare on price and limits.
Written by the editorial team
For most SaaS teams, the best starting pick for drip campaigns is Drip. Its listed plans start at $39 a month for 1 to 2,500 people, and most tiers in the listing include unlimited email sends, so the bill is driven by how many people you email rather than how many messages each person receives. That matters in subscription businesses, where one trial user can get a dozen lifecycle messages in two weeks. Drip is a marketing automation tool, though. It does not know whether a payment failed or whether a feature was used. Those signals have to reach it from your product and billing systems, and that wiring is where most of the work sits.
This guide covers the lifecycle stages a SaaS drip program should map, the sequences worth building first, the data each one needs, and how Drip and Close compare on price and limits. It ends with a setup checklist and a short FAQ.
Who this guide is for
This is written for the person who owns activation, conversion or retention at a software company with a free trial, a freemium tier or a paid plan with monthly or annual billing. If your email list is mostly a newsletter with no product state behind it, the sequences below will be more than you need. If you have trials that expire, customers who churn in their first quarter, or a payment provider that sends failed-card events, the sequences here map directly to revenue.
Map the lifecycle before you write a single email
Drip campaigns fail most often because the stages are vague. A user who signed up for a newsletter and a user who is three days into a paid trial should not receive the same message. Define each stage by an observable event, so the entry and exit rules can be checked in your data:
- Visitor: Has not created an account. Exits when the account is created.
- Lead: Subscribed to content but has not started a trial. Exits when a trial starts.
- Trial: Has an active trial. Exits when the trial converts, lapses or is cancelled.
- Customer: Has an active paid subscription. Exits on downgrade, cancellation request or failed renewal.
- Champion: Paying, and active on the features tied to retention. Exits when activity drops below your threshold.
- At-risk: Paying, but usage or engagement has fallen. Exits on recovery or cancellation.
- Churned: Subscription ended. Exits on reactivation.
Write the exit condition next to each stage. If you cannot name the event that moves someone out of a stage, you cannot build a sequence that stops at the right moment.
The sequences worth building first
Build a small number of sequences that each protect one revenue event, then add others once you can measure the first ones. The order below reflects how much revenue each one usually touches, not a ranking of importance.
1. Trial onboarding
Goal: Get trial users to the first action that shows the product solves their problem.
Trigger: Trial started. The entry event should come from your product, not from the moment someone joined a form.
Front-load the messages. For a 14-day trial, a workable pattern is a welcome with one specific first step on day 0, a quick-win tutorial on day 1, a core feature walkthrough on day 3, a customer example on day 5 and a branch on day 8: advanced tips for users who have been active, a re-engagement note for users who have not. Send a trial-ending reminder on day 11 and a final prompt on day 14. Every message after the first should stop as soon as the user reaches the activation event, so a successful user never receives a rescue email.
2. Trial conversion
Goal: Turn trial users into paying customers before the trial lapses.
Trigger: Trial within three days of expiring, or a high-engagement signal in the final week.
Summarize what the user has built or used so far, name the plan that matches their usage, and be plain about what will change when the trial ends. Use two branches: high-engagement trials get a plan recommendation based on the features they used, while low-engagement trials get a single offer to book a short setup call or a reminder of the one feature they have not tried. Avoid discounts in the first version of the sequence. You will learn more about the conversion problem from the copy than from a price cut you cannot yet attribute.
3. First-paid onboarding
Goal: Get new paying customers to use the features they bought within the first month.
Trigger: First successful payment or subscription activation.
Four to six emails over the first 30 days work for most products: a welcome that states what the plan includes, a note on the paid-only features they now have, a best-practice guide for their use case, a suggested integration if one applies, a link to support resources, and a check-in once a key milestone has been reached. Use the plan name from the billing system rather than a generic greeting, and stop the sequence if the customer contacts support, since that conversation will supersede the scripted messages.
4. Activation rescue
Goal: Help people who signed up but never reached the first meaningful milestone.
Trigger: Account created, with no activation event after a window you define from your own data.
Keep this narrower than general onboarding. Ask what blocked progress, offer one low-effort next step, and point to a human or help-center route. Exit immediately when activation arrives. A rescue message that lands after a user has already succeeded makes the product look like it does not notice what people do.
5. Feature adoption
Goal: Drive use of the features that correlate with retention in your own cohort data.
Trigger: A paying user has not used a specific feature after a set number of days.
Choose the features by analysis, not by what the marketing team wants to promote. Pull the cohort of customers who stayed past their first renewal, see which features they used early, and build the adoption sequence around those. Each message should introduce one feature, show one example from a customer in a similar role and offer a guided first step. Do not send a feature sequence to people who already use the feature.
6. Usage milestone
Goal: Reinforce a habit after a customer completes something valuable, such as inviting a teammate or publishing a project.
Trigger: A defined milestone event.
This is more than a congratulatory email. Explain what the milestone unlocks, suggest the next workflow that builds on it and ask one question about the customer's use case while the context is fresh. Teach depth without turning every successful action into an upsell. If the milestone is a team invitation, the useful follow-up is advice on setting permissions, not a plan comparison.
7. Payment failure recovery
Goal: Get the customer to update a payment method before the subscription lapses.
Trigger: A failed-payment event from your billing provider. This requires a webhook or connector, and you should confirm the exact event names and retry schedule in your billing provider's documentation before you build anything.
Send a short message that names the subscription, links straight to the card-update page and states the date service will be affected. Keep the wording factual. Stop all remaining messages the moment a successful payment event arrives. Avoid implying that the customer did something wrong, and do not add a promotional offer to a billing message.
8. At-risk re-engagement
Goal: Re-engage paying customers whose usage has dropped before they cancel.
Triggers: Login frequency falls below your baseline, key feature usage drops, or the customer stops opening product emails for several weeks.
Remind the customer what they have already accomplished, name one feature they may have missed, share a short example from a similar account and offer a short call or help article. A brief survey asking what changed is useful, but keep it to one question so the response rate stays high. Treat the at-risk stage as a hypothesis: if a customer replies that they are simply busy, record that and reduce the frequency.
9. Cancellation save
Goal: Offer a real alternative to customers who have started to cancel.
Trigger: A cancellation request is submitted.
Acknowledge the request without pressure. Offer the options your product actually supports, such as a downgrade, a pause or a discount if you have approved one, and address the most common cancellation reasons from your support records. If the customer proceeds, send a short closing message that confirms the end date and explains how to return. Respond quickly, because the decision is often made within hours of the request.
10. Win-back
Goal: Bring back customers who have already cancelled.
Trigger: A set number of days after the subscription ended, commonly 30 to 90 days, followed by periodic touches.
Write about what has changed since the customer left, specifically. A general "we miss you" with no product news is easy to ignore. If you have a feature that addresses the reason they gave when they left, lead with that. Limit the sequence to a few messages, and suppress anyone who has resubscribed or who asked to stop.
Data each sequence needs
Every sequence above depends on a signal your email tool does not generate by itself. Before you pick a platform, list the events you need and where each one lives. Typical sources are your product (activation, feature use, team invitations), your billing provider (trial start, subscription activated, payment failed, plan changed, cancellation requested), your support desk (ticket opened, ticket closed) and your CRM (deal stage, account owner). Engagement signals such as high or low activity periods are usually derived from product events, so define the thresholds in writing and review them after each cohort.
Expect the wiring to take longer than the emails. Most of the risk is in event naming, duplicate events, time zones and customers who belong to more than one account. A sequence that sends the wrong message to the wrong person does more damage than a missing sequence.
Drip and Close compared
The two tools below cover different parts of the job. Drip is an email automation platform. Close is a CRM with workflow automation and sales calling built in. Convert, which is also a common name in this space, is an experimentation tool for testing pages, so it is not a drip platform and appears only for completeness.
| Tool | Best for | Starting price (plan and billing) | Key limitation |
|---|---|---|---|
| Drip | SaaS and product teams running lifecycle sequences from a contact list with segments and workflows | $39 a month for 1 to 2,500 people, monthly billing as listed on the pricing page | Listed tiers cap workflows at 50; higher bands include a fixed number of sends rather than unlimited sends |
| Close | Sales-led SaaS teams that want email sequences and calling on the same contact record | Growth plan at $109 per user a month billed monthly, or $99 per user a month billed annually; Essentials from $49 a month or $35 billed annually | Priced per user, and automated workflows are only on Growth and above; calling and SMS usage is passed through at cost |
| Convert | Testing landing pages and trial sign-up flows, not sending sequences | Growth at $399 a month, or $299 a month billed annually, for 100,000 monthly tested users | Does not send email; use it beside a sending platform, not instead of one |
Drip
Drip is the strongest fit for the sequences in this guide when the job is to send many lifecycle messages to a known audience and to segment that audience dynamically. Its listed features include unlimited email sends on most tiers, dynamic segments, onsite campaigns and up to 50 workflows. Higher tiers add chat and email support, personalized onboarding and, at the 22,501 to 25,000 band, free migration. Those features matter for SaaS teams because trial, activation and win-back sequences all depend on segments that update as people's status changes.
Its limits are the pricing structure and the workflow cap. Pricing is tied to active people, so a list that grows quickly moves up the bands even if your message volume stays the same. The listed tiers include workflow limits, so a large program with many branches will need to plan which sequences to consolidate. Drip does not list a permanent free plan; it offers a 14-day free trial with no credit card required. Confirm the native connectors for your billing and product systems in its documentation before you commit to a build plan. The pricing page is at drip.com/pricing.
Close
Close is a CRM first. It suits a SaaS company whose trial and expansion conversations are handled by a small sales team and where the sequence should sit beside the sales record. Its Growth plan includes automated workflows and bulk email, along with the power dialer and custom activities. The Scale plan adds role-based access, lead visibility rules and live call coaching, which matter once several teams share one account database.
The main cost consideration is that pricing is per user. Using the Growth plan at $99 per user a month billed annually, a three-person team pays $3,564 a year ($99 × 3 × 12), and a five-person team pays $5,940 a year ($99 × 5 × 12). The same team on monthly billing at $109 per user would pay $3,924 and $6,540 a year. Seats are charged whether or not a person sends sequences, and calling and SMS usage is passed through at cost. A 14-day free trial is available with no credit card required, and there is no ongoing free plan in the listing. Pricing details are at close.com/pricing.
Convert
Convert is included because teams often confuse it with email software. It is a testing platform for pages, and it can help you measure whether a trial sign-up page or an onboarding screen changes behavior before you rewrite a sequence around it. Its Growth plan lists $399 a month, or $299 a month billed annually, for 100,000 monthly tested users, and its Pro plan lists $599 a month, or $420 billed annually. It has a 15-day free trial and no ongoing free plan. Use it alongside your sending platform if you run experiments on the pages that feed your sequences. Pricing is at convert.com/pricing.
What the price means at your list size
For Drip, the price depends on the number of people in your band. The table below uses list sizes that fall inside the listed bands. Figures are monthly prices from Drip's pricing page as listed on October 7, 2026. If your list falls between two bands, use the calculator on the pricing page rather than estimating.
| People in your list (example) | Drip band | Monthly price | What the listing includes |
|---|---|---|---|
| About 2,000 | 1 to 2,500 people | $39 | Unlimited email sends, dynamic segments, onsite campaigns, up to 50 workflows |
| 5,000 | 4,501 to 5,000 people | $89 | Same as above, plus email support |
| 10,000 | 9,001 to 10,000 people | $154 | Unlimited email sends, chat and email support, dynamic segments, up to 50 workflows |
| 15,000 | 12,501 to 15,000 people | $209 | Unlimited email sends; check the pricing page for the full feature list in this band |
| 25,000 | 22,501 to 25,000 people | $369 | Unlimited email sends, chat and email support, free migration, personalized onboarding |
| 40,000 | 37,501 to 40,000 people | $609 | Includes 480,000 email sends per month as listed |
Two points follow from the table. First, the jump from one band to the next is the biggest cost driver, so plan your segments with the band edges in mind. Removing inactive contacts from your active list can keep you in a lower band, but only do this with a suppression rule you can explain to a customer. Second, the 40,000 band includes a fixed send allowance, so a program that sends a high volume to a large list should compare the included sends against the message schedule you have designed.
Decision table: which tool for which job
Use this table to decide before you open a free trial. Each row names one requirement, the tool to test first and the reason.
| If you need | Start with | Because |
|---|---|---|
| High-volume lifecycle email to a large contact base | Drip | Pricing is set by people in the band, and most listed tiers include unlimited sends |
| Sequences that sit beside sales calls and deal records | Close on the Growth plan | Automated workflows and bulk email are included, and the sequence shares the contact record with sales activity |
| Payment-failure emails tied to billing events | The platform that supports your billing provider natively | The trigger quality depends on the connector; confirm event names and retries before you buy |
| Tests of trial sign-up pages before you rewrite the sequence | Convert, used alongside your sender | It measures page behavior; it does not send messages |
| A free starting point | Run a trial of each tool with your own event data | Neither Drip nor Close lists an ongoing free plan; both list 14-day trials with no credit card |
How to choose
Start with the revenue event you most need to protect. For a trial-heavy product, that is trial conversion, so the platform must send timed messages that stop on the conversion event and must be able to segment by trial status. For a product with annual contracts, it is renewal and expansion, so the platform needs reliable access to plan data and a clean way to branch by usage. For a product with a high churn rate in the first quarter, the first build is onboarding and activation rescue.
Then check four things during the trial. Import a real segment, not a sample. Build one sequence end to end with a stop condition. Send a test to internal accounts that have each stage state. Confirm where the unsubscribe and suppression records live, because a sequence that keeps messaging a customer who has already converted is the most common expensive error in this work.
Finally, compare the total cost, not the first invoice. Add the per-seat cost of a CRM, the band cost of a list that will grow over the next year and the engineering time needed to send events. A cheaper tool that needs a custom integration for every event may cost more in the first quarter than a higher-priced tool with a native connector.
Setup and launch checklist
Work through the steps in order. Each step has a condition that tells you it is complete, so you can check progress without a status meeting.
| Step | What to do | Done when |
|---|---|---|
| 1. Name the events | List every product, billing and support event each sequence needs, with exact names | Each trigger has a documented source system |
| 2. Define consent and suppression | Record how each contact opted in, and list purchases, replies, unsubscribes and competing journeys that should pause a sequence | Every sequence has a written suppression rule |
| 3. Set one outcome per sequence | Name one primary conversion and a review window, such as 30 days for onboarding | Each sequence has one metric and one owner |
| 4. Build the first sequence | Start with trial onboarding or payment recovery, not all twelve sequences at once | The sequence runs end to end in test mode |
| 5. Test with internal accounts | Move internal accounts through each stage and confirm the right messages arrive and the right ones stop | Every stop condition has been exercised at least once |
| 6. Launch and review | Release to a defined audience, then review after one full cycle of the sequence | The review records what changed and what you will try next |
Metrics that matter for SaaS drip programs
Opens and clicks are weak signals for subscription businesses. Measure the outcome each sequence protects and compare it against a holdout group where you can.
- Trial-to-paid conversion: The main measure for trial sequences. Compare users who received the sequence with a comparable group that did not.
- Time to conversion: How quickly trial users convert after their first message, which shows whether early sequences are working.
- Activation rate: The share of new accounts that reach the milestone the activation sequence is built around.
- Feature adoption: The share of paying customers using the feature targeted by an adoption sequence, measured from product data rather than clicks.
- Save rate: The share of customers who begin cancellation and then keep their subscription after the save sequence.
- Recovered payments: The share of failed payments that are updated within the sequence window, reported from your billing system.
Segment these by signup cohort. A trial that started in January can behave differently from one that started in March, and customers from different acquisition sources often respond differently to the same copy. Review the cohorts after each full sequence cycle rather than after each send.
Frequently asked questions
Does Drip have a free plan?
Drip does not list an ongoing free plan on its pricing page. It offers a 14-day free trial with no credit card required. Check the pricing page before you plan a budget, because listed terms can change.
How many emails can I send with Drip?
Most listed tiers, from 1 to 2,500 people up to 22,501 to 25,000 people, include unlimited email sends. The 37,501 to 40,000 band lists 480,000 sends, and the 45,001 to 50,000 band lists 600,000 sends. For large programs, compare the included sends against your sequence schedule.
Can Close run drip sequences without a separate email tool?
Close's Growth plan includes automated workflows and bulk email, so it can run sequences. It is best suited to teams whose sequences should sit next to sales activity and deal records. If your main need is high-volume lifecycle email to a large audience of product users, compare the per-user cost against a per-person plan before you commit.
Why not use the emails my payment provider sends?
Payment providers usually cover receipts and card-update notices. Onboarding, activation rescue, feature adoption and win-back sequences need segments, timing rules and content that a billing notice does not provide. Use the provider's notices for transactional billing and a sending platform for the lifecycle sequences.
How long should a trial sequence run?
Match the sequence to the length of the trial. A 14-day trial needs its messages front-loaded, with the conversion push in the last three to four days. Every message after the first should stop when the user converts or cancels, so the sequence does not continue after the decision has been made.
Which sequence should I build first?
For most subscription products, start with trial onboarding and payment recovery. Trial onboarding affects conversion directly, and payment recovery protects revenue you already have. Add expansion, feature adoption and win-back once you can measure the first two against a holdout group.
Do I need a data warehouse before I start?
No. You need reliable event names, a way to pass them to your sending platform and a place to record the outcome of each sequence. A warehouse becomes useful when you want cohort analysis across many sources, but a simple export from your product and billing systems is enough to start.