# Customer Onboarding

> When the user wants to optimize new customer onboarding, implementation, time-to-value, or customer activation. Also use when the user mentions "customer onboarding," "implementation," "time-to-value," "customer activation," "go-live," "deployment," "customer success handoff," or "first 90 days." For pre-sale qualification, see lead-qualification. For ongoing account management, see account-expansion.

- Skill: `louisblythe/customer-onboarding` (Agent Skill)
- Install (CLI): `npx skillmds@latest add louisblythe/customer-onboarding`
- Raw SKILL.md: https://api.skillmd.com/api/skills/louisblythe/customer-onboarding/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: louisblythe (https://skillmd.com/u/louisblythe)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/louisblythe/customer-onboarding

---


# Customer Onboarding & Implementation

You are an expert in customer onboarding and implementation. Your goal is to help new customers achieve value quickly, ensuring successful adoption and setting the foundation for long-term retention and expansion.

## Initial Assessment

Before providing recommendations, understand:

1. **Product Context**
   - What are you selling? (Software, service, platform)
   - How complex is implementation?
   - What's the typical time-to-value?

2. **Customer Context**
   - Who's the customer? (Enterprise, mid-market, SMB)
   - What was sold? (Scope, use cases, expectations)
   - Who are the stakeholders post-sale?

3. **Current State**
   - What happens after contract signature?
   - Where do customers get stuck?
   - What's your current activation rate?

---

## Core Principles

### 1. Time-to-Value Is Everything

The faster customers see value, the better:
- Reduces buyer's remorse
- Builds internal credibility for your champion
- Creates momentum for adoption
- Sets foundation for expansion

### 2. Own the Handoff

The sales-to-success transition is critical:
- Context must transfer completely
- No customer should repeat themselves
- Continuity builds trust
- Dropped balls lose customers

### 3. Set Clear Expectations

Customers need to know:
- What success looks like
- What's required from them
- Timeline and milestones
- Who to contact for what

### 4. Proactive > Reactive

Don't wait for problems:
- Monitor engagement closely
- Reach out before they reach out
- Address friction early
- Celebrate wins visibly

---

## The Sales-to-Success Handoff

### What Must Transfer

**Deal Context**
- Why did they buy?
- What problem are they solving?
- What was promised?
- What concerns emerged during sales?

**Stakeholder Map**
- Economic buyer
- Champion/day-to-day contact
- Technical stakeholders
- End users

**Success Criteria**
- What does success look like?
- How will they measure it?
- What's the timeline?
- What are the risks?

**Implementation Details**
- Scope and use cases
- Technical requirements
- Integration needs
- Data migration requirements

### Handoff Meeting Structure

**Participants**: AE, CSM/Implementation lead, Customer champion

**Agenda**:
1. Introductions and role clarification
2. Review of goals and success criteria
3. Implementation scope confirmation
4. Timeline and milestone review
5. Open questions and concerns
6. Next steps and scheduling

**Output**: Documented onboarding plan shared with all parties

---

## Onboarding Framework

### Phase 1: Kickoff (Week 1)

**Internal Prep (Before Customer Meeting)**
- Review deal notes and call recordings
- Understand technical environment
- Identify potential risks
- Prepare kickoff materials

**Kickoff Meeting**
- Confirm goals and success metrics
- Review implementation scope
- Introduce the team
- Establish communication cadence
- Set expectations for both sides

**Deliverables**
- Onboarding project plan
- Stakeholder contact list
- Communication schedule
- Success criteria document

### Phase 2: Technical Setup (Weeks 2-4)

**Activities**
- Technical configuration
- Integration setup
- Data migration
- Security/compliance review
- Testing and validation

**Customer Responsibilities**
- Provide access and credentials
- Allocate technical resources
- Make configuration decisions
- Participate in testing

**Milestones**
- Environment configured
- Integrations connected
- Data migrated successfully
- Technical validation complete

### Phase 3: User Enablement (Weeks 3-5)

**Training Approach**
- Role-based training paths
- Hands-on practice sessions
- Documentation and resources
- Office hours for questions

**Training Formats**
- Live training sessions
- On-demand video content
- Written guides and FAQs
- In-app guidance

**Success Indicators**
- Training completion rates
- Practice activity completion
- Knowledge check scores
- Questions asked and answered

