10 Examples of Marketing Funnels for SaaS

Most SaaS funnels lose far more customers between lifecycle stages than founders expect. One 2026 benchmark synthesis found that B2B funnels typically convert only 1% to 3% of website visitors into leads, about 31% of leads into MQLs, 13% of MQLs into SQLs, 30% to 59% of SQLs into opportunities, and 22% to 30% of opportunities into customers. Taken together, those stage rates imply roughly 2% to 5% end-to-end lead-to-customer conversion, or about 20 to 50 customers from 10,000 website visitors in a typical B2B funnel. The benchmark synthesis also identifies the MQL-to-SQL transition as one of the steepest losses.

That changes how SaaS teams should think about examples of marketing funnels. A funnel isn't just an acquisition diagram that ends at signup. It's a connected lifecycle system that moves a user from signup to activation, adoption, expansion, retention, advocacy, and payment recovery.

Use this lifecycle map as the operating model:

Signup → Activation → Feature adoption → Expansion → Re-engagement → Churn save → Dunning → Advocacy

The ten examples below show the production mechanics behind each stage, including the trigger, audience, reusable email sequence, success metric, optimization loop, and the role an AI lifecycle tool such as Mara can play while keeping approval gates in place. For acquisition teams exploring adjacent creative workflows, AI video tools for SaaS can support product education and campaign production, but the revenue system still depends on timely event-based messaging.

Table of Contents

• 1. Welcome Series Funnel
• Trigger and sequence
• 2. Activation and Trial Extension Funnel
• Event logic and branches
• 3. Feature Adoption and Product Launch Funnel
• Segment, teach, reinforce
• 4. Expansion and Upsell Funnel
• Build separate expansion paths
• 5. Re-engagement and Win-back Funnel
• Sequence and measurement
• 6. Churn-Save and Cancellation Prevention Funnel
• Trigger logic and escalation
• 7. Dunning and Failed Payment Recovery Funnel
• Design for fast correction
• 8. Educational and Thought Leadership Funnel
• Sequence and editorial system
• 9. Referral and Advocacy Activation Funnel
• Sequence and referral mechanics
• 10. Onboarding and Implementation Funnel
• Milestones, ownership, and risk
• 10 Marketing Funnels: Side-by-Side Comparison
• Turn Funnel Examples Into a Lifecycle Operating System

1. Welcome Series Funnel

A welcome funnel begins the moment a user signs up, but its job isn't just to say hello. It must move the new account toward a first meaningful product interaction while setting expectations for support, education, and value.

Slack can use this sequence to introduce workspace setup, team invitations, and first-message templates. Notion can point new users toward its template gallery and database creation. Stripe can prioritize API documentation and test-mode activation. The common pattern is a single early action that helps the user understand why the product matters.

Trigger and sequence

Trigger the first email immediately after signup, ideally within the first 30 minutes, then branch according to product behavior.

• Email one, welcome: Confirm the account, establish the product promise, and give one CTA, such as “Create your first workspace.”
• Email two, orientation: Explain the shortest route to value, with a product overview or brief setup guide.
• Email three, activation prompt: Branch based on an event such as created_first_item, invited_team_member, or connected_integration.
• Email four, help offer: Provide documentation, a short demo, or a human support option to users who haven't completed the key event.

Segment users by signup source, role, plan, and completed product events. A user who created a project needs a different message from one who never logged in. Measure activation rate after the sequence, then compare performance by source, subject line, send time, and branch.

Mara can read a SaaS website, repository, and past emails to draft messages in the existing company voice. It can propose event-driven branches and variants, while approval-only controls keep every new sequence or send policy behind a human review.

2. Activation and Trial Extension Funnel

Trial users don't need more product information in the abstract. They need help completing the specific action that predicts whether the trial will become a real evaluation.

Notion might promote its template gallery shortly before trial expiration. Loom can message users who haven't recorded a video by day three. Typeform can suggest a ready-made survey when someone hasn't launched a form by day five. Each example connects urgency to a blocker instead of sending the same reminder to every trial account.

Event logic and branches

Define one activation event first, such as created_campaign, completed_workflow, or invited_team_member. Then build the sequence around the user's observed state:

