MCP HubMCP Hub
Volver a habilidades

onboarding-orchestrator

guia-matthieu
Actualizado 2 days ago
3 vistas
111
20
111
Ver en GitHub
Diseñoautomationdesign

Acerca de

La habilidad onboarding-orchestrator permite a los desarrolladores diseñar y ejecutar manuales de incorporación de clientes basados en hitos con puntos de contacto automatizados. Ayuda a crear programas estructurados que miden métricas de éxito e impulsan un rápido tiempo de valor para los nuevos usuarios. Utilice esta habilidad al construir o mejorar sistemas de incorporación para automatizar puntos de contacto y rastrear la efectividad.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add guia-matthieu/clawfu-skills -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/guia-matthieu/clawfu-skills
Git CloneAlternativo
git clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/onboarding-orchestrator

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

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

Repositorio GitHub

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

Habilidades relacionadas

executing-plans

Diseño

Utilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.

Ver habilidad

requesting-code-review

Diseño

Esta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.

Ver habilidad

connect-mcp-server

Diseño

Esta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.

Ver habilidad

web-cli-teleport

Diseño

Esta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.

Ver habilidad