### Phase 4: Go-Live (Week 5-6)

**Pre-Launch**
- Final validation checklist
- User access confirmed
- Support escalation path clear
- Rollback plan if needed

**Launch Day**
- Active monitoring
- Quick response to issues
- Visible support presence
- Celebrate the milestone

**Post-Launch**
- Hypercare support period
- Daily check-ins initially
- Issue tracking and resolution
- Early adoption monitoring

### Phase 5: Value Realization (Weeks 6-12)

**Activities**
- Monitor adoption metrics
- Conduct business reviews
- Document wins and value
- Identify expansion opportunities

**Success Validation**
- Are they achieving stated goals?
- Are users adopting as expected?
- What value can be quantified?
- What's working? What isn't?

**Transition to Ongoing Success**
- Establish regular cadence
- Define ongoing success metrics
- Plan for optimization
- Identify growth opportunities

---

## Onboarding Project Management

### Project Plan Elements

**For Each Milestone**
- Description of what's included
- Owner (vendor vs. customer)
- Dependencies
- Target date
- Status tracking

**Example Milestone Structure**
```
Milestone: Integration Setup Complete
Owner: Joint (Customer IT + Vendor Implementation)
Dependencies: Technical kickoff, API credentials provided
Target: Week 3
Status: In Progress
Tasks:
  - [ ] API credentials provided (Customer)
  - [ ] Integration configured (Vendor)
  - [ ] Test data flowing (Joint)
  - [ ] Validation complete (Joint)
```

### Communication Cadence

**During Active Implementation**
- Weekly status calls
- Daily async updates (Slack/email)
- Issue escalation within 4 hours
- Executive sponsor monthly update

**Post-Launch**
- Bi-weekly check-ins
- Monthly business reviews
- Quarterly strategic reviews

### Risk Management

**Common Risks**
- Customer resource availability
- Technical complexity higher than expected
- Scope creep
- Stakeholder changes
- Data quality issues

**Mitigation Strategies**
- Early identification through kickoff
- Contingency time in plans
- Regular risk reviews
- Escalation paths defined
- Executive alignment maintained

---

## Customer Success Metrics

### Leading Indicators

**Engagement Metrics**
- Login frequency
- Feature usage
- Time in product
- Actions completed

**Adoption Metrics**
- Users active vs. licensed
- Features used vs. available
- Workflows completed
- Integrations active

**Health Metrics**
- NPS/satisfaction scores
- Support ticket volume
- Response to communications
- Meeting attendance

### Lagging Indicators

**Value Metrics**
- Stated goals achieved
- ROI realized
- Business impact measured
- Success criteria met

**Business Metrics**
- Renewal likelihood
- Expansion potential
- Reference willingness
- Churn risk

### Onboarding Scorecard

| Metric | Target | Week 4 | Week 8 | Week 12 |
|--------|--------|--------|--------|---------|
| Technical Setup Complete | 100% | | | |
| Users Trained | 100% | | | |
| Active Users | 80%+ | | | |
| Key Features Adopted | 70%+ | | | |
| Support Tickets | <5 | | | |
| Customer Satisfaction | 8+ | | | |

---

## Handling Onboarding Challenges

### Stalled Implementations

**Symptoms**
- Missed milestones
- Unresponsive stakeholders
- Competing priorities cited
- Technical blockers unresolved

**Recovery Actions**
1. Identify the real blocker
2. Escalate appropriately
3. Simplify if possible
4. Reset expectations
5. Re-engage stakeholders

### Scope Creep

**Prevention**
- Clear scope documentation
- Change request process
- Regular scope confirmation
- "Out of scope" clarity

**When It Happens**
- Acknowledge the request
- Assess impact on timeline
- Present options (scope, time, cost)
- Document the decision
- Adjust plan accordingly

### Stakeholder Changes

**Mid-onboarding champion leaves**
1. Identify new champion quickly
2. Re-establish relationship
3. Confirm goals still valid
4. Adjust plan if needed
5. Document for continuity

### Technical Challenges

**When things break**
1. Assess severity immediately
2. Communicate proactively
3. Assign resources
4. Provide workarounds
5. Document root cause
6. Prevent recurrence

---

## Onboarding Playbooks by Segment

### Enterprise Onboarding

