Onboarding activation

Move new users from account creation to first product action without rewriting the same welcome flow.

Open linked layout View Core

Workflow assembly

Trigger to production output

Trigger

Real send event

Workflow

Message journey

Layout

Complete structure

Components

Reusable blocks

Email

Production output

Workflow structure

Sent after a user creates an account but before activation milestones are complete.

Goal

Drive first meaningful action and reduce first-week drop-off.

Layout

SaaS Welcome System

Core included

This workflow is part of Core and remains included in Pro. Use it as a starter production system, then move to Pro when recurring lifecycle, transactional, campaign, and newsletter work needs the full archive.

Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.

What the production package needs.

A workflow is useful when the implementation contract is visible before anyone starts editing markup.

user.first_name

Example: Amelia

Recipient personalisation for the opening line.

account.verify_url

Example: https://app.example.com/verify?token=abc123

Primary activation destination.

support.contact_url

Example: https://app.example.com/support

Fallback support route for blocked users.

Variant routes

No-activity reminder: Follow-up send when activation has not happened within 48 hours.
Partially complete profile: Alternative copy when setup started but was not finished.

Package access

Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
Core archive: MJML source, compiled HTML, preview, and setup guidance for this starter workflow.
Pro archive: this workflow plus the full recurring workflow set, QA notes, implementation guidance, Studio waitlist priority while Studio is in development, and updates.

Linked production layout

SaaS Welcome System

Welcome email recipe for SaaS products, combining an onboarding hero, step card, app-download route, and onboarding footer.

Component stack

Header, Welcome Email Hero, Onboarding Step Card, App Download Strip, Footer Onboarding Legal

Source file

welcome-email.mjml

Open layout

QA and handoff.

The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.

QA risks to review

Long first names can wrap in hero lines on narrow mobile clients.
Verification links with long query strings can force horizontal overflow in some ESP editors.

Handoff steps

Edit copy and block order in MJML, keeping utility and footer sections unchanged unless requirements demand it.
Compile MJML to HTML and run client checks in Gmail, Outlook Desktop, and Apple Mail before handoff.
Import compiled HTML into the ESP, map merge variables, and send an internal seed round for QA sign-off.

Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.

Start with this workflow in Core.

Core is enough when the essential starter workflows solve the immediate implementation. Pro is the upgrade when the same source-to-handoff process becomes recurring work across more sends.

View Core