customer-onboarding-and-implementation

Featured

Takes 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.

AI & Automation 1,673 stars 251 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Customer onboarding and implementation The period between signature and first real use is where the largest share of preventable churn is created, and where a customer's opinion of the product is formed permanently. ## Agree what live means before the contract is signed The most common implementation failure happens in the sales cycle: nobody wrote down what success would look like, so the project has no finish line and every party quietly holds a different one. Define the go-live criteria concretely — which teams, doing what, with what data in place — along with the date, who does what on each side, and what the customer must supply. Put it in the contract or an agreed plan before the deal closes, not after. **Sales commitments become implementation scope.** If a deal was won on something the product does not do yet, the implementation team inherits it. Route that decision back to whoever can make it rather than absorbing it silently. ## Plan the implementation as a project with a customer-side owner Nothing predicts implementation failure like the absence of a named, empowered owner on the customer side. They need authority to make decisions and time genuinely allocated. If the customer cannot name that person, the project is at risk before it starts, and saying so early is a service. Set a cadence from the beginning and hold it — a stalled implementation almost never announces itself; the calls quietly stop being attended. ## Sequence for early value, not for co...

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

AI & Automation Listed

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.

1 Updated 4 weeks ago
gaintrace
AI & Automation Featured

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`).

116 Updated 2 days ago
ericrisco