customer-onboarding-and-implementation
FeaturedTakes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing relationship. Use this to design an onboarding motion, rescue a stalled implementation, work out why customers who bought never went live, or scope the services a deal actually needs.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- cbrock84
- Repository
- cbrock84/headcount
- Created
- 4 weeks ago
- Last Updated
- 1 weeks ago
- Language
- Markdown
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
onboarding-plan
When the user needs to plan, run, audit, or rescue a new customer's onboarding and implementation — from the sales handover through to first value and steady-state handoff. Also use when the user mentions 'implementation is behind', 'weeks behind', 'plan their onboarding', 'onboarding plan', 'implementation plan', 'we just closed Acme, what now', 'kickoff call', 'kickoff agenda', 'time to value', 'time to first value', 'go-live plan', 'first 90 days', 'onboarding checklist', 'sales to CS handoff', 'this implementation is stalled', 'they signed three months ago and still aren't live', or 'when will they actually be live'. Use this whenever a customer has signed but has not yet reached first value, even if they never say the word 'onboarding' — a question as small as 'what should I do with this new account' is this skill. For risk after onboarding, see churn-risk. For the kickoff brief, see pre-call-brief. For the review after handover, see qbr-builder. For the first renewal, see renewal-prep.
client-onboarding
Use when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is `customer-support`), NOT renewals/churn past the onboarded gate (that is `retention`).