10 Welcome Email Examples for SaaS (and How to Send Them)

A welcome email is usually the first message a new user gets from your SaaS. It arrives seconds after they sign up, when they're most ready to take a first step. The welcome email examples below are original mock-ups for different kinds of SaaS, each with a short breakdown of why it works.

Use them as starting points, not scripts. Placeholders in square brackets, such as [First name] and [Product], show where your own details go.

At the end, you'll see how to hand the job to Claude Code: describe the email you want, review the draft, and let Claude Code build and test it.

10 welcome email examples, with a breakdown of each

1. The one-step starter

SubjectYou're in, [First name]. Here's your first step

Hi [First name],

Welcome to [Product]. The fastest way to see what it can do is to create your first project. It takes about two minutes.

Button: Create your first project

If you get stuck, reply to this email and we'll help.

The [Product] team

Why it works: It asks for one action, not five. A single button leaves nothing to weigh up, and the reply line shows there are people behind the product.

2. The three-step checklist

SubjectThree steps to get [Product] ready

Hi [First name],

Welcome aboard. Most people are up and running after these three steps:

1. Add your logo and business name
2. Connect your calendar
3. Share your booking page

Button: Start step 1

Do them in any order. Your progress saves as you go.

Why it works: Some products, like this booking tool, need a little setup first. A short numbered list shows how much is left, and "in any order" takes the pressure off.

3. The founder's note

SubjectA quick hello from [Your name]

Hi [First name],

I'm [Your name], and I built [Product] because [one-line reason]. Thanks for signing up.

One question: what made you sign up today? Hit reply and tell me. I read every reply.

[Your name], founder of [Product]

Why it works: A plain-text note from a named person feels personal, and the question starts a conversation that tells you what new users came for. Only promise to read replies if you will.

4. The free trial welcome

SubjectYour free trial of [Product] has started

Hi [First name],

Your trial runs until [Trial end date], and you get every feature on the [Plan name] plan until then.

A good first step: [one action that shows the product's value].

Button: Get started

We'll email you three days before your trial ends, so there are no surprises.

Why it works: It states the end date and what happens next, so the trial ending never feels like a trick. Pair it with a trial ending reminder that keeps the promise.

5. The paid plan welcome

SubjectWelcome to [Product] [Plan name]

Hi [First name],

Thanks for subscribing. Here are your plan details:

Plan: [Plan name], [Price] per [month or year] Next payment: [Date]

You can change your plan or download receipts any time from your billing page.

Now unlocked: [Feature 1] and [Feature 2].

[Button: Try [Feature 1]]

Why it works: Someone who has paid wants to know the payment went through. Leading with the plan details answers that, then points them to what they paid for.

6. The team member welcome

SubjectYou've joined [Team name] on [Product]

Hi [First name],

[Inviter name] added you to [Team name]. You can now see and edit [what the team works on].

Your teammates are already working in [main area]. That's the best place to start.

[Button: Open [Team name]]

Why it works: A colleague chose the product, not this person. The email says who brought them in and where the work already is, rather than giving a product tour.

7. The goal-based welcome

SubjectLet's get your first [goal] done

Hi [First name],

You told us you want to [goal from sign-up]. Here's the quickest way: [the one step for that goal].

Button: Do it now

Want to start somewhere else? [Other goal 1] · [Other goal 2]

Why it works: If your sign-up form asks one question, the welcome email can use the answer. The reader gets a first step that matches why they came, not a generic one.

8. The help-first welcome

SubjectWelcome to [Product]. Here's where to get help

Hi [First name],

There's a lot in [Product], so here's where to turn when you need a hand:

• [Getting started guide]: the basics in five minutes
• [Short video]: a two-minute tour
• Reply to this email: our team answers within [response time]

Button: Open the getting started guide

Why it works: In a product with lots of features, knowing where help lives stops people giving up quietly. Three clear options beat a long feature list.

9. The waitlist-to-welcome email

SubjectYour [Product] access is ready

Hi [First name],

Thanks for waiting. Your account is ready, and you're one of the first people using [Product].

Button: Set your password and log in

Because you're early, your feedback shapes what we build next. Reply any time.

Why it works: People who joined a waitlist want to know the wait is over, and the subject line tells them. Inviting feedback rewards them for being early.

10. The short confirmation

SubjectWelcome to [Product]

Hi [First name],

Your account is ready. You can log in any time at [login link] with [email address].

Button: Log in

Questions? Reply to this email.

Why it works: Not every product needs a tour. For a focused tool, confirming the account and how to log in is enough.

What do the best welcome emails have in common?

Good welcome emails confirm what happened, give one clear next step and invite a reply. Here's where those patterns show up above.

A few more habits help:

• Send it straight away. It should go out the moment the account is created, not in a nightly batch.
• Lead with the account, not a sale. The first message should be about what the person signed up for.
• Use the preview line. Most inboxes show the first line of text next to the subject, so make that line useful rather than "View this email in your browser".
• Plan what comes next. A welcome email starts onboarding but doesn't finish it. For the emails that follow over the first few days, see onboarding emails for your SaaS.

How do you send your welcome email with Claude Code?

Connect SimpleSends once, then describe the welcome email you want to Claude Code in a normal message. Claude Code drafts the email, connects it to your sign-up flow and sends you a test before any real user sees it.

SimpleSends is a transactional email service: it delivers the emails your product sends automatically, such as welcome emails and password resets. Claude Code talks to it through a connector, also called an MCP server, which lets Claude Code use SimpleSends while you build.

1. Sign up on the SimpleSends website and follow the steps there to set up the email address you'll send from. To send from your own domain, such as hello@yourcompany.com, this includes adding a few DNS records (settings that tell email providers your domain is allowed to send) where your domain is registered.
2. In Claude Code, open Customize, then Connectors, choose Add, then Add custom connector. Fill in these details:

3. When Claude prompts you to connect, log in to SimpleSends.
4. Back in the Claude Code chat, tell Claude Code: "I've connected SimpleSends for all transactional email." It takes it from there, including adding what your project needs to send email.

Then brief Claude Code on your welcome email the way you'd brief a copywriter:

When someone signs up, I'd like them to get a welcome email like the one-step starter in this guide. The first thing new users should do is create a project, so make that the button. Keep it short and friendly, sign it from the [Product] team, and send me a test before it goes live.

Claude Code drafts the wording and design and shows you a preview. It then connects the email to your sign-up, so it goes out whenever someone creates an account, and sends a test to your inbox. Ask for changes in plain English: "Make it shorter" or "Use our brand color for the button." See how to brief Claude Code like a copywriter, and before launch, test your emails as a new user would see them.

Once your project is live, it sends each welcome email through SimpleSends, and Claude Code doesn't need to be open. If a new user says theirs never arrived, ask Claude Code. It can read your send logs through SimpleSends and tell you whether the email went out.

For a full walkthrough of this one email, see how to send a welcome email when someone signs up. For the other emails your SaaS will need, see 12 transactional emails every SaaS needs.