CRM and Lifecycle skill 06 of 13

Onboarding and Activation Sequences SKILL.md

The Onboarding and Activation skill makes Claude, Codex or another AI agent design programmes that get new customers to first value fast. It defines one activation goal with a window, maps the path to value and its drop-offs, fixes product friction first, and builds behaviour-triggered email, in-app, push, SMS and human touchpoints with exits, stall branches, segment branching and a holdout to prove the effect.

onboarding-activation/SKILL.md, version 1.0.0, 1,731 words.

By Afeez Adebayo, Marketing, SEO & Growth Expert with 10+ years of experience.

Created 10 October 2026. Updated 10 October 2026. Free to use under CC BY 4.0.

Follow me onX LinkedIn

Download .md Skill folder (.zip)All 13 in one folder (.zip)

The first days after sign-up or first purchase decide whether someone becomes a lasting customer. Most onboarding is a welcome email, a feature tour and a discount. Effective onboarding has one job: get each new customer to the moment they experience real value, as quickly as possible, then build the habit.

This skill designs onboarding and activation programmes across email, in-app messages, push, SMS or WhatsApp and human touchpoints, driven by behaviour rather than a fixed calendar, with stall branches for people who get stuck and a holdout to prove it works.

Operating principles

One goal per sequence. Usually the value moment from the journey map: first project, first order received, second purchase.
Behaviour-triggered, not calendar-driven. Messages respond to what people have and haven't done.
Remove steps before adding messages. If onboarding friction is in the product, fix the product first.
Exit when the goal is met. Don't keep teaching someone a step they already took.
Measure activation against a holdout, not opens or clicks.

When to use, and when not to

Use it for new SaaS sign-ups and trials, first-time buyers in e-commerce, new subscribers, new app users and new B2B accounts after a sale.

Don't use it for existing customers at risk (retention-churn-prevention) or lapsed customers (win-back-reactivation).

Inputs to ask for, in one message

The value moment and activation definition (or the data to find it).
Steps between sign-up and value, with drop-off at each.
Channels available: email, in-app, push, SMS, WhatsApp, sales or customer success.
Current onboarding messages and results.
Segments that need different paths (role, use case, plan, acquisition source).

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as onboarding-activation/SKILL.md.

---
name: onboarding-activation
description: "Design onboarding and activation programmes that get new customers to first value fast: one activation goal with a window, the path to value and its drop-offs, product friction fixes, behaviour-triggered email, in-app, push, SMS and human touchpoints with exits, stall branches, segment branching, habit building, post-purchase sequences for e-commerce and holdout measurement. Use whenever someone asks about onboarding emails, welcome series, activation, trial conversion, first-week experience, post-purchase flows, time to value or why new users don't stick."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/onboarding-activation/
  category: marketing
  subcategory: crm-lifecycle
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Onboarding and Activation Sequences

The first days after sign-up or first purchase decide whether someone becomes a lasting customer. Most onboarding is a welcome email, a feature tour and a discount. Effective onboarding has one job: get each new customer to the moment they experience real value, as quickly as possible, then build the habit.

This skill designs onboarding and activation programmes across email, in-app messages, push, SMS or WhatsApp and human touchpoints, driven by behaviour rather than a fixed calendar, with stall branches for people who get stuck and a holdout to prove it works.

## Operating principles
1. **One goal per sequence.** Usually the value moment from the journey map: first project, first order received, second purchase.
2. **Behaviour-triggered, not calendar-driven.** Messages respond to what people have and haven't done.
3. **Remove steps before adding messages.** If onboarding friction is in the product, fix the product first.
4. **Exit when the goal is met.** Don't keep teaching someone a step they already took.
5. **Measure activation against a holdout,** not opens or clicks.

## When to use, and when not to
Use it for new SaaS sign-ups and trials, first-time buyers in e-commerce, new subscribers, new app users and new B2B accounts after a sale.

Don't use it for existing customers at risk (`retention-churn-prevention`) or lapsed customers (`win-back-reactivation`).

## Inputs to ask for, in one message
1. The value moment and activation definition (or the data to find it).
2. Steps between sign-up and value, with drop-off at each.
3. Channels available: email, in-app, push, SMS, WhatsApp, sales or customer success.
4. Current onboarding messages and results.
5. Segments that need different paths (role, use case, plan, acquisition source).

