Customer Success Plan Template

Customer context, desired outcomes with baselines and targets, milestones, adoption metrics, roles on both sides, risks, review cadence, sign-off

カスタマーサクセス標準success plan更新 2026/10/29

エディタで開く.mdをダウンロード

使い方: Use it when a customer signs and you need a joint plan for the whole contract term. Fill the desired outcomes with the customer sponsor first, with baselines and data sources. The main pitfall is listing product activities instead of business outcomes the sponsor would report upward.

プレビュー

Customer Success Plan: [Customer name]

A joint success plan agreed between a customer and its supplier: the business outcomes the customer bought the product for, how each one is measured, the milestones to get there, the adoption metrics that show progress and who does what on both sides. Based on common customer success practice. Replace every [bracketed] value and every row marked Example.

Document control

Field	Value
Plan ID	[SP-YYYY-NNN]
Customer	[Customer name]
Contract	[Contract reference], term YYYY-MM-DD to YYYY-MM-DD
Version	[1.0]
Status	[Draft / Agreed / Under review]
Supplier owner	[@csm]
Customer owner	[Customer sponsor name, role]
Last updated	YYYY-MM-DD
Next review	YYYY-MM-DD (next quarterly business review)
Classification	[Confidential, shared with customer]

Revision history

Version	Date	Author	Change
1.0 (Example)	2026-04-30	CSM	First plan agreed at kick-off

1. Customer context

Example: Quellmoor Freight (fictional) runs regional road freight with [12] depots. It bought [Product] to replace spreadsheets for delivery planning, because late deliveries were costing contract penalties and planners spent most of Monday rebuilding schedules.

Item	Value
Industry and size	[Industry, employees, regions]
Products in use	[Product, edition, number of seats]
Strategic priorities this year	[From the customer's own plan or annual report]
Why they bought	[Problem in the customer's words]
Constraints	[Budget cycle, IT freeze windows, regulation, staffing]

2. Desired outcomes

ID	Outcome	Measure	Baseline	Target	By	Data source
OUT-01 (Example)	Fewer late deliveries	Share of deliveries arriving after the agreed slot	9%	4%	2027-06-30	Customer delivery report
OUT-02 (Example)	Faster weekly planning	Planner hours to publish the weekly plan	14 h	4 h	2027-03-31	Customer time log, sampled monthly
OUT-03 (Example)	One planning system	Depots planning only in [Product]	0 of 12	12 of 12	2027-03-31	Usage report
OUT-[NN]	[Outcome]	[Measure]	[Baseline]	[Target]	YYYY-MM-DD	[Source]

3. Milestones

ID	Milestone	Supports	Supplier owner	Customer owner	Target date	Status
MS-01 (Example)	Baselines confirmed for OUT-01 and OUT-02	OUT-01, OUT-02	CSM	Operations manager	2026-05-29	Done
MS-02 (Example)	Pilot at 3 depots live	OUT-03	Onboarding lead	Depot lead	2026-07-15	Done
MS-03 (Example)	Route rules configured for all depots	OUT-01	Solutions consultant	Planning lead	2027-01-31	On track
MS-04 (Example)	All 12 depots planning in [Product]	OUT-03	CSM	Operations manager	2027-03-31	On track
MS-05 (Example)	Six-month outcome review	All	CSM	Sponsor	2027-06-30	Not started

4. Adoption metrics

ID	Metric	Definition	At kick-off	Target	Review
AD-01 (Example)	Weekly active planners	Planners who publish at least one plan per week, divided by licensed planners	40%	85%	Monthly
AD-02 (Example)	Plans built from route rules	Share of plans generated with rules, not built by hand	10%	70%	Monthly
AD-03 (Example)	Driver app usage	Deliveries confirmed in the app	55%	90%	Monthly
AD-[NN]	[Metric]	[Definition]	[Value]	[Value]	[Cadence]

These metrics also feed the account health score (customer-success/health-score-model).

5. Roles and responsibilities

Role	Supplier	Customer	Responsible for
Executive sponsor	[VP customer success]	[Sponsor name]	Outcomes, priorities, escalation
Plan owner	[@csm]	[Operations manager]	Plan, milestones, reviews
Champion	n/a	[Name]	Internal promotion, user feedback
Technical lead	[Solutions consultant]	[IT contact]	Integrations, data, access
Support	[Support desk]	[Super users]	How-to questions, incidents

6. Risks and dependencies

ID	Risk or dependency	Affects	Likelihood	Impact	Mitigation	Owner
RSK-01 (Example)	Depot leads keep spreadsheets in parallel	OUT-03	Medium	High	Sponsor message, retire shared spreadsheet on go-live date	Customer operations manager
RSK-02 (Example)	Telematics feed delayed by customer IT freeze in December	MS-03	High	Medium	Configure rules on test data first	Solutions consultant
RSK-[NN]	[Risk]	[ID]	[L/M/H]	[L/M/H]	[Mitigation]	[Owner]

7. Review cadence

Meeting	Frequency	Attendees	Inputs
Working check-in	Every two weeks	Plan owners	Milestones, adoption metrics
Quarterly business review	Quarterly	Sponsors, plan owners	Outcomes, value delivered, roadmap
Plan refresh	Yearly, and before renewal	Sponsors	Updated outcomes for the next term

8. Sign-off

Side	Name	Role	Date
Customer	[Name]	[Sponsor]	YYYY-MM-DD
Supplier	[Name]	[CSM]	YYYY-MM-DD

This plan records shared goals. It does not change the contract, service levels or prices.

Standard and licence note

Based on common customer success practice for joint success plans and outcome-based account management. No standard governs this document. All text and the fictional Quellmoor Freight example are original. Template licence: MIT.