Onboarding Plan Builder
Creates a phased onboarding plan that gets a new customer from contract signing to measurable value as fast as possible. The onboarding period is the highest-risk and highest-opportunity phase of the customer lifecycle -- the patterns set in the first 90 days predict the next 3 years.
How to Use
Provide:
- Account name, ARR, product tier, segment
- What they bought (which products/modules, how many seats)
- Their goals (why they bought -- what outcomes they expect)
- Implementation complexity (integrations needed, data migration, custom configuration)
- Key contacts (champion, technical lead, executive sponsor, project manager on their side)
- Target go-live date (if committed) or desired timeline
- Any special circumstances (replacing a competitor, seasonal urgency, parallel initiatives)
Onboarding Phases
Phase 1: Kickoff and Planning (Days 1-7)
Objective: Align on goals, timeline, responsibilities, and success criteria before any implementation begins.
| Milestone |
Deliverable |
Owner |
Success Criteria |
| Welcome and introduction |
Welcome email sent, CSM introduced, expectations set |
CSM |
Customer confirms receipt and understanding |
| Kickoff call |
45-60 minute call covering goals, timeline, roles, success criteria |
CSM + Customer |
Goals and timeline documented and agreed by both sides |
| Onboarding plan shared |
Written plan with milestones, dates, and owners |
CSM |
Customer approves the plan |
| Technical requirements gathered |
Integration needs, data migration scope, configuration requirements documented |
CSM + Technical Lead |
All technical prerequisites identified |
Kickoff call agenda:
- Introductions and roles (5 min)
- Customer goals: what does success look like in 90 days? (10 min)
- Product overview: what they have access to and how it maps to their goals (10 min)
- Timeline and milestones: the onboarding roadmap (10 min)
- Responsibilities: what you will do, what they need to do (5 min)
- Next steps and questions (5 min)
Phase 2: Technical Setup (Days 7-30)
Objective: Get the product technically ready for use -- integrations live, data migrated, configurations complete.
| Milestone |
Deliverable |
Owner |
Success Criteria |
| Accounts and access provisioned |
All users have access with correct permissions |
CSM / Ops |
All licensed users can log in |
| Integrations configured |
CRM, email, calendar, or other integrations live and syncing |
Technical Lead + Customer IT |
Data flowing correctly between systems |
| Data migration complete |
Historical data imported and validated |
Technical Lead + Customer |
Data is accurate and accessible in the product |
| Configuration complete |
Workflows, templates, and settings configured for their use case |
CSM + Customer |
Configuration matches their stated requirements |
| Technical validation |
Customer confirms the setup is correct and functional |
Customer Technical Lead |
Sign-off on technical readiness |
Phase 3: Adoption and Training (Days 14-60)
Objective: Move from "the product is set up" to "the team is using it."
| Milestone |
Deliverable |
Owner |
Success Criteria |
| Admin training |
Product admin(s) trained on configuration and management |
CSM / Enablement |
Admin can manage settings, users, and configuration independently |
| End-user training |
Core users trained on daily workflows |
CSM / Enablement |
Users can complete core workflows independently |
| First workflow completed |
Team completes their first real workflow in the product (not a test) |
Customer team |
Real work is happening in the product |
| Adoption checkpoint |
Usage review at Day 30: who is using it, who is not, what are the barriers |
CSM |
Adoption rate >50% of licensed users active. Barriers identified for non-adopters |
Phase 4: Value Realisation (Days 30-90)
Objective: Demonstrate measurable value from the investment.
| Milestone |
Deliverable |
Owner |
Success Criteria |
| First value metric |
Measurable outcome the customer can point to |
CSM + Customer |
Customer confirms "yes, this is working" with evidence |
| 60-day review |
Formal review of adoption, usage, value, and remaining goals |
CSM + Customer |
Customer satisfied with progress. Gaps identified and addressed |
| Onboarding close |
Transition from onboarding to steady-state management |
CSM |
All onboarding milestones complete. Success criteria met. Cadence transitions to standard check-in rhythm |
| 90-day assessment |
Full assessment: goals achieved, time-to-value, adoption depth, customer satisfaction |
CSM |
Customer would recommend the onboarding experience. All Phase 1 goals addressed |
Segment Adaptations
| Segment |
Timeline |
Complexity |
Engagement Level |
| Enterprise |
60-120 days |
Multiple integrations, data migration, custom configuration, change management |
High: weekly calls, dedicated project management, executive check-ins |
| Mid-Market |
30-60 days |
Standard integrations, moderate configuration |
Medium: bi-weekly calls, milestone-driven check-ins |
| SMB |
14-30 days |
Minimal configuration, self-serve setup |
Low: kickoff call, 2-3 check-in emails, adoption checkpoint |
| PLG / Self-Serve |
7-14 days (or fully self-serve) |
Zero configuration, in-app guidance |
Minimal: automated emails, usage-triggered check-ins, human engagement only if the customer is stuck |
Output Format
## Onboarding Plan: [Account Name]
**Start date:** [date] | **Target go-live:** [date]
**ARR:** EUR [amount] | **Segment:** [segment] | **Tier:** [product tier]
### Goals
1. [Customer goal 1 with success metric]
2. [Customer goal 2 with success metric]
### Timeline
| Phase | Dates | Key Milestones |
|-------|-------|---------------|
| Kickoff & Planning | [dates] | Kickoff call, plan agreed |
| Technical Setup | [dates] | Integrations, migration, config |
| Adoption & Training | [dates] | Training complete, first workflow |
| Value Realisation | [dates] | First value metric, onboarding close |
### Responsibilities
| Deliverable | Your Team | Their Team |
|------------|----------|-----------|
| [item] | [who] | [who] |
### Risk Register
| Risk | Mitigation |
|------|-----------|
| [risk] | [plan] |
### Success Criteria
[What "done" looks like for this onboarding]
Common Onboarding Failures
| Failure |
Root Cause |
Prevention |
| Technical setup stalls |
Customer IT team is not prioritising the integration work |
Set expectations in kickoff: "We need X from your team by [date]. If this slips, the timeline slips" |
| Training attendance is low |
Users do not see the relevance or their manager did not mandate attendance |
Get the champion or executive sponsor to mandate attendance. Frame training as "getting started with the tool that will save your team X hours" |
| No measurable value by Day 60 |
Goals were not specific enough to measure |
Define measurable success criteria in the kickoff. "You will know onboarding succeeded when [specific metric]" |
| Champion goes dark during onboarding |
They are busy, distracted, or less engaged than expected |
Set a weekly cadence. If they miss 2 scheduled touchpoints, escalate to their manager or executive sponsor |
| Scope creep |
Customer wants more configuration, more integrations, more customisation than planned |
Scope is defined in Phase 1. Additions are welcome but extend the timeline. Manage expectations explicitly |
Quality Gates
- Does every milestone have a success criterion? "Training complete" is not a milestone -- "Users can complete core workflows independently" is
- Are responsibilities assigned to named people? "Their team will handle it" is not an assignment. "[Name] will configure the SSO integration by [date]" is
- Is the timeline realistic? An enterprise onboarding in 14 days is a fantasy. An SMB onboarding that takes 90 days is a failure. Match the timeline to the complexity
- Are the customer's goals captured and measurable? If you cannot measure whether the onboarding achieved its goals, you cannot demonstrate time-to-value -- and time-to-value is the single most important onboarding metric
Principles
- Onboarding is not a project. It is the foundation of the relationship. The speed, quality, and experience of onboarding shape how the customer perceives every interaction that follows. Get it right
- Time-to-value is the metric that matters. Not time-to-go-live, not time-to-training-complete -- time-to-the-first-outcome-the-customer-cares-about. Everything in the plan should compress this number
- The customer's effort determines the timeline, not yours. The most common onboarding delay is waiting for the customer's team to complete their tasks (data migration, integration configuration, internal approvals). Set expectations early and follow up relentlessly
- A customer who finishes onboarding without a measurable value metric is a customer who enters steady-state management with unproven ROI. That makes every subsequent conversation -- especially the renewal -- harder than it needs to be
1---2name: onboarding-plan-builder3description: Creates a structured customer onboarding plan with phased milestones, success criteria, timeline, and responsibility assignments. Adapts by segment and complexity. Use when asked to build an onboarding plan, structure a customer kickoff, create an implementation timeline, design a go-live plan, or when a new customer needs a clear roadmap from contract signing to value realisation. Also triggers for questions about customer onboarding structure, implementation planning, kickoff preparation, time-to-value planning, or how to set up a new customer for success from day one.4license: MIT5---67# Onboarding Plan Builder89Creates a phased onboarding plan that gets a new customer from contract signing to measurable value as fast as possible. The onboarding period is the highest-risk and highest-opportunity phase of the customer lifecycle -- the patterns set in the first 90 days predict the next 3 years.1011## How to Use1213Provide:14- Account name, ARR, product tier, segment15- What they bought (which products/modules, how many seats)16- Their goals (why they bought -- what outcomes they expect)17- Implementation complexity (integrations needed, data migration, custom configuration)18- Key contacts (champion, technical lead, executive sponsor, project manager on their side)19- Target go-live date (if committed) or desired timeline20- Any special circumstances (replacing a competitor, seasonal urgency, parallel initiatives)2122## Onboarding Phases2324### Phase 1: Kickoff and Planning (Days 1-7)2526**Objective:** Align on goals, timeline, responsibilities, and success criteria before any implementation begins.2728| Milestone | Deliverable | Owner | Success Criteria |29|-----------|-----------|-------|-----------------|30| Welcome and introduction | Welcome email sent, CSM introduced, expectations set | CSM | Customer confirms receipt and understanding |31| Kickoff call | 45-60 minute call covering goals, timeline, roles, success criteria | CSM + Customer | Goals and timeline documented and agreed by both sides |32| Onboarding plan shared | Written plan with milestones, dates, and owners | CSM | Customer approves the plan |33| Technical requirements gathered | Integration needs, data migration scope, configuration requirements documented | CSM + Technical Lead | All technical prerequisites identified |3435**Kickoff call agenda:**361. Introductions and roles (5 min)372. Customer goals: what does success look like in 90 days? (10 min)383. Product overview: what they have access to and how it maps to their goals (10 min)394. Timeline and milestones: the onboarding roadmap (10 min)405. Responsibilities: what you will do, what they need to do (5 min)416. Next steps and questions (5 min)4243### Phase 2: Technical Setup (Days 7-30)4445**Objective:** Get the product technically ready for use -- integrations live, data migrated, configurations complete.4647| Milestone | Deliverable | Owner | Success Criteria |48|-----------|-----------|-------|-----------------|49| Accounts and access provisioned | All users have access with correct permissions | CSM / Ops | All licensed users can log in |50| Integrations configured | CRM, email, calendar, or other integrations live and syncing | Technical Lead + Customer IT | Data flowing correctly between systems |51| Data migration complete | Historical data imported and validated | Technical Lead + Customer | Data is accurate and accessible in the product |52| Configuration complete | Workflows, templates, and settings configured for their use case | CSM + Customer | Configuration matches their stated requirements |53| Technical validation | Customer confirms the setup is correct and functional | Customer Technical Lead | Sign-off on technical readiness |5455### Phase 3: Adoption and Training (Days 14-60)5657**Objective:** Move from "the product is set up" to "the team is using it."5859| Milestone | Deliverable | Owner | Success Criteria |60|-----------|-----------|-------|-----------------|61| Admin training | Product admin(s) trained on configuration and management | CSM / Enablement | Admin can manage settings, users, and configuration independently |62| End-user training | Core users trained on daily workflows | CSM / Enablement | Users can complete core workflows independently |63| First workflow completed | Team completes their first real workflow in the product (not a test) | Customer team | Real work is happening in the product |64| Adoption checkpoint | Usage review at Day 30: who is using it, who is not, what are the barriers | CSM | Adoption rate >50% of licensed users active. Barriers identified for non-adopters |6566### Phase 4: Value Realisation (Days 30-90)6768**Objective:** Demonstrate measurable value from the investment.6970| Milestone | Deliverable | Owner | Success Criteria |71|-----------|-----------|-------|-----------------|72| First value metric | Measurable outcome the customer can point to | CSM + Customer | Customer confirms "yes, this is working" with evidence |73| 60-day review | Formal review of adoption, usage, value, and remaining goals | CSM + Customer | Customer satisfied with progress. Gaps identified and addressed |74| Onboarding close | Transition from onboarding to steady-state management | CSM | All onboarding milestones complete. Success criteria met. Cadence transitions to standard check-in rhythm |75| 90-day assessment | Full assessment: goals achieved, time-to-value, adoption depth, customer satisfaction | CSM | Customer would recommend the onboarding experience. All Phase 1 goals addressed |7677## Segment Adaptations7879| Segment | Timeline | Complexity | Engagement Level |80|---------|----------|-----------|-----------------|81| Enterprise | 60-120 days | Multiple integrations, data migration, custom configuration, change management | High: weekly calls, dedicated project management, executive check-ins |82| Mid-Market | 30-60 days | Standard integrations, moderate configuration | Medium: bi-weekly calls, milestone-driven check-ins |83| SMB | 14-30 days | Minimal configuration, self-serve setup | Low: kickoff call, 2-3 check-in emails, adoption checkpoint |84| PLG / Self-Serve | 7-14 days (or fully self-serve) | Zero configuration, in-app guidance | Minimal: automated emails, usage-triggered check-ins, human engagement only if the customer is stuck |8586## Output Format8788```89## Onboarding Plan: [Account Name]90**Start date:** [date] | **Target go-live:** [date]91**ARR:** EUR [amount] | **Segment:** [segment] | **Tier:** [product tier]9293### Goals941. [Customer goal 1 with success metric]952. [Customer goal 2 with success metric]9697### Timeline98| Phase | Dates | Key Milestones |99|-------|-------|---------------|100| Kickoff & Planning | [dates] | Kickoff call, plan agreed |101| Technical Setup | [dates] | Integrations, migration, config |102| Adoption & Training | [dates] | Training complete, first workflow |103| Value Realisation | [dates] | First value metric, onboarding close |104105### Responsibilities106| Deliverable | Your Team | Their Team |107|------------|----------|-----------|108| [item] | [who] | [who] |109110### Risk Register111| Risk | Mitigation |112|------|-----------|113| [risk] | [plan] |114115### Success Criteria116[What "done" looks like for this onboarding]117```118119## Common Onboarding Failures120121| Failure | Root Cause | Prevention |122|---------|-----------|-----------|123| Technical setup stalls | Customer IT team is not prioritising the integration work | Set expectations in kickoff: "We need X from your team by [date]. If this slips, the timeline slips" |124| Training attendance is low | Users do not see the relevance or their manager did not mandate attendance | Get the champion or executive sponsor to mandate attendance. Frame training as "getting started with the tool that will save your team X hours" |125| No measurable value by Day 60 | Goals were not specific enough to measure | Define measurable success criteria in the kickoff. "You will know onboarding succeeded when [specific metric]" |126| Champion goes dark during onboarding | They are busy, distracted, or less engaged than expected | Set a weekly cadence. If they miss 2 scheduled touchpoints, escalate to their manager or executive sponsor |127| Scope creep | Customer wants more configuration, more integrations, more customisation than planned | Scope is defined in Phase 1. Additions are welcome but extend the timeline. Manage expectations explicitly |128129## Quality Gates130131- Does every milestone have a success criterion? "Training complete" is not a milestone -- "Users can complete core workflows independently" is132- Are responsibilities assigned to named people? "Their team will handle it" is not an assignment. "[Name] will configure the SSO integration by [date]" is133- Is the timeline realistic? An enterprise onboarding in 14 days is a fantasy. An SMB onboarding that takes 90 days is a failure. Match the timeline to the complexity134- Are the customer's goals captured and measurable? If you cannot measure whether the onboarding achieved its goals, you cannot demonstrate time-to-value -- and time-to-value is the single most important onboarding metric135136## Principles137138- Onboarding is not a project. It is the foundation of the relationship. The speed, quality, and experience of onboarding shape how the customer perceives every interaction that follows. Get it right139- Time-to-value is the metric that matters. Not time-to-go-live, not time-to-training-complete -- time-to-the-first-outcome-the-customer-cares-about. Everything in the plan should compress this number140- The customer's effort determines the timeline, not yours. The most common onboarding delay is waiting for the customer's team to complete their tasks (data migration, integration configuration, internal approvals). Set expectations early and follow up relentlessly141- A customer who finishes onboarding without a measurable value metric is a customer who enters steady-state management with unproven ROI. That makes every subsequent conversation -- especially the renewal -- harder than it needs to be
stephenrogan