## Workflow

### Step 1. Define activation
One measurable event with a window: "created first invoice within 7 days", "second order within 45 days".

### Step 2. Map the path to value
List each step, its completion rate and median time. Identify the biggest drop-off.

### Step 3. Fix product friction
Work with product on the biggest drop-off: fewer fields, templates, sample data, better empty states, clearer prompts.

### Step 4. Design the core sequence
For each step: the message that helps complete it, the channel, the trigger (event or time since last action) and the exit rule.

### Step 5. Add stall branches
If someone hasn't completed a step within its expected time, send a branch that addresses the likely obstacle: a template, a short video, a case example, an offer of help from a person.

### Step 6. Personalise by segment
Different use cases need different first steps. Ask one question at sign-up ("What do you want to do first?") and branch on it.

### Step 7. Build the habit
After activation, a short sequence that encourages the second and third use, introduces one more valuable feature at a time and sets expectations for what comes next.

### Step 8. Measure
Activation rate, time to activate, retention at day 30, 60 and 90, compared with a holdout that receives minimal onboarding.

## Sequence blueprint (SaaS example)
| Trigger | Channel | Message intent | Exit |
|---|---|---|---|
| Sign-up | Email + in-app | Welcome, one first step, what to expect | Step done |
| No first action in 24h | Email | Remove the obstacle: template or 2-minute video | Step done |
| First action done | In-app | Celebrate briefly, show the next step | Next step done |
| No progress in 72h | Email from a named person | Offer help, ask what they're trying to do | Reply or progress |
| Activated | Email | What's possible next, one feature | Habit stage |
| Day 7 not activated | Sales or CS task (higher-value accounts) | Personal outreach | Activated |

## E-commerce post-purchase sequence
| Trigger | Message intent |
|---|---|
| Order placed | Confirmation with clear delivery expectations (transactional) |
| Shipped | Tracking, what to expect, how to get the best result from the product |
| Delivered + 3 days | How to use or care for it; short video or guide |
| Delivered + 14 days | Review request; help if something's wrong |
| Typical replenishment or second-purchase window | Relevant next product or reorder reminder |

## Writing onboarding messages
- One action per message, stated in the subject and the button.
- Show the outcome, not the feature ("send your first invoice in 2 minutes").
- Use the customer's data where it helps ("Your workspace 'Acme' is ready").
- Sign some messages from a real person and accept replies.
- Keep promotional offers out of the first messages unless the business model depends on them.

## Stall diagnosis: why people get stuck
| Stall signal | Likely obstacle | Branch message |
|---|---|---|
| Signed up, never returned | Unclear first step or wrong expectations | Restate the outcome and give one tiny first action |
| Started setup, abandoned it | Too many fields or missing information | Template, sample data or "finish in 2 minutes" link |
| Completed setup, no first use | Doesn't know what to do next | Example of a finished result similar to theirs |
| Used once, not again | No reason to return | Show the second use case or a reminder tied to their goal |
| Invited team, team never joined | Invitees lack context | Message the admin with a ready-to-send note for colleagues |

## Holdout design for onboarding
- Randomly assign a small share of new users (often 5 to 10%) to a minimal version: transactional messages only, or a single welcome.
- Keep the holdout for long enough to measure retention, not just activation (at least 30 to 60 days).
- Compare activation rate, time to activate and retention at fixed points.
- Report the difference with its range, and rotate or end the holdout once the answer is clear.

## Activation metrics dashboard
| Metric | Definition | Use |
|---|---|---|
| Activation rate | Share of new users reaching the goal within the window | Headline |
| Median time to activate | From sign-up to goal | Speed of onboarding |
| Step completion rates | Share completing each step | Finds friction |
| Stall branch recovery | Share who complete a step after its stall message | Branch effectiveness |
| Retention by activation status | Day 30, 60, 90 retention for activated vs not | Validates the goal |

## Channel roles in onboarding
- **In-app:** guidance at the moment of use; best for next steps.
- **Email:** bringing people back and teaching away from the product.
- **Push:** timely nudges for mobile apps, after permission is earned.
- **SMS or WhatsApp:** time-sensitive steps (delivery, appointments, verification) with consent.
- **Humans:** high-value accounts, complex setups and anyone who replies.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Team products (several users per account) | Track activation per account and per user; message admins and members differently |
| Long implementation (enterprise) | Combine automated messages with customer success milestones |
| Free plan with no trial deadline | Focus on habit and usage limits rather than urgency |
| Mobile apps | Use push and in-app first; request push permission after first value, not at launch |
| Gift purchases | Detect gift orders and skip product education for the buyer |

