Template preview · B2B services
Customer onboarding
Guide a new customer from purchase to a first meaningful outcome.
An onboarding plan for a fictional customer implementation.
Sample purpose
Guide a new customer from purchase to a first meaningful outcome.
Audience: Implementation manager, Customer success manager- Structure
- 4 sections
- Criteria
- 12
- Sources
- 8
- Watches
- 3
- Default approach
- Review first
Set the purpose first. Then change every section, criterion, and agent setting before anything runs.
Fictional sample
Structure and criteria
Sample content shows the shape of a useful document. Copying it is optional.
01 Review firstDesired first outcome
For this customer onboarding, defines customer-specific first value and target date.
Criteria
- Outcome is the firm’s own result, such as a first client form approved, with a date tied to their calendar.
- Evidence is something the customer observes, not vendor uptime.
- Acceptance criteria are agreed in writing by the customer lead before work starts.
Sources
- Asana client onboarding process asana.comMilestone structure for client onboarding.
- Northwind implementation guide (fictional) docs.northwind-forms.exampleHow first-value outcomes are captured.
Sample content
- First approved form
- Due Oct 23
- Implementation period
- 21 days
- Customer project lead
- Samira Khan
02 Review firstImplementation plan
For this customer onboarding, assigns tasks to vendor and customer owners.
Criteria
- Each task has a named owner, due date and the task it depends on.
- Customer-side tasks, such as a sample form or approver email, block the next step explicitly.
- Each customer dependency has a vendor fallback, such as a test sample if data is late.
Sources
- Northwind implementation playbook (fictional) docs.northwind-forms.exampleTypical sequence and delays.
- Asana project templates asana.comDependency tracking patterns.
Watches
- Follows Desired first outcome
Sample content
- 2026-10-05 · KickoffConfirm form owner, review route, and data source.
- 2026-10-12 · ConfigureImport one approved sample form.
- 2026-10-23 · First valueCustomer sends first approved client form.
03 ManualReadiness and risks
For this customer onboarding, tracks access, data, dependencies, and blockers.
Criteria
- Each access need names the system, owner and a go or no-go date with a fallback.
- Each data dependency states source, format, size and owner.
- Each blocker has an owner, deadline, escalation contact and the consequence if missed.
Sources
- Northwind readiness checklist (fictional) api.northwind-forms.exampleStandard items for accounting firms.
- NIST Cybersecurity Framework nist.govVocabulary for access and data-handling checks.
Watches
- Follows Implementation plan
Sample content
- ☐ Northwind Forms provides one redacted sample form
- ☐ Vendor confirms reviewer permissions
- ☐ Pause launch if approval owner is not assigned
04 Review firstValue confirmation
For this customer onboarding, confirms outcome with customer evidence.
Criteria
- Evidence is from the firm’s use, such as forms submitted and approved, read by the firm.
- The confirmation method and date are set before go-live.
- The customer lead signs off and says whether the outcome helped their process.
Sources
- Northwind usage metrics (fictional) api.northwind-forms.exampleForm submissions and approvals for the account.
- Gainsight QBR guide gainsight.comJoint outcome review practice.
Watches
- Follows Readiness and risks
Sample content
Milestone Customer owner Vendor owner Acceptance First approved form Asha Samira Customer confirms end-to-end approval completed