Onboarding Plan

Goal

Transform a new customer profile into a structured 30/60/90-day onboarding plan with concrete milestones, assigned owners, and measurable success checkpoints.

Trigger

Invoke when a new customer is signed and needs a structured onboarding roadmap before kickoff.

Steps

1. 1

   Analyze the customer profile below to extract key details: company size, industry, use case, stated goals, technical complexity, and any stated risks or constraints. $customer_profile

   • □Company size and industry identified
   • □Primary use case and goals captured
   • □Technical complexity and risk factors noted
2. 2

   Define the Day 1–30 (Foundation) phase: list 3–5 milestones focused on account setup, stakeholder alignment, and initial product activation. Assign a likely owner role (e.g., CSM, IT Admin, Champion) to each milestone.

   • □At least 3 milestones defined for days 1–30
   • □Each milestone has an assigned owner role
3. 3

   Define the Day 31–60 (Adoption) phase: list 3–5 milestones focused on workflow integration, team training, and first measurable usage targets. Each milestone should include a success checkpoint — a specific, observable condition that confirms the milestone is met.

   • □Milestones address training and integration
   • □Each milestone has a concrete success checkpoint
4. 4

   Define the Day 61–90 (Value Realization) phase: list 3–5 milestones focused on ROI validation, expansion opportunities, and executive review. Include a success checkpoint and owner for each milestone.

   • □ROI or outcome metric included in at least one milestone
   • □Executive review or business review milestone present
5. 5

   Identify 2–3 key risks or blockers that could derail the onboarding plan based on the customer profile, and suggest a mitigation action for each.

   • □Risks are specific to this customer's profile
   • □Each risk has a paired mitigation action
6. 6

   Summarize the full onboarding plan with a one-paragraph executive summary suitable for sharing with the customer's executive sponsor, highlighting the overall journey, key outcomes by phase, and the definition of onboarding success.

   • □Summary is written for a non-technical executive audience
   • □Definition of success is clearly stated

Output format

Present the plan in three clearly labeled phase sections (Days 1–30, 31–60, 61–90). Within each phase, use a table or structured list with columns: Milestone | Owner Role | Success Checkpoint | Target Date (relative). Follow with a Risks & Mitigations section, then close with the Executive Summary paragraph.