## Handoffs to related skills
- Finding the value moment: `customer-journey-mapping`
- Segments for branching: `lifecycle-segmentation`
- Message writing and design: `lifecycle-email-copy-design`
- SMS and WhatsApp steps: `sms-whatsapp-lifecycle`
- Holdout testing: `lifecycle-experimentation`
- B2B sales handoff: `lead-scoring-routing`

## Worked example
An invoicing app had a 22% activation rate (first invoice sent within 7 days). Most users dropped at adding a client. Product added a sample client and a template invoice; the new sequence asked one question at sign-up (freelancer or small business), sent a 90-second video when no invoice was created in 24 hours, and a reply-to-a-person email at 72 hours. Activation rose against a 10% holdout, and the holdout comparison showed the sequence, not the product change alone, added a meaningful share of the lift.

## Output format
```
# Onboarding plan: <product>, <date>
## Activation definition and current rate
## Path to value with drop-offs
## Product friction fixes
## Sequence blueprint (trigger, channel, intent, exit)
## Stall branches
## Segment variations
## Measurement and holdout design
```

## Common mistakes
- A fixed calendar of emails regardless of behaviour.
- Feature tours instead of a path to one outcome.
- Messages continuing after the step is done.
- Discount-led onboarding that trains customers to wait.
- No holdout, so nobody knows if onboarding works.

## Questions to ask before you design
- Which action best predicts retention, and how many reach it today?
- Where is the biggest drop-off, and can product fix it?
- Which channels can reach users when they're not in the product?

## Self-check before you answer
- Is there one activation goal with a window?
- Are messages triggered by behaviour with clear exits?
- Are stall branches designed for the biggest drop-offs?
- Is there a holdout to measure the effect?

## Further reading
- Customer.io, behaviour-based messaging guides: https://customer.io/learn
- Braze, onboarding resources: https://www.braze.com/resources

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/onboarding-activation/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Define activation

One measurable event with a window: "created first invoice within 7 days", "second order within 45 days".

Step 2. Map the path to value

List each step, its completion rate and median time. Identify the biggest drop-off.

Step 3. Fix product friction

Work with product on the biggest drop-off: fewer fields, templates, sample data, better empty states, clearer prompts.

Step 4. Design the core sequence

For each step: the message that helps complete it, the channel, the trigger (event or time since last action) and the exit rule.

Step 5. Add stall branches

If someone hasn't completed a step within its expected time, send a branch that addresses the likely obstacle: a template, a short video, a case example, an offer of help from a person.

Step 6. Personalise by segment

Different use cases need different first steps. Ask one question at sign-up ("What do you want to do first?") and branch on it.

Step 7. Build the habit

After activation, a short sequence that encourages the second and third use, introduces one more valuable feature at a time and sets expectations for what comes next.

Step 8. Measure

Activation rate, time to activate, retention at day 30, 60 and 90, compared with a holdout that receives minimal onboarding.

Sequence blueprint (SaaS example)

Trigger	Channel	Message intent	Exit
Sign-up	Email + in-app	Welcome, one first step, what to expect	Step done
No first action in 24h	Email	Remove the obstacle: template or 2-minute video	Step done
First action done	In-app	Celebrate briefly, show the next step	Next step done
No progress in 72h	Email from a named person	Offer help, ask what they're trying to do	Reply or progress
Activated	Email	What's possible next, one feature	Habit stage
Day 7 not activated	Sales or CS task (higher-value accounts)	Personal outreach	Activated

E-commerce post-purchase sequence

Trigger	Message intent
Order placed	Confirmation with clear delivery expectations (transactional)
Shipped	Tracking, what to expect, how to get the best result from the product
Delivered + 3 days	How to use or care for it; short video or guide
Delivered + 14 days	Review request; help if something's wrong
Typical replenishment or second-purchase window	Relevant next product or reorder reminder

Writing onboarding messages

