Success Plan Creator
Builds a mutual success plan that both sides own. The success plan is the single most important document in the customer relationship because it answers the question that drives every renewal conversation: "Did we achieve what we set out to achieve?"
How to Use
Provide:
- The customer's goals (what outcomes they expect -- from the sales process, onboarding, or direct conversation)
- Your goals for the account (retention, expansion, advocacy, strategic alignment)
- Available metrics (how outcomes can be measured)
- Key contacts on both sides (who is accountable for what)
- Timeline (when should these outcomes be achieved)
- The starting baseline (where things stand today on each metric)
Success Plan Structure
1. Shared Objectives
Define 3-5 objectives that both sides agree on. These must be outcomes, not activities.
| Objective |
Measure |
Baseline |
Target |
Timeline |
Owner |
| Reduce manual reporting time |
Hours/week spent on manual reports |
20 hours/week |
<5 hours/week |
90 days |
Customer (adoption) + CSM (enablement) |
| Increase team adoption |
Active users / licensed seats |
12 of 60 (20%) |
48 of 60 (80%) |
120 days |
Customer (change management) + CSM (training) |
| Prove ROI to leadership |
EUR value of time saved vs. investment |
No measurement |
3x ROI documented |
180 days |
CSM (calculation) + Customer (validation) |
Objective rules:
- Outcomes, not activities: "Reduce manual reporting time" not "Complete training"
- Measurable: if you cannot define the metric, you cannot define success
- Time-bound: an objective without a deadline is a wish
- Mutually owned: both sides have responsibilities. A success plan where only the CSM has actions is a project plan, not a partnership
2. Milestones
Break each objective into milestones that show progress:
| Milestone |
Linked Objective |
Target Date |
Status |
Notes |
| Onboarding complete -- all 60 users trained |
Adoption |
Apr 15 |
Not started |
Depends on customer's training schedule |
| First automated report run by analytics team |
Manual reporting |
Apr 30 |
Not started |
Quick win opportunity |
| 50% of team using product weekly |
Adoption |
May 15 |
Not started |
Change management critical here |
| Q2 value report delivered with customer-confirmed metrics |
ROI |
Jun 30 |
Not started |
Requires customer data access |
3. Responsibilities
| Area |
CSM Responsibility |
Customer Responsibility |
| Training |
Deliver sessions, provide materials, track completion |
Ensure attendance, allocate team time, manager endorsement |
| Adoption |
Monitor usage data, identify barriers, provide recommendations |
Drive internal adoption, address resistance, enforce accountability |
| Value measurement |
Build the ROI model, present evidence, track metrics |
Validate methodology, confirm outcomes, provide internal data |
| Communication |
Regular check-ins, QBR preparation, status updates |
Timely responses, escalation of blockers, honest feedback |
4. Review Cadence
| Review |
Frequency |
Content |
| Milestone check |
Monthly |
Are milestones on track? Any blockers? Status update on each objective |
| Success plan review |
Quarterly (aligned with QBR) |
Full review: objectives progressing? Targets still relevant? Adjustments needed? |
| Annual reset |
Yearly |
New objectives for the next period based on what was achieved and what the customer's priorities are now |
5. Risk and Dependency Register
| Risk/Dependency |
Impact |
Mitigation |
Owner |
| Customer IT team overloaded -- integration delayed |
Extends onboarding timeline by 2-4 weeks |
Get IT resource commitment in kickoff. Escalate to champion if delayed |
Customer champion |
| Low training attendance |
Adoption target at risk |
Manager mandate for attendance. Offer flexible session times |
Customer manager + CSM |
| No baseline data for ROI |
Cannot measure value improvement |
Establish baseline in first 30 days before process changes |
CSM + Customer |
Creating the Plan with the Customer
The success plan should be built collaboratively, not presented unilaterally:
The conversation:
- "What does success look like for you in 6 months?" (Their goals in their language)
- "How would we measure that?" (Co-define the metrics)
- "What do you need from us to get there?" (Your responsibilities)
- "What do we need from your team?" (Their responsibilities -- sets mutual accountability)
- "Let me draft this into a shared plan for us both to reference" (Formalise the agreement)
The customer should see the plan as their document, not yours. If it feels like a vendor template they signed, it will be ignored. If it feels like a shared commitment to their goals, it will be referenced.
When to Create a Success Plan
| Trigger |
Why Now |
| Post-onboarding (Day 30-60) |
The customer has enough product experience to set meaningful goals |
| Start of a new contract year |
Reset objectives for the next period |
| After a QBR where goals are discussed |
Formalise what was agreed |
| After a save play (relationship repair) |
Establish a fresh commitment to value delivery |
| Before a renewal (if no plan exists) |
Build the evidence framework for the renewal conversation |
Output Format
## Mutual Success Plan: [Account Name]
**Created:** [date] | **Review cadence:** [quarterly]
**CSM:** [name] | **Customer lead:** [name]
### Shared Objectives
[Objective table with measures, baselines, targets, timelines, owners]
### Milestones
[Milestone table with dates and status]
### Responsibilities
[Responsibility matrix]
### Review Schedule
[Next milestone check, next QBR, annual reset date]
### Risks and Dependencies
[Risk register]
Quality Gates
- Is every objective measurable with a baseline and a target? "Improve adoption" fails. "Move from 20% to 80% active user rate in 120 days" succeeds
- Does the customer co-own the plan? If all actions are on the CSM's side, it is not a mutual plan. Both sides must have responsibilities
- Are there milestones between now and the target? A 6-month objective with no intermediate milestones will drift. Monthly checkpoints prevent this
- Is the plan referenced in every QBR and major touchpoint? A success plan that is created and then ignored is worse than no plan -- it sets expectations that are not tracked
Principles
- The success plan is the renewal conversation in advance. If the plan's objectives are achieved by renewal time, the renewal conversation is "look at what we achieved together -- shall we set new goals for next year?" If they are not achieved, at least you know why and can address it honestly
- The customer's goals are the plan's goals, not your goals for them. If they want to reduce manual reporting time and you want to increase adoption breadth, the plan leads with their goal. Your goal (adoption) may be the mechanism, but their goal (time savings) is the objective
- A success plan that is reviewed every quarter is 10x more valuable than one reviewed once. The plan is a living commitment, not a one-time document. Every review reinforces the partnership and surfaces issues early
- The best success plans evolve. Goals that were ambitious 6 months ago may be baseline now. New priorities emerge. The plan should grow with the relationship, not become a historical artefact
1---2name: success-plan-creator3description: Builds a mutual success plan with the customer that defines what success looks like, how it will be measured, who is responsible, and what the timeline is. Produces a shared document that both sides reference throughout the engagement. Use when asked to create a success plan, build a customer outcome framework, define success criteria with a customer, structure mutual goals, or when a CSM needs to align with a customer on what they are trying to achieve together. Also triggers for questions about success planning, outcome definition, customer goal alignment, mutual accountability frameworks, or how to ensure both sides know what success looks like.4license: MIT5---67# Success Plan Creator89Builds a mutual success plan that both sides own. The success plan is the single most important document in the customer relationship because it answers the question that drives every renewal conversation: "Did we achieve what we set out to achieve?"1011## How to Use1213Provide:14- The customer's goals (what outcomes they expect -- from the sales process, onboarding, or direct conversation)15- Your goals for the account (retention, expansion, advocacy, strategic alignment)16- Available metrics (how outcomes can be measured)17- Key contacts on both sides (who is accountable for what)18- Timeline (when should these outcomes be achieved)19- The starting baseline (where things stand today on each metric)2021## Success Plan Structure2223### 1. Shared Objectives2425Define 3-5 objectives that both sides agree on. These must be outcomes, not activities.2627| Objective | Measure | Baseline | Target | Timeline | Owner |28|-----------|---------|----------|--------|----------|-------|29| Reduce manual reporting time | Hours/week spent on manual reports | 20 hours/week | <5 hours/week | 90 days | Customer (adoption) + CSM (enablement) |30| Increase team adoption | Active users / licensed seats | 12 of 60 (20%) | 48 of 60 (80%) | 120 days | Customer (change management) + CSM (training) |31| Prove ROI to leadership | EUR value of time saved vs. investment | No measurement | 3x ROI documented | 180 days | CSM (calculation) + Customer (validation) |3233**Objective rules:**34- Outcomes, not activities: "Reduce manual reporting time" not "Complete training"35- Measurable: if you cannot define the metric, you cannot define success36- Time-bound: an objective without a deadline is a wish37- Mutually owned: both sides have responsibilities. A success plan where only the CSM has actions is a project plan, not a partnership3839### 2. Milestones4041Break each objective into milestones that show progress:4243| Milestone | Linked Objective | Target Date | Status | Notes |44|-----------|-----------------|------------|--------|-------|45| Onboarding complete -- all 60 users trained | Adoption | Apr 15 | Not started | Depends on customer's training schedule |46| First automated report run by analytics team | Manual reporting | Apr 30 | Not started | Quick win opportunity |47| 50% of team using product weekly | Adoption | May 15 | Not started | Change management critical here |48| Q2 value report delivered with customer-confirmed metrics | ROI | Jun 30 | Not started | Requires customer data access |4950### 3. Responsibilities5152| Area | CSM Responsibility | Customer Responsibility |53|------|-------------------|----------------------|54| Training | Deliver sessions, provide materials, track completion | Ensure attendance, allocate team time, manager endorsement |55| Adoption | Monitor usage data, identify barriers, provide recommendations | Drive internal adoption, address resistance, enforce accountability |56| Value measurement | Build the ROI model, present evidence, track metrics | Validate methodology, confirm outcomes, provide internal data |57| Communication | Regular check-ins, QBR preparation, status updates | Timely responses, escalation of blockers, honest feedback |5859### 4. Review Cadence6061| Review | Frequency | Content |62|--------|-----------|---------|63| Milestone check | Monthly | Are milestones on track? Any blockers? Status update on each objective |64| Success plan review | Quarterly (aligned with QBR) | Full review: objectives progressing? Targets still relevant? Adjustments needed? |65| Annual reset | Yearly | New objectives for the next period based on what was achieved and what the customer's priorities are now |6667### 5. Risk and Dependency Register6869| Risk/Dependency | Impact | Mitigation | Owner |70|----------------|--------|-----------|-------|71| Customer IT team overloaded -- integration delayed | Extends onboarding timeline by 2-4 weeks | Get IT resource commitment in kickoff. Escalate to champion if delayed | Customer champion |72| Low training attendance | Adoption target at risk | Manager mandate for attendance. Offer flexible session times | Customer manager + CSM |73| No baseline data for ROI | Cannot measure value improvement | Establish baseline in first 30 days before process changes | CSM + Customer |7475## Creating the Plan with the Customer7677The success plan should be built collaboratively, not presented unilaterally:7879**The conversation:**801. "What does success look like for you in 6 months?" (Their goals in their language)812. "How would we measure that?" (Co-define the metrics)823. "What do you need from us to get there?" (Your responsibilities)834. "What do we need from your team?" (Their responsibilities -- sets mutual accountability)845. "Let me draft this into a shared plan for us both to reference" (Formalise the agreement)8586**The customer should see the plan as their document, not yours.** If it feels like a vendor template they signed, it will be ignored. If it feels like a shared commitment to their goals, it will be referenced.8788## When to Create a Success Plan8990| Trigger | Why Now |91|---------|--------|92| Post-onboarding (Day 30-60) | The customer has enough product experience to set meaningful goals |93| Start of a new contract year | Reset objectives for the next period |94| After a QBR where goals are discussed | Formalise what was agreed |95| After a save play (relationship repair) | Establish a fresh commitment to value delivery |96| Before a renewal (if no plan exists) | Build the evidence framework for the renewal conversation |9798## Output Format99100```101## Mutual Success Plan: [Account Name]102**Created:** [date] | **Review cadence:** [quarterly]103**CSM:** [name] | **Customer lead:** [name]104105### Shared Objectives106[Objective table with measures, baselines, targets, timelines, owners]107108### Milestones109[Milestone table with dates and status]110111### Responsibilities112[Responsibility matrix]113114### Review Schedule115[Next milestone check, next QBR, annual reset date]116117### Risks and Dependencies118[Risk register]119```120121## Quality Gates122123- Is every objective measurable with a baseline and a target? "Improve adoption" fails. "Move from 20% to 80% active user rate in 120 days" succeeds124- Does the customer co-own the plan? If all actions are on the CSM's side, it is not a mutual plan. Both sides must have responsibilities125- Are there milestones between now and the target? A 6-month objective with no intermediate milestones will drift. Monthly checkpoints prevent this126- Is the plan referenced in every QBR and major touchpoint? A success plan that is created and then ignored is worse than no plan -- it sets expectations that are not tracked127128## Principles129130- The success plan is the renewal conversation in advance. If the plan's objectives are achieved by renewal time, the renewal conversation is "look at what we achieved together -- shall we set new goals for next year?" If they are not achieved, at least you know why and can address it honestly131- The customer's goals are the plan's goals, not your goals for them. If they want to reduce manual reporting time and you want to increase adoption breadth, the plan leads with their goal. Your goal (adoption) may be the mechanism, but their goal (time savings) is the objective132- A success plan that is reviewed every quarter is 10x more valuable than one reviewed once. The plan is a living commitment, not a one-time document. Every review reinforces the partnership and surfaces issues early133- The best success plans evolve. Goals that were ambitious 6 months ago may be baseline now. New priorities emerge. The plan should grow with the relationship, not become a historical artefact
stephenrogan