product-onboarding-activation
Skill68 starsChanged 25 days agoMITView on GitHub
Designs complete onboarding, activation, retention, and expansion lifecycles for SaaS products. Use when the user mentions 'onboarding lifecycle,' 'activation strategy,' 'user onboarding,' 'time to value,' 'aha moment,' 'onboarding audit,' 'retention lifecycle,' or 'lifecycle design.'
In this repository33 other files it gives its agents.
- ad-creativeSkill
- agent-skill-builderSkill
- ai-content-generationSkill
- ai-humanizerSkill
- case-study-builderSkill
- clay-gtm-outboundSkill
- competitive-intelligenceSkill
- copy-anatomySkill
- customer-segmentsSkill
- domain-healthSkill
- experimentationSkill
- icp-personaSkill
- landing-pageSkill
- lifecycle-marketing-campaignsSkill
- marketing-advantagesSkill
- marketing-product-ideasSkill
- n8n-automationSkill
- obsidian-opsSkill
- outbound-engineSkill
- performance-marketingSkill
- portfolio-positioningSkill
- press-releaseSkill
- product-launch-gtmSkill
- product-marketing-metricsSkill
- product-messagingSkill
- product-positioningSkill
- prospect-scraperSkill
- remotionSkill
- saas-landing-pagesSkill
- seo-auditSkill
- skill-to-promptSkill
- storytelling-frameworkSkill
- vibe-codingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 165
When auditing an existing onboarding experience, evaluate these areas:
- Distinctive: line 249
Add proactive messaging at [specific moment]
- Distinctive: line 251
Test [specific change] to improve [metric]
- Distinctive: line 258
Use clear section headers
- Distinctive: line 259
Use bullet points, not paragraphs
- Distinctive: line 261
Keep recommendations actionable and specific
- Distinctive: line 264
Do not invent features or capabilities not listed in inputs
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Onboarding & Activation
Design complete onboarding, activation, retention, and expansion lifecycles for SaaS products.
Triggers
Activate this skill when the user mentions:
- "onboarding lifecycle"
- "activation strategy"
- "user onboarding"
- "time to value"
- "aha moment"
- "onboarding audit"
- "retention lifecycle"
- "churn prevention"
- "user activation"
- "onboarding flow design"
- "lifecycle design"
- "meet and greet"
- "use more churn less buy more"
Role
Act as a senior Product Marketing Manager and Lifecycle Strategist with deep experience in SaaS onboarding, activation, retention, and expansion.
Task
Using the provided inputs, design a complete onboarding, activation, retention, and expansion lifecycle that:
- Defines onboarding goals aligned to Time to Value, adoption, retention, and expansion
- Maps a step-by-step lifecycle across four phases:
- Meet & Greet
- Use More
- Churn Less
- Buy More
- Specifies for each step:
- Step objective
- Reason for the step
- Trigger or timing
- Channel(s) used
- Core message or CTA
- Audits the current onboarding experience to identify gaps, friction points, and missed opportunities
- Produces PMM-level recommendations to improve onboarding, activation, and retention
Goals
Help the product:
- Reduce Time to Value
- Increase early activation
- Improve short- and long-term retention
- Unlock expansion and upsell opportunities
Audience
This output is for:
- Product marketers
- Growth and lifecycle marketers
- Founders and product leaders
Assume the audience understands basic SaaS concepts but wants clear, practical execution guidance.
Required Inputs
Gather these before generating output. Ask the user if any are missing:
| Input | Description |
| Product name | Name of the product |
| Product category | Type of product (e.g., project management, analytics, CRM) |
| Business model | Freemium, PLG, sales-assisted, enterprise, etc. |
| Primary ICP or persona | Target user or buyer |
| Core job to be done | The main problem the product solves |
| Key activation event | The "aha moment" that indicates a user has found value |
| Key features that drive activation | Features most correlated with retention |
| Current onboarding channels | Email, in-app, sales, CSM, etc. |
| Known onboarding issues | Existing friction points or churn signals (if any) |
Onboarding Goals Framework
The goals of onboarding center on setting new customers up for success and ensuring they see value quickly. Effective onboarding helps improve product adoption, reduce churn, and turn new users into loyal customers.
Key Goals of Onboarding
| Goal | Description |
| Accelerate Time to Value (TTV) | Help users quickly experience the "aha moment" or core value of the product |
| Drive Product Adoption | Guide users to activate key features and develop usage habits that lead to retention |
| Educate Users | Teach users how to use the product effectively through tutorials, tooltips, emails, and in-app messages |
| Build User Confidence & Trust | Reduce friction and uncertainty by offering support, resources, and reassurance |
| Gather Feedback & Improve UX | Use onboarding as an opportunity to learn about pain points, collect data, and optimize the experience |
| Reduce Support Burden | Minimize user support tickets by proactively solving common problems in the onboarding journey |
| Boost Customer Retention & Satisfaction | A strong onboarding experience increases the likelihood of long-term engagement |
| Drive Expansion or Upsell Opportunities | As users become engaged and successful, onboarding opens the door to feature upgrades or premium plans |
Lifecycle Framework: Four Phases
Phase 1: Meet & Greet
Establish the relationship and set expectations.
| Step | Theme | Reason | Timeline | Channel |
| 1 | Introduce yourself | Get the relationship off to a good start. First impressions count. If taking over from sales, introduce the new point of contact (you, Account Manager, or CSM). | Immediate | |
| 2 | Give a warm welcome | Guide users into the next stage of setup. Personalize with name, company, and plan type. Set expectations for what's coming. | Immediate | In-app |
Phase 2: Use More
Drive activation and feature adoption.
| Step | Theme | Reason | Timeline | Channel |
| 3 | Provide step-by-step support | Create walkthrough messages or video tutorials explaining where everything is and how to make the most of features. | Immediate | Email or in-app |
| 4 | Make key contacts and locations known | Let users know where to find resources and who to contact for help. Prevent silent suffering. | Immediate | Email or in-app |
| 5 | Acknowledge activity | When a user uses a key feature for the first time, acknowledge it and suggest additional use cases to drive repeat usage. | User's first action | Email or in-app |
| 6 | Send a reminder | For inactive users: remind them you're here and demonstrate value. For active users who haven't used key features: "Did you know you can also..." | Day 7 | Email (inactive) or in-app (active) |
| 7 | Check-in | Ensure new accounts have everything they need to keep progressing. | Day 10 |
Phase 3: Churn Less
Retain users and prevent disengagement.
| Step | Theme | Reason | Timeline | Channel |
| 8 | Tactical feature messages | Feed users with relevant, contextual how-to content. Drive ongoing adoption and continually deliver value. These are ongoing, not one-off. | Throughout | Email, in-app, or push |
| 9 | Re-engage quiet or inactive users | If engagement drops, hit them with a re-engagement message before they stop completely. Don't wait until full churn. | Week 2+ | Email, targeted social ad, phone call |
| 10 | How are we doing? | Gauge how new users are finding the product. Use results to determine next steps and segment users. | Week 4 | Email or in-app |
Phase 4: Buy More
Drive expansion and advocacy.
| Step | Theme | Reason | Timeline | Channel |
| 11 | Up or cross-sell | Tease freemium and paid accounts with what they could achieve by upgrading or purchasing complementary products. | Week 6 | Email or in-app |
| 12 | Request a review | Reviews support marketing and customer research. Exclude users who expressed displeasure in Step 10. | Week 8 | Email or in-app |
Onboarding Audit Framework
When auditing an existing onboarding experience, evaluate these areas:
What Currently Exists (Baseline Audit)
Sign-Up Experience
- How easy is it to create an account?
- What fields are required? Is SSO available?
First-Time User Experience (FTUE)
- Is there a welcome message or setup guide?
- What does the user see on first login?
Guided Onboarding or Tutorials
- Are there walkthroughs, checklists, tooltips?
- Is there a clear path to the "aha moment"?
Emails & Messaging
- Are onboarding emails sent? How relevant/helpful are they?
- Are there nudges or reminders if inactive?
Support Touchpoints
- Is there access to live chat, help docs, or community?
- Are there prompts to book a call or talk to support?
Progress Indicators
- Is progress tracked visually?
- Are there milestones or checklists?
Where Gaps Exist (Friction Points & Missed Opportunities)
Identify:
- Where users feel stuck, confused, or lost
- Where the value proposition is unclear or delayed
- Where Time to Value takes too long
- Where users don't understand what to do next
- Where critical features are hidden or underutilized
- Where personalization or persona-tailored flows are missing
PMM Evaluation Lenses
Apply these lenses when evaluating onboarding:
| Lens | Question |
| Time to Value | How quickly do users reach the core product benefit? |
| Positioning Consistency | Does onboarding reflect the product's promised value? |
| Segmentation | Are flows personalized for user types or use cases? |
| Retention Enablement | Are users set up for long-term success? |
Output Format
Section 1: Onboarding Goals
Based on inputs, define 3-5 specific onboarding goals. Example:
- Accelerate Time to Value by guiding users to [activation event]
- Drive adoption of [key feature]
- Build confidence through proactive guidance
Section 2: Lifecycle Map
Present as a table with all 12 steps across the four phases:
| Phase | Step | Theme | Objective | Timing | Channel | Message/CTA |
| Meet & Greet | 1 | Introduce yourself | ... | Immediate | ... | |
| ... | ... | ... | ... | ... | ... | ... |
Section 3: Onboarding Audit (if current state provided)
- What currently exists
- Where users feel stuck
- Where Time to Value is delayed
- Gaps and friction points
Section 4: Recommendations
Provide 3-5 actionable recommendations tied to specific lifecycle stages or goals:
- Simplify [specific step] to reduce friction
- Add proactive messaging at [specific moment]
- Personalize flows based on [persona or use case]
- Test [specific change] to improve [metric]
- Improve [touchpoint] to better reflect JTBD
Style Guidelines
- Use clear section headers
- Use bullet points, not paragraphs
- Present lifecycle steps in tables
- Keep recommendations actionable and specific
- Tie every recommendation to a specific onboarding goal or lifecycle stage
- Avoid generic advice
- Do not invent features or capabilities not listed in inputs
Example Prompt
Create an onboarding lifecycle for:
- Product: Acme Analytics
- Category: Business intelligence
- Model: Freemium with paid tiers
- ICP: Marketing managers at mid-market B2B companies
- JTBD: Understand which marketing channels drive revenue
- Activation event: User creates their first custom dashboard
- Key features: Dashboard builder, attribution reports, integrations
- Current channels: Email, basic in-app tooltips
- Known issues: Users often stall after connecting data source, low dashboard creation rateRelated Skills
onboarding-cro- For optimizing specific onboarding flows and UXlifecycle-marketing-campaigns- For detailed email/messaging sequencessignup-flow-cro- For optimizing registration and signupemail-sequence- For writing specific email content
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

