Design and execute customer onboarding playbooks with milestones, success metrics, and automated touchpoints
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill onboarding-orchestrator
> Create structured onboarding programs that drive rapid time-to-value through milestone-based playbooks, proactive touchpoints, and early success metrics.
Based on Lincoln Murphy's First Value Delivery and Gainsight Onboarding Best Practices, focusing on:
| Claude Does | You Decide |
|-------------|------------|
| Designs milestone frameworks | Implementation timeline |
| Creates touchpoint schedules | Resource allocation |
| Identifies success metrics | Definition of "success" |
| Suggests automation triggers | Tool selection |
| Builds playbook templates | Customization per segment |
Standard 4-Phase Model:
| Phase | Duration | Focus | Exit Criteria |
|-------|----------|-------|---------------|
| Kickoff | Week 1 | Alignment, access | Kickoff complete, logins work |
| Setup | Week 2-3 | Configuration | Core setup done |
| Adoption | Week 4-6 | First use case | TTFV achieved |
| Optimization | Week 7-12 | Full rollout | Steady state reached |
Kickoff Milestones:
Setup Milestones:
Adoption Milestones:
Optimization Milestones:
| Day | Type | Purpose | Owner |
|-----|------|---------|-------|
| 0 | Email | Welcome + next steps | Auto |
| 1 | Call | Kickoff call | CSM |
| 3 | Email | Setup checklist | Auto |
| 7 | Call | Setup review | CSM |
| 14 | Email | Training resources | Auto |
| 21 | Call | Adoption check-in | CSM |
| 30 | Email | 30-day survey | Auto |
| 45 | Call | Value review | CSM |
| 60 | Email | Optimization tips | Auto |
| 90 | Call | QBR/Health check | CSM |
| Metric | Target | Measurement |
|--------|--------|-------------|
| Time to Kickoff | <3 days | Contract → Kickoff |
| Time to Setup | <14 days | Kickoff → Setup complete |
| Time to First Value | <30 days | Contract → First use case |
| 30-day activation | >70% | Users logged in |
| 60-day adoption | >50% | Users weekly active |
| Onboarding CSAT | >4.5 | Survey score |
| Onboarding NPS | >50 | Survey score |
Output:
## Customer Onboarding Playbook: Enterprise Segment
### Overview
- **Segment**: Enterprise ($100K+ ARR)
- **Target TTFV**: 45 days
- **CSM:Account Ratio**: 1:15
- **Onboarding Duration**: 90 days
---
### Phase 1: Kickoff (Days 0-7)
**Objectives:**
- Establish relationship and trust
- Align on success criteria
- Set expectations and timeline
**Milestones:**
| Milestone | Owner | Day | Status |
|-----------|-------|-----|--------|
| Welcome email sent | Auto | 0 | |
| Kickoff scheduled | CSM | 1 | |
| Kickoff call completed | CSM | 3 | |
| Success criteria doc sent | CSM | 4 | |
| Technical requirements gathered | CSM | 5 | |
| Project plan shared | CSM | 7 | |
**Kickoff Call Agenda (60 min):**
1. Introductions (5 min)
2. Business objectives (15 min)
3. Success criteria definition (15 min)
4. Technical overview (10 min)
5. Timeline and milestones (10 min)
6. Q&A and next steps (5 min)
**Success Criteria Template:**
Business Objectives:
Success Metrics:
| Metric | Baseline | Target | Timeline |
|--------|----------|--------|----------|
| [Metric 1] | X | Y | 90 days |
Key Stakeholders:
| Name | Role | Involvement |
|------|------|-------------|
Risks/Dependencies:
-
**Exit Criteria → Phase 2:**
- [ ] Kickoff call complete
- [ ] Success criteria documented and signed off
- [ ] Technical requirements understood
- [ ] Project timeline agreed
---
### Phase 2: Setup (Days 8-21)
**Objectives:**
- Complete technical implementation
- Configure product for use case
- Provision and train admins
**Milestones:**
| Milestone | Owner | Day | Status |
|-----------|-------|-----|--------|
| SSO/Auth configured | Tech | 10 | |
| Core integration connected | Tech | 12 | |
| Data migration complete | Tech | 14 | |
| Admin accounts created | CSM | 14 | |
| Admin training session | CSM | 16 | |
| Setup review call | CSM | 21 | |
**Setup Check-In Call (Day 14, 30 min):**
1. Progress review (10 min)
2. Blocker resolution (10 min)
3. Admin training preview (5 min)
4. Next steps (5 min)
**Admin Training Agenda (60 min):**
1. Platform overview (15 min)
2. User management (15 min)
3. Core workflows (20 min)
4. Reporting basics (10 min)
**Exit Criteria → Phase 3:**
- [ ] Technical setup 100% complete
- [ ] At least 1 admin trained
- [ ] Users provisioned
- [ ] No open blockers
---
### Phase 3: Adoption (Days 22-45)
**Objectives:**
- Achieve first value moment
- Drive user adoption
- Establish usage patterns
**Milestones:**
| Milestone | Owner | Day | Status |
|-----------|-------|-----|--------|
| End user training scheduled | CSM | 22 | |
| First training session | CSM | 25 | |
| First workflow live | Customer | 28 | |
| 50% users logged in | - | 30 | |
| First value achieved | - | 35 | |
| Adoption review call | CSM | 45 | |
**End User Training (60 min per session):**
- Session 1: Core functionality
- Session 2: Advanced features
- Session 3: Best practices
**First Value Checklist:**
- [ ] Primary use case configured
- [ ] First real work completed
- [ ] Customer confirms value
- [ ] Quote-worthy moment captured
**30-Day Survey:**
**Exit Criteria → Phase 4:**
- [ ] First value moment achieved
- [ ] 50%+ users logged in
- [ ] No critical blockers
- [ ] Customer confirms progress
---
### Phase 4: Optimization (Days 46-90)
**Objectives:**
- Full use case deployment
- Drive to steady-state adoption
- Prepare for ongoing success
**Milestones:**
| Milestone | Owner | Day | Status |
|-----------|-------|-----|--------|
| Second use case identified | CSM | 50 | |
| Full team rollout | Customer | 60 | |
| 80% adoption achieved | - | 75 | |
| QBR scheduled | CSM | 80 | |
| Handoff to ongoing success | CSM | 90 | |
**60-Day Check-In (30 min):**
1. Adoption metrics review (10 min)
2. Value realization check (10 min)
3. Expansion opportunities (5 min)
4. Ongoing cadence (5 min)
**90-Day QBR Handoff:**
- Full value review
- Health score baseline
- Ongoing success plan
- Expansion discussion
---
### Automation Triggers
| Trigger | Action | Timing |
|---------|--------|--------|
| Contract signed | Welcome email | Immediate |
| Day 3, no kickoff | Alert CSM | Day 3 |
| Setup incomplete | Nudge email | Day 18 |
| Day 30, <25% login | Risk alert | Day 30 |
| First value achieved | Celebration email | On event |
| Day 45, low adoption | Intervention call | Day 45 |
---
### Risk Indicators
| Signal | Risk Level | Response |
|--------|------------|----------|
| No kickoff by Day 5 | 🟠 High | Escalate internally |
| Setup blocked >7 days | 🟠 High | Technical escalation |
| <25% login at Day 30 | 🔴 Critical | Intervention call |
| Champion disengaged | 🟠 High | Find alternate contact |
| No first value by Day 45 | 🔴 Critical | Executive involvement |
account-health - Post-onboarding healthchurn-prediction - Onboarding risk signalsexpansion-signals - Early expansion opportunitiesComprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII), for FDA regulatory data analysis and safety research.
MATLAB and GNU Octave numerical computing for matrix operations, data analysis, visualization, and scientific computing. Use when writing MATLAB/Octave scripts for linear algebra, signal processing, image processing, differential equations, optimization, statistics, or creating scientific visualizations. Also use when the user needs help with MATLAB syntax, functions, or wants to convert between MATLAB and Python code. Scripts can be executed with MATLAB or the open-source GNU Octave interpreter.
UMAP dimensionality reduction. Fast nonlinear manifold learning for 2D/3D visualization, clustering preprocessing (HDBSCAN), supervised/parametric UMAP, for high-dimensional data.
Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.
Access AlphaFold 200M+ AI-predicted protein structures. Retrieve structures by UniProt ID, download PDB/mmCIF files, analyze confidence metrics (pLDDT, PAE), for drug discovery and structural biology.
Take guia-matthieu/onboarding-orchestrator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.