• Within 24 hours: Ask the user to complete the activation event and link directly to the relevant screen.
• By day three: Address the likely blocker with a short demonstration, template, or setup explanation.
• Before expiration: Explain what the user will lose or preserve, then offer a clear path to continue.
• High-potential branch: Offer a call or demo to accounts showing substantial usage, multiple stakeholders, or advanced setup intent.

Separate “logged in but didn't create” from “never logged in.” The first group needs friction removal. The second may need a reminder of the original use case, a simpler entry point, or a different acquisition-source message. Test urgency against benefit-led language rather than assuming every user responds to a countdown.

The personalized email campaign guidance from Mara is useful here because behavior-based branches can reflect what a trial user has done, not just who they are. Track activation, trial-to-paid conversion, replies, and negative feedback by branch. If users click but don't activate, fix the product path or CTA. If they never engage, revisit audience fit and timing.

Practical rule: A trial email should answer one question, “What should this user do next, given what they've already done?”

3. Feature Adoption and Product Launch Funnel

Feature announcements often fail by describing capabilities instead of explaining why each recipient should care. A project manager who never uses dependencies needs a clear connection between the feature and the workflow already in use.

Asana can target users who create projects but do not set dependencies. Figma can promote prototyping or sharing to design teams that have not adopted collaboration features. Airtable can introduce automation and API capabilities to power users still working in basic views. Stripe can announce payment methods to merchants in relevant geographies, while Zapier can recommend automations based on connected apps.

Segment, teach, reinforce

Start with product telemetry. Identify feature clusters linked to deeper engagement or expansion, then build separate journeys for reporting, automation, integrations, and collaboration. Segment by plan, role, workflow, connected tools, and current usage.

A reusable sequence:

• Email one, relevance: Connect the feature to a specific customer problem.
• Email two, demonstration: Show the workflow in a short video or GIF.
• In-product reinforcement: Place a tooltip, banner, or modal where the feature appears.
• Email three, proof: Explain how similar customers use the capability without claiming unsupported results.
• Follow-up: Ask whether the user adopted it and offer help if usage stalled.

Define the adoption event before launch, such as enabling automation, creating a report, or sharing a prototype. Send the first message only to eligible users, suppress adopters, and route users who click without completing the event into a help branch. Keep users who have not engaged in a separate branch, since they may need a clearer use case rather than more product detail.

Measure time-to-adoption first, then feature usage, repeat usage, expansion signals, and replies. Test benefit-led copy against feature-led copy, and compare launch timing by audience. Developer tools may need implementation time, while enterprise capabilities may need to reach decision-makers before planning meetings.

Mara can draft variants from product context, maintain messaging as the repository changes, and route proposed sends through approval controls. Its event-based segmentation can suppress promotion after adoption and leave a review trail before automation goes live.

4. Expansion and Upsell Funnel

Expansion messaging works best when the customer has already demonstrated a need for more capacity. Sending an upgrade offer because a calendar date arrived is weaker than responding to usage growth, team expansion, or a plan limit that has become operationally relevant.

Stripe can message accounts approaching transaction thresholds. Calendly can identify teams whose members are sharing one account. GitHub can promote organization features and advanced CI/CD to users managing multiple repositories. In each case, telemetry creates the reason for the conversation.

Build separate expansion paths

Don't combine seat expansion, plan upgrades, and feature add-ons in one generic journey. They represent different buying motivations and often require different proof.

• Seat expansion: Trigger after repeated invitations, shared-account behavior, or team growth.
• Plan upgrade: Trigger when usage approaches a meaningful plan limit or the account adopts capabilities associated with a higher tier.
• Feature add-on: Trigger when the user encounters a workflow that the add-on solves.
• Sales-assisted branch: Route high-value accounts to a human owner when account context requires negotiation or security review.

Use billing data from Stripe, Polar, or another payment source to show the relevant plan and limit. The email should explain what the next tier enables, reduce uncertainty around proration or commitment, and provide one obvious CTA. Automation can handle self-serve customers, while sales or customer success should take over accounts where expansion depends on multiple stakeholders.

