SaaS drip campaigns are pre-written email sequences that start on a user event and stop when the user reaches a goal. A solo founder needs four: trial onboarding, activation nudges, trial-to-paid, and expansion. Each runs on one trigger, one exit event, and a handful of emails, and you can ship the first in an afternoon.
Get one build teardown like this in your inbox each week: subscribe to the SaasFlywheel newsletter.
What a SaaS Drip Campaign Is, and the Four a Solo Founder Needs
A drip campaign is a fixed series of emails sent on a schedule after a trigger. The part that separates a useful drip from spam is the stop rule, and most guides skip it. I would argue it is the only part worth getting right first, because a sequence that cannot stop will eventually email a paying customer about their trial.
| Drip | Trigger | Emails and timing | Exit event | Number to watch |
|---|---|---|---|---|
| Trial onboarding | Signup | 3 emails: day 0, day 1 to 2, day 3 | Activation event reached, or trial ends | Share of signups reaching activation |
| Activation nudges | Signup plus N hours with no activation event | 2 nudges, then one plain question | Activation event reached | Activation rate among stalled signups |
| Trial-to-paid | Trial start, timed to the trial clock | 2 to 3 emails around days 10 to 14 of a 14-day trial | Paid plan started | Trial-to-paid rate |
| Expansion | Usage threshold or approaching a plan limit | 1 to 2 emails | Plan changed | Upgrade rate among triggered accounts |
For a reference point on the last row of the funnel, Growth Unhinged, with ChartMogul and ProductLed, reported a median free-to-paid conversion of 8% across 200 software products (survey of January 2026, published 2026-02-04, conversion counted within six months). The sample skews above bootstrap scale (34% of respondents under $1M ARR), so read 8% as a reference, not a target.
A solo founder also skips four things at this stage: lead scoring, a branching journey canvas, dunning for failed payments, and a win-back sequence. Win-back is its own build, covered in the win-back campaign guide. Teams already running a full lifecycle stack should read the AI lifecycle email automation piece instead.
Write the Drip Spec Before the First Email
The Drip Spec is a six-line definition you fill in before writing email 1 of any drip: trigger event, entry filter, goal event, exit rule, delays, and suppression or priority rule. Add a send cap as a seventh. The goal event doubles as the exit rule, so a user who converts or activates stops receiving the sequence.
Budget 20 minutes per drip for the spec. It feels like paperwork, and it is the cheapest insurance you will buy. It prevents the rewrite that happens when a paying customer is still receiving “your trial ends soon.”
Tools implement the exit rule differently. Customer.io's docs say a person continues through an automation until they stop matching its trigger or filter, and custom exit conditions (profile attributes, events, segments) work as OR statements. In Loops Workflows, you place an audience filter node and set it to apply to all following nodes, so a contact who stops matching is removed when they reach a later node. Same idea, different wiring, which is why you read the docs for your tool before you trust the spec to it.
The five events to track first
Track five events, one track() call each: signup, activation event reached, key feature used, trial ending, and plan changed. Those five feed every drip here.
The activation event is an input here, not something this article decides for you. Pick it first, using how to define your activation event; Drips 1 and 2 both exit on it.
One drip at a time per user
Give every drip a rank and send only the highest-ranked drip a user qualifies for. The order: trial-to-paid, then activation nudges, then onboarding, then expansion. The logic is distance to revenue. A user in the last days of a trial should get the conversion email, not a “have you tried feature X” nudge.
Expansion only applies to paying accounts, so it rarely collides with the others. A higher-ed CRM's documentation calls the one-record-one-drip idea an exclusivity group. Without a native setting, enforce it with exit conditions and a “last emailed” attribute. It is a little clumsy, and it works.
Drip 1, Trial Onboarding: Days 0 to 3, Three Emails
Trial onboarding has one job: get a first successful setup. The trigger is signup. The exit is the activation event or the end of the trial, whichever comes first.
For timing, Sequenzy's published trial rows put the welcome at day 0, a setup check-in at day 1 to 2, and a value demo at day 3 to 5. Sequenzy is an email vendor and states no methodology or sample size, so treat the timing as directional. Compress the last email to day 3, because a trial is short and every day you wait is a day the user forgets you.
Email 1 asks for one action. Plain text is fine, and the reply-to is your real inbox: a founder who answers replies has an edge no template tool sells, and the replies show where setup breaks.
Ask a segmentation question only if the answer changes the path. CXL's 2018 piece on SaaS drips suggested letting new users self-segment, which pays off only if you have two different emails to send afterwards. If you have one email, the question is just friction.
The minimum viable version is two emails: the welcome and the day 1 to 2 check-in. Ship that, then add the third once you have seen the first two work.
Drip 2, Activation Nudges: Trigger on the Event, Not the Day
Activation nudges fire on the absence of an event, not on a calendar day. The trigger is signup plus N hours without the activation event. Pick N from your own event data: the median time your activated users took to reach the event, not a number from a blog post.
A day-count sequence emails the user who activated on day 1 with “need help getting started?” on day 3. That is the fastest way I know to look like you are not paying attention. An event-gated nudge checks the goal first and stays silent.
Send at most two nudges. After the second, stop and send one plain question: “What stopped you?” The replies are the cheapest user research available at this stage, and they cost you nothing but the willingness to read them.
Sequenzy's vendor-published guidance calls above 40% “okay” and above 55% “great”, while noting that companies define activation differently. Directional only.
The minimum viable version is one nudge and the question.
Drip 3, Trial-to-Paid: Run It Off the Trial Clock
The trial-to-paid drip converts an active trial at the end, so its schedule hangs off trial length, not signup. In the Growth Unhinged survey, 14 days was the most common trial length at 62% of products, with 7 days and 30 days at 14% each. For a 14-day trial, Sequenzy's rows put the “ending soon” email at day 10 to 12 and the “trial ended” email at day 14 or later.
If you bill through Stripe, you can trigger the ending email from the customer.subscription.trial_will_end event. Per Stripe's docs (accessed 2026-11-09), it is sent according to the Trial ending events setting in the Dashboard, which defaults to 3 days before the trial ends. If the trial is shorter than the configured interval, it triggers immediately. Stripe-hosted reminder emails go out 7 days before. Check your own Dashboard setting.
Here is the Drip Spec filled in for this drip, in a shape you can copy:
| Spec line | Trial-to-paid, 14-day trial |
|---|---|
| Trigger event | trial_started |
| Entry filter | Trial plan, not an existing customer |
| Goal event | Paid plan started |
| Exit rule | Leave on goal event; leave if the trial is canceled |
| Delays | Ending-soon email near day 11 (Stripe default) or day 10 to 12; trial-ended email at day 14 |
| Suppression and priority | Rank 1: suppresses onboarding and activation drips while active |
| Send cap | 3 emails |
On the card-upfront question, report the correlation and stop. The same Growth Unhinged survey found trials requiring a credit card converted at about 30%, described as more than 5x trials without one, and 20% of trial products require a card. The survey also found 80% of free-trial products have human touchpoints, and the same skew above bootstrap scale applies. It shows an association, not proof that a card wins for your product. If you are still choosing a model, free trial vs freemium covers it.
RevenueCat's analysis of 17,000+ subscription apps (consumer apps on the App Store and Google Play, August 2025 to July 2026) found longer trials converted better, a pattern RevenueCat itself calls correlational. It is not B2B SaaS evidence, so do not stretch your trial to 30 days on the strength of it.
An illustrative sum: 200 trials a month at the report's 8% median is 16 paying customers. Lifting that to 10% is 20. Four extra customers from one sequence is a modest win, and it compounds every month the drip keeps running.
Drip 4, Expansion: Fire on Usage, Not on the Calendar
Expansion drips move an active paying account to a higher tier or to annual billing, and they should fire on usage. The trigger is a usage threshold or a plan limit coming into view. The exit is the plan changing.
A calendar trigger (“30 days after signup, upsell”) ignores whether the account is near its limits; a usage trigger fires when the upgrade is the obvious next move. Sequenzy's vendor-published figures for usage-targeted product emails are 45% to 60% opens and 15% to 25% clicks, with no stated sample: directional at best.
CXL's 2018 article gave an annual-plan example that stated the exact dollars the customer would save. Put the number from the customer's own account in the email. A specific saving beats any amount of persuasive copy.
One caution from the same source: upselling for its own sake can push customers to churn. If a customer is not near a limit, do not email them. For the strategy behind when and why to expand, see the expansion revenue playbook. Keep it to one or two emails.
Which Tool at Solo Scale: Price Floor and Time to First Live Drip
Choose by two criteria: monthly price at 1,000 to 5,000 contacts, and whether the tool can receive your events and stop a sequence on an exit event. A newsletter tool that cannot take events cannot run Drips 2 to 4. HubSpot can do it all, but it is a heavier suite than a one-person product needs.
Prices are from first-party pricing pages, as of 2026-11-09. Verify before you buy.
| Tool | Entry price | Events in, exit out |
|---|---|---|
| Loops | Free: 1,000 contacts, 4,000 sends per rolling 30 days. Growth $49/month: 5,000 contacts, unlimited sends | Workflows with event triggers and audience-filter exits are documented; confirm they are on the Free plan |
| Resend | Free: 3,000 emails/month, 100/day. Pro $20/month | Custom events trigger automations (documented); verify exit-on-event |
| MailerLite | Free to 250 subscribers; Comfort from $12/month | Verify custom product-event triggers and exits |
| Kit | Free plan has no automated sequences; Creator $33/month for 1,000 subscribers | Built for creators and newsletters; verify app-event triggers |
| Customer.io | Essentials from $100/month (5,000 profiles); startup program for companies that raised under $10M | Automations with exit conditions documented; above the solo price floor |
On fit, Loops and Resend sit closest to a developer-led product at this size, Kit and MailerLite are newsletter-first, and Customer.io is where you land when the stack grows. None of that is a verdict. Test one thing in the first hour: send an event, watch the automation start, fire the goal event, and confirm the user drops out. If that takes more than a Saturday, pick another tool. For the broader stack, see the full marketing automation stack.
Where AI Earns Its Place in a Drip (and Where It Does Not)
AI is a helper in exactly three jobs inside a drip. It cannot do the deciding.
First, draft two or three copy variants per email from the filled-in spec, then edit by hand before sending. The failure mode is generic copy from an unedited draft, and readers can smell it in one line.
Second, turn a free-text signup answer or a stall reply into a one-line personalized opener. The precondition is an open text field on your form.
Third, summarize the replies to your “what stopped you?” email into themes. The failure mode is trusting the summary without skimming the raw replies.
AI does not pick the activation event, set the timing, or define the exit rule. Those come from the Drip Spec and your own event data. A model has never seen your users' median time to first success, and you have.
Loops announced an Email Metrics API and Loops in ChatGPT on 2026-10-08, and Customer.io published “Get behavioral insights with AI” on 2026-09-10. These tools ship and rename features often, so verify the current set first.
Frequently Asked Questions
What is an example of a drip campaign?
The trial-to-paid drip. A user starts a 14-day trial, gets an "ending soon" email around day 10 to 12 and a "trial ended" email at day 14 or later, and leaves the sequence the moment they start a paid plan. Timing comes from vendor-published guidance (Sequenzy, directional).
What are drip campaigns?
A drip campaign is a pre-written sequence of emails that starts on a trigger and stops on a goal. For SaaS, four cover most needs: trial onboarding, activation nudges, trial-to-paid, and expansion. Each needs a trigger event, a goal event, and an exit rule.
What is the best software for drip campaigns?
No single winner exists; choose by fit. The tool must receive your product events, stop a sequence when a goal event fires, and fit your price floor at 1,000 to 5,000 contacts. Loops, Resend, MailerLite, Kit and Customer.io meet those tests differently, so verify current plans before buying.
How long should a drip campaign be?
As long as it takes the user to reach the goal event, then stop. In practice that means three emails for trial onboarding and a schedule tied to trial length for trial-to-paid, such as 14 days, the most common trial length in the Growth Unhinged survey (62% of products).
Ship One Drip This Week
Build trial-to-paid first if you have a trial and any activated users, because it sits closest to revenue. If you have no trial, start with activation nudges. Fill in the Drip Spec, write the minimum viable version, and turn it on. Do not wait for the perfect subject line; a live drip with a rough email teaches you more than a polished one sitting in drafts.
Set a calendar reminder for 30 days out. As a rule of thumb, not a sourced figure: if you cannot read the goal-event rate for a drip, rewrite it or kill it. Sequenzy notes that Apple Mail Privacy Protection inflates opens, so the goal-event rate is the number that counts.
Want the next build in this series? Subscribe to the SaasFlywheel newsletter.