Welcome Email for SaaS

Trigger and timing. Send the welcome the instant signup confirms, not inside a 24-hour nurture window. In SaaS the activation window is brutal. Users who reach their first value moment in the first session retain at 2 to 3 times the rate of users who leave and come back tomorrow. Fire the email from your product event stream within 60 seconds of the signup webhook. Wait an hour and half your trial signups have already ghosted.

The offer is not a discount. Retail welcome emails hand out 15 percent off and free shipping. That model breaks for software, where the thing you sell is a working habit, not a cart total. Your offer is a single named next step that produces value inside the product: connect your first data source, ship your first preview deploy, flip your first feature flag, send your first test event. Name it in the subject line, repeat it in the hero, and make it the only button.

Copy angle: helpful, not hyped. Write it from the product or engineering team, not the marketing crew. Short sentences, one idea per line. Subject lines should read like a quiet internal ping, not a sale: "Your Forge workspace is ready", "One step left: flip your first flag", "Riya, your trial ends in 14 days. Here is the 5-minute start." Cut the exclamation-mark pileup that signals a blast.

The CTA: one button, one job, linked straight into the logged-in product at the exact screen for the activation step. "Open Forge", "Finish setup", "Flip your first flag." Deep-link past the dashboard to the flag-creation screen and you lift click-to-activation by a measurable margin. Drop the "follow us on Twitter" row and the "rate us on G2" row. Those belong in a day-7 email, not the welcome.

Numbers you can plan against. SaaS welcome emails usually open at 50 to 60 percent and click at 4 to 8 percent, well above the 20 percent open and 2 percent click you will see on later lifecycle mail. The metric that actually matters is activation rate within 24 hours of send, not open rate. Track the click to a product event and tie it to 7-day retention.

Real example (Forge, a feature-flag tool). Subject: "Your Forge workspace is ready." Preheader: "Flip your first flag in under five minutes." Hero headline: "Your workspace is ready. One step left." Body: "You signed up to ship behind a flag. The fastest way to feel it work is to create one flag, target it to yourself, and reload your app. It takes about four minutes." Button: "Flip your first flag."

Klaviyo and Mailchimp both render whatever HTML you paste, then hand it to Gmail, Apple Mail, and Outlook. Outlook desktop still runs the Word rendering engine, which ignores flexbox, ignores border-radius on anchors, and ignores most CSS written after 2009. This template ships as nested HTML tables, not divs, so structure survives every client including Outlook.

Inline CSS on every element. Gmail strips your style block when it sits in the body, and several webmail clients keep only inline styles. Every text size, padding, and color lives on the element it styles, so nothing vanishes in transit.

Bulletproof button for Outlook. The call-to-action is a real anchor inside a table cell, with a VML rectangle fallback wrapped in Outlook conditional comments. Word-engine Outlook users see a solid filled button with working corners instead of a gray rectangle or a link with no background. MJML writes this VML for you when you use the button component, and the compiled output carries 33 MSO conditionals.

Live text, not image text. The headline and body are selectable text, not PNGs. Image-only emails arrive blocked by default in many clients, and screen readers need real text to read your headline aloud. The product wordmark is the only image, hosted on a stable CDN URL.

Dark-mode safety. The head carries a color-scheme meta (light dark) so Apple Mail and Outlook dark modes auto-invert the light surfaces instead of leaving a blinding white card. Text colors pick slate tones that hold up on both light and dark backgrounds. The template avoids pure black on pure white.

One mobile media query. A single max-width:480px query bumps font sizes and collapses the three-step row into a single stack. No hover states, no animation. Mobile clients ignore them or break on them.

Web fonts with fallbacks. The font stack starts with system fonts (Apple System, Segoe UI, Roboto, Helvetica, Arial). If you load Inter or IBM Plex via a web font, the system font fills in for every client that blocks remote fonts, which is most of them.

1. Copy the HTML. Use the Export HTML button on this page. It compiles the MJML into one self-contained HTML file with all CSS inlined.

2. Paste it into your ESP. In Klaviyo, create a new email and pick Code Email (not Drag and Drop), then paste the HTML into the source view. In Mailchimp, start a campaign, select Code Your Own, then Paste In Code. Both editors accept the raw table HTML without reflowing it.

3. Swap brand and links. Replace the "Forge" wordmark, the indigo (#4F46E5) and slate (#0F172A) hex values, and every href with your own. The hex values live in the attributes block at the top of the MJML, so a single edit recolors the whole email if you rebuild from source.

4. Wire the merge tags. This is where SaaS differs from retail. You are not dropping in a first name and a coupon. You are dropping in product state. In Klaviyo, use {{ first_name|default:'there' }} for the greeting, {{ workspace.name }} for the workspace, {{ plan.name }} for the plan, and {{ trial.ends_at|date:'short' }} for the trial countdown. In Mailchimp, the equivalents are *|FNAME|*, *|WORKSPACE|*, *|PLAN|*, *|TRIAL_END|*, with *|FNAME|* falling back to a default you set inside the merge-tag settings. Map these to the signup event payload you already send from your product database.

5. Test before you send. Run a real send to a seed list that includes Outlook desktop on Windows, Gmail web, the Apple Mail app on iOS, and Apple Mail in dark mode. Look at the button in Outlook and confirm it fills with color. Confirm the preheader shows under the subject. Click the CTA on a phone and confirm it deep-links into the logged-in product, not the homepage.