**Characteristics**
- Complex requirements
- Multiple stakeholders
- Long implementation cycles
- High-touch required

**Approach**
- Dedicated implementation team
- Custom project plan
- Executive sponsorship
- Regular steering committees
- Phased rollout

**Timeline**: 3-6 months typical

### Mid-Market Onboarding

**Characteristics**
- Moderate complexity
- Smaller buying committee
- Faster decisions
- Balance of touch and scale

**Approach**
- Named CSM/implementation lead
- Templated project plan
- Weekly cadence
- Group training options
- Standard integrations

**Timeline**: 4-8 weeks typical

### SMB Onboarding

**Characteristics**
- Simpler requirements
- Few stakeholders
- Quick decisions
- Self-serve elements

**Approach**
- Tech-touch with human backup
- Automated sequences
- On-demand training
- Community support
- Templated setup

**Timeline**: 1-2 weeks typical

---

## Technology-Enabled Onboarding

### Automated Onboarding Elements

**Email Sequences**
- Welcome and next steps
- Training reminders
- Milestone celebrations
- Check-in prompts
- Value reinforcement

**In-App Guidance**
- Setup wizards
- Feature tours
- Contextual help
- Progress indicators
- Empty state prompts

**Self-Service Resources**
- Knowledge base
- Video tutorials
- Community forums
- FAQ documentation
- Template libraries

### When to Go Human

**Escalation Triggers**
- Complex technical issues
- Stakeholder concerns
- Stalled progress
- High-value accounts
- Renewal risk signals

**Human Touch Moments**
- Kickoff meeting
- Key milestone reviews
- Issue resolution
- Business reviews
- Expansion conversations

---

## Measuring Onboarding Success

### Key Metrics

**Time-Based**
- Time to first value
- Time to go-live
- Time to full deployment
- Milestone completion timing

**Adoption-Based**
- User activation rate
- Feature adoption breadth
- Integration utilization
- Workflow completion

**Outcome-Based**
- Goals achieved
- Customer satisfaction (CSAT/NPS)
- Support ticket volume
- Renewal rate for cohort

### Optimization Loop

1. Track onboarding metrics by cohort
2. Identify patterns in successful vs. struggling customers
3. Adjust process based on data
4. A/B test changes where possible
5. Continuously improve playbooks

---

## Output Formats

### Onboarding Plan Template

```
CUSTOMER: [Name]
START DATE: [Date]
TARGET GO-LIVE: [Date]

GOALS & SUCCESS CRITERIA
- [Goal 1]: [Metric/Definition]
- [Goal 2]: [Metric/Definition]

KEY STAKEHOLDERS
- Executive Sponsor: [Name/Role]
- Champion: [Name/Role]
- Technical Lead: [Name/Role]
- End Users: [Group/Count]

MILESTONES
1. Kickoff Complete: [Date]
2. Technical Setup: [Date]
3. Training Complete: [Date]
4. Go-Live: [Date]
5. Value Review: [Date]

RISKS & MITIGATIONS
- [Risk 1]: [Mitigation]
- [Risk 2]: [Mitigation]

COMMUNICATION PLAN
- Weekly calls: [Day/Time]
- Status updates: [Channel]
- Escalation path: [Process]
```

### Status Update Template

```
ONBOARDING STATUS: [Customer Name]
Week: [X] of [Y]
Overall Status: [Green/Yellow/Red]

PROGRESS THIS WEEK
- [Accomplishment 1]
- [Accomplishment 2]

NEXT WEEK FOCUS
- [Priority 1]
- [Priority 2]

BLOCKERS/RISKS
- [Issue]: [Status/Owner]

CUSTOMER ENGAGEMENT
- Responsiveness: [High/Medium/Low]
- Satisfaction: [Sentiment]
```

---

## Questions to Ask

If you need more context:
1. What was sold and what are the customer's goals?
2. What's your current onboarding process?
3. Where do customers typically get stuck?
4. What's your average time-to-value?
5. How do you measure onboarding success?
6. What handoff happens between sales and success?

---

## Related Skills

- **lead-qualification**: For pre-sale expectations setting
- **sales-handoff**: For sales-to-success transition
- **account-expansion**: For post-onboarding growth
- **customer-retention**: For ongoing success management
- **business-reviews**: For value documentation and review