One action per message, stated in the subject and the button.
Show the outcome, not the feature ("send your first invoice in 2 minutes").
Use the customer's data where it helps ("Your workspace 'Acme' is ready").
Sign some messages from a real person and accept replies.
Keep promotional offers out of the first messages unless the business model depends on them.

Stall diagnosis: why people get stuck

Stall signal	Likely obstacle	Branch message
Signed up, never returned	Unclear first step or wrong expectations	Restate the outcome and give one tiny first action
Started setup, abandoned it	Too many fields or missing information	Template, sample data or "finish in 2 minutes" link
Completed setup, no first use	Doesn't know what to do next	Example of a finished result similar to theirs
Used once, not again	No reason to return	Show the second use case or a reminder tied to their goal
Invited team, team never joined	Invitees lack context	Message the admin with a ready-to-send note for colleagues

Holdout design for onboarding

Randomly assign a small share of new users (often 5 to 10%) to a minimal version: transactional messages only, or a single welcome.
Keep the holdout for long enough to measure retention, not just activation (at least 30 to 60 days).
Compare activation rate, time to activate and retention at fixed points.
Report the difference with its range, and rotate or end the holdout once the answer is clear.

Activation metrics dashboard

Metric	Definition	Use
Activation rate	Share of new users reaching the goal within the window	Headline
Median time to activate	From sign-up to goal	Speed of onboarding
Step completion rates	Share completing each step	Finds friction
Stall branch recovery	Share who complete a step after its stall message	Branch effectiveness
Retention by activation status	Day 30, 60, 90 retention for activated vs not	Validates the goal

Channel roles in onboarding

In-app: guidance at the moment of use; best for next steps.
Email: bringing people back and teaching away from the product.
Push: timely nudges for mobile apps, after permission is earned.
SMS or WhatsApp: time-sensitive steps (delivery, appointments, verification) with consent.
Humans: high-value accounts, complex setups and anyone who replies.

Edge cases and judgement calls

Situation	What to do
Team products (several users per account)	Track activation per account and per user; message admins and members differently
Long implementation (enterprise)	Combine automated messages with customer success milestones
Free plan with no trial deadline	Focus on habit and usage limits rather than urgency
Mobile apps	Use push and in-app first; request push permission after first value, not at launch
Gift purchases	Detect gift orders and skip product education for the buyer

Finding the value moment: customer-journey-mapping
Segments for branching: lifecycle-segmentation
Message writing and design: lifecycle-email-copy-design
SMS and WhatsApp steps: sms-whatsapp-lifecycle
Holdout testing: lifecycle-experimentation
B2B sales handoff: lead-scoring-routing

Worked example

An invoicing app had a 22% activation rate (first invoice sent within 7 days). Most users dropped at adding a client. Product added a sample client and a template invoice; the new sequence asked one question at sign-up (freelancer or small business), sent a 90-second video when no invoice was created in 24 hours, and a reply-to-a-person email at 72 hours. Activation rose against a 10% holdout, and the holdout comparison showed the sequence, not the product change alone, added a meaningful share of the lift.

Output format

# Onboarding plan: <product>, <date>
## Activation definition and current rate
## Path to value with drop-offs
## Product friction fixes
## Sequence blueprint (trigger, channel, intent, exit)
## Stall branches
## Segment variations
## Measurement and holdout design

Common mistakes

A fixed calendar of emails regardless of behaviour.
Feature tours instead of a path to one outcome.
Messages continuing after the step is done.
Discount-led onboarding that trains customers to wait.
No holdout, so nobody knows if onboarding works.

Questions to ask before you design

Which action best predicts retention, and how many reach it today?
Where is the biggest drop-off, and can product fix it?
Which channels can reach users when they're not in the product?

Self-check before you answer

Is there one activation goal with a window?
Are messages triggered by behaviour with clear exits?
Are stall branches designed for the biggest drop-offs?
Is there a holdout to measure the effect?

When to use this skill, and when not to

Use it for new SaaS sign-ups and trials, first-time buyers in e-commerce, new subscribers, new app users and new B2B accounts after a sale.

The first days decide whether someone becomes a lasting customer. A welcome email, a feature tour and a discount rarely change that. Onboarding that responds to what each person has and hasn’t done, and helps them past the step where most people stop, does.

Don’t use it for existing customers at risk (use Retention and Churn Prevention) or lapsed customers (use Win-Back and Reactivation).

