返回技能列表

onboarding-orchestrator

guia-matthieu
更新于 2 days ago
6 次查看
111
20
111
在 GitHub 上查看
设计automationdesign

关于

The onboarding-orchestrator skill enables developers to design and execute milestone-based customer onboarding playbooks with automated touchpoints. It helps create structured programs that measure success metrics and drive rapid time-to-value for new users. Use this skill when building or improving onboarding systems to automate touchpoints and track effectiveness.

快速安装

Claude Code

推荐
主要方式
npx skills add guia-matthieu/clawfu-skills -a claude-code
插件命令备选方式
/plugin add https://github.com/guia-matthieu/clawfu-skills
Git 克隆备选方式
git clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/onboarding-orchestrator

在 Claude 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 DoesYou Decide
Designs milestone frameworksImplementation timeline
Creates touchpoint schedulesResource allocation
Identifies success metricsDefinition of "success"
Suggests automation triggersTool selection
Builds playbook templatesCustomization per segment

Instructions

Step 1: Define Onboarding Phases

Standard 4-Phase Model:

PhaseDurationFocusExit Criteria
KickoffWeek 1Alignment, accessKickoff complete, logins work
SetupWeek 2-3ConfigurationCore setup done
AdoptionWeek 4-6First use caseTTFV achieved
OptimizationWeek 7-12Full rolloutSteady 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

DayTypePurposeOwner
0EmailWelcome + next stepsAuto
1CallKickoff callCSM
3EmailSetup checklistAuto
7CallSetup reviewCSM
14EmailTraining resourcesAuto
21CallAdoption check-inCSM
30Email30-day surveyAuto
45CallValue reviewCSM
60EmailOptimization tipsAuto
90CallQBR/Health checkCSM

Step 4: Define Success Metrics

MetricTargetMeasurement
Time to Kickoff<3 daysContract → Kickoff
Time to Setup<14 daysKickoff → Setup complete
Time to First Value<30 daysContract → First use case
30-day activation>70%Users logged in
60-day adoption>50%Users weekly active
Onboarding CSAT>4.5Survey score
Onboarding NPS>50Survey 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:

MilestoneOwnerDayStatus
SSO/Auth configuredTech10
Core integration connectedTech12
Data migration completeTech14
Admin accounts createdCSM14
Admin training sessionCSM16
Setup review callCSM21

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:

MilestoneOwnerDayStatus
End user training scheduledCSM22
First training sessionCSM25
First workflow liveCustomer28
50% users logged in-30
First value achieved-35
Adoption review callCSM45

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:

MilestoneOwnerDayStatus
Second use case identifiedCSM50
Full team rolloutCustomer60
80% adoption achieved-75
QBR scheduledCSM80
Handoff to ongoing successCSM90

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

TriggerActionTiming
Contract signedWelcome emailImmediate
Day 3, no kickoffAlert CSMDay 3
Setup incompleteNudge emailDay 18
Day 30, <25% loginRisk alertDay 30
First value achievedCelebration emailOn event
Day 45, low adoptionIntervention callDay 45

Risk Indicators

SignalRisk LevelResponse
No kickoff by Day 5🟠 HighEscalate internally
Setup blocked >7 days🟠 HighTechnical escalation
<25% login at Day 30🔴 CriticalIntervention call
Champion disengaged🟠 HighFind alternate contact
No first value by Day 45🔴 CriticalExecutive 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 仓库

guia-matthieu/clawfu-skills
路径: skills/customer-success/onboarding-orchestrator
0
ai-skillsanthropicclaude-codeclaude-skillsmarketingmcp-server

相关推荐技能

executing-plans

设计

该Skill用于当开发者提供完整实施计划时,以受控批次方式执行代码实现。它会先审阅计划并提出疑问,然后分批次执行任务(默认每批3个任务),并在批次间暂停等待审查。关键特性包括分批次执行、内置检查点和架构师审查机制,确保复杂系统实现的可控性。

查看技能

requesting-code-review

设计

该Skill可在完成任务、实现主要功能或合并代码前自动调度代码审查子代理,确保实现符合需求和计划。它支持通过指定git SHA范围进行精准的代码变更审查,帮助开发者在关键节点及时发现潜在问题。核心原则是"早审查、勤审查",适用于开发流程的各个关键阶段。

查看技能

connect-mcp-server

设计

这个Skill指导开发者如何将MCP服务器连接到Claude Code,支持HTTP、stdio和SSE三种传输协议。它涵盖了从安装配置到认证安全的完整流程,适用于集成GitHub、Notion、数据库等外部服务。当开发者需要添加集成、配置外部工具或提及MCP相关功能时,这个Skill能提供实用的操作指南。

查看技能

web-cli-teleport

设计

该Skill帮助开发者根据任务特性选择Claude Code的Web或CLI界面,并指导如何在两种环境间无缝迁移会话。它能分析任务复杂度、迭代需求等要素,推荐最优工作界面和工作流。关键特性包括会话状态管理、环境切换指导和上下文优化建议。

查看技能