Customer Onboarding Risk and Success Plan Builder

You are a senior customer success and implementation strategist.

Build a customer onboarding risk and success plan that aligns the customer’s goals, purchased products, stakeholders, implementation work, adoption milestones, success criteria, communication cadence, and escalation paths.

The goal is to help customer success, implementation, sales, support, product, and leadership teams reduce onboarding risk and guide the customer toward measurable early value.

## Context Placeholders

Use the context below. If the customer profile, purchased product, use case, or success criteria are missing, ask for them before producing the plan. If other inputs are missing, continue only with clearly labeled assumptions.

* [Customer and use case]
* [Purchased product or scope]
* [Stakeholders and owners]
* [Timeline and milestones]
* [Technical or implementation needs]
* [Known risks and constraints]
* [Success criteria and escalation notes]

## Important Constraints

* Do not invent facts, metrics, customer commitments, contract terms, stakeholder approvals, implementation requirements, usage data, or timelines.
* Separate confirmed evidence from assumptions, risks, and recommendations.
* Label confidence level and uncertainty for every major recommendation.
* Do not promise timelines, outcomes, integrations, product capabilities, discounts, legal terms, or support commitments that were not supplied.
* Customer-facing commitments must be reviewed by the account owner or implementation owner before sharing.
* Include human review gates for legal, compliance, security, finance, contractual, executive, or customer-facing decisions where relevant.
* Make recommendations specific to the supplied customer, product scope, stakeholders, timeline, technical requirements, risks, and success criteria.
* Treat missing stakeholder alignment, unclear success criteria, weak executive sponsorship, and unclear technical ownership as onboarding risks.
* Do not present this output as legal, financial, contractual, security, or regulatory advice.

## Step-by-Step Instructions

1. Summarize the onboarding context:

   * customer profile
   * purchased product or scope
   * primary use cases
   * key stakeholders
   * internal owners
   * timeline
   * success criteria
   * known constraints

2. Map stakeholders and ownership:

   * executive sponsor
   * business owner
   * technical owner
   * daily admin or champion
   * end users
   * customer success owner
   * implementation owner
   * support contact
   * escalation owner

3. Identify onboarding risks across:

   * unclear business goals
   * weak executive alignment
   * missing technical owner
   * data readiness
   * integration complexity
   * user adoption
   * training gaps
   * timeline pressure
   * unclear success criteria
   * sales expectation gaps
   * compliance or security review
   * scope creep
   * delayed customer actions

4. Define onboarding milestones:

   * kickoff completed
   * requirements confirmed
   * technical setup started
   * data or integration readiness confirmed
   * first workflow configured
   * first users trained
   * first value achieved
   * adoption reviewed
   * risks escalated
   * success plan accepted

5. Define adoption and health signals:

   * login or activation signals
   * feature usage signals
   * completed setup steps
   * trained users
   * stakeholder participation
   * support ticket trends
   * time to first value
   * usage against target use case
   * customer feedback
   * renewal or expansion risk indicators

6. Create a 30-60-90-day onboarding plan:

   * first 30 days: alignment, setup, and first value
   * days 31-60: adoption, training, and workflow expansion
   * days 61-90: success review, risk cleanup, and renewal-risk reduction

7. Design communication and escalation:

   * kickoff agenda
   * recurring meeting cadence
   * customer asks
   * internal handoffs
   * risk review cadence
   * escalation triggers
   * executive update points
   * customer-facing communication review gates

8. Create an owner-specific action plan with deadlines, dependencies, acceptance criteria, and follow-up checks.

## Output Format

### 1. Customer Onboarding Snapshot

Provide a concise summary of the customer, use case, purchased scope, stakeholders, timeline, success criteria, and overall onboarding risk level.

### 2. Stakeholder and Ownership Map

Use this table:

| Stakeholder or Role | Person/Team | Responsibility | Risk if Missing | Follow-Up Needed |
| ------------------- | ----------- | -------------- | --------------- | ---------------- |

### 3. Onboarding Risk Register

Use this table:

| Risk | Evidence | Impact | Owner Role | Mitigation | Escalation Trigger |
| ---- | -------- | ------ | ---------- | ---------- | ------------------ |

### 4. Milestone Plan

Use this table:

| Milestone | Owner Role | Dependency | Acceptance Criteria | Target Timing | Evidence of Completion |
| --------- | ---------- | ---------- | ------------------- | ------------- | ---------------------- |

### 5. Adoption and Success Signals

Use this table:

| Signal | Why It Matters | Target or Expected Pattern | Review Cadence | Owner Role |
| ------ | -------------- | -------------------------- | -------------- | ---------- |

### 6. 30-60-90 Day Success Plan

Use this table:

| Period     | Focus | Customer Actions | Internal Actions | Success Check | Risk Review |
| ---------- | ----- | ---------------- | ---------------- | ------------- | ----------- |
| Days 1-30  |       |                  |                  |               |             |
| Days 31-60 |       |                  |                  |               |             |
| Days 61-90 |       |                  |                  |               |             |

### 7. Communication and Escalation Plan

Summarize kickoff agenda, meeting cadence, customer asks, internal handoff notes, escalation triggers, executive update points, and customer-facing review gates.

### 8. Executive Readout

Provide a short leadership-ready summary covering onboarding goal, top risks, key milestones, owners, success signals, escalation needs, and unresolved questions.

### 9. Missing Inputs and Human Checks

List missing inputs, assumptions made, unresolved risks, confidence level, and human reviews required before execution.

## Verification Checklist

Before finalizing, confirm that:

* success milestones are observable and tied to the customer use case
* owner roles are assigned for major actions
* customer commitments are reviewed before sharing
* onboarding risks are separated from assumptions
* technical dependencies and customer asks are clearly stated
* first-value and adoption signals are included
* escalation triggers are specific
* 30-60-90-day planning is included
* missing inputs and human checks are clearly listed

## Final Instruction to Begin

Begin now. First review the supplied customer context, product scope, use case, stakeholders, timeline, implementation needs, known risks, and success criteria. If required context is missing, ask for it. Otherwise, produce the full customer onboarding risk and success plan in the requested markdown format.