Measure upgrade conversion, added recurring revenue, usage after upgrade, and downgrade or refund signals. If clicks are strong but upgrades are weak, inspect pricing clarity, checkout friction, and whether the offer matches the actual usage problem.

5. Re-engagement and Win-back Funnel

Dormancy has to be defined relative to the product. A daily collaboration product and a monthly reporting tool shouldn't use the same inactivity rule. The trigger might be a missing core event, a drop in usage frequency, or a lapsed subscription, but it should reflect a meaningful change in customer behavior.

Spotify can use personalized recommendations and an account recap. Dropbox can connect a return message to file activity. Medium can surface new work from authors a reader follows. These messages restore relevance by showing what the customer can do now, not merely saying the company misses them.

Sequence and measurement

Use a two-stage journey:

• Soft re-engagement: Remind the customer of unfinished work, recent product value, or a relevant use case.
• Barrier removal: Offer help with setup, migration, forgotten workflows, or a feature the customer may have missed.
• Win-back: Present a carefully chosen incentive, extended trial, or feature access when price sensitivity is plausible.
• Exit survey: Ask what prevented continued use and feed the response into product and lifecycle analysis.

Segment by last meaningful action, prior feature adoption, plan, customer value, acquisition source, and stated reason for inactivity. Don't send a discount to someone who left because the product was confusing. That customer needs education or assistance. Measure reactivation rate, restored usage frequency, retained recurring revenue, offer acceptance, unsubscribes, and negative replies.

A useful optimization loop compares value-led and incentive-led branches, then checks whether reactivated accounts remain active. Mara can draft personalized win-back messages from product and billing context, classify replies, and prepare suggested responses for review. That helps small teams handle individual context without turning every dormant account into a manual campaign.

6. Churn-Save and Cancellation Prevention Funnel

A cancellation request is a high-intent event. The customer has given you a direct signal about risk, so a scheduled newsletter or generic retention campaign is the wrong tool. The message must address the reason for cancellation and offer a credible alternative.

Amazon Prime can present a retention offer during cancellation. SurveyMonkey can acknowledge the decision, then connect product changes to the customer's stated problem. Intercom can use support context to offer training when complexity, rather than price, drives dissatisfaction.

Trigger logic and escalation

Use multiple real-time triggers:

• Cancellation started: Ask the reason and present the most relevant alternative.
• Failed payment: Move the customer into dunning, not a generic churn-save flow.
• Extended inactivity: Offer help, training, or a simpler workflow.
• Negative support sentiment: Escalate the account when the issue needs human attention.

Build the sequence around likely causes, including price sensitivity, complexity, a competitor, changing needs, or missing functionality. The first message can explain a relevant solution. The next can present a plan adjustment or incentive. The final message should make cancellation easy if the customer still wants to leave.

For high-value accounts, assign a human owner immediately. Automation is more appropriate for self-serve customers with clear, repeatable reasons. Track cancellation prevention, avoided recurring revenue, accepted alternatives, survey responses, support sentiment, and later churn. Review the results separately from ordinary email performance because a saved account may still require product or service changes.

The guide to reducing customer churn from Mara fits this workflow's event-driven approach. Mara can draft reason-specific messages, use Stripe or Polar webhook context, and keep approval-only sending in place for sensitive retention offers.

A churn-save email shouldn't pressure a customer into staying. It should make the right next option obvious.

7. Dunning and Failed Payment Recovery Funnel

Dunning is a revenue-protection funnel, but it isn't a cancellation funnel. The customer may still want the product. Their card may have expired, their billing address may have changed, or the account may need another payment method.

Stripe's recommended dunning approach uses three emails over three to eight days before suspension, as documented in the Stripe dunning sequence reference. Netflix can provide a direct payment-method update path while preserving access. Dropbox can combine payment-failure notices with a suspension countdown and support option.

Design for fast correction

Send the first message within 24 hours of the failed payment, with the amount owed, subscription details, and a direct update link. Segment known failure reasons where the payment provider supplies them.

• Expired card: Ask the customer to replace the expired method.
• Insufficient funds: Offer another method and avoid accusatory language.
• Address or verification issue: Explain the exact correction required.
• High-value account: Include a direct support contact or human billing route.

