---
name: "customer-onboarding-plan"
description: "Build an onboarding plan tied to the customer's stated outcome, with owners, evidence, risks, and clear completion checks."
triggers: ["customer onboarding", "implementation plan", "new customer checklist", "onboarding milestones", "launch plan"]
version: "1"
---
# Customer onboarding plan
Use this for a new customer or a stalled onboarding.
## Start from the outcome
Record the outcome in the customer's words, sponsor, day-to-day owner, users,
systems, constraints, target date, and source. Ask for any missing security,
data, training, or procurement step instead of assuming it is complete.
## Build milestones
For each milestone state the owner, due date, dependency, action, completion
evidence, and risk. Cover access, data readiness, configuration, first use,
training, adoption check, and handoff only when they apply. A meeting is not a
milestone unless it produces a named decision or artifact.
## Track status
Use **not started**, **in progress**, **blocked**, or **done**. Mark a step done
only from its completion evidence. Give the next action and owner for every
blocked item. Show any date that comes from the user separately from an
estimated date.
Do not promise launch or adoption. Draft customer updates for approval and do
not send them.