Pick a goal, an audience, and a length. You get the full sequence framework: what each email does, when it sends, and what moves someone out of it. Every sequence ends by widening the relationship, not just closing the loop.
Get a new account to its first real win fast, then turn the win into expansion surface.
New customer lensThey already said yes. The job is momentum, not persuasion. Cut any block that re-sells the product; replace claims with their own usage. Speed-to-first-win is the metric.
EMAIL 01Set the one outcome that defines success in week one.
Day 0, within an hour of signup/kickoff
Subject angle
Name the win, not the welcome. "Your first ___ by Friday."
CTA
Do the one action.
Body skeleton
- One sentence: the single outcome to hit this week.
- The one action that gets it (link straight into the product, not a docs portal).
- Their human, by name and face. Not a support alias.
Exit / branchAction completed → skip to email 3. No action in 48h → email 2.
EMAIL 02Remove the first blocker before they name it.
Day 2, only if the first action hasn't happened
Subject angle
Address the stall directly. "Stuck on step one? It's usually this."
CTA
Finish the step (one click back in).
Body skeleton
- Name the most common blocker plainly.
- A 90-second video or GIF showing the fix.
- An interactive checklist of the 3 setup steps, with the next one highlighted.
Exit / branchStill no action in 3 more days → route to CSM as a human task. Action → email 3.
EMAIL 03Mark the first win and show what it makes possible.
On the first-win event (or day 7, whichever comes first)
Subject angle
Mirror their result. "You just did ___. Here's what that unlocks."
CTA
Try the next capability.
Body skeleton
- Show their own number or artifact back to them.
- One next capability that builds directly on the win.
- A customer example one step ahead of them.
Exit / branchCapability adopted → email 5. Ignored twice → stay journey-paced, no pressure sends.
EMAIL 04Turn one user into a team.
Day 14
Subject angle
The team angle. "This gets better when ___ sees it too."
CTA
Invite one teammate.
Body skeleton
- One concrete multi-seat use case in their world.
- Make inviting a teammate the entire email: one action, zero friction.
- What the teammate sees on first open (so the invite feels safe).
Exit / branchInvite sent → tag account as expansion-curious; CS notified. None → email 5 anyway.
EMAIL 05Establish the value cadence: usage back to them, monthly.
Day 30
Subject angle
Their number, not yours. "Your first month: ___."
CTA
One-click into the underused feature.
Body skeleton
- A small usage recap. 3 numbers max, theirs.
- One underused feature tied to their actual pattern.
- Set the rhythm: this recap arrives monthly.
Exit / branchHealthy usage → graduate to the expansion track. Flat usage → CSM alert with the recap attached.