Trial Expiration Emails That Convert Free Users to Paid
A trial expiration email is the message that turns a free user's accumulated habit into a paid decision. Most trial users don't decide at signup — they decide in the final days, when the deadline forces a choice. That's why the trial expiration email carries more weight than any onboarding message you send. It has three jobs: recap the value the user actually got, remove the specific friction blocking the upgrade, and make the next step obvious.
Treat it as a short sequence, not a single send. Three to four messages over the final week, each with a distinct purpose, consistently outperform a lone "your trial ends tomorrow" blast. The sequence below is built for a 14-day trial; a 7-day trial compresses the same logic into four days.
Why the trial expiration email decides the upgrade
Onboarding emails teach people how to use the product. Trial expiration emails ask them to commit to it. Those are different conversations, and the second one is harder because the user has to weigh cost, effort, and risk in a single moment.
The sequence works because each message answers a different question. The first reminds the user what they've already built or learned. The second addresses the reason they're hesitating. The third states the deadline plainly. The fourth catches the people who let it lapse.
If you send only one email, you're betting that every user reaches the same decision at the same moment. They don't. Some are ready on day -7; others need the deadline to feel real before they move.
When to send each message in the sequence
| Timing | Message | Job |
|---|---|---|
| Day -7 | Value recap | Remind them what they've done and what it's worth |
| Day -3 | Objection handling | Remove the specific reason they're hesitating |
| Day -1 | Deadline | State the exact expiry time and the upgrade path |
| Day 0 | Last call | What happens to access and data at expiry |
| Day +1 to +3 | Win-back | One easy way back in, no guilt |
For a 7-day trial, collapse this to day -3 (recap), day -1 (objection + deadline combined), and day +1 (win-back).
The sequence should branch on behavior. A user who logged in twice and created nothing needs a different message than one who ran twenty reports. Mailerflow automations can trigger on dates, events, and inactivity, so you can split the flow: activated users get the value recap, inactive users get a "here's what you haven't tried yet" angle. The automation builder handles waits and conditions visually, and you can describe the whole branching flow in a sentence to get a draft you review before activating.
Template 1: The value recap (send 5-7 days before expiry)
Subject: Your [product] trial — here's what you built Preview: A quick recap before your trial ends on [date].
Hi [first name],
You've been using [product] for about a week now. Here's what you've done so far:
- [Number] projects created
- [Number] reports run
- [Feature] set up on [date]
You signed up because [outcome they wanted — e.g. "you wanted to stop building reports by hand"]. That's exactly what [feature] is doing for you.
Your trial ends on [date]. If you'd like to keep everything you've built, upgrading takes about two minutes:
[Upgrade to [plan] →]
Any questions before then, just reply.
[Name]
When to adapt: For low-activity users, replace the recap list with what they haven't tried yet — one specific feature tied to their stated goal. For high-activity users, lead with the numbers and skip the explanation.
How to populate it: Pull the recap fields from event data, not from guesses. If your product tracks logins, items created, or reports run, those events can feed dynamic fields in the email. In Mailerflow, dynamic segments can be built on fields, tags, engagement, events, and website behavior, so the same template renders differently per contact without you writing separate versions.
Template 2: Objection handling (send 2-3 days before expiry)
Subject: Before your trial ends — a few honest answers Preview: Price, timing, and approval — the three things people ask us.
Hi [first name],
Your trial ends [date]. Before it does, here are the three questions we get most often:
"Is it worth the price?" [Plan] is [$X/month]. Most users replace [manual task] that took [time] a week — if that's true for you, the math is straightforward. If it isn't yet, don't upgrade.
"I haven't had time to evaluate it." Fair. Reply and I'll extend your trial by [X] days, or send you a 15-minute walkthrough of the one feature most relevant to [their use case].
"I need approval first." I can send a one-page summary you can forward — pricing, what's included, and a security overview. Just reply.
[Upgrade to [plan] →] · [Reply for an extension]
[Name]
When to adapt: Don't cram all three objections into every send. Look at your replies and support tickets, find the one that dominates, and lead with it. The other two become secondary lines.
Format note: This is the email where plain text often beats a designed layout. It reads like a person answering a question, not a campaign. Test both — Mailerflow's A/B testing can compare a plain-text version against a designed one on the same campaign.
Template 3: The deadline email (send the day before expiry)
Subject: Your trial ends tomorrow at [time] Preview: What happens to your [data/projects] after that.
Hi [first name],
Your [product] trial ends tomorrow, [date], at [exact time in their timezone].
After that:
- Your [projects/reports] stay saved, but you'll lose access to [key feature]
- [Any data retention detail — e.g. "exports remain available for 30 days"]
To keep everything running:
[Upgrade to [plan] →]
Not ready? You can [downgrade to the free plan / export your data / pause your account] instead — no penalty either way.
[Name]
When to adapt: State the exact expiry time in the recipient's timezone. "Your trial ends soon" gets ignored; "tomorrow at 4:12pm your time" doesn't. Keep the body under 120 words. The secondary path matters — it stops the email from feeling like a trap and often increases trust enough that people upgrade anyway.
Template 4: The post-expiry win-back (send 1-3 days after expiry)
Subject: Your [project] is still here when you're ready Preview: No pressure — just a way back in.
Hi [first name],
Your trial ended on [date], but the [report/dashboard/project] you built is still saved.
The thing you used most was [feature] — [one line on what it did for them]. If that's still useful, you can pick up where you left off:
[Restart with [plan] →]
If now isn't the right time, that's fine. Reply and I'll close your account cleanly, or leave it and come back whenever.
[Name]
When to adapt: If you don't retain data after expiry, say so plainly and offer a fresh start instead of implying their work is waiting. This is also the right slot for a time-limited incentive — but only if it's genuine. A fake "expires in 24 hours" offer that reappears next week costs you more trust than it earns.
Subject lines and preview text that match each stage
| Stage | Subject options | Preview text |
|---|---|---|
| Value recap | "What you built in [product]" / "Your trial, in numbers" | "A quick recap before [date]." |
| Objection | "Before your trial ends — honest answers" / "The three questions we get most" | "Price, timing, approval." |
| Deadline | "Your trial ends tomorrow at [time]" / "[Date] is your last day" | "What happens to your data after." |
| Win-back | "Your [project] is still here" / "No pressure — just a way back" | "Pick up where you left off." |
Keep subject lines under roughly 50 characters where you can. Preview text should extend the subject, not repeat it. Avoid ALL CAPS and manufactured urgency. And be careful with the word "free" in subject lines — it can trip spam filters depending on your sending reputation.
The AI email builder can generate subject line and preview text variants from a short description, which is useful for producing options fast. Pick the ones that match your voice rather than shipping the first draft.
How to personalize without sounding like a robot
First-name personalization is table stakes and barely registers. Behavior is what makes a trial ending email feel written for one person.
Generic: "Hi Sarah, we hope you're enjoying your trial!"
Behavior-based: "Hi Sarah, you ran 14 reports this week — mostly on the [feature] tab. That's the workflow your trial was built for."
The second version requires event data, not guesswork. Build the sequence around two or three splits: activated vs. not activated, used feature A vs. feature B, engaged with emails vs. ignored them. Dynamic segments on fields, tags, engagement, events, and website behavior let you do this without maintaining separate lists.
Website-behavior data is underused here. If you know which pricing or feature pages a contact read, the recap can reference the right feature instead of the most popular one. Over-personalization backfires, though — referencing a page someone visited once can feel surveillant. Stick to behavior that's clearly in-product.
If building these splits manually is slow, AI segmentation from a plain-language description ("users who logged in fewer than three times and never created a project") gets you the segment without writing filter logic by hand.
Mistakes that kill trial conversion
Sending one email instead of a sequence. A single send catches only the users who were already decided. Fix: build the four-message flow.
Hiding the price until the last message. Users who don't know the cost can't decide, so they stall. Fix: put pricing in the objection-handling email, not just at checkout.
Linking to a generic pricing page. It forces a comparison task at the worst moment. Fix: link to the specific plan that matches their usage.
One sequence for everyone. Activated and inactive users need different messages. Fix: branch on event and inactivity triggers.
Fake countdown timers. They work once and damage trust permanently. Fix: use the real expiry date and time.
Sending trial emails from a shared domain. Trial sequences often get high complaint rates, which hurts deliverability for everything else. Fix: send from your own domain with DKIM, SPF, and DMARC configured, and let automatic suppression handle bounces and complaints.
No post-expiry follow-up. Most lapsed trials are recoverable weeks later. Fix: add the win-back and a second touch at day +14.
Treating the email as a pitch. The trial expiration email is a decision aid. Users can tell the difference, and they respond better to the version that helps them decide.
FAQ
How many emails should a trial expiration sequence have? Three to four for a standard 14-day trial: a recap, an objection-handling message, a deadline email, and a post-expiry win-back. Longer trials can support a fifth touch earlier in the sequence.
How far in advance should the first trial ending email go out? About a week before expiry for a 14-day trial. That's enough time to act without feeling premature. For a 7-day trial, start at day -3.
Should the trial expiration email include pricing? Yes, at least by the objection-handling message. Withholding price until the last moment creates a stall, not urgency. State the plan and what's included.
What if the user never activated during the trial? Don't send a value recap — there's no value to recap. Send a "here's the one thing to try" email with a single concrete action, and consider extending the trial rather than pushing an upgrade.
Can we extend the trial instead of pushing an upgrade? Yes, and for users who engaged but ran out of time, an extension often converts better than a discount. Offer it as a reply-based option so it stays personal and doesn't become an expectation for everyone.
If you'd rather not build the branching logic by hand, describe the sequence in a sentence — trigger, waits, conditions, emails — and Mailerflow drafts the workflow for you to review before it goes live. Start free and have the first version running today.
