A SaaS needs five automated email workflows: welcome and onboarding, activation nudges, a trial-ending or upgrade flow, win-back for lapsed users, and transactional email such as receipts and password resets. Build them roughly in that order, start with the one that touches every new signup, and measure each by the product action it is supposed to cause rather than by opens.

Below: what each workflow does, the order to build them in, what to measure, and the sender rules to check before the first send.

The five workflows at a glance

  • Welcome and onboarding: triggered by signup. Gets the new user to a first useful action.
  • Activation nudges: triggered by a missing action. Reaches people who signed up and stalled.
  • Trial-ending or upgrade: triggered by the trial clock or a usage limit. Shows what the user built and the next step.
  • Win-back: triggered by inactivity or cancellation. Gives one specific reason to come back.
  • Transactional: triggered by an account event. Verification, receipts, invoices, password resets.

All five are trigger-based. A newsletter goes to a list on a date you chose. An automated workflow goes to one person because of something they did, or something they did not do after a set number of days. Userpilot's guide to SaaS email automation warns against fixed-date emails such as a win-back sent 30 days after last login, because they ignore what the user has actually done.

Transactional and marketing email follow different rules

Transactional messages are needed to use the product: password resets, email verification, receipts. Marketing messages try to change behavior: nudges, upgrade prompts, win-backs. Google's sender FAQ says one-click unsubscribe is required only for marketing and promotional messages, and that transactional messages are excluded, with password resets, reservation confirmations and form-submission confirmations as examples.

The line is narrower than it looks. The FTC's CAN-SPAM guide lists five categories of transactional or relationship content, such as confirming a transaction the recipient already agreed to, and says the law views these categories narrowly. When a message mixes both kinds, the primary purpose decides, and a subject line that reads as commercial makes the whole message commercial. Google adds that recipients, not Google, determine the nature of a message. A trial-ending email with an upgrade button is marketing in practice, so give it an unsubscribe link and a postal address.

If your email platform allows it, send the two kinds from separate streams. A burst of complaints about a promotional nudge should not slow down someone's password reset.

1. Welcome and onboarding

Trigger: account created, or email verified if you require verification. Send it immediately, because the user is looking at your product right now. The first email confirms the account and names one next action. It does not tour every feature. A full five-email structure with timing, subject lines and tracking is in our onboarding sequence guide.

2. Activation nudges

Start by defining activation for your product: the one in-product action most associated with users who stay. For a form builder it might be publishing a first form, for an analytics tool installing the tracking snippet. Your own data tells you which.

The workflow is then short. Signed up, activation event not done after a set number of hours, send one email about that event, and stop the moment the event happens. Kompassify's onboarding guide calls these stop conditions the most important thing to build first, since continuing to email someone about a step they already finished costs deliverability and goodwill.

3. Trial-ending and upgrade

Trigger: two to three days before the trial ends, which is the window Kompassify suggests, or a free-plan user hitting a usage limit if you do not run trials. The email shows what the user did in the product, says what happens when the trial ends, and has one button. Kompassify and Userpilot both recommend recapping the user's own work over a generic countdown.

Skip anyone who already converted. Treat users who never activated as a separate case: in our view, an offer of help with the step they stalled on beats an upgrade push, since they have not yet seen what they would be paying for.

4. Win-back

Two audiences get mixed up here. Lapsed trial users never paid, and churned customers did, so write separate emails. Trigger on no login or no key action for a period that fits your product's normal rhythm. A tool people open weekly lapses faster than one they open quarterly, and the number should come from your usage data.

Send one email with one specific reason to return: a feature they asked about shipped, pricing changed, or their data is still there. Userpilot describes a 90-day re-engagement path for silent users, followed by suppressing people who never respond, which protects deliverability for everyone else on your list.

How to prioritize when you cannot build all five

The order follows two questions: how many users does the workflow reach, and how close is it to a payment? Welcome reaches the most users, trial-ending sits closest to payment, and win-back is last on both counts.

  1. Audit transactional email. Verification, receipt and reset emails usually exist already. Check that they send from your own domain and carry no promotional content. It takes an afternoon, and a broken reset email loses users without anyone noticing.
  2. Build the welcome flow. Every new signup passes through it, so a small improvement applies to everyone.
  3. Add one activation nudge, for the single activation event you defined.
  4. Add the trial-ending email, which reaches users while they still have the product open.
  5. Add win-back last. It reaches the fewest people, and they are the coldest.

What to measure

Measure each workflow by an outcome inside your product. Open rates are unreliable: Apple's Mail Privacy Protection preloads images, including tracking pixels, so Postmark warns that you could see a 100% open rate for Apple Mail recipients, and it turns pixel-based open tracking off by default. Clicks, product events, unsubscribes, bounces and spam reports are sturdier signals.

  • Welcome: share of recipients who complete the first action within a window you choose, such as 48 hours.
  • Activation nudge: activation rate for users who received it, compared with a small holdout that did not if your volume allows, or with the cohort before launch.
  • Trial-ending: trial-to-paid conversion among recipients, split by users who activated and users who did not.
  • Win-back: reactivations (a login or key action) per send, plus unsubscribes.
  • Every workflow: unsubscribe rate, bounce rate and spam-complaint rate.

Hostinger's onboarding guide advises against reacting to one cohort or a short-term swing, so wait for a repeated pattern before rewriting a workflow.

Deliverability and compliance checks before the first send

Google defines a bulk sender as one that sends close to 5,000 or more messages a day to personal Gmail accounts, and a sender that crosses the line stays classed as a bulk sender. Most early-stage SaaS products send far less, but the practices are cheap, so adopt them from day one. CAN-SPAM has no volume threshold: the FTC guide says it covers all commercial messages, with no exception for business-to-business email.

  • Authenticate your sending domain with SPF and DKIM and publish a DMARC record. Google requires DMARC for bulk senders and accepts a policy of none. Yahoo asks bulk senders for SPF, DKIM and a DMARC policy of at least p=none.
  • Support one-click unsubscribe on marketing messages through the List-Unsubscribe headers, and keep a visible unsubscribe link in the body.
  • Process unsubscribes quickly. Yahoo says within 2 days, Google recommends 48 hours, and CAN-SPAM allows up to 10 business days. Design for the shorter window.
  • Keep spam complaints low. Google says to stay below 0.10% in Postmaster Tools and never reach 0.30%. Yahoo says below 0.3%.
  • On marketing email, include a valid physical postal address, accurate sender fields and a subject line that matches the content.

This is a summary of the linked sources, not legal advice, and sender requirements change, so read the current pages before you launch.

If you would rather have these sequences written and set up in your own email platform, the Automated Email Sequence and Email Campaign Setup offers are the place to start, and the Email Marketing Automation page describes the service.