Offer more than one payment method when the infrastructure supports it. Test shorter and longer sequences, but watch unsubscribe rates, complaint signals, and negative replies. More pressure isn't automatically more recovery. The message should become clearer over time, not just more threatening.

Measure recovered invoices, averted involuntary churn, time to recovery, suspension rate, support contacts, and negative feedback. Connect payment events to suppression rules so a successful payment immediately stops the sequence. Mara can propose dunning journeys from Stripe, Polar, webhooks, or its Events API, then keep new copy and policy changes behind an approval gate.

8. Educational and Thought Leadership Funnel

Some prospects and customers aren't ready for an upgrade, but they still need a reason to keep paying attention. An educational funnel maintains that relationship by teaching a useful practice, showing credible use cases, and connecting the lesson to the product without turning every message into a sales pitch.

Buffer can publish a newsletter about social media trends, content strategy, and company culture. Superhuman can teach productivity and email efficiency. Loom can share use cases across sales, HR, and engineering. These examples work because the content reflects a specific audience and a recognizable point of view.

Sequence and editorial system

Start with role and problem segmentation. Engineers, founders, marketers, and operations leaders may use the same product but need different evidence and language.

A reusable sequence might include:

• Insight email: Explain a practical problem and the underlying principle.
• Use case email: Show how a team applies that principle in a real workflow.
• Format variation: Invite the reader to a webinar, recorded presentation, or product demonstration.
• Soft product CTA: Offer one relevant next step, such as exploring a workflow or reading implementation guidance.
• Feedback branch: Use clicks, replies, and topic choices to determine the next theme.

Measure engagement by topic, qualified product visits, replies, assisted conversions, and eventual adoption or expansion. Don't optimize only for clicks. A provocative topic may generate attention without helping the right accounts progress.

The best editorial programs also create reusable assets. Turn a strong email into a blog post, LinkedIn article, webinar segment, or sales enablement note. Mara can draft in the company's existing voice and maintain sequence relevance as the website and repository evolve. Human approval remains important because thought leadership depends on judgment, customer evidence, and a distinct perspective.

9. Referral and Advocacy Activation Funnel

A referral request should arrive after a customer has experienced success, not immediately after a purchase. The strongest advocates are both successful and willing to communicate. Product usage, positive feedback, support outcomes, and completed milestones can identify that group more reliably than a broad customer export.

Dropbox can reward both the referrer and the referred customer with storage. Slack can identify power users for case studies and webinars. Superhuman can use exclusivity and invitation mechanics to turn enthusiastic users into participants in growth.

Sequence and referral mechanics

Use a short advocacy journey:

• Success recognition: Remind the customer what they've accomplished with the product.
• Advocacy invitation: Ask whether they'd share the product with a peer or participate in a case study.
• Low-friction referral: Provide a pre-populated email, copyable link, and referral landing page.
• Progress update: Tell the advocate when the referral advances, subject to privacy and program rules.
• Status reward: Offer recognition, access, or tiered rewards to customers who contribute repeatedly.

Segment promoters by successful use case, recent satisfaction, usage depth, account health, and communication behavior. Suppress customers with unresolved support problems or recent negative feedback. Measure referrals generated, referred conversion, referred acquisition cost, referred customer quality, and advocate participation.

The optimization loop should test the request timing, reward structure, and landing-page friction. A monetary incentive may work for some advocates, while recognition, early access, or a public customer story may motivate others. Keep attribution clean with trackable links and explicit referral events.

10. Onboarding and Implementation Funnel

Enterprise onboarding is a coordinated delivery process with different stakeholders, timelines, and definitions of progress. Admins, everyday users, executives, procurement teams, and customer success owners each require a relevant path.

Salesforce can pair enterprise deals with implementation consultants. Workday can coordinate multi-week journeys with client success partners and executive check-ins. HubSpot Enterprise can use implementation playbooks, training workshops, and success planning sessions.

Milestones, ownership, and risk

A practical plan can run across 30 to 90 days, covering setup, data import, workflow configuration, team training, and first measurable success. Create separate journeys by customer size, use case, integration complexity, and stakeholder role.

