SaaS Onboarding Email Templates

Below are nine complete templates you can paste into your ESP today, each with its trigger, delay, merge fields and exit condition. They’re written for a fictional but realistic product, Northbeam Analytics, a B2B product analytics tool where first value means connecting a data source and building one chart.

Change the specifics, keep the structure. And keep them plain text.

The nine templates

Each one is short on purpose. The merge fields in curly braces map to product data your ESP needs access to, which is listed in full further down.

1. Welcome. Trigger: signup. Delay: immediate. Exit: none.

Subject: your Northbeam account

Hi {first_name},

You’re in. The fastest route to something useful is connecting a data source, which takes about four minutes: {setup_link}

If you get stuck, reply to this email. It comes to me directly.

Priya Northbeam

2. Setup nudge. Trigger: 24 hours after signup, only if no data source connected. Exit: data source connected.

Subject: stuck on the data source step?

Hi {first_name},

Your account is set up but there’s no data flowing in yet. Most people who stall here are on {most_common_source}, and this walkthrough covers it: {docs_link}

What are you trying to connect? Happy to point you at the right doc.

3. First value. Trigger: first data source connected. Delay: 15 minutes. Exit: none.

Subject: data’s in, here’s the first chart to build

Nice work, {source_name} is connected and we’re seeing {event_count} events.

The chart most teams build first is weekly active accounts by plan. Takes about two minutes: {chart_link}

4. Invite a teammate. Trigger: day 3, only if seat count equals 1. Exit: second seat added.

Subject: who else needs to see this?

Hi {first_name},

Accounts with two or more people set up in the first week are the ones still active at day 90. Usually it’s whoever asks you for numbers on Mondays.

Add them here: {invite_link}

5. Integration prompt. Trigger: user visits the integrations page without connecting. Delay: 2 hours. Exit: any integration connected.

Subject: connecting {integration_name}

Saw you were looking at the {integration_name} integration. It’s a three-step OAuth connection and it backfills 90 days automatically.

Setup: {integration_docs}

One thing worth knowing: the backfill takes about 20 minutes, so the charts look empty for a bit.

6. Use case education. Trigger: day 5. Delay: none. Exit: none.

Subject: three things teams do with Northbeam in week one

Hi {first_name},

Not a feature list, just what people actually build first:

Churn signal report. Accounts whose weekly usage dropped 40 percent or more. Activation funnel. Signup through to first successful action. Feature adoption by plan tier. Usually the one that changes the roadmap.

Each takes under ten minutes: {templates_link}

7. Usage recap. Trigger: day 7. Exit: none.

Subject: your first week

{first_name}, here’s where you got to:

{chart_count} charts built {seat_count} people on the account {event_count} events tracked

The teams who stick with us usually have a report someone checks every Monday by the end of week two. Do you have one yet?

8. Social proof. Trigger: day 10. Exit: trial converted.

Subject: how {similar_company_segment} teams use this

Hi {first_name},

A 60-person fintech on the same plan cut their weekly reporting time from six hours to about twenty minutes, mostly by replacing a spreadsheet nobody trusted.

Short write-up here if it’s useful: {case_study_link}

9. Human reply ask. Trigger: day 13, trial ending. Exit: trial converted.

Subject: quick question before your trial ends

{first_name}, your trial ends {trial_end_date}.

I’m not going to pitch you. I want to know what didn’t work, because that’s more useful to me than a conversion.

What got in the way?

Priya

Self serve versus sales assisted variants

The nine above are the self serve set. If a rep is working the account, running all nine in parallel makes you look like two companies that haven’t met.

Email	Self serve	Sales assisted
Welcome	From a named marketer	From the assigned rep, sent manually
Setup nudge	Automated at 24h	Rep handles it. Suppress
First value	Automated on trigger	Keep. It is timely and product-specific
Invite teammate	Automated day 3	Rep asks on the call. Suppress
Integration prompt	Automated on behaviour	Keep
Use case education	Automated day 5	Keep
Usage recap	Automated day 7	Send to the rep instead, not the user
Social proof	Automated day 10	Rep sends a relevant one. Suppress
Human reply ask	Automated day 13	Suppress. The rep owns this conversation

The usage recap row is the useful trick. Same data, different recipient. A rep who opens a call with “you built four charts but nobody’s connected Salesforce yet” is running a better call than one who asks how the trial is going.

Merge fields your product needs to expose

The templates are only as good as the data behind them. If your ESP can’t access these, the emails degrade to generic copy and lose most of their effect.

Note the fallback column. The rule is that a missing merge field means suppress the email, not send it with a placeholder. “Hi there, you’ve built 0 charts” is worse than silence.

Getting this data into the ESP is usually the real project. Most teams pipe product events through Segment or a direct API integration into Customer.io or Intercom, and the setup takes longer than writing all nine emails. Budget for it. Lesson 3 of the lifecycle email course walks through shipping the first one end to end.

Editing rules

Six rules that keep the set from degrading as different people edit it over two years.

The monitored address rule gets broken constantly. Sending from priya@ and routing replies to a black hole is worse than sending from a no-reply address, because you’ve invited a conversation and ignored it. If nobody will read the replies, don’t write email nine.

On the plain text point specifically: heavy HTML with tracking-laden image headers correlates with promotions-tab placement and depresses reply rates. For onboarding, where the goal is behaviour and conversation rather than clicks on a hero button, that trade is clearly the wrong way round. The benchmarks in SaaS email benchmarks are worth reading before you argue about this with a designer.

Where to go next

Paste the nine into your ESP as drafts today, then spend the real effort on the event data behind the triggers. That’s the part that determines whether these are good emails or generic ones.

Once shipped, pull them apart against real examples in SaaS onboarding email teardowns, and if activation rather than trial conversion is your problem, the structure in activation email sequences targets it more directly. The full sequence design logic sits in the SaaS onboarding email sequence, the trial end of the lifecycle in the trial expiry email sequence, and if you want to size the upside first, the SaaS email revenue calculator will do it. Definitions worth agreeing on internally, like drip campaign, are in the glossary, and the wider programme is at SaaS email marketing.