Most marketing automation guides describe what a workflow is. This guide focuses on which workflows to build first, how to build them well, and how to know when they are working.
The gap between teams that generate real pipeline from automation and teams that generate activity reports is almost never the platform. It is the workflow design: wrong triggers, wrong content at the wrong stage, no defined goal, and no measurement that connects workflow activity to revenue outcomes.
This guide is written for B2B SaaS marketing and growth teams - not ecommerce or creator-focused operations. The workflow templates, sequencing guidance, and measurement framework are specific to the B2B buying cycle: longer sales timelines, buying committees, product-led growth motions, and sales-marketing handoffs. For the broader strategic context that determines which workflows belong in your programme, see our marketing automation strategy guide 2026.
Anatomy of a Marketing Automation Workflow
Every marketing automation workflow has the same four structural components, regardless of the platform, the use case, or the complexity of the logic:
Trigger. The event that enrolls a contact in the workflow. Triggers are either time-based (send at 9am on Tuesday), action-based (contact submits a specific form), or property-based (contact's lead score reaches 60). The quality of your trigger determines the quality of your workflow - a precise trigger produces a relevant, timely message; a broad trigger produces noise.
Conditions and branching. The logic that determines what happens next based on a contact's properties or behaviour. A condition might be: if the contact's job title contains 'Director' or above, send version A; otherwise send version B. Branching allows a single workflow to serve different segments with different content without building separate workflows for each segment.
Actions. What the workflow does: sends an email, updates a contact property, assigns a task to a sales rep, adds the contact to a list, enrolls in another workflow, or sends an internal notification. Actions are the executable steps - they are what the contact experiences or what your team is notified of.
Goal and exit criteria. The defined outcome that marks the workflow as complete for a given contact. A goal might be: contact books a demo, contact reaches SQL lifecycle stage, or contact completes a specific feature in the product. Exit criteria ensure contacts are removed from the workflow when they are no longer relevant - a contact who books a demo should exit the demo-request nurture sequence immediately, not continue receiving 'have you considered booking a demo?' emails.
A well-designed workflow has all four components defined before a single email is written. Teams that start with email copy and add logic later produce workflows that feel arbitrary to the contact because the logic is arbitrary.
Mapping Customer Journeys Before Building Workflows
A workflow cannot be better than the journey map it is built on. Before building any automation, map the journey that the target contact is on - not the journey you want them to be on, but the journey they actually take based on your data.
For B2B SaaS, the journey typically has five stages: Awareness, Consideration, Evaluation, Decision, and Expansion. Each stage has different signals, different content requirements, and different handoff points.
The four things a journey map must define to be useful for workflow design:
- Entry point and initial intent. How did this contact enter your database? Organic content download, paid ad click, trial signup, webinar registration, outbound sequence reply, referral? Each entry point implies a different initial intent and starting context. A trial signup needs onboarding. An ebook download needs nurture. A pricing page visit needs a sales-alert trigger.
- Key decision points. Where in the journey does the contact make a meaningful decision - to continue evaluating, to engage with sales, to trial the product, or to disengage? These decision points are where your most important automation triggers live. Miss them and your automation runs in the background while the contact makes decisions based on entirely different information.
- The marketing-to-sales handoff. At exactly what point does marketing ownership of the contact transition to sales? This needs to be a specific, agreed-upon trigger - not a judgment call made by whichever team notices the contact first. The handoff trigger is your MQL definition in executable form.
- Expansion and churn signals. For existing customers, what events indicate readiness to expand (seat limit approaching, feature adoption milestone, usage spike) or risk of churn (usage drop, support ticket spike, login frequency decline)? Post-sale automation is consistently the most underinvested category in B2B SaaS, and typically the highest-margin opportunity.
Document the journey as a diagram before building any workflow. Teams that skip this step build overlapping sequences that send conflicting messages to the same contact - a problem that is expensive to untangle once it is live. For how website data feeds into these journey stages, see our HubSpot Webflow integration guide.
The Highest-Leverage B2B SaaS Workflows: Templates and Guidance
The table below lists the eight workflows that produce the highest pipeline impact for B2B SaaS teams, ranked by the balance of implementation speed and revenue leverage. The sequencing guidance is specific: build what sales will notice first.
Workflow 1: Welcome and Onboarding Sequence
Purpose: Set the engagement tone, deliver immediate value, and move new contacts or trial users toward the next meaningful action.
Trigger: Contact submits a demo request form, signs up for a trial, or registers for a webinar.
Template structure for a SaaS trial onboarding sequence:
- Immediate - Welcome email (sent within 5 minutes): Confirm the trial is active. One CTA: the single most important action to take in the first 10 minutes (complete profile, connect a data source, invite a team member). No product tour links, no social proof, no ask to speak to sales. Get them into the product.
- Day 1 - Value email: One concrete outcome the user can achieve today. Specific to the product. Not 'here is everything you can do' - that is a product tour. 'Here is the one thing that takes 5 minutes and produces a result you will see immediately.'
- Day 3 - Feature activation check: Has the contact completed the day 1 action? If yes, branch to the next step. If no, re-send day 1 CTA with a different subject line and slightly different framing. Most platforms support this check via goal-based branching or conditional wait steps.
- Day 5 - Social proof email: A specific customer outcome relevant to the contact's industry or role. One sentence about the result, one quote, one link to the full case study. Not a generic 'our customers love us' email.
- Day 7 - Friction-reduction email: 'What's getting in the way?' Directly acknowledge that trials often stall, offer two or three specific resources for the most common friction points, and include an easy way to book a 20-minute call. This email should feel like it is from a human, even if it is automated.
- Day 10 - Conversion email: Make the case for upgrading. One clear CTA: upgrade or book a call. No other links. Subject line should acknowledge that the trial is ending, not pretend it is not.
Goal: Contact upgrades to paid, books a call, or reaches a specific product engagement milestone. Exit immediately on goal completion.
Workflow 2: Lead Scoring and Routing
Purpose: Identify contacts who have reached commercial readiness and route them to the appropriate sales follow-up without delay.
Trigger: Contact's lead score reaches the agreed MQL threshold (e.g., 60 points).
Score construction for a typical B2B SaaS model:
- Demographic signals (set on record creation or enrichment): Job title match to buyer persona (+10 to +20), company size in ICP range (+10), industry match (+10), competitor domain (−20)
- Behavioural signals (accumulate over time): Pricing page visit (+15), demo request form abandon (+10), product comparison content download (+10), case study view (+8), webinar attendance (+8), email click (+3), email open (+1), unsubscribe (−50)
The scoring model must be agreed with sales before it is configured - not reviewed by sales after the first MQLs arrive. A model that sales did not contribute to is a model sales will not trust.
Actions on MQL trigger: (1) Set lifecycle stage to MQL. (2) Assign to the correct sales rep based on territory or account size. (3) Send internal sales-alert email with contact summary, score breakdown, recent activity, and a suggested outreach message. (4) Enroll in a 5-minute-delay email sequence that sends the contact a personalised follow-up from the assigned rep's email address.
Goal: Contact books a meeting or is marked SQL by sales within 5 business days.
Workflow 3: Sales-Alert Notification
Purpose: Alert the assigned sales rep at the exact moment a known contact displays high-intent behaviour - before the intent signal fades.
Trigger: Known contact visits the pricing page twice in 7 days, or visits the demo request page and does not complete the form, or opens a proposal email for the third time.
This is the fastest-ROI workflow to build in any B2B SaaS marketing programme. It requires no email design, no content creation, and minimal logic. It is a CRM notification: who the contact is, what they did, when they did it, their current score, their company name and size, and a suggested first message.
The notification should be in the rep's inbox or CRM task queue within 5 minutes of the trigger event. Every hour of delay at this intent level reduces conversion probability.
Actions: (1) Create CRM task assigned to the contact owner: 'High-intent signal - [contact name] visited pricing page twice. Suggested action: send personalised outreach today.' (2) Send internal email to the contact owner with contact summary and activity log.
Goal: Rep makes first contact within 24 hours of trigger. Track this - if the SLA is not being met, the alert is not working.
Workflow 4: Behavioural Nurture (Content-Triggered)
Purpose: Serve relevant content to contacts based on what they have already consumed, advancing them through the funnel without forcing a linear sequence.
Trigger: Contact downloads a specific gated asset, visits a specific topic cluster on the website, or clicks a specific link in a previous email.
The difference between behavioural nurture and a standard drip sequence: behavioural nurture responds to what the contact does, not what day it is since they subscribed. A contact who downloads a guide about lead scoring has signalled interest in lead scoring - the next email should be about lead scoring, not the next item in a fixed content calendar.
To build behavioural nurture, your content library must be tagged by topic, buyer stage, and persona. This is the prerequisite that most teams skip. A content audit that maps existing assets to these three dimensions is a one-time investment that makes every subsequent behavioural workflow significantly faster to build.
Template structure: (1) Trigger email: a direct follow-on to the consumed content - the next logical resource, not a different topic. (2) Day 3: related case study or social proof specific to the topic. (3) Day 7: offer a more in-depth resource (webinar, longer guide) or a low-commitment next step (short consultation, free audit). Goal event check at each step - exit if goal is reached.
Workflow 5: Free Trial Activation and Feature Adoption
Purpose: Drive trial users to activate the features most correlated with paid conversion - before the trial window closes.
Trigger: Trial signup; specific feature not activated by day 3.
This workflow requires product event data flowing into your CRM or automation platform - the platform needs to know which features each trial user has and has not used. This is the integration work that separates Level 2 automation (email-only) from Level 3 (email informed by product behaviour).
For teams without product event integration, a partial version of this workflow is still possible: use login frequency (available via many email platforms through their native app integrations) as a proxy for activation, and design the workflow around re-engagement rather than specific feature adoption.
Template: Day 1 (if feature X not activated): 'Here is why feature X matters - three-minute setup.' Day 3 (if still not activated): different angle, different CTA. Day 5 (if still not activated): offer a live walkthrough with a CS team member. Day 7: final trial urgency email.
Goal: Feature X activated or CS call booked.
Workflow 6: Re-Engagement
Purpose: Recover cold contacts who have not opened or clicked in 90 days before they become permanently unengageable.
Trigger: Last email activity (open or click) more than 90 days ago; lifecycle stage is Lead or MQL.
Re-engagement is one of the cheapest workflows to build and one of the most neglected. Cold contacts do not disappear - they sit in the database and damage deliverability as their engagement rate trends toward zero. A 3-email re-engagement sequence that asks directly whether the contact still wants to hear from you costs almost nothing to build and produces three outcomes: re-activation, a clean unsubscribe (which improves deliverability), or confirmation that the contact should be suppressed.
Template: Email 1: 'We have not heard from you in a while - still interested in [specific topic/value prop]?' Direct subject line, no marketing language, single CTA. Email 2 (5 days later, if no engagement): different angle, acknowledge the silence. Email 3 (7 days later, if still no engagement): 'Should we stop sending?' with a clear yes/no choice. Suppress non-responders after email 3.
Workflow 7: Expansion and Upsell Trigger
Purpose: Identify existing customers showing signals of expansion readiness and trigger a targeted commercial conversation before the opportunity is missed.
Trigger: Team reaches 80% of their seat limit, contact activates an enterprise-only feature in a standard plan, customer passes 12 months with no expansion conversation, or usage surpasses the current plan's threshold.
Expansion automation is the most underdeveloped workflow category in B2B SaaS marketing programmes. Most teams focus automation entirely on acquisition. For SaaS businesses, expansion revenue from existing customers costs 5-7× less to generate than new logo revenue and typically has higher close rates.
Expansion workflows require coordination with Customer Success: the CS team should be alerted before any automated commercial email goes to an existing customer. The worst expansion automation pattern is a marketing email reaching a customer who has just logged a support ticket. CS and marketing suppression rules are a governance requirement, not a suggestion.
Template: (1) CS-alert notification: 'Customer [name] is approaching seat limit - expansion opportunity.' (2) After CS review (automated 48-hour delay): personalised email from the CS manager or account owner, not a marketing send. (3) If no CS action within 5 days: automated check-in from marketing with a specific upgrade path and a direct link to the upgrade page.
Workflow 8: Churn Risk Alert
Purpose: Alert the CS team when an existing customer shows early churn signals - before the customer has made a decision.
Trigger: Login frequency drops by 50% compared to prior 30-day average, a support ticket is opened and unresolved after 72 hours, or a key power user changes their email to a different domain (suggesting they have left the company).
Churn risk automation is operational, not marketing. The output is a CS task, not a marketing email. The workflow reads product and support data, identifies the signal, and routes it to the right CS owner with enough context to act: which customer, what the signal was, what the account's usage history looks like, and a suggested first response.
The email the customer receives, if any, should come from their assigned CS manager - not from a marketing automation sequence. This is a relationship save, and it should feel like one.
Building Workflows Step by Step
Once the workflow is designed on paper - trigger defined, conditions mapped, content outlined, goal set - building it in the platform is the fastest part of the process. The steps are the same regardless of platform:
- Define the enrollment trigger precisely. Avoid broad triggers. 'Contact is in the database' is not a trigger - it is a list. 'Contact submitted the pricing page demo request form on or after [date]' is a trigger. Precision at the trigger determines relevance throughout the workflow.
- Set the goal and exit criteria first. Before writing a single email, define the event that marks the workflow complete for a given contact. Configure this as the goal event in the platform. Contacts who reach the goal should exit immediately, regardless of where they are in the sequence.
- Build the logic skeleton before adding content. Configure the steps, delays, conditions, and branching in the workflow builder without the actual email content. Review the skeleton with a colleague or sales stakeholder before writing. It is faster to change logic before emails are written than after.
- Write emails in the context of the step position and contact state. Email 1 is read by someone who just took a specific action. Email 4 is read by someone who has received three previous emails and not yet converted. Write each email with that context explicit - not as a standalone piece of content.
- Test with real contacts before going live. Enroll yourself and a colleague as test contacts. Go through every branch. Check that goal exits work. Verify that the email timing is correct. Confirm that CRM properties are being set as expected.
- Define the first optimisation review before launch. Set a calendar event for the first performance review 2-3 weeks after launch. Identify the three metrics you will check first. A workflow that is launched without a scheduled review date will not be reviewed.
The Role of Website Data in Workflow Triggers
The most powerful workflow triggers in B2B SaaS are not form submissions - they are page-visit behaviours: pricing page visits, feature comparison views, ROI calculator completions, and documentation searches. These are intent signals that happen before a contact is ready to fill out a form, and they are the signals most teams miss.
Capturing these signals requires the automation platform's tracking script to be installed on the website and set up to identify known contacts from their browser cookies. When a contact who has previously submitted a form visits the pricing page, the platform should recognise them, update their contact record, and optionally trigger a workflow - all without a second form submission.
For Webflow sites, HubSpot's tracking script (installed via Webflow's site settings custom code section) captures page-view events for known contacts in real time. See our HubSpot Webflow integration guide for the specific setup. For paid ad attribution - connecting Google Ads clicks and LinkedIn ad views to specific contacts in your automation platform - see our HubSpot Google Ads integration guide and HubSpot LinkedIn integration guide.
The practical implication for workflow design: every page on your website that a contact visits after converting on a form is a potential trigger or scoring event. A contact who visits your pricing page six months after downloading a guide is a re-engagement opportunity. A contact who visits your documentation site three days into a trial is showing product engagement that your onboarding sequence should acknowledge.
Measurement and Optimisation Framework
The most common measurement failure in workflow management is looking at email-level metrics - open rate, click rate - instead of workflow-level outcome metrics - goal completion rate, MQL-to-SQL rate, trial-to-paid rate, revenue influenced. Email metrics tell you whether a contact engaged with a specific email. Outcome metrics tell you whether the workflow is doing its job.
The optimisation process that works in practice:
- Monthly workflow audit. Review the three lowest-performing workflows by goal completion rate. For each, identify the step with the highest drop-off (where contacts are exiting without completing the goal). Make one change per workflow per review - not five.
- A/B test at the step level, not the workflow level. Test subject line variants, CTA copy, email timing, or branching conditions at the individual step level. Testing the entire workflow as a single A/B experiment produces data too slowly and makes it impossible to attribute improvement to a specific change.
- Review goal and exit criteria quarterly. The event that defines 'success' for a workflow can become stale as the product, the sales process, or the ICP evolves. A churn risk alert workflow built around login frequency may need to incorporate a new usage signal added to the product six months later.
- Align optimisation reviews with the sales pipeline review. The workflows most worth optimising are the ones directly connected to sales pipeline - lead scoring, sales-alert, and MQL routing. Include sales leadership in the quarterly workflow review to identify cases where the automation is passing leads that sales is not accepting.
Common Workflow Mistakes
Broad triggers that enroll everyone. A welcome sequence that triggers for every new contact in the database, regardless of how they were added, sends onboarding emails to cold leads generated by an outbound sequence - confusing and reputation-damaging. Every trigger should have a specific condition that limits enrollment to contacts for whom the workflow is relevant.
No defined goal or exit criteria. A workflow with no goal never knows when it has succeeded. A contact who books a demo while enrolled in a 'have you considered booking a demo?' nurture sequence continues to receive those emails until the sequence ends. This is avoidable and damaging - it is exactly the kind of automation that makes buyers distrust marketing.
Re-enrolling contacts in completed workflows. A contact who completes a welcome sequence and later re-enters the trigger condition (e.g., submits another form) should not receive the welcome sequence again. Most platforms have re-enrollment settings - audit them. Re-enrollment is appropriate for some workflows (re-engagement, for example) and inappropriate for almost all others.
Building workflows before the content exists. A behavioural nurture workflow that sends 'related content coming soon' emails because the content library is not ready is worse than no automation. Build the content before building the workflow, or design the workflow around the content that currently exists.
Sending automated emails during a live sales conversation. A contact in an active opportunity should be suppressed from most marketing automation sequences. Marketing emails that arrive while a rep is mid-conversation create confusion, undermine the rep's credibility, and signal that the marketing and sales systems are not connected. Suppression rules that exclude contacts with an open deal are a baseline governance requirement.
Treating the workflow as a set-and-forget system. Workflows decay. Content becomes stale. Pricing references become outdated. Triggers that were precise when built become over-broad as the contact database grows. A workflow that was working six months ago needs to be reviewed, not assumed to still be working. Schedule the review before launch, not retrospectively.
Tool Considerations for Workflow Execution
Workflow capability varies significantly across email and automation platforms. The right platform depends on which workflows you need to run and how much complexity they require. For teams evaluating platforms, our ActiveCampaign alternatives guide and Mailchimp alternatives guide cover this in detail.
For B2B SaaS teams, the capability requirements that most directly constrain workflow design:
- Behavioural trigger support: Can the platform trigger workflows based on website page visits, not just form submissions? This requires a tracking script and a contact identification layer. ActiveCampaign, HubSpot, and Klaviyo support this natively. Brevo and MailerLite have more limited behavioural tracking.
- Native lead scoring: Does the platform support lead scoring as a native feature, not a manual workaround? HubSpot (Professional), ActiveCampaign, and GetResponse support native scoring. MailerLite and Brevo require scoring logic to be replicated through segmentation or external tools.
- CRM field triggers: Can workflows be triggered by changes to CRM properties - deal stage, lifecycle stage, contact owner assignment? This is required for sales-handoff and expansion workflows. HubSpot and ActiveCampaign support this natively.
- Goal-based branching: Can the workflow automatically exit a contact when a defined goal is reached, regardless of which step they are currently on? This is a basic requirement that some entry-level platforms still do not support cleanly.
- Product event integration: Can the platform receive events from the product (feature activated, usage milestone reached) and use those events as triggers or scoring signals? This typically requires a Segment integration, a direct API connection, or a Customer Data Platform (CDP) layer. HubSpot supports this via its Events API and Operations Hub.
Work with Belt Creative
Belt Creative implements HubSpot and builds Webflow sites for B2B SaaS teams that need their website, automation, and CRM connected from day one. If you are building workflows from scratch, rebuilding a system that is not producing pipeline, or connecting website behaviour data to your automation platform, we can help.
See our work for examples of automation and website builds, or get in touch to discuss your workflow requirements.
A Note on Sources
HubSpot Marketing Blog - workflow and automation documentation: blog.hubspot.com. ActiveCampaign automation documentation: activecampaign.com. B2B SaaS workflow templates, trigger recommendations, and sequencing guidance reflect commonly observed implementation patterns across mid-market B2B SaaS companies. Individual results vary by platform, list quality, content relevance, and sales cycle length.
Frequently Asked Questions
What Is a Marketing Automation Workflow?
A marketing automation workflow is a pre-built sequence of actions - emails, notifications, property updates, task assignments - that executes automatically when a specific trigger event occurs. The trigger might be a form submission, a page visit, a lead score threshold, or a change in a contact's CRM properties. The workflow executes the same logic for every enrolled contact without manual intervention, at whatever scale and at whatever time the trigger fires.
What Is the Best First Workflow to Build?
For B2B SaaS teams: a welcome and onboarding sequence triggered by demo request or trial signup. It has the highest direct connection to revenue (trial-to-paid conversion), the lowest implementation effort, and it establishes a baseline engagement pattern you can measure and improve over time. Build this before any other workflow. The second workflow to build is a sales-alert notification for high-intent page visits - it requires almost no design and produces immediate, visible results with the sales team.
How Many Workflows Should a B2B SaaS Team Run Simultaneously?
Start with two or three well-designed workflows and optimise them before adding more. A common mistake is building eight workflows before any of them are working well. Depth before breadth: a welcome sequence with a 40% goal completion rate is more valuable than four sequences each completing at 10%. Add new workflows when the existing ones are performing at or above benchmark and the optimisation work is returning diminishing improvements.
What Is the Difference Between a Workflow and an Email Sequence?
An email sequence is a specific type of workflow - a series of emails sent in a defined order with defined delays. A workflow is the broader system that includes the trigger, all the logic and conditions, the actions (which may include emails, but also CRM updates, task assignments, and notifications), and the goal criteria. A workflow can contain multiple email sequences, route contacts to different sequences based on conditions, and perform actions that have nothing to do with email.
How Do I Measure Whether a Workflow Is Working?
Measure goal completion rate (the percentage of enrolled contacts who reach the defined goal), not just open and click rates. Open and click rates tell you about email engagement; goal completion tells you whether the workflow is driving the commercial outcome it was built for. For pipeline-connected workflows (lead scoring, sales-alert), also track MQL-to-SQL conversion rate and sales acceptance rate - these tell you whether the workflow is producing leads that sales trusts.
How Does Website Behaviour Feed Into Workflow Triggers?
Most modern automation platforms (HubSpot, ActiveCampaign, Klaviyo) include a JavaScript tracking script that installs on your website and identifies known contacts from browser cookies when they revisit. Once identified, their page visits, time on page, and specific content interactions can trigger workflows or update lead scoring in real time - without a form submission. For Webflow sites, see our HubSpot Webflow integration guide for the specific tracking setup.
What Is the Most Common Workflow Mistake?
Building workflows with no defined goal or exit criteria. When a workflow has no goal, it runs every contact through every step regardless of whether they have already converted. A contact who books a demo while enrolled in a nurture sequence should exit immediately - but without a configured goal event, they continue receiving 'have you considered booking a demo?' emails. This is the single most common and most avoidable automation failure in B2B SaaS marketing.
How Do I Connect Expansion and Churn Workflows to Customer Success?
Expansion and churn workflows should be designed as CS-alert sequences, not marketing sends. The output of the workflow is a task in the CRM for the assigned CS manager - not an email to the customer from a marketing sequence. If a follow-up email to the customer is warranted, it should come from the CS manager's email address via a personalised send, not from a marketing template. Co-design these workflows with the CS team lead before building them, and include explicit suppression rules that pause the workflow if a support ticket is open for the account.
How Long Should a B2B SaaS Nurture Sequence Be?
Long enough to move the contact toward a defined goal; short enough that each step justifies its existence. For most B2B SaaS nurture sequences, 4-7 emails is the right range. Beyond 7 emails without a goal event, sequence completion rates drop significantly and unsubscribe rates rise. The question is not 'how many emails can we send?' - it is 'what is the minimum number of high-quality touches that moves this contact toward the goal?' Design to that number, not to a calendar-driven drip.
Which Platforms Best Support Advanced B2B SaaS Workflows?
HubSpot Marketing Hub (Professional) and ActiveCampaign (Plus or above) are the strongest platforms for the full B2B SaaS workflow stack - behavioural triggers, lead scoring, CRM field triggers, goal-based branching, and product event integration. GetResponse covers most standard B2B use cases at a lower price. Brevo and MailerLite handle simpler workflow requirements well but have limitations on lead scoring and CRM-triggered logic. See our ActiveCampaign alternatives guide for a detailed capability comparison.
Sources: HubSpot Marketing Blog (blog.hubspot.com); ActiveCampaign automation documentation (activecampaign.com); B2B SaaS workflow benchmarks reflect commonly observed implementation patterns. Individual results vary.