• Admin path: Configuration, permissions, data, and integrations.
• User path: Training, first workflow, and repeat usage.
• Executive path: Progress summaries, risks, and success criteria.
• At-risk path: Low participation, missed milestones, unresolved support issues, or incomplete handoff context.

Use product events as triggers rather than relying only on calendar dates. After the first campaign goes live, congratulate the team and assign the next action. If implementation stalls, offer training or schedule a check-in. Send executive summaries at 30, 60, and 90 days, while passing contract terms, success criteria, stakeholders, and sales context from sales to success.

A timeline visualization can align every stakeholder around the same definition of progress. See this customer journey automation framework for a practical way to connect milestones, ownership, and automated actions.

Measure time-to-value, milestone completion, implementation completion, adoption by role, support volume, and renewal risk. Mara can propose event-triggered messages and maintain the operational sequence. Approval controls let customer success review high-stakes communications before sending, which is useful when messages involve risks, executives, or contractual commitments.

The optimization loop should compare completion rates by segment, identify the milestone where accounts stall, and adjust ownership, training, or message timing accordingly.

10 Marketing Funnels: Side-by-Side Comparison

Turn Funnel Examples Into a Lifecycle Operating System

These ten examples work best as one connected operating system, not ten disconnected campaigns. Start with activation because new users can't expand or advocate for a product they haven't learned to use. Then deepen adoption with feature education, identify expansion signals, and protect revenue through re-engagement, churn-save, and payment recovery.

A sensible implementation order is straightforward:

• Define the event taxonomy: Name signup, activation, adoption, billing, cancellation, and recovery events consistently.
• Choose one success event per journey: Avoid measuring a welcome email against a vague engagement goal. Tie it to a concrete next action.
• Write segment-specific branches: Separate never-activated users from partially activated users, self-serve accounts from high-value accounts, and payment failures from intentional cancellations.
• Connect product and billing sources: Combine application events with Stripe, Polar, webhooks, or a direct Events API so the message reflects the customer's current state.
• Establish approval rules: Decide which journeys can draft only, which require approval for every send, and which may eventually use approved auto-send policies.
• Review performance weekly: Monitor conversion, adoption, recovery, replies, unsubscribes, complaints, and negative feedback together.

The benchmark data makes the business case for this stage-by-stage approach. A 2026 First Page Sage funnel benchmark report separates Lead to MQL, MQL to SQL, SQL to Opportunity, and Opportunity to Closed, and reports B2B SaaS rates of 39%, 38%, 42%, and 37% across those transitions. The same report shows why one blended conversion number hides the actual problem. A team may have healthy acquisition but lose momentum during qualification, activation, checkout, or retention.

Behavior-based segmentation is especially important in email. One 2025 industry summary reports click-through improvements of 20% to 30% for behavior-based segments, compared with 5% to 12% for demographic splits, while engaged cohorts can see 15% to 25% improvement when content matches past actions. The segmentation summary supports a practical conclusion: segment around what users did, what they need next, and what risk or opportunity their behavior reveals.

Mara can help small SaaS teams turn that system into maintained journeys. It drafts in the company voice after reading the website, repository, and previous emails, proposes programs from product and payment events, generates variants, handles replies for review, and reports performance in plain language. Its default approval-only workflow and audit log keep human control available, which matters when a message can affect retention, billing, or customer trust.

Governance should cover more than a final approval button. An approval workflow audit guide defines an audit trail as a chronological record of requests, evidence, people, rules, actions, and outcomes, including submissions, assignments, changes, reviews, decisions, escalations, overrides, and closures. Some workflow systems also formalize review through recurring exports. Smartsheet's auditing documentation describes a CSV audit log for the previous month made available at the beginning of each month.

Build the event foundation first, then launch one journey at a time. If activation is weak, fix that before adding expansion campaigns. If churn is rising, prioritize cancellation reasons and payment recovery. A lifecycle funnel becomes valuable when every message responds to a real customer state and every optimization cycle improves the next decision.

Mara helps SaaS teams draft, automate, and maintain lifecycle email journeys from signup through activation, expansion, win-back, churn-save, and dunning, with product and billing events driving segmentation. Visit Mara to review an approval-controlled approach for turning these funnel examples into operating journeys.