write-a-customer-success-plan

name	write-a-customer-success-plan
category	write
description	Create a mutual customer-success plan with verified outcomes, milestones, responsibilities, evidence, risks, and review points. Use when onboarding or discovery must become an accountable path to sustained customer value.

write-a-customer-success-plan

Translate customer outcomes into a shared operating plan. Keep customer responsibilities, provider commitments, commercial goals, and product-usage signals distinct.

Inputs

• Gather the customer's stated outcomes, baseline, stakeholders, use cases, constraints, onboarding state, and commitments.
• Confirm product capabilities, support model, success ownership, commercial dates, and available measurement.
• Identify security, privacy, procurement, integration, change-management, and adoption dependencies.

Procedure

1. Restate each desired outcome in customer language and define observable success evidence.
2. Record baseline, target, measurement method, owner, time window, and limitations.
3. Select the critical use cases and users required to produce those outcomes.
4. Build milestones with provider action, customer action, dependency, date, and completion proof.
5. Define adoption, quality, operational, and business signals without substituting activity for value.
6. List risks, early warnings, mitigations, escalation triggers, and decision owners.
7. Set communication, working-session, executive-review, and plan-change cadence.
8. Link the authoritative configuration, training, support, security, and commercial documents.
9. Review the plan jointly and record disagreement, exclusions, and unresolved assumptions.
10. Update from observed progress and close goals that are achieved, invalid, or no longer valuable.

Boundaries

Do not invent customer goals, baselines, targets, adoption, impact, or executive agreement. Never promise product work or commercial remedies without authority. Protect customer strategy, usage, employee, and commercial data according to access rules.

Done

• Outcomes, baselines, targets, measures, owners, and time windows are written and verified
• Mutual milestones include dependencies, dates, and observable completion evidence
• Risks, escalation triggers, review cadence, and change rules are agreed
• The customer and provider can access the current plan and correct its claims