TL;DR — B2B SaaS onboarding works best when the email sequence does the heavy lifting and the app handles the interactive parts. Seven email patterns cover most B2B onboarding journeys — welcome, setup nudge, milestone celebration, feature reveal, check-in, expansion, and win-back.
In-app onboarding tours assume the user is in the app. B2B users often are not. Decision makers approved the purchase but the admin will use it, finance reviews the invoice, IT runs the integration. Email reaches everyone — the app reaches whoever is logged in right now.
The seven patterns
1. Welcome
Day 0. Plain text from a real person. What to do next, who to ask if stuck, where to find the docs. No marketing.
2. Setup nudge
Day 2-3. Sent only if setup is incomplete. Specific about what is missing — “you have not added users yet” beats “complete your setup”.
3. Milestone celebration
When the tenant hits a meaningful milestone (first 10 users, first export, etc.). Confirms they are on track, suggests the next step.
4. Feature reveal
Week 2-3. One feature they have not used that would be valuable based on their usage pattern. Specific to their context.
5. Check-in
Day 14, day 30. From a human, signed by a real person. Asks if there is anything in the way. Replies actually go to someone who can help.
6. Expansion
Day 45-60. Suggests the next tier or a related product based on usage. Always tied to a value moment they have already experienced.
7. Win-back
When engagement drops. Acknowledges the gap. Specific about what changed since they last engaged.
The single rule
Every email is sent because the data says it is the right moment. Not because the cron job said so. Trigger by behaviour, not schedule.
Frequently asked questions
Why email and not in-app?
Email reaches everyone who matters, not just the person who clicked Sign Up. Decision makers, finance, IT — they all read email. They do not all log into your app.
Should onboarding emails be automated or written by hand?
Automated with personalization. The structure is templated; the variables (tenant name, user role, current usage stage) come from your data. Hand-written feels artisanal but does not scale and breaks consistency.
Working on something similar?
T-Square architects, builds and operates production systems for learning, AI and custom software products. Talk to a senior engineer for a second opinion.