Choosing the right automation platform matters less than what you actually build inside it — see my breakdown of automation tools by startup stage for the platform decision itself. This is the workflow layer: the five automations that consistently move the needle for SaaS companies, regardless of which platform runs them.
1. Onboarding activation workflow
Triggered at signup, this workflow's only job is getting a new user to their first meaningful "aha" moment — not just logging in, but completing the action that correlates with retention. Map the specific action that predicts long-term usage in your product, and build the workflow entirely around nudging toward it, rather than sending a generic welcome sequence.
2. Trial-to-paid nurture workflow
For trial-based SaaS, this workflow should be triggered by usage milestones inside the trial, not just calendar days elapsed. A user who's hit key feature milestones by day 3 needs a different message than one who's logged in once and gone quiet — treating both the same wastes the workflow's most valuable lever: relevance to actual behavior.
3. Dunning / failed payment recovery workflow
Failed payments are one of the highest-leverage automations in SaaS because the customer already wants to keep paying — the failure is usually an expired card or a bank decline, not a decision to churn. A sequence of retry attempts paired with clear, non-alarming emails recovers a meaningful share of failed payments that would otherwise silently churn.
4. Product-led upsell / expansion workflow
Triggered by usage hitting a plan's limits (seats, API calls, storage) rather than by a fixed time interval, this workflow reaches the customer at the moment expansion is most relevant to them — not on an arbitrary quarterly cadence disconnected from actual need.
5. Churn-risk re-engagement workflow
Triggered by a drop in usage frequency or depth relative to a customer's own historical baseline, this workflow should reach out before cancellation, not after. The trigger needs to be relative to each account's own normal usage pattern — a drop that's alarming for a power user might be normal variance for a light user.
| Workflow | Best Trigger | Common Mistake |
|---|---|---|
| Onboarding activation | Signup, sequenced toward the key "aha" action | Generic welcome emails unrelated to the specific activation action |
| Trial-to-paid nurture | Usage milestones, not calendar days | Same sequence sent regardless of actual trial engagement |
| Dunning recovery | Failed payment event | A single retry attempt with no follow-up sequence |
| Expansion / upsell | Usage hitting plan limits | Fixed quarterly upsell emails disconnected from actual usage |
| Churn-risk re-engagement | Usage drop relative to account's own baseline | A single account-wide usage threshold applied to all customers equally |
FAQ
What's the most commonly missed marketing automation workflow in SaaS?
Dunning (failed payment recovery) is the most commonly under-built workflow relative to how much revenue it protects. Failed payments are usually a card expiration or bank decline, not a decision to churn, so a retry sequence paired with clear emails recovers a meaningful share of revenue that would otherwise silently lapse without anyone noticing until the customer is gone.
- Dunning failures are often invisible until reporting specifically breaks them out from voluntary churn.
- A multi-attempt retry sequence recovers significantly more than a single retry.
Should SaaS trial nurture emails be triggered by calendar days or usage milestones?
Usage milestones produce better results than calendar-day triggers, because trial engagement varies enormously between users. A user who's hit key feature milestones by day three needs a different message than one who's logged in once and gone quiet — sending both the same generic day-based sequence wastes the workflow's biggest advantage: relevance to actual behavior.
- Usage-based triggers let the workflow respond to what a specific trial user has actually done.
- Calendar-only sequences treat highly engaged and disengaged trial users identically.