
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.
- Installs
- 426
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/louisblythe/sales-skills --skill customer-onboarding- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads customer-onboarding automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
-
Product Context
- What are you selling? (Software, service, platform)
- How complex is implementation?
- What's the typical time-to-value?
-
Customer Context
- Who's the customer? (Enterprise, mid-market, SMB)
- What was sold? (Scope, use cases, expectations)
- Who are the stakeholders post-sale?
-
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:
- Introductions and role clarification
- Review of goals and success criteria
- Implementation scope confirmation
- Timeline and milestone review
- Open questions and concerns
- 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
- Identify the real blocker
- Escalate appropriately
- Simplify if possible
- Reset expectations
- 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
- Identify new champion quickly
- Re-establish relationship
- Confirm goals still valid
- Adjust plan if needed
- Document for continuity
Technical Challenges
When things break
- Assess severity immediately
- Communicate proactively
- Assign resources
- Provide workarounds
- Document root cause
- 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
- Track onboarding metrics by cohort
- Identify patterns in successful vs. struggling customers
- Adjust process based on data
- A/B test changes where possible
- 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:
- What was sold and what are the customer's goals?
- What's your current onboarding process?
- Where do customers typically get stuck?
- What's your average time-to-value?
- How do you measure onboarding success?
- 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
FAQ
What does the customer-onboarding skill do?
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.
How do I install customer-onboarding?
Run npx skills add https://github.com/louisblythe/sales-skills --skill customer-onboarding in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/customer-onboarding/ (personal) or .claude/skills/customer-onboarding/ (project).
Which AI agents can use customer-onboarding?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is customer-onboarding safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains customer-onboarding?
It is published by louisblythe in louisblythe/sales-skills. It has 426 recorded installs.
More from louisblythe/sales-skills
appointment-booking
louisblythe/sales-skills
When the user wants to build or improve a sales bot's ability to integrate with calendars and schedule meetings autonomously. Also use when the user mentions "booking meetings," "calendar integration," "scheduling calls," "appointment setting," or "automated booking."
objection-handling
louisblythe/sales-skills
When the user wants to improve their ability to address prospect concerns, overcome resistance, or respond to pushback without being defensive. Also use when the user mentions "handling objections," "overcoming resistance," "common objections," "prospect pushback," "they said no," or "dealing with concerns."
sales-presentations
louisblythe/sales-skills
When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.
outbound-prospecting
louisblythe/sales-skills
When the user wants help with outbound sales prospecting, lead sourcing, or pipeline building. Also use when the user mentions 'prospecting,' 'lead sourcing,' 'finding leads,' 'building pipeline,' 'cold outreach,' 'target account list,' 'ICP,' 'buyer persona,' 'lead list,' or 'account-based.' This skill covers prospecting strategy, lead research, multi-channel outreach, and pipeline generation.
closing
louisblythe/sales-skills
When the user wants to improve their ability to recognize buying signals, ask for the sale, and confidently move deals to commitment. Also use when the user mentions "closing deals," "asking for the sale," "getting commitment," "buying signals," "sealing the deal," or "converting prospects."
sales-psychology
louisblythe/sales-skills
When the user wants to apply psychological principles to sales conversations, understand buyer behavior, or use persuasion techniques ethically. Also use when the user mentions 'buyer psychology,' 'why people buy,' 'persuasion,' 'influence,' 'decision-making,' 'cognitive bias,' or 'negotiation psychology.' This skill provides 70+ mental models organized for sales application.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.