Beyond the Welcome Email: A Stage-by-Stage Lifecycle Marketing Guide for Day 30, 60, and 90
Beyond the Welcome Email: A Stage-by-Stage Lifecycle Marketing Guide for Day 30, 60, and 90
In 1900, André and Édouard Michelin had a tyre company with a problem. There were fewer than 3,000 cars in all of France. People weren't driving much — which meant tyres weren't wearing out — which meant nobody needed new ones.
Instead of waiting, the Michelin brothers did something nobody expected: they printed a small red booklet. It had maps, hotel listings, petrol stations, and restaurant recommendations. They gave it away free to anyone who wanted one. The idea was simple — get people driving more, and eventually they'd need new tyres.
That booklet became the Michelin Guide. More than 120 years later, it's one of the most culturally powerful publications in the world. Chefs dedicate their careers to earning stars they hand out. Not bad for a tyre catalogue.
Here's what strikes me about that story in the context of lifecycle marketing: Michelin didn't just sell a product and disappear. They created a reason for customers to keep engaging with them — to come back, to travel further, to need more. They understood that the relationship starts at the point of sale, but it deepens through everything that follows.
Most brands are doing the opposite. They obsess over the first 7 days — the welcome sequence, the onboarding checklist, the "getting started" nudges — and then go completely dark. The customer hears from them on day 1, day 3, maybe day 7, and then... silence. Maybe a monthly newsletter. Maybe a promotional email when there's a sale.
That silence is killing retention.
According to Pendo's 2025 user retention benchmarks, software products lose 70% of users over three months. The average 30-day retention rate sits at 39%. After 90 days, only about 30% of users are still actively returning. And per Salesso's 2025 SaaS churn analysis, 70% of new users churn within the first 90 days — almost always because of failed onboarding or a mismatch between what was promised and what was delivered.
The welcome sequence is not onboarding. It's the introduction. The real work starts at day 30.
This guide maps out exactly what customers need at the 30, 60, and 90-day marks: the feature adoption nudges, the milestone celebrations, the community invitations, and the social proof moments that turn trial users into long-term customers. We'll show you how to build these campaigns dynamically using Customer.io's branching journeys and custom objects — so your messaging adapts based on what users have and haven't done, rather than just the calendar.
Let's get into it.
Why Most Lifecycle Programmes Stop at Day 7
The welcome sequence gets all the attention because it's the easiest part to justify. High open rates, clear goals (get them to log in, complete setup), and a defined ending point. Marketing teams ship it, tick the box, and move on.
The post-welcome lifecycle is harder. There's no single goal. Users are in different places. Some have adopted three features; others have barely touched the product. You can't write one email that works for everyone, and building dynamic, branching campaigns takes more effort than a linear drip.
Litmus's 2024 State of Email in Lifecycle Marketing report found that fewer than 44% of marketers actually use lifecycle emails to activate, engage, and retain customers. 34% say boosting customer retention is a top goal — but it didn't even make their top five priorities. There's a gap between knowing retention matters and actually building the systems that drive it.
That gap is where churn lives.
The good news: most of your competitors are neglecting this too. If you build a thoughtful 90-day post-onboarding programme, you're already ahead of the majority of the market.
The Framework: Behaviour Over Calendar
Before we walk through each stage, let's establish the most important principle: your campaigns should respond to what users do, not just how many days they've been a customer.
Calendar-based drips are better than nothing. But they treat the 30-day mark the same for a power user who's adopted five features as they do for someone who's barely logged in since day one. Those two users need completely different messages.
Customer.io's branching journeys let you build this logic visually. A true/false branch checks a condition — "Has this user created their first project?" — and routes them down different paths depending on the answer. A multi-split branch can route users into three, four, or more paths based on plan type, feature usage, or account attributes.
Custom objects take it further. They let you bring non-person data — accounts, subscriptions, feature usage records, completed milestones — into Customer.io and use it to drive campaigns. You can trigger a campaign when a custom object is updated (e.g., when an account's feature adoption score crosses a threshold) or branch users based on their relationship to an object (e.g., what plan they're on, whether they've connected an integration).
The result is a lifecycle programme that feels personal, because it responds to what each customer has actually done.
Day 30: Consolidation and the Second "Aha" Moment
What's happening at day 30
By day 30, your customer has made some decisions about your product — consciously or not. They've either built a habit around at least one core feature, or they haven't. They've either told a colleague about it, or they're using it alone. They've either seen clear value, or they're starting to wonder why they signed up.
The 30-day mark is a critical inflection point. Users who haven't experienced a second meaningful "aha" moment by now are at significantly higher churn risk. Userlens's 2025 B2B SaaS retention benchmarks found that customers engaging with over 70% of core features are twice as likely to stay compared to those with low feature adoption. Getting users to a second or third feature — past the one they signed up for — is the goal of this stage.
Healthy engagement benchmarks at day 30
- Login frequency: At least 4-6 logins in the past 30 days for weekly-use products; daily for daily-use tools
- Feature adoption: Engagement with at least 2 core features (not just the one from onboarding)
- Completion of at least one meaningful output: A saved report, a published piece of content, a completed project, a sent communication — whatever your "done" looks like
- Email engagement: Open rates for triggered/lifecycle emails typically hit 45.38% on average — if your 30-day emails are well below that, the content or timing needs work
Red flags at day 30
- User has only ever used one feature
- No logins in the past 7 days
- Hasn't completed the core activation event (the thing that signals they've actually done something with the product)
- Has opened emails but not clicked through — they're passively interested but haven't re-engaged with the product
What to send at day 30
1. The Feature Adoption Nudge
This is not a generic "did you know about X feature?" email. It's a message tied to what they've already done. If they've used your reporting feature, you nudge them toward the export or share function. If they've created content, you surface the collaboration tools.
The trigger is behavioural: the email fires when the user has used Feature A but hasn't touched Feature B within 28 days. In Customer.io, you build this as an event-triggered campaign with a true/false branch: "Has this person performed event feature_b_used?" If no, they go down the nudge path.
Here's the structure that works best for feature adoption emails, per Sequenzy's research on feature adoption campaigns:
- Open with behavioural evidence — reference something they've actually done ("You've been using the reports dashboard regularly...")
- Name the problem the next feature solves, not the feature itself
- One CTA that goes directly to the feature, not the dashboard home page
- Keep it short — under 150 words in the body
2. The Milestone Celebration
If they've hit a meaningful milestone — their first export, their 10th session, their first published output — celebrate it. Not with a generic "congrats!" but with context about the value they've created.
Milestone emails work because they remind users of the compounding effect of using your product. According to UserList's guide to SaaS milestone emails, celebrating feature activations helps build confidence and encourages users to repeat the behaviour. Think Duolingo's streak emails: they're not just celebratory — they're designed to reinforce the habit loop.
In Customer.io, milestone emails are typically event-triggered. When the user fires report_exported_first_time, they enter a journey that sends a celebration email within the hour. The message acknowledges what they did, gives them a quick win they can take next, and — if they're on a plan where it's relevant — surfaces a subtle upsell.
3. The "Are You Getting Value?" Check-In
For users who hit the 30-day mark with low engagement, a direct check-in outperforms a feature nudge. This email asks a single question: "Are you getting what you hoped for?"
Keep it conversational and from a real person's address. The goal isn't to sell them anything — it's to surface friction so you can address it. Even if only 10% reply, those replies are gold for product and customer success teams.
The branch logic here: if the user hasn't logged in for 10 or more days AND hasn't performed the core activation event, they go down the re-engagement path rather than the feature adoption path.
Customer.io setup for day 30
Build a segment-triggered campaign that fires when users enter a "30 days since signup, low feature adoption" segment. Use a multi-split branch based on a custom object (e.g., a user_health object with attributes like features_used_count and last_active_date) to route users into:
- Path A: Power users (3+ features used) → Milestone celebration + social proof ask
- Path B: Moderate users (1-2 features used) → Feature adoption nudge for their logical "next" feature
- Path C: Low-engagement users (1 feature or less, not logged in recently) → Check-in email + re-engagement offer
Custom objects released new branching capabilities in December 2024 that let you use object and relationship conditions across all campaign types — including segment-triggered campaigns. This means your user_health score, stored as a custom object attribute, can drive branching even in campaigns not triggered by an object event.
Day 60: Deepening Commitment
What's happening at day 60
Users who reach day 60 with healthy engagement have passed the highest-risk churn window. But "staying" is not the same as "invested." At this stage, the goal shifts from activation to commitment — getting users to integrate the product more deeply into their workflow, connect with other users, and build switching costs that make staying the obvious choice.
According to research from Bain & Company, increasing retention by just 5% can increase profits by 25–95%. And customers who stay past 90 days spend 67% more than new customers. Day 60 is when you lay the foundations for that deeper economic relationship.
Healthy engagement benchmarks at day 60
- Feature adoption depth: Engagement with 3+ core features, or deep usage of 1-2 complex features
- Integrations: At least one external integration connected (if your product supports them)
- Collaboration signals: If it's a team product, at least one other team member invited or active
- Support interactions: Few or no support tickets (especially not repeat queries about the same issue)
- NPS or CSAT: If you're surveying at 60 days, look for scores of 7+ (promoters and passives are fine; detractors at this stage are a strong churn signal)
Red flags at day 60
- Login frequency declining compared to days 1-30
- Only one user active on a team account
- No integrations connected on a product that has them
- NPS score of 6 or below
- Clicked a cancellation or downgrade link at any point, even if they didn't complete it
What to send at day 60
1. The Community Invitation
At 60 days, engaged users are ready to connect with their peers. A community invitation — to a Slack group, a user forum, a live webinar, or an in-person event — deepens commitment in a way no email sequence can replicate on its own.
The key is making the invitation feel earned, not generic. "Join 5,000 other [product] users" is weak. "You've been using [product] for 60 days and you've already done X — here's a community of people doing the same thing, at the same stage" is compelling.
If you have a case study or community member whose 60-day experience mirrors the recipient's, lead with that story. "Meet Sarah — she was exactly where you are 60 days in" is a powerful frame for a community invitation.
2. The Social Proof Moment
Day 60 is the right time to ask for a review or testimonial — and to show your user that others like them are getting results. This is a two-directional social proof play:
- Inbound: Ask for a review (G2, Capterra, Trustpilot, Google) or a brief testimonial
- Outbound: Share a relevant case study, a stat about what customers at their stage typically achieve, or a quote from a user with a similar profile
Moosend's research on social proof emails shows that reviews and testimonials perform best when they're specific, contextual, and matched to the recipient's situation — not generic five-star summaries.
For the review ask: keep it simple. One sentence of context, one direct link to the review platform. The email that says "It would mean the world to us if you'd leave a quick review — here's the link" outperforms the one with three paragraphs of preamble.
And don't underestimate the retention effect of asking. Research cited by Custify found that customers who submit feedback are 14% more likely to stay than those who don't. The act of reflection deepens the relationship.
3. The Integration or Expansion Nudge
If your product connects to other tools — CRM, analytics, Slack, etc. — day 60 is the time to push integrations for users who haven't connected them yet. Integrations create switching costs and deepen product value. An integrated user is considerably harder to churn than an isolated one.
Branch this campaign on whether the user has connected an integration. If yes, acknowledge it and introduce advanced usage tips for that integration. If no, make the value of connecting clear — not in abstract terms ("unlock even more power") but in specific terms ("If you're using Salesforce, here's what changes when you connect it").
4. The Progress Review
At 60 days, a personalised progress summary — "Here's what you've accomplished" — is a high-performing retention tool. Think Spotify Wrapped, but delivered at a meaningful lifecycle milestone instead of December.
What did they create? What did they achieve? What's the tangible output of 60 days of using your product? Pull this from your product data and include it in the email. Even a simple number ("You've processed 47 orders", "You've sent 23 campaigns", "Your team has saved an estimated 12 hours") makes the email feel personal and reminds users of the sunk cost — in a good way.
Customer.io setup for day 60
Use a segment-triggered campaign anchored on the 60-day mark, with branching based on your user_health custom object and a new attribute: integrations_connected (boolean) and team_size (integer).
Path structure:
- Branch 1: High engagement + team account → Community invitation + social proof ask
- Branch 2: High engagement + solo account → Progress review + integration nudge
- Branch 3: Medium engagement → Progress review + feature nudge for the next logical feature
- Branch 4: Low engagement → Winback sequence (this is now an at-risk user)
For the progress review email, use Customer.io's Liquid templating to pull in live data from the user's profile attributes. If you're tracking outputs as events, you can use Customer.io's aggregation features to count events and display them dynamically in the email.
Day 90: Investment and Expansion
What's happening at day 90
Day 90 is the end of the highest-churn window. Users who make it here with healthy engagement are significantly more likely to renew, expand, and refer. SaaS churn data from Salesso shows that monthly contracts churn at 18%, while annual plans churn at just 8% — and the 90-day period is often when the annual commitment conversation becomes relevant.
This is also the moment when net revenue retention (NRR) starts to matter. Userlens's 2025 benchmarks show the median NRR for B2B SaaS at 106%, with top-quartile performers exceeding 120%. Getting to NRR above 100% means your expansion revenue from existing customers outpaces your churn losses — and day 90 engaged users are your expansion cohort.
Healthy engagement benchmarks at day 90
- Retention: User still active with no cancellation signals
- Feature adoption rate: 60%+ of core features used at least once (top-quartile target: 75%+)
- NPS: 7 or above; you should be actively collecting this by day 90
- Referrals: Any evidence of word-of-mouth (referral link clicks, invited colleagues, shared outputs)
- Expansion signals: Any engagement with pricing pages, feature upgrade prompts, or higher-tier content
Red flags at day 90
- NPS score of 6 or below
- Zero logins in the past 14 days
- Any support ticket expressing dissatisfaction that wasn't resolved to their satisfaction
- Monthly plan user approaching renewal with no expansion
- Has visited cancellation or downgrade flow
What to send at day 90
1. The 90-Day Anniversary
Celebrate the milestone. Not with a generic "thanks for being a customer" — with a real summary of what they've achieved, what changed, and where they could go next.
Structure: backward look (what they've done) + forward look (what's next). The backward look validates their investment. The forward look creates momentum.
If you have data on what your top users look like at the 6-month mark, share that as a vision for where they're headed. "Customers like you who reach this point typically expand to [X] within the next 90 days" is a powerful anchor for both retention and upsell.
2. The Upsell or Expansion Ask
Day 90 is the right time for a direct expansion conversation — but it only works if it's grounded in their usage data. "You've hit the limit of your current plan 3 times this month" is a compelling upsell prompt. "Upgrade to Pro" is not.
Branch this campaign heavily. Only show expansion messaging to users with genuine expansion signals. Users without those signals should get a retention-focused message, not a pitch they'll ignore (or resent).
For team accounts, surface the multi-seat value: "You're the only active user on your account — here's how to bring your team in." Expanding seat count within an existing account is often easier than acquiring a new customer, and it's the fastest path to NRR above 100%.
3. The Referral Invitation
At 90 days, engaged users are primed to refer — they've seen enough value to recommend confidently, and the initial excitement hasn't worn off. A referral programme prompt at this stage typically outperforms earlier asks.
Keep the ask simple. Don't over-engineer the referral mechanic. The best referral emails focus on the outcome for the person being referred ("Give your team the same tool you've been using") rather than the incentive for the referrer.
4. The Renewal Anchor (for monthly plans)
For monthly subscribers approaching their third renewal, introduce the annual plan conversation. Frame it around savings and stability, not just price. "You've been getting value every month — locking in for a year saves you 20% and gives your team a committed tool to build around" is a retention play as much as a sales one.
Monthly SaaS plans churn at more than double the rate of annual plans (18% vs 8%). Moving monthly customers to annual is one of the highest-ROI retention activities a lifecycle programme can deliver.
Customer.io setup for day 90
The 90-day campaign is your most sophisticated. It branches on:
- Plan type (monthly vs annual vs enterprise)
- Feature adoption score (high vs medium vs low, from custom object)
- Team size (solo vs team account)
- Expansion signals (has visited pricing page, has used feature that requires upgrade, has hit usage limits — tracked as events)
- NPS score (if collected, stored as a profile attribute and available for branching)
A user on a monthly plan with high feature adoption and expansion signals gets the anniversary email + annual plan upsell + referral ask.
A user on an annual plan with low engagement gets the anniversary email + a personal check-in from customer success + a re-engagement offer.
A solo user on any plan gets a team invitation nudge.
The multi-split branch in Customer.io lets you handle all of this in a single campaign workflow rather than building separate campaigns for each segment. Less maintenance, more coherent logic.
How Custom Objects Make This All Dynamic
The campaigns above assume you have reliable data about what users have and haven't done. That data lives in your product — not by default in your email platform. Custom objects are how you bridge that gap.
Here's a practical example. Build a user_health custom object with these attributes:
features_used_count(integer — updated by your product)last_active_date(timestamp)integrations_connected(boolean)team_size(integer)nps_score(integer — updated when survey response received)health_tier(string — "green", "amber", "red" — calculated in your product or data warehouse and synced via Reverse ETL)
Each person in Customer.io is related to their user_health object. Every time the object updates — new feature used, new team member added, NPS score received — Customer.io can trigger a campaign or update a person's journey based on that change.
This is the object-triggered campaign approach released in January 2024. When the user_health object updates and the health_tier changes from "green" to "amber", the user enters a re-engagement journey automatically. You don't need a marketer to notice they're at risk and manually send something. The system does it.
Pair this with Customer.io's event schema and you have a lifecycle programme that adapts in real time to what's happening in your product — not just what calendar day it is.
For a deeper dive into how to structure your data model, our guide on integrating data sources with Customer.io covers APIs, Reverse ETL, and webhooks in detail.
Putting It Together: The 90-Day Retention Architecture
Here's how the full programme looks as a system:
Days 0–7 (Welcome sequence)
Linear drip. Gets users to activation. Standard stuff. This is where almost everyone stops.
Days 8–29 (Post-activation monitoring)
Track product events. Build your user_health object. Identify who's healthy and who's drifting. Send a mid-point check-in around day 14 for low-engagement users.
Day 30 (Consolidation)
Branch on health_tier and features_used_count. Feature adoption nudge OR milestone celebration OR check-in — based on behaviour.
Days 31–59 (Deepening)
Continuous behavioural triggers: new feature adoption emails when users are ready, not on a fixed schedule. Integration nudge if not connected. Progress tracking.
Day 60 (Commitment)
Branch on team_size and integrations_connected. Community invitation for engaged users. Progress review for mid-engagement users. Winback for low-engagement users.
Days 61–89 (Investment)
Social proof drip. Case studies matched to user profile. Referral seeding. Expansion-signal tracking.
Day 90 (Expansion and renewal)
Branch on plan type, expansion signals, NPS. Anniversary email everywhere. Upsell for ready users. Annual plan push for monthly subscribers. Re-engagement for low-health users.
Benchmarks Summary: What Healthy Looks Like at Each Stage
| Metric | Day 30 Healthy | Day 60 Healthy | Day 90 Healthy |
|---|---|---|---|
| Features used | 2+ core features | 3+ core features | 60%+ of all core features |
| Login frequency | 4-6x in past 30 days | Consistent with days 1-30 | Consistent or increasing |
| Email open rate | 40%+ (triggered) | 35%+ (triggered) | 30%+ (triggered) |
| NPS/CSAT | Not yet collected | 7+ if collected | 7+ (mandatory) |
| Team accounts | 1+ invited | 2+ active | 3+ active |
| Integrations | N/A | 1+ connected | 1+ connected |
| Expansion signals | None expected | Optional | Expected for healthy tier |
Any user hitting below these benchmarks is a re-engagement target at that stage — not a lost cause, but a signal to route them into a more direct outreach path.
One Final Thought
The Michelin brothers didn't create a restaurant guide to be nice. They created it because they understood that customer relationships require sustained investment. Every mile a driver put on their tyres was a result of a relationship Michelin had built — with a booklet, a star rating, a reason to keep going.
Your lifecycle marketing is that booklet. Not the welcome email — the whole thing. The 30-day check-in. The milestone celebration. The community invitation. The anniversary email. Every touchpoint is another reason for your customer to keep going, to go further, to need what you sell.
Stop going dark after day 7.
Frequently Asked Questions
What is lifecycle marketing beyond the welcome sequence?
Lifecycle marketing beyond the welcome sequence refers to the campaigns, automations, and communications you send after a customer has completed initial onboarding. While most brands focus on the first 7 days, post-welcome lifecycle marketing covers the 30, 60, and 90-day milestones — delivering feature adoption nudges, milestone celebrations, community invitations, and expansion prompts based on what users have and haven't done. The goal is to deepen engagement, reduce churn, and increase customer lifetime value through sustained, behaviour-driven communication.
Why do so many brands go dark after the welcome email?
Mainly because post-welcome lifecycle campaigns are harder to build. The welcome sequence has clear goals and a defined endpoint. Post-onboarding programmes require dynamic branching, product data integration, and the ability to handle divergent user paths. Litmus's 2024 lifecycle marketing report found that fewer than 44% of marketers use lifecycle emails for ongoing activation and retention — partly because it requires cross-functional effort and doesn't map neatly to a single KPI like open rate or revenue.
What should I send at day 30?
At day 30, your messaging should branch based on engagement level. High-engagement users should receive a feature adoption nudge (introducing the logical next feature based on what they've already used) or a milestone celebration. Moderate users should get a feature nudge. Low-engagement users should receive a direct check-in email — a single question asking if they're getting value, from a real person's email address. Avoid sending the same email to all three groups.
What is the difference between feature adoption and feature discovery emails?
Feature discovery emails tell users a feature exists. Feature adoption emails connect a feature to a specific user behaviour or need, making it relevant to that particular user at that particular moment. Discovery is calendar-based ("On day 14, tell them about Feature X"). Adoption is behaviour-based ("When a user has done A but not B, tell them about B because it solves the problem they're clearly experiencing"). Adoption emails consistently outperform discovery emails because they feel helpful rather than promotional.
How should I use Customer.io custom objects for lifecycle campaigns?
Custom objects let you bring non-person data — like account health scores, feature adoption counts, integration status, and team size — into Customer.io and use it to drive campaign branching. Build a user_health custom object with attributes like features_used_count, health_tier, last_active_date, and nps_score. Relate each person to their object, and use Customer.io's object-triggered campaigns and multi-split branches to route users into different lifecycle paths based on that data. This makes your campaigns respond to real product behaviour rather than calendar dates.
What is a healthy 30-day retention rate for SaaS?
According to Pendo's 2025 benchmarks, the average 30-day software user retention rate is 39%. Top-quartile performers retain significantly more. For B2B SaaS specifically, the 30-day retention expectation varies by product complexity, but a rate below 50% for a core productivity tool should trigger a review of your onboarding and early lifecycle communications. Userlens's 2025 data shows the median user retention rate for B2B SaaS at 85% annually, with top-quartile teams hitting 92%+.
When is the right time to ask for a referral?
Day 90 is the sweet spot for referral programme invitations. By 90 days, engaged users have seen enough value to recommend confidently, and they haven't yet settled into a passive "set and forget" usage pattern. Referral asks at day 7 or 14 are premature — users haven't had enough experience to make credible recommendations. Referral asks after 12 months risk catching users who are so habituated they've stopped thinking actively about the product's value.
How do I identify users at risk of churning before they cancel?
Build a customer health score that tracks leading indicators rather than lagging ones. Leading churn indicators include: declining login frequency (especially week-over-week drops), failing to adopt more than one core feature, not completing the core activation event, low NPS scores, multiple support tickets without resolution, and engaging with cancellation or downgrade flow pages. In Customer.io, store these as custom object attributes (e.g., health_tier: "amber" or health_tier: "red") and trigger re-engagement journeys automatically when a user drops into a lower health tier.
What is NRR and why does it matter for lifecycle marketing?
Net Revenue Retention (NRR) measures the revenue you retain and expand from your existing customer base over a period of time. NRR above 100% means your expansion revenue (upsells, seat additions, plan upgrades) from existing customers outpaces the revenue you lose to churn. Userlens's 2025 benchmarks show median NRR for B2B SaaS at 106%, with top performers above 120%. Lifecycle marketing at the 60 and 90-day marks directly drives NRR by creating the conditions for expansion — through feature adoption, team growth, and integration depth that justify plan upgrades.
How often should I email customers in the post-onboarding lifecycle?
There's no universal answer, but a useful framework: behaviour-triggered emails can fire whenever the trigger condition is met (with sensible frequency caps to avoid overwhelming users). For calendar-based lifecycle touchpoints, aim for one meaningful communication at day 30, one at day 60, and one at day 90 — supplemented by triggered emails as users hit (or miss) key milestones. Frequency fatigue is real; a re-engagement email that arrives too soon after a feature nudge undermines both. Use Customer.io's subscription centre to let users control their preference so the most engaged customers hear from you more and the passive ones don't disengage entirely.
Should B2B and B2C lifecycle programmes look different at these stages?
Yes, significantly. B2B programmes need to account for multiple users on a single account, role-based messaging (admins vs end users get different content), and account-level health metrics alongside individual user metrics. Custom objects in Customer.io make this easier — you can store account-level data as an object and use it to personalise messaging for every person related to that account. B2C programmes typically focus on individual behaviour and are more heavily influenced by purchase history and usage patterns. The 30/60/90 framework applies to both, but the content, tone, and branching logic will differ substantially.
What's the fastest way to improve retention if I'm starting from scratch?
Start with what you can ship fastest. A 30-day re-engagement email for inactive users — a single question, from a real person — takes a few hours to build and can surface churn risk before it becomes churn. Next, add a feature adoption email triggered when users have used Feature A but not Feature B within 28 days. These two campaigns alone address the most common post-onboarding failure modes. Build the full 30/60/90 architecture over the following weeks as you gather data on which paths drive the most impact. Perfect is the enemy of shipped — a decent 30-day programme running today beats a perfect 90-day architecture launching in three months.
Can I build these campaigns without a developer?
For the basic versions: yes. Customer.io's Journeys interface lets marketers build branching campaigns, set conditions, and write Liquid-based personalisation without writing code. The advanced version — where campaigns branch on custom object attributes synced from your product database — typically requires a developer to set up the initial data pipeline (whether via API, Reverse ETL, or direct integration). Once that plumbing is in place, marketers can build and modify campaigns independently. Our guide to Customer.io integrations covers the technical setup in detail.
How does behaviour-triggered messaging compare to calendar-based drips?
Behaviour-triggered messaging consistently outperforms calendar-based drips because it responds to what a user is actually experiencing, not just how many days they've been signed up. Acoustic's 2024 benchmark report found that automated and triggered communications yield superior results to standard campaign sends. A user who hit a feature limit yesterday is infinitely more receptive to an upgrade prompt today than they will be on a calendar-scheduled day 45. Calendar-based campaigns are a good starting point; behaviour-triggered campaigns are where the real retention lift lives. Our article on why time-based drips are dead covers the technical transition in detail.
Sources
- Pendo — SaaS Churn and User Retention Rate Benchmarks (2025)
- Salesso — SaaS Churn Statistics 2025: 10 Key Data Points for Growth
- Litmus — The State of Email in Lifecycle Marketing 2024
- Userlens — Retention Benchmarks for B2B SaaS in 2025
- GrowthFlow — 2024 Email Marketing Benchmarks
- Acoustic — 2024 Benchmark Report: How Email Marketing Is Evolving to Elevate Customer Engagement
- Customer.io — The Developer's Guide to Custom Objects (2024)
- Customer.io — Create Branches Based on Object and Relationship Conditions (December 2024)
- Epirus.vc — The Genius Marketing Strategy of Michelin (2025)
- MarketingLTB — Customer Retention Statistics 2025: 92+ Stats & Insights
- Sequenzy — Feature Adoption Emails: Getting Users to Discover and Adopt Features
- UserList — SaaS Milestone Emails + Examples (2024)
- Custify — SaaS Customer Onboarding and Retention Statistics
- Moosend — 10 Social Proof Email Examples and Best Practices (2024)
- Loyalty.cx — SaaS Onboarding Optimisation to Reduce Early Churn (2025)
