Case study 01 / Activation
Stop the welcome series once the work is done.
Five emails that take a new team from an empty workspace to its first shared task — and why the branch that stops the sequence matters more than any subject line in it.
Activation path preview
- Sector
- B2B SaaS, team plan
- Lifecycle focus
- Signup → activation
- Read
- 6 minutes
The situation before the build.
This case study follows a B2B SaaS product with no shortage of new signups. The problem is what happens afterward.
Some customers create a workspace immediately. Others invite teammates. Some complete meaningful shared work on their own. But the onboarding emails continue according to a fixed schedule regardless of what the customer has already done.
Signup was happening. Activation was inconsistent.
The existing onboarding program treated every new customer as though they were at the same point in the journey.
A user who had already created a workspace could still receive an email asking them to create one. Someone who had already invited a teammate could receive another reminder to do exactly that.
The emails were technically automated, but the journey itself was not responding to customer behavior. The real problem was not the welcome email. It was that the CRM did not have a clear definition of where a customer was in the activation journey or what should happen when they moved forward without help.
We made customer progress control the sequence.
Instead of treating onboarding as five emails that had to be sent, the journey became a series of customer milestones.
The important question at every step became: What has this customer already done, and what is the next useful action?
Workspace creation became an entry signal. Inviting a teammate became another milestone. Completing the first shared task became the activation goal.
Once that goal was reached, the customer exited the onboarding sequence automatically. The work was done, so the workflow stopped.
A behavior-driven onboarding journey.
The lifecycle begins when a new customer creates their workspace.
If they have not invited a teammate after the agreed delay, the next email focuses on collaboration rather than giving them another generic product introduction.
If a teammate joins and the customer completes their first shared task, the activation goal is met and the sequence ends. If they do not progress, they move into a stalled-onboarding branch with messaging designed around the obstacle they still need to overcome.
Activation lifecycle path
Data contract
What the workflow needs to know.
| Property | Mode | Source |
|---|---|---|
| workspace_created_date | Reads | Product event |
| teammate_count | Reads | Product sync, hourly |
| first_shared_task_date | Reads | Product event · goal criteria |
| activation_stalled | Writes | Created as part of the build |
How we would know the new onboarding journey is working.
The measurement plan is built around activation behavior, not email engagement. We would judge the sequence by whether more new workspaces reach the shared-task milestone inside the agreed window.
We would compare an exposed group with a holdout over the same activation window. The workflow succeeds only if more new workspaces reach the shared-task milestone without creating a worse unsubscribe or complaint rate.
Signups reaching a first shared task within 14 days
Workspaces with a second member inside 7 days
Unsubscribe rate must not rise against the holdout
Your lifecycle
Have a similar problem in your system?
Tell us what is happening and what you want customers to do next.