mcpField
O
onboarding-specialist

onboarding-specialist

github.com/ncklrsMarketing & growth53164 installsUpdated 35w ago
Repository

About onboarding-specialist

An onboarding guidance skill for customer success teams, covering the journey from sales handoff and kickoff through go-live and transition. It combines segmentation, risk signals, training guidance, and measurement frameworks.

Key features

  1. 01Plan a phased onboarding journey
  2. 02Set kickoff goals and project plans
  3. 03Segment service by customer size
  4. 04Track health indicators and early risks
  5. 05Plan training, pilots, and go-live
  6. 06Define onboarding metrics

Use cases

  1. 01Plan a new customer’s path from kickoff to launch
  2. 02Adjust engagement for different customer segments
  3. 03Spot delays or weak adoption and intervene
  4. 04Clarify responsibilities across sales, customer success, and customer teams

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ncklrs/startup-os-skills --skill onboarding-specialist

After installing, type/onboarding-specialistin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
_sections.md
automation-tech-touch.md
golive-readiness.md
handoff-sales-cs.md
implementation-management.md
measurement-optimization.md
program-design.md
signals-early-warning.md
stakeholder-management.md
training-enablement.md
ttv-optimization.md

Details

From the project README

Onboarding Specialist

Expert guidance for transforming new customers into successful, activated users. The onboarding phase is the most critical window for customer retention — get it right, and you create advocates; get it wrong, and you create churn.

Philosophy

Customer onboarding is not a checklist — it's a transformation:

  1. Time-to-value is everything — Every day before value is a day closer to churn
  2. Onboarding is not training — It's guiding customers to their specific outcomes
  3. Structured flexibility — Framework with personalization, not rigid scripts
  4. Proactive, not reactive — Anticipate obstacles before they become blockers
  5. Handoff is a process — From sales to CS to ongoing success

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

  • program-* — Onboarding program design and kickoff frameworks
  • implementation-* — Project management and execution
  • training-* — Enablement and learning delivery
  • handoff-* — Sales to CS transitions
  • automation-* — Tech-touch and scaled onboarding
  • signals-* — Early warning detection and intervention
  • golive-* — Readiness criteria and launch success

Core Frameworks

The Onboarding Journey
┌─────────────────────────────────────────────────────────────────────────┐
│                                                                         │
│  HANDOFF → KICKOFF → CONFIGURE → TRAIN → PILOT → GO-LIVE → TRANSITION  │
│                                                                         │
│     ↓         ↓          ↓         ↓       ↓        ↓          ↓        │
│  Context   Alignment   Setup    Skills   Validate  Launch   Ongoing    │
│  Transfer  & Goals     & Data   & Usage  & Iterate Success  Success    │
│                                                                         │
└─────────────────────────────────────────────────────────────────────────┘
Onboarding Segmentation Model
SegmentARR RangeTouch ModelDurationResources
Enterprise$100K+High-touch, dedicated CSM90-180 daysImplementation team
Mid-Market$25K-$100KMedium-touch, pooled CSM60-90 daysShared resources
SMB$5K-$25KLow-touch, digital-led30-60 daysScaled programs
Self-Serve<$5KTech-touch, automated14-30 daysIn-app + email
Time-to-Value Framework
MilestoneDefinitionTargetMeasurement
Time to First LoginAccount created to first access<24 hoursLogin event
Time to SetupFirst login to basic config<3 daysConfig complete
Time to First ValueSetup to "aha moment"<7 daysValue event
Time to Full ValueFirst value to adoption<30 daysUsage metrics
Time to ExpansionAdoption to growth60-90 daysUpsell/add users
The IMPACT Kickoff Framework
PhaseFocusKey Actions
IntroductionsPeople & rolesStakeholder mapping, team intros
Mutual objectivesAligned goalsSuccess criteria definition
PlanTimeline & milestonesProject plan creation
AccountabilityOwnershipRACI establishment
CommunicationRhythm & channelsMeeting cadence, tools
TimelineCritical datesGo-live target, checkpoints
Customer Health During Onboarding
IndicatorGreenYellowRed
EngagementActive participationSporadic responsesNo-shows, silence
ProgressOn or ahead of planMinor delaysSignificantly behind
AdoptionUsing core featuresLimited explorationNo usage
SentimentEnthusiasticConcernedFrustrated
ChampionStrong advocateNeutralAbsent/departed
Onboarding Metrics
MetricFormulaBenchmark
Time to First ValueDays from signup to value event<7 days
Onboarding Completion RateCompleted / Started85%+
Time to Go-LiveDays from kickoff to productionBy segment
Onboarding NPSPost-onboarding survey50+
90-Day RetentionStill active at day 9095%+
Feature AdoptionCore features used / Available60%+
Onboarding Effort ScoreCustomer effort rating<3 (1-5 scale)
Risk Categories
CategorySignalsIntervention
TechnicalIntegration failures, data issuesTechnical escalation
AdoptionLow usage, training gapsAdditional enablement
ChampionKey person absent or leavingRelationship building
TimelineMissed milestones, delaysReplan and resource
ScopeExpanding requirementsChange management
PoliticalInternal resistanceExecutive alignment

Onboarding Project Phases

Phase 1: Pre-Kickoff (Days -7 to 0)
ActivityOwnerDeliverable
Sales handoff callAE + CSMHandoff document
Account researchCSMCompany brief
Success criteria draftCSMDraft goals
Kickoff prepCSMAgenda, materials
Technical assessmentSE/CSMReadiness checklist
Phase 2: Kickoff (Day 1)
ActivityDurationParticipants
Introductions10 minAll stakeholders
Goals alignment20 minDecision makers
Success criteria20 minAll
Project plan review15 minProject leads
Q&A15 minAll
Next steps10 minAll
Phase 3: Configuration (Days 2-14)
ActivityOwnerDependency
Instance setupVendorKickoff complete
Data migrationJointData prep complete
Integration configTechnicalAPI access
User provisioningCustomerUser list
Custom settingsJointRequirements
Phase 4: Training (Days 15-30)
AudienceFormatContent
AdminsLive workshopFull platform training
Power usersLive + self-pacedCore workflows
End usersSelf-paced + guidesDaily usage
ExecutivesBrief overviewDashboards, value
Phase 5: Pilot & Go-Live (Days 30-45)
MilestoneCriteriaValidation
Pilot readyCore config completeChecklist sign-off
Pilot launchTest group identifiedUser feedback
Pilot successCriteria metMetrics review
Go-live readyAll criteria metReadiness checklist
Go-liveFull rolloutLaunch communication

Anti-Patterns

  • Skipping kickoff alignment — Assumes everyone knows goals
  • Feature training without outcomes — Teaching buttons, not value
  • No documented success criteria — "Success" becomes subjective
  • Single-threaded relationships — One contact = fragile onboarding
  • Rigid timelines — No flexibility for customer reality
  • Disappearing after go-live — Onboarding is not adoption
  • Ignoring early warning signs — Hoping problems resolve themselves
  • Same process for all customers — Segment needs differ dramatically
  • Delayed value demonstration — All setup, no quick wins
  • No post-onboarding handoff — Unclear ongoing ownership

Comments

Markdown supported