customer-success-plan
This skill generates a structured joint customer success plan document that aligns a company and customer on business outcomes, key metrics, and mutual commitments across a 90-180 day timeline. Use it when building success plans, onboarding plans, mutual action plans, or preparing for customer kickoff calls and quarterly business reviews. Output includes partnership objectives, success metrics with baselines and targets, ownership assignments, and a phased milestone roadmap ready to co-author with the customer.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/customer-success-plan && cp -r /tmp/customer-success-plan/plugins/pm-cs/skills/customer-success-plan ~/.claude/skills/customer-success-planSKILL.md
# Customer Success Plan Skill This skill produces a joint customer success plan — a living document shared between the CSM and the customer that aligns on outcomes, milestones, and mutual commitments. Output is ready to co-author with the customer in a kickoff call or QBR. ## Required Inputs Ask the user for these if not provided: - **Account name** and industry - **Product / plan purchased** - **Key stakeholders** — customer champion and economic buyer - **Customer's stated business goals** — why did they buy? What problem are they solving? - **Contract term and renewal date** - **Current onboarding stage** (new customer / expanding / post-QBR / pre-renewal) - **Seats / licenses / usage purchased** - **Any known risks** — adoption gaps, champion uncertainty, competing priorities ## Output Structure --- # Customer Success Plan: [Account Name] **Product:** [Product name / plan tier] **Contract term:** [Start date → Renewal date] **CSM:** [Name] **Customer champion:** [Name, Title] **Customer executive sponsor:** [Name, Title — if known] **Last updated:** [Date] **Status:** [Active / Under review / Completed] --- ## 1. Partnership Objectives > *What does success look like for [Account Name] at contract end?* [Write 2–3 sentences describing the customer's core objective in plain English — what they are trying to achieve in their business, not what features they are using.] **Primary business goal:** [e.g. Reduce time-to-hire by 30% across engineering teams] **Secondary goal:** [e.g. Consolidate three legacy tools into one platform, saving £X/year] **Success statement (customer's words):** "[Direct quote from champion about what success looks like — ask for this in kickoff]" --- ## 2. Success Metrics Define how both parties will measure success. Agreed in the kickoff call and tracked in QBRs. | Metric | Baseline (today) | Target | By when | Data source | |---|---|---|---|---| | [e.g. Seat utilisation] | [X%] | [≥ 80%] | [Month 3] | [Product analytics] | | [e.g. Time to hire] | [X days] | [< Y days] | [Month 6] | [Customer's ATS] | | [e.g. Reports produced/month] | [X] | [≥ Y] | [Month 3] | [Product analytics] | | [e.g. NPS] | [X] | [≥ 8] | [Month 6] | [Quarterly survey] | **Leading indicators** (early signs the plan is on track): - [e.g. 5+ users log in within the first 2 weeks] - [e.g. First workflow automated within 30 days] - [e.g. Champion presents the tool to their team by end of Month 1] --- ## 3. Milestone Roadmap Break the success journey into phases with clear milestones and owners: ### Phase 1: Onboard (Month 1) | Milestone | Owner | Due date | Status | |---|---|---|---| | Admin setup complete (SSO, permissions, data integration) | [IT contact] | [Date] | [ ] | | All purchased seats activated and users invited | [Champion] | [Date] | [ ] | | Core workflow [X] configured and tested | [CSM + Champion] | [Date] | [ ] | | First training session delivered (all teams) | [CSM] | [Date] | [ ] | | Kickoff call completed and success plan co-signed | [CSM + Champion] | [Date] | [ ] | ### Phase 2: Adopt (Months 2–3) | Milestone | Owner | Due date | Status | |---|---|---|---| | [Core feature] in active daily use by ≥ X users | [Champion] | [Date] | [ ] | | First business outcome achieved and documented | [Champion + CSM] | [Date] | [ ] | | 30-day check-in completed | [CSM] | [Date] | [ ] | | [Power user workflow] enabled for advanced users | [CSM] | [Date] | [ ] | ### Phase 3: Value (Months 4–6) | Milestone | Owner | Due date | Status | |---|---|---|---| | QBR 1 delivered — ROI evidence presented | [CSM + AE] | [Date] | [ ] | | Success metric [X] hit target | [Champion] | [Date] | [ ] | | Expansion use case identified and introduced | [AE] | [Date] | [ ] | | Reference call or case study agreed | [Champion] | [Date] | [ ] | ### Phase 4: Renew & Expand (Months 7–12) | Milestone | Owner | Due date | Status | |---|---|---|---| | QBR 2 delivered — renewal conversation started | [CSM + AE] | [Date] | [ ] | | Renewal proposal sent | [AE] | [Date] | [ ] | | Expansion or flat renewal signed | [AE] | [Date] | [ ] | --- ## 4. Mutual Commitments Success plans work when both parties commit. Document what each side will do: **[Vendor] commits to:** - Dedicated CSM available [X days/week / by email within 24 hours] - Monthly [call / check-in / async update] with champion - QBR every [90 days] with executive summary and ROI report - Priority support for [Account] — response SLA of [X hours] for P1 issues - Roadmap preview for relevant upcoming features - [Any other specific commitment made in sales cycle] **[Account Name] commits to:** - Champion available for [30-min monthly] check-in - Users complete onboarding training by [date] - Feedback on product experience shared monthly (async or sync) - Executive sponsor participates in QBR 1 and renewal discussion - Provide outcome data to CSM quarterly for ROI tracking --- ## 5. Stakeholder Engagement Plan | Stakeholder | Role | Engagement frequency | Format | Owner | |---|---|---|---|---| | [Champion] | Day-to-day owner | Weekly (async) + Monthly (call) | Slack / Email + Zoom | CSM | | [Economic buyer] | Budget holder | Quarterly | QBR (in-person or video) | CSM + AE | | [IT contact] | Integration owner | As needed | Email | CSM | | [End users] | Active users | Training only | Group session | CSM | --- ## 6. Risk & Mitigation | Risk | Likelihood | Impact | Mitigation plan | |---|---|---|---| | Low adoption in first 30 days | [M] | [H] | CSM hosts live onboarding; champion sends internal comms day 1 | | Champion changes role | [L] | [H] | Multi-thread: introduce CSM to 2 additional stakeholders by Month 2 | | Budget pressure at renewal | [M] | [H] | Build ROI case monthly; document value continuously | | Competing priorities delay rollout | [H] | [M] | Agree minimum viable adoption path with champion; don't require perfection to declare value | --- ## 7. Communication Plan | Communication | Audience | Frequency | Format |
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.