Trial Conversion Emails: Sequence, Timing and Triggers

For most SaaS teams running card-on-file trials through Stripe, Loops is the best starting point for a six-email trial sequence. Its Stripe integration documentation covers trial-end events, so the pre-charge email can run as a workflow instead of a calendar guess, and the Growing Audience plan is $99 a month with unlimited sends to subscribers. Customer.io is the stronger pick when the sequence has to branch on product events, with its Essentials plan starting at $100 a month billed monthly. Prices below were checked on 7 October 2026 against each vendor's pricing page, and every price links to the page it came from.

A good trial conversion sequence runs on two clocks: the trial's end date, which your billing system knows, and the person's activation, which your product knows. Time-only sequences send the same "trial ending" email to someone who uses the product every day and to someone who never logged in. The sequence below uses six emails, three triggers (signup, an activation event, and Stripe's trial-end event) and a stop rule on each message, so converters leave the sequence as soon as they pay.

What the arithmetic is worth

Suppose a product starts 400 trials a month and charges $40 a month per account. Each percentage point of trial-to-paid conversion is 4 customers, or $160 of new monthly recurring revenue for that cohort. Moving from 20% to 24% takes a cohort from 80 paying customers to 96, which adds $640 of MRR per month, and that gain carries into every later cohort. These numbers are an illustration of how the lever works, not a benchmark. Your own cohort baseline is the only comparison that counts.

The arithmetic also shows where small fixes pay. Sending the pre-charge notice only to people who have not converted, and not to everyone on a fixed date, often matters more than rewriting a subject line. Email tools are priced differently per contact, per profile or per send, so the sequence design affects cost as well as conversion. The cost table later in this guide puts numbers to that.

How the trial type changes your emails

Stripe lets you start a subscription trial with a set number of days and either with or without a payment method on file. For trials without a card, the trial settings also decide what happens when the trial ends without one. That choice determines which emails you owe people, so decide it before you write any copy.

With a card collected at signup, the trial converts automatically. Stripe creates an invoice and attempts the charge at the end, so your pre-charge email should state the date, the amount and how to cancel. With no card and the trial set to cancel, the subscription ends when the trial ends and a deletion event follows, so the add-a-card reminder must go out before the end and a restart link after it. With no card and the trial set to pause, the subscription stops generating invoices until someone resumes it, so the email after the pause should link into the billing portal. With no card and the trial set to create an invoice, Stripe invoices at the end, and if no payment method exists the subscription becomes past due, which means your failed-payment flow takes over from the trial emails.

Stripe's trial documentation also warns that card-free trials can attract fake sign-ups, and it recommends a user account and a captcha before the trial starts. Stripe offers its own reminder emails for collecting payment details, configured in the Dashboard's trial messaging settings. If you send your own reminders, either turn Stripe's off or decide which messages come from which system, so customers do not receive two requests for a card on the same day.

The six emails

The sequence is built around six sends. Each has a timing rule, a purpose and a condition that removes the person from the sequence. The stop conditions do most of the work, because they keep the sequence from pushing people who have already paid.

• Email 1, at signup. Sent within minutes. It confirms the trial length and gives one first step. It is sent once and is never suppressed.
• Email 2, 48 hours after signup. Sent only to people without the activation event. It names the first step and offers a reply address that a person reads. It is skipped for anyone who is already active.
• Email 3, around the trial midpoint. A recap of what the person did, plus the next feature that follows naturally. It stops if they have converted.
• Email 4, on the Stripe trial-end event, about three days before the end. The pre-charge notice for card-on-file trials, or the add-a-card request for trials without a card. It stops if the subscription is already active or canceled.
• Email 5, on the final day. A plain deadline with one link and nothing else. It stops for converters.
• Email 6, the day after the trial ends. An offer to restart, with a checkout or portal link. It stops for unsubscribed people and for anyone already paying. It is the only place a discount belongs, if you use one.

Email 4 is the message most worth getting right, because it is triggered by billing rather than by the calendar. For a card-on-file trial, the body might read: "Your trial ends on [date]. On that day we charge [amount] to the card ending [last four]. You can cancel or change plan here." For a trial without a card it should read differently: "Add a payment method by [date] to keep your projects. Here is the link." Both versions should fit on a phone screen without scrolling past the link.

Email 3 is where personalization earns its place. Refer to the person's own project, import or integration, using the name the product itself uses for it, and avoid generic phrases like "your journey". Leave out customer quotes or result figures unless you can link a real source, because invented testimonials do more harm than a plain recap. The personalization guide shows how to build those branches without breaking when a field is empty.

Branching on behavior

A single linear sequence treats every trial the same, and that is the main reason time-only sequences underperform. Branching needs only three signals: whether the activation event has happened, whether the person has been active recently, and whether the account has more than one user. The branches below are what each signal should change.

• Activated and engaged. Skip the nudges. Lead with pricing and the plan that fits the usage they already show.
• Started, then stalled. Name the step where they stopped and offer a short call or a trial extension. People who ask for more time are usually still evaluating, so the extension gives you a signal as well as a second chance.
• Never started. One help email, then a quiet expiry with no pricing push. Pushing a sales message at someone who never logged in does little for conversion and raises the spam complaint risk.
• Team trial. Address the account owner for billing messages, and send product messages to each user. Two people on one account should not each receive a card request.

Keep the branching rules in a document alongside the sequence. Each rule needs a named event, a stop condition and an owner who can change it. When a rule is unclear, the usual symptom is a converter who gets a pre-charge notice, and that is a fast way to lose trust.

Choosing a tool: the comparison

The four tools below cover the most common setups for trial sequences. The starting price column shows the plan and billing view that applies, and the limitation column names the constraint most likely to matter once the trial program is running. The prices come from each vendor's pricing page as checked on 7 October 2026.

Each row answers a different question. Loops answers "how do we get a working trial sequence on Stripe this month". Customer.io answers "how do we branch on what people actually do in the product". Userlist answers "how do we keep messages, in-app prompts and account segments together for a small team". None of them removes the need for an activation event, because every branch depends on it.

What the trial program costs at three list sizes

Cost depends on what each vendor counts. Customer.io and Userlist count profiles or users, while Loops counts contacts and sends. The table below uses three representative audience sizes and shows only what the published pricing covers. Where a plan has no published price for a size, the cell says so rather than estimating.

For the Loops column, the send count matters more than the contact count on the free tier. A program that starts 500 trials a month and sends the six-email sequence to each of them can approach 3,000 trial emails, leaving little room for other messages before the 4,000-send allowance. The stop rules that keep converters out of the sequence also keep the bill down.

The billing side has its own costs. Stripe, Paddle and Lemon Squeezy all charge per transaction on their pricing pages and show no monthly platform fee for standard plans. Those fees apply whether or not you run any email tool, so they do not change the email comparison above. Read each vendor's current fee schedule before you model revenue for a trial program.

Decision guide: which tool to pick

The table below turns the comparison into a set of choices. It assumes you already have a trial in your product and a billing system that sends trial-end events. If you do not, start with the setup checklist in the next section.

A useful test is to write the first branch of the sequence on paper before choosing a tool. If it needs only the trial-end date and the activation flag, a connector-based tool is enough. If it needs three or more product events to decide who gets Email 2 or Email 3, pick the tool that can keep those events in its segment logic without a separate spreadsheet.

Setup checklist for the trial sequence

The steps below apply to any of the four tools. Each step ends with a check you can run before the next one, which keeps a broken trigger from reaching customers.

Migration matters if you already run a trial sequence in a tool that cannot read trial-end events. Export the current contacts with their trial end dates and activation flags, then run the old and new sequences side by side for one trial cohort before you switch the old one off. Comparing cohort conversion across the switch tells you whether the new triggers are working, and it guards against a silent gap in the sequence.

Measuring the sequence

Report trial-to-paid conversion by signup cohort, not by calendar month, because conversions land after the trial ends. Add time to activation and the share of each cohort that reached the activation event, since activation is the input your emails can influence most directly. Attribute with care: an Email 4 click that comes before a conversion does not prove the email caused it. Where your volume allows, hold out a small random group from one email and compare the two groups.

Track unsubscribes and spam complaints for each email separately. A pushy message shows up quickly in those numbers, and fixing it early protects the sending domain for the rest of your lifecycle mail. For metric definitions, the metrics guide covers the terms used here. Once a customer is paying, the onboarding email guide and the churn prevention guide take over the sequence.

Connecting the billing webhooks

Every tool in this comparison relies on the same billing signals: a trial start, a trial-end warning, a conversion, a cancellation and a failed payment. Stripe's subscription webhooks guide lists these events, and it is the authoritative source for their names. Verify the webhook signature on your side before using any event to send email, so that a forged request cannot trigger a message. Log each event with its subscription identifier so you can trace a complaint back to the send that caused it.

The Stripe email integration guide covers the webhook plumbing in more detail. The short version for trial sequences is this: the pre-charge email should depend on the trial-end event and the current subscription status, read together at send time, because the status is the thing that tells you whether the message is still correct.

Which setup to choose

If your trial is card-on-file, you already use Stripe, and you want the pre-charge email working quickly, Loops is the simplest route, and its $99 a month plan keeps the cost predictable as contacts grow. If activation depends on rich product events and the sequence has to branch on them, Customer.io is the stronger base, and the Customer.io vs Loops comparison sets out the trade-offs between the two. If your team is small and wants messages, in-app prompts and account-level segments together, Userlist covers that in one place at $149 a month for up to 10,000 users.

If you want a short trial sequence with transactional sends on one account, Loops is one of the options to compare. Its Early Stage plan is free up to 4,000 sends in any rolling 30 days, and Growing Audience is $99 a month. Confirm that your event payload contains the trial and conversion states before you commit the sequence design. For a broader view of the category, the free-trial platform list covers more tools.

Frequently asked questions