Run: Customer Onboarding Kickoff SOP

The implementation owner verifies that the customer has signed, the kickoff meeting is on the calendar, and the required internal and customer stakeholders have been invited. The owner confirms the meeting objective, expected duration, and any pre-read materials sent in advance. Record any missing attendee, missing document, or scheduling conflict as a deviation and escalate to the account owner if it may delay onboarding.

The customer success manager prepares a concise agenda that includes introductions, goals, scope, timeline, responsibilities, risks, and next steps. The manager drafts the success plan with measurable outcomes, milestone dates, and acceptance criteria. Keep the agenda time-boxed and ensure each topic has an owner.

The facilitator welcomes participants, introduces the meeting purpose, and confirms the agenda. The facilitator states the expected outcomes, including alignment on goals, responsibilities, timeline, and early risks. The facilitator asks whether any participant needs an agenda adjustment before continuing.

The facilitator asks each internal and customer participant to state their name, role, and responsibility in the onboarding process. The facilitator records the primary contact, decision-maker, technical owner, and escalation contact for both sides. If a critical role is unassigned, the facilitator flags the gap as a risk and assigns follow-up before the next milestone.

The implementation owner reviews the onboarding goals, in-scope deliverables, assumptions, and exclusions. The owner confirms the success criteria, milestone dates, and any measurable targets that define completion. The owner documents any scope deviation or conflicting expectation and escalates unresolved items for decision.

The project manager reviews the responsibility matrix and confirms who owns tasks, approvals, customer updates, and issue escalation. The project manager also confirms meeting cadence, status report frequency, and the preferred communication channel. Record any mismatch between expected and assigned ownership as a deviation and correct it before the next status update.

The facilitator asks the customer and internal team to identify any early risks, dependencies, access issues, data gaps, resource constraints, or timeline concerns. The facilitator records each risk with an owner, due date, and mitigation action. If any risk could affect the agreed timeline, compliance requirement, or customer go-live date, escalate it to the implementation sponsor immediately.

The facilitator reviews all action items, owners, and due dates with the group. The facilitator confirms the next meeting date, any required pre-work, and the expected deliverables before the next checkpoint. The facilitator closes by summarizing decisions, open issues, and escalation items.

The project manager finalizes the meeting notes, including agenda topics covered, decisions made, action items, identified risks, and escalation points. The project manager distributes the notes to all attendees and stores them in the project record in accordance with documented information requirements. If any decision or action item is disputed after the meeting, log it as a non-conformance and route it to the appropriate owner for correction.