onboarding-orchestrator
정보
온보딩 오케스트레이터 스킬은 개발자가 자동화된 터치포인트를 갖춘 마일스톤 기반 고객 온보딩 플레이북을 설계하고 실행할 수 있게 합니다. 이 스킬은 성공 지표를 측정하고 신규 사용자의 빠른 가치 실현 시간을 추진하는 구조화된 프로그램을 구축하는 데 도움을 줍니다. 온보딩 시스템을 구축하거나 개선할 때 이 스킬을 사용하여 터치포인트를 자동화하고 효과성을 추적하세요.
빠른 설치
Claude Code
추천npx skills add guia-matthieu/clawfu-skills -a claude-code/plugin add https://github.com/guia-matthieu/clawfu-skillsgit clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/onboarding-orchestratorClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Onboarding Orchestrator
Create structured onboarding programs that drive rapid time-to-value through milestone-based playbooks, proactive touchpoints, and early success metrics.
When to Use This Skill
- Designing new onboarding programs
- Improving existing onboarding metrics
- Creating segment-specific playbooks
- Automating onboarding touchpoints
- Measuring onboarding effectiveness
Methodology Foundation
Based on Lincoln Murphy's First Value Delivery and Gainsight Onboarding Best Practices, focusing on:
- Time to First Value (TTFV)
- Milestone-based progression
- Success criteria definition
- Risk identification during ramp
What Claude Does vs What You Decide
| 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 |
Instructions
Step 1: Define Onboarding Phases
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 |
Step 2: Map Milestones per Phase
Kickoff Milestones:
- Kickoff call completed
- Success criteria documented
- Admin account created
- Integration requirements identified
- Timeline agreed
Setup Milestones:
- Technical setup complete
- Data migration (if needed)
- Integrations connected
- User accounts provisioned
- Admin trained
Adoption Milestones:
- First workflow created
- 50% users logged in
- First value moment achieved
- End user training complete
- Champion identified
Optimization Milestones:
- 80% users active
- Full use case deployed
- Self-service adoption
- QBR scheduled
- Expansion discussed
Step 3: Design Touchpoint Cadence
| Day | Type | Purpose | Owner |
|---|---|---|---|
| 0 | Welcome + next steps | Auto | |
| 1 | Call | Kickoff call | CSM |
| 3 | Setup checklist | Auto | |
| 7 | Call | Setup review | CSM |
| 14 | Training resources | Auto | |
| 21 | Call | Adoption check-in | CSM |
| 30 | 30-day survey | Auto | |
| 45 | Call | Value review | CSM |
| 60 | Optimization tips | Auto | |
| 90 | Call | QBR/Health check | CSM |
Step 4: Define Success Metrics
| 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 |
Examples
Example 1: B2B SaaS Onboarding Playbook
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:**
```markdown
## [Customer] Success Criteria
**Business Objectives:**
1. [Primary goal]
2. [Secondary goal]
**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):
- Progress review (10 min)
- Blocker resolution (10 min)
- Admin training preview (5 min)
- Next steps (5 min)
Admin Training Agenda (60 min):
- Platform overview (15 min)
- User management (15 min)
- Core workflows (20 min)
- 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:
1. How easy was onboarding? (1-5)
2. Did you achieve your first goal? (Y/N)
3. What could we improve?
4. NPS: How likely to recommend? (0-10)
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):
- Adoption metrics review (10 min)
- Value realization check (10 min)
- Expansion opportunities (5 min)
- 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 |
## Skill Boundaries
### What This Skill Does Well
- Structuring onboarding programs
- Defining milestones and metrics
- Creating touchpoint schedules
- Building playbook templates
### What This Skill Cannot Do
- Know your specific product setup
- Execute onboarding automatically
- Replace customer relationship skills
- Predict implementation blockers
### When to Escalate to Human
- Technical implementation issues
- Customer relationship problems
- Scope changes or delays
- Executive involvement needs
## References
- Lincoln Murphy's Customer Success Onboarding
- Gainsight Onboarding Best Practices
- Totango Time to First Value Guide
- ChurnZero Onboarding Automation
## Related Skills
- `account-health` - Post-onboarding health
- `churn-prediction` - Onboarding risk signals
- `expansion-signals` - Early expansion opportunities
## Skill Metadata
- **Domain**: Customer Success
- **Complexity**: Intermediate
- **Mode**: cyborg
- **Time to Value**: 2-4 hours for playbook design
- **Prerequisites**: Product knowledge, segment definitions
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
