What Should a SaaS Trial Expiry Email Say?

Why do most SaaS trial expiry emails fail to convert?

Because they talk about the deadline instead of the decision. A typical expiry email says "your trial ends in three days" and links to the pricing page. The buyer already knew that. What they need is help deciding whether the product solved their problem, what they lose by walking away, and what the next step costs.

I review a lot of B2B SaaS lifecycle email as part of go-to-market work, and the trial expiry message is often the weakest one in the sequence. It is usually written once, at launch, by whoever had time. Then it runs for years while the product, the pricing, and the buyers all change around it.

That is a waste, because this email lands at the exact moment a buyer is deciding. Few messages in your whole funnel get more attention. Here is what I think it should say, and how to structure it so it helps the buyer make a clear choice.

What is a trial expiry email supposed to do?

A trial expiry email has one job: help a trial user make a clear decision before access ends. That decision can be to buy, to ask for more time, to talk to someone, or to leave. A good expiry email makes each option easy. A bad one only pushes the buy button and hopes.

That framing changes what you write. If the goal is a clear decision, then a fast "no" is better than silence. A buyer who replies "not for us, we went with another tool" gives you a reason you can learn from. A buyer who ignores the email gives you nothing.

It also changes how you measure the email. Conversion to paid matters most, but replies, extension requests, and booked calls are useful outcomes too. Track all of them. An email that gets fewer upgrades but far more honest replies might still be the better email.

What should the subject line and first sentence say?

Say what is changing and when, in plain words, then move straight to value. A subject like "Your trial ends Friday, here is what you set up" works better than "Don't miss out." The first sentence should name the date and one concrete thing the user did in the product.

Specific beats urgent. If your product tracks usage, pull one real detail into the opening line. "You connected your HubSpot account and built two reports" tells the buyer you noticed, and it reminds them what they would lose. Generic urgency like "Time is running out" reads like every other promotional email in the inbox.

If you do not have usage data, be honest about it. "Your trial ends on Friday. Here is a quick way to decide if it is worth keeping" is still clear and calm. What you should avoid is pretending to know things about their usage that you do not.

Should the email change based on how the trial went?

Yes, and this is the single biggest improvement most teams can make. A user who activated and used the product weekly needs a different message from a user who signed up and never logged in again. Sending both the same email wastes the one moment when each of them is paying attention.

I like to split trial users into three groups. Active users who reached your activation milestone get an email focused on keeping their work and choosing a plan. Partly active users who started but stalled get an offer of help, such as a short call or an extension. Inactive users get a short, honest note asking if the timing was wrong.

The data for this usually already exists. If your product sends events to a tool like Segment, Mixpanel, or Amplitude, or straight into HubSpot, you can branch the email on a single property such as "activated" or "last active date." It does not need to be clever. Two or three branches beat one message for everyone.

What should active trial users hear?

Show them what they built and what happens to it. List the work they created, explain whether it stays, goes read-only, or gets deleted when the trial ends, and name the plan that fits how they used the product. Then make upgrading a single click from the email.

The "what happens to my data" question is the one buyers worry about most and the one emails answer least. Be precise. If projects stay available for 30 days after expiry, say so. If they disappear immediately, say that too, with a clear warning. Vague language here creates anxiety and support tickets.

Recommend a plan rather than sending them to a pricing page with four options. If they used features that only exist on one tier, name that tier. If a team member joined during the trial, mention the seat count. The fewer decisions you leave them, the easier the yes becomes.

What should stalled or inactive users hear?

Offer help, not pressure. A stalled user hit an obstacle, and an upgrade link will not fix it. Ask what got in the way, offer a short call or a setup guide for the step where most people get stuck, and offer a trial extension if they need more time to evaluate properly.

Extensions are underused. Many B2B buyers start a trial, get pulled into other work, and come back two weeks later to find it expired. A simple "reply with extend and I will add seven days" keeps the door open at almost no cost. Some teams worry this trains people to wait. In my view, a buyer who asks for more time is still engaged, and that is worth protecting.

For users who never really started, keep it short and human. One or two sentences, a question about what they were hoping to solve, and an easy way to say "not now." Their replies are some of the most useful research you will get about who your product is actually for.

Who should the trial expiry email come from?

From a real person whose reply goes to a real inbox. For most early-stage SaaS companies, that means the founder or the person who runs customer onboarding. A no-reply sender tells the buyer you do not want to hear from them at the exact moment you most need their feedback.

This does not mean faking a personal note. Buyers can tell when a templated email pretends to be hand-written. A short, plainly formatted message from a named person, with a line that says replies come straight to them, is honest and effective. Then make sure someone actually reads and answers those replies.

As the company grows, the sender can shift to a sales or success owner, especially for accounts that match your ideal customer profile. Routing replies from high-fit trials straight to a rep is one of the simplest ways to connect product-led signups to a sales-assisted close.

What mistakes should you avoid in a trial expiry email?

The biggest mistakes are fake urgency, a wall of features, vague data-retention language, and a pricing page link with no recommendation. Others include sending the same email to every user, using a no-reply address, and never updating the copy after your pricing or packaging changes.

Fake urgency deserves its own warning. Countdown timers, "last chance" language, and invented scarcity might lift clicks in consumer email, but B2B buyers often share these emails with a manager or a finance team. A pushy message looks worse when it gets forwarded. Calm and clear travels better inside a buying committee.

Stale copy is the quiet killer. Set a reminder to reread your expiry emails every time pricing, plans, or onboarding changes. An email that names a plan you retired, or a feature you renamed, tells the buyer that nobody is paying attention.

What should you do next?

Pull up your current trial expiry email and read it as a buyer would. Check that it names the date, mentions real usage where you have it, explains exactly what happens to their data, recommends one plan, comes from a real person, and offers help or an extension. Then split it into at least two versions.

If you are rebuilding the whole trial sequence, start with my onboarding email sequence for B2B trial users, since the expiry email works best when earlier emails have already guided activation. For the question of who signs these messages, my take on whether a SaaS onboarding email should come from the founder covers the tradeoffs.

The expiry email is small, but it sits right at the moment of decision. If you want help rewriting yours or wiring the branches into your CRM and product data, reach out and let's chat.