# Customer Onboarding — Standard Operating Procedure > Source: https://b2bprocess.com/customer-onboarding > Last updated: 2026-07-08. Adapt owners, tools, and thresholds to your organization. ## 1. Purpose Customer onboarding is the process that takes a newly signed B2B customer from contract to first realized value: technical setup and integration, configuration to their use case, training of their users, migration of their data where relevant, and a verified go-live against the success criteria agreed during the sale. It begins where the sales-to-CS handoff ends and concludes when the customer is demonstrably achieving the outcome they bought — not when the kickoff deck has been presented. ## 2. Scope & prerequisites Every B2B product needs an onboarding process; what varies is weight. High-touch (dedicated implementation manager, project plan) for enterprise and complex products; low-touch (guided in-app flows, office hours, milestone emails) for high-velocity SMB. Prerequisites: a completed sales handoff with documented success criteria, and a definition of 'onboarded' more rigorous than 'account provisioned'. ## 3. Roles & responsibilities | Role | Responsibility | | --- | --- | | Onboarding / Implementation Manager | Owns the project: plan, cadence, blockers, go-live verification. | | Customer Success Manager | Owns the relationship continuum; leads onboarding directly in models without a dedicated team. | | Solutions / Implementation Engineer | Technical setup, integrations, data migration, and acceptance testing. | | Customer executive sponsor | Holds their organization to the plan; unblocks internal adoption resistance. | | Customer project lead / admin | Day-to-day counterpart; owns customer-side tasks and internal comms. | | Account Executive | Stays available for context and relationship continuity; attends kickoff. | ## 4. Procedure ### Step 1: Define 'onboarded' as an outcome **Owner:** CS leadership Before improving onboarding, define its exit: the measurable state at which a customer is live and receiving value — e.g., integration active, N users completing the core workflow weekly, first business result produced and acknowledged. This definition gates completion, drives the time-to-value metric, and stops onboarding from ending by fade-out. - [ ] Write the go-live criteria checklist per product/segment - [ ] Define the activation event(s) that mark first value - [ ] Set target time-to-value per segment ### Step 2: Receive the handoff and build the project plan **Owner:** Onboarding Manager / CSM Convert the sales handoff — success criteria, stakeholder map, commitments, technical environment — into a dated project plan with workstreams, owners on both sides, dependencies, and the go-live target. The customer's own obligations (data access, IT resources, admin availability) are explicit line items with names attached. - [ ] Translate success criteria into milestones with dates - [ ] Assign owners on both sides for every workstream - [ ] Identify the critical-path dependency (usually customer IT or data access) and schedule it first ### Step 3: Run the kickoff within the first week **Owner:** Onboarding Manager / CSM The kickoff confirms — not discovers — goals, walks the plan, sets the communication cadence, and gets the customer's executive sponsor on record supporting the timeline. Momentum is the deliverable: the first working session should be scheduled before the kickoff call ends. ### Step 4: Execute technical implementation **Owner:** Implementation / Solutions team Provisioning, SSO, integrations, data migration, environment configuration — sequenced so something works visibly early. Long silent technical phases kill executive confidence; ship a working slice (one integration live, one dashboard populated) inside the first two weeks. - [ ] Stand up a visible early win before deep configuration - [ ] Track blockers with owner and age; escalate customer-side blockers within days, not weeks - [ ] Validate against the technical acceptance checklist ### Step 5: Train for the workflow, not the interface **Owner:** Onboarding Manager / Enablement Role-based training built around the customer's actual use case and the workflows from the success plan — admins, end users, and executives each get what they need. Recorded sessions, a customer-specific quick-start doc, and self-serve academy links cover the people who join later. - [ ] Train on the customer's own data/configuration wherever possible - [ ] Certify or check comprehension for admin roles - [ ] Leave behind role-based quick-start materials ### Step 6: Drive adoption to the activation threshold **Owner:** Onboarding Manager / CSM Between training and go-live sits the real work: watching usage data against the activation definition, unblocking lagging teams, re-engaging the sponsor when internal adoption politics stall, and adjusting configuration where the workflow meets reality. This is where onboarding earns retention. ### Step 7: Verify go-live against success criteria **Owner:** Onboarding Manager + Customer sponsor A formal go-live review with the customer: walk the criteria from step 1, demonstrate the first value delivered in business terms, capture open items with owners, and get explicit customer sign-off that onboarding is complete. Celebrate it — the moment marks a psychological commitment on both sides. - [ ] Score each go-live criterion with evidence - [ ] Collect onboarding CSAT/feedback while it's fresh - [ ] Log remaining items into the steady-state success plan ### Step 8: Transition to steady-state CS **Owner:** Onboarding Manager → CSM Where onboarding and steady-state are different people, run a full internal handoff (context, relationships, open items) and introduce the ongoing CSM to the customer before the onboarding manager exits — the same no-repetition standard as the sales handoff. Schedule the first business review before the transition closes. - [ ] Internal handoff doc: adoption state, stakeholder map, risks, open items - [ ] Customer-facing introduction with explicit ownership dates - [ ] First QBR/check-in on the calendar before onboarding closes ## 5. Metrics to monitor | Metric | Definition | Formula | Target | | --- | --- | --- | --- | | Time to value (TTV) | Days from contract (or kickoff) to the customer's first realized value per the activation definition. | First-value date − start date | segment-specific; the trend matters most | | Time to go-live | Days from kickoff to verified go-live sign-off. | Go-live date − kickoff date | vs. the plan; slippage < 20% | | Onboarding completion rate | Share of new customers reaching verified go-live within the target window. | On-time go-lives ÷ onboardings started (cohort) | > 85% | | Activation rate | Share of provisioned users/teams crossing the activation threshold. | Activated users ÷ provisioned users | > 70% by go-live | | Onboarding CSAT | Customer satisfaction measured at go-live. | Survey at go-live review | ≥ 4.5/5 | | Early churn / 90-day retention | The outcome onboarding protects: customers lost or dormant in the first quarter post-sale. | Churned/dormant ≤ 90 days ÷ new customers | < 5% | ## 6. Known failure modes | Failure | Symptom | Corrective action | | --- | --- | --- | | Onboarding with no defined end | Accounts linger 'in onboarding' for months; completion means the CSM got busy elsewhere. | Outcome-based go-live criteria, verified with the customer, gating the transition to steady state. | | Feature tour instead of outcome path | Customers trained on everything, using nothing; 'we saw the demo again' energy at kickoff. | Sequence everything toward the one workflow that delivers the first success criterion; defer the rest. | | Customer-side stall, vendor-side silence | Waiting weeks for IT access or data while the project quietly dies; blame arrives at renewal. | Customer obligations as named, dated plan items; escalation to the sponsor after days of slippage, framed as protecting their timeline. | | Momentum lost at the start | Two weeks between signature and kickoff; the champion's internal announcement energy is spent. | Kickoff SLA inside 5 business days; first working session booked in the kickoff itself. | | Executive sponsor disappears | End-users resist the change, mid-level owners deprioritize, adoption plateaus below threshold. | Sponsor commitments captured at kickoff; a standing executive touchpoint at each milestone; escalate adoption stalls as business-risk, not usage trivia. | | Training ends where turnover begins | The trained cohort moves on; six months later nobody knows how the product works. | Recorded, role-based, self-serve training assets from day one; admin certification; new-joiner path owned in steady state. | | Go-live equals abandonment | Intense attention through launch, then nothing until renewal; the customer's usage decays unwatched. | Formal transition to a named CSM with the first review pre-scheduled; activation metrics feed the ongoing health score. | --- This SOP is maintained as part of the B2B process encyclopedia at https://b2bprocess.com. Check the source page for the latest revision.