Example prompts

“Design a behaviour-based onboarding sequence to raise trial activation.”
“Most users drop at adding a client. Fix onboarding around that step.”
“Build a post-purchase sequence for first-time buyers.”
“Set up a holdout to prove onboarding works.”
“Write stall branches for users who sign up and never return.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Onboarding plan: example invoicing app, 10 October 2026

## Activation
First invoice sent within 7 days. Current: 22%.

## Biggest drop-off
Adding a client (product fix: sample client and template invoice)

## Sequence
| Trigger | Channel | Intent | Exit |
| Sign-up | Email + in-app | One first step | Invoice sent |
| No invoice in 24h | Email | 90-second video | Invoice sent |
| No progress in 72h | Email from a person | Offer help | Reply or progress |

## Holdout: 10% minimal onboarding for 60 days

Every message has a trigger and an exit, so nobody keeps being taught a step they already took.

What the agent needs from you

The skill asks for the value moment and activation definition (or the data to find them), the steps between sign-up and value with drop-off at each, available channels, current onboarding messages and results, and the segments that need different paths, such as role, use case, plan or acquisition source.

How this skill hands off to related skills

Onboarding depends on the rest of the set. The value moment comes from Customer Journey Mapping, branches from Lifecycle Segmentation, messages from Lifecycle Email Copy and Design, SMS and WhatsApp steps from SMS and WhatsApp, holdouts from Lifecycle Experimentation and B2B handoffs from Lead Scoring and Routing.

How to run Onboarding and Activation step by step

Install the skill as onboarding-activation/SKILL.md.
Share the activation definition, or event data to find it.
Export step completion and drop-off between sign-up and value.
List channels and current messages with results.
Review product fixes, the sequence, stall branches and segment paths.
Launch with a holdout and compare activation and retention.

Situations this skill handles

Onboarding fails in different places. The skill handles these situations:

Situation	What the skill does
Sign-ups never return	Restates the outcome and gives one tiny first step
Setup abandoned halfway	Offers templates, sample data or a short finish link
Team product, invitees never join	Gives admins a ready-to-send note for colleagues
First-time e-commerce buyers	Builds post-purchase care, review and second-purchase steps
Enterprise implementations	Combines automation with customer success milestones
Gift orders	Skips product education for the buyer

What makes this skill different

Most onboarding is a calendar of emails and a feature tour. This skill builds around one activation goal, fixes product friction before adding messages, triggers each message from behaviour, stops when the step is done and branches when someone stalls.

It also measures the right thing: activation and retention against a holdout, not opens or clicks, so the team knows whether onboarding changes behaviour or just adds mail.

Practical tips from real projects

One action per message, named in the subject and the button.
Fix the biggest drop-off in the product before writing a single email.
Sign some messages from a real person and accept replies.
Exit as soon as the goal is met.

A worked example: an invoicing app had a 22% activation rate, with most users dropping at adding a client. Product added a sample client and a template invoice. The new sequence asked one question at sign-up (freelancer or small business), sent a 90-second video when no invoice was created in 24 hours and a reply-to-a-person email at 72 hours. Activation rose against a 10% holdout, and the comparison showed the sequence added meaningful lift beyond the product change alone.

Post-purchase onboarding matters as much in e-commerce. A confirmation with clear delivery expectations, a shipping message with tips for getting the best result, a care or how-to message a few days after delivery, a review request and a well-timed reminder at the typical second-purchase window turn a first order into a relationship.

Channel roles keep messages from piling up. In-app guides people at the moment of use; email brings them back and teaches away from the product; push nudges mobile users once permission is earned; SMS and WhatsApp handle time-sensitive steps with consent; and people step in for high-value accounts and anyone who replies.

The skill also includes a stall diagnosis table that links each stall signal to its likely obstacle and the branch message that addresses it, plus an activation dashboard: activation rate, median time to activate, step completion, stall recovery and retention by activation status.

Holdouts are what make onboarding defensible. A small random group receiving only transactional messages, kept for long enough to measure retention, turns “we think onboarding helps” into a number leadership can plan around.

Ask one question at sign-up, such as what people want to do first, and branch on the answer. Different use cases need different first steps.

Changelog

1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.

Previous skillLead Scoring and Routing Next skillRetention and Churn Prevention

All CRM and Lifecycle Marketing skills