Growth
Growth · ◉ Evergreen

Your onboarding emails are a re-activation loop wearing a welcome mat.

by · ·4 min·Working Theory

Most onboarding email tries to teach. The sequences that actually move retention do something humbler: each message buys one return trip to the moment the product pays off. Here's how to design and measure email as a loop, not a lecture.

Open almost any product’s onboarding email sequence and you’ll find a curriculum. “Welcome!” Then “Here are 5 features you’ll love.” Then “Did you know you can…” It reads like a syllabus, and it performs like one: people skim it, feel vaguely behind, and don’t come back. The open rates look fine. The retention curve doesn’t move. Everyone concludes email doesn’t work for their product and quietly lets the sequence rot.

The mistake is in the genre. Onboarding email isn’t education. It’s a loop — and its one job is to generate return trips to the single moment where your product actually pays off, during the short window before that return becomes a habit the user makes on their own.

Here’s the window. A new user has, at best, felt your product’s value once. One good moment is not a habit; it’s a memory, and memories decay. For a while the user still could come back, but they have no cue telling them to and no groove worn yet. That gap — between the first taste of value and the point where returning is automatic — is where almost all your activated users leak away. Email (and push, and any channel you own) is the thing that reaches across the gap and pulls them back for trip two, and trip three, until the product’s own payoff is doing the pulling instead of you.

Which means a good onboarding message has exactly one move: get the user to do one valuable thing again. Not learn about five things. Do one thing — the thing — one more time. Everything else is noise competing with that single call to action.

odds of returning unprompted, left alone value moment one email = one return trip user leaves pulled back
Email isn't the curriculum. It's the pull across the gap — each message buys one more return trip until the product's own payoff takes over. Original diagram · Working Theory

If that’s the job, two things follow for how you build it. First, design the sequence backward from the sessions you need, not forward from your feature list. You want a second session and a third; so message one aims at the second session’s single most valuable action, and its timing is set by how fast the memory of value fades, not by “send on day 1, 3, 7” out of habit. Reach them while the slope still favors a return — on the shoulder of the forgetting curve, not at the bottom of it. Second, the content is a doorway, not a destination. The email’s whole purpose is to end inside the product, at the value moment, with the smallest possible distance between the tap and the payoff. If your email teaches someone something and they close it satisfied, you lost.

Now the measurement, which is where most teams go wrong and conclude email is dead. Opens and clicks measure the email. They don’t measure the loop. The number that matters is return trips the email actually caused — users who came back and did the valuable thing because the message reached them, proven against a holdout that got no message. An email with a mediocre open rate that reliably drags people back to value is worth ten beautiful ones that get admired and closed.

Do this and the sequence stops being a welcome mat you lay down once and forget. It becomes what it always was underneath: a loop you own, running quietly in the gap, buying return trips one at a time until the user doesn’t need it anymore. That last part is the goal. The best onboarding loop is one that works so well it makes itself unnecessary.

Sources

  • Hermann Ebbinghaus's forgetting curve
  • holdout-test causal measurement practice

Liked this? Get the next one in Working Theory.

Going weekly in August (it's in beta now). One genuinely interesting read on building, the brain, and the science most people missed.

Subscribe →
Got a reaction, a counter-example, or something I missed? Reply by email — I read everything.
◉ join in

Where have you hit this — in a product you use, or one you're building?

Threads open here soon. For now, the conversation lives two clicks away — discuss on GitHub, or just reply by email. I read and answer everything.