Most welcome sequences fail the same way: someone copies a "best practices" list, sends three emails a day apart, and wonders why the third one gets ignored. Timing is not decoration on top of good copy. It is the part that decides whether the email arrives while the moment it is about still means anything.
Below are five sequences that hold up, with the delay between each step and the reasoning behind it. None of them need custom code. Any of them can be built with a trigger event and a goal.
1. The bare-minimum SaaS trial
For a product simple enough that someone can get value in one sitting.
- Immediately: welcome + the one thing to do first. Not a feature tour. One action, one link. If your product has a clear "aha" step, this email exists to get them to it.
- Day 1: did that work? A short check-in, branched if you can: one version for people who completed the first action, a different nudge for people who did not.
- Day 4: something they probably haven't found yet. A second feature, picked for relevance rather than completeness. This is also where a soft upgrade mention belongs, if your trial has a paid tier.
Goal: activation.completed or whatever event marks the aha moment. Anyone who hits it stops receiving the rest of the sequence automatically, so a person who activates on day 1 never gets a day-4 email nudging them toward something they already did.
2. The longer B2B trial (14-21 days)
Enterprise-ish tools where the buyer isn't the only user and the decision takes longer than a week.
- Immediately: welcome, plus who else should be here. Team products die quietly when only the signer ever logs in. Ask them to invite someone in the first email, not the fifth.
- Day 2: the setup step most people skip. Whatever configuration unlocks the real value (a data source connected, an integration turned on) and skipping it is why so many trials end with "we never really used it."
- Day 7: a proof point, not a feature. A number, a before/after, a short case study. Halfway through a long trial is when doubt sets in; this is the email that answers "is this actually worth switching to."
- Day 12: trial ending, here's what happens. Plain information: what converts, what doesn't, what to do before it expires. No countdown theatrics, just the facts someone needs to make a decision.
Goal: subscription.created. This is the sequence most worth simulating before it goes live, since a wrong delay here costs you a week, not a day.
3. Ecommerce, post-purchase
The trigger isn't signup, it's order.placed, and the job is retention, not activation.
- Immediately: order confirmation. This one is usually transactional, not part of the sequence, but it sets the tone for what follows.
- Day 3: how to get the most out of it. Care instructions, setup, pairing suggestions, whatever turns "I bought a thing" into "I use this thing." Too early and it arrives before the box does; too late and they've already formed an opinion without your help.
- Day 10: a review ask. By now they've had time to actually use it. Asking on day 1 gets you "seems fine so far," which isn't worth much to anyone reading reviews later.
- Day 21: a relevant second purchase. Timed to the product's natural replenishment or upgrade cycle, not a fixed number that's the same for a $12 item and a $400 one.
Goal: a second order.placed event, so the sequence stops nagging someone who already came back on their own.
4. Free tool, no trial clock
Free forever, or free until a usage cap, with no expiration pressure to create urgency around.
- Immediately: welcome + the fastest path to output. No countdown to fight against, so the whole job is getting them to a result before they forget why they signed up.
- Day 5: a use case they probably haven't tried. Free tools tend to get used for one narrow thing. This is the email that shows the second thing, picked for whoever hasn't done it yet.
- Day 14: what upgrading actually gets you. Only if there's a paid tier, and only framed around something they've already bumped into (a cap, a limit, a locked feature), not a generic pricing pitch.
Goal: usually none, or a soft one like feature.used a second time. Without urgency, timing is the only lever you have. Space it too tight and it reads as needy; too loose and the product has already left their mind.
5. Newsletter or community signup
Lowest stakes, but still worth sequencing instead of dropping straight into the regular send schedule.
- Immediately: welcome + what to expect. Frequency, topics, and one genuinely good piece of existing content, so the first impression isn't "we'll be in touch."
- Day 3: your best evergreen piece. Not your latest post. Your best one, regardless of when it was published, since this person hasn't seen any of it yet.
- Then: fold into the regular schedule. A welcome sequence for a newsletter should be short. Its only job is the handoff from "just signed up" to "now getting the normal emails," and it shouldn't outlast that.
What the delays have in common
None of these are arbitrary. Each gap is answering a specific question: how long does it take someone to actually do the thing the previous email asked, and how long can you wait before the moment stops being relevant. A day-1 check-in on a five-minute setup is too early to matter. A day-1 check-in on a two-week enterprise trial is too early to know anything either, just for different reasons.
If you're not sure a delay is right, simulate the sequence with a test contact and watch the timeline before it goes to real signups. Adjusting a wait step later is easy; the harder problem to notice is a sequence that's been mistiming every welcome email for a month because nobody watched it run once.
Start with build a welcome sequence if you're setting up your first one, or describe the flow you want and Pombo drafts the steps for you to adjust.