Onboarding guide · 5 minute read

Your first email needs one useful job.

Choose the smallest unfinished action that brings the right user closer to a result they signed up for.

← All guides

What is a first-value email?

It helps a new user complete a meaningful task in your product. Account creation tells you they arrived; it does not tell you they received value. Start by naming an observable result, then work backward to the next missing step.

Choose an outcome you can verify

For a shared project tool, that might be a task completed with a teammate. For caption software, it might be a corrected caption export. For a practice app, it might be a first session logged. These are illustrative hypotheses: confirm what matters for your own product and audience before using them.

Write to the person who can act

A workspace owner may be able to invite teammates; an invited member may only be able to accept an invitation. Sending both people the same instructions creates avoidable friction. Define the recipient’s role and permissions before writing the subject line.

Make one request

A helpful draft can be brief: “Your first project is ready. Add the task you want to finish next, then invite the teammate who will work on it with you.” Use this only if those facts are true. Add a destination you have verified, describe the action in ordinary language, and avoid invented button names or promises about how long it will take.

Stop once the task is complete

Check the user’s current state when the email is about to send. If they completed the task, left the workspace, paused onboarding or opted out, the original nudge may no longer belong in their inbox. Unknown state should pause delivery until it can be resolved.

Measure the task, then test the email

Track eligible recipients, delivery and completion of the intended action in an agreed window. An increase after launch is not proof the email caused it. A suitable randomized holdout can help estimate incremental effect when your traffic is sufficient. Avoid declaring success from opens alone.

Research behind this recommendation

Sequenzy’s welcome-sequence guide provides a useful practitioner perspective. Its examples should be adapted to your product; they do not establish one optimal sequence for every SaaS.

Next: write the event and stop rules.

Find the next useful email for your product.

Start with your website or a short description. The diagnostic is free.

Start free