Build a structured account plan for any key customer

Account Plan Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

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.

---
name: account-plan
description: "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."
---

# Account Plan Skill

Produces a structured account plan — the document that separates account managers who grow accounts from those who just service them.

## Required Inputs
- **Account name**
- **Current ARR / revenue**
- **Contract renewal date**
- **Key contacts** (names, roles, relationship strength)
- **Products/services currently in use**
- **Known opportunities or expansion areas**
- **Known risks**
- **Planning horizon** (6 / 12 / 24 months)

Overview

Produces a structured account plan — the document that separates account managers who grow accounts from those who just service them.

Manual install (npx, ZIP)

Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill account-plan -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \
  | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/account-plan

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/9442634d0baeb3f69676/account-plan.zip" -OutFile "$env:TEMP\account-plan.zip"; Expand-Archive "$env:TEMP\account-plan.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.4 KB

Read the files here

mohitagw15856/f6ca7931 file

SKILL.md3.4 KB

SKILL.md

Show the full text105 lines

account-plan/SKILL.md105 lines · 3.4 KB

PreviewCode

Outline

RawView on GitHub

Account Plan Skill

Produces a structured account plan — the document that separates account managers who grow accounts from those who just service them.

Required Inputs

Account name
Current ARR / revenue
Contract renewal date
Key contacts (names, roles, relationship strength)
Products/services currently in use
Known opportunities or expansion areas
Known risks
Planning horizon (6 / 12 / 24 months)

Output Structure

Account Plan: [Account Name]

Account Manager: [Name] | Period: [Date range]

Account Snapshot

Metric	Current	Target (EOY)
ARR / Revenue	£[amount]	£[target]
NPS / Health score	[Score]	[Target]
Products in use	[List]	[Expansion targets]
Renewal date	[Date]	—
Risk level	Low / Medium / High	—

Relationship Map

Name	Title	Influence	Relationship	Notes
[Name]	[Role]	Decision maker / Influencer / User	Strong / Neutral / Weak	[Insight]

Relationship gaps: [Who we do not have access to that we should] Executive sponsor: [Do we have one? If not — who could become one?]

Why They Stay (Retention Anchors)

[2-3 specific reasons this account renews. If the list is short, that is the risk signal.]

Growth Opportunities

Opportunity	Product	Est. Value	Timeline	Next Action
[Opportunity]	[Product]	£[value]	[Q/Year]	[Specific action]

Whitespace: What products do we have that this account does not use, and why?

Risks and Mitigation

Risk	Likelihood	Impact	Mitigation	Owner
[Risk]	H/M/L	H/M/L	[Action]	[Name]

90-Day Action Plan

Action	Why	Owner	Due
[Specific action]	[Why it matters]	[Name]	[Date]

Next QBR / EBR: [Date — if no EBR cadence, flag as a risk]

Success Criteria

At end of [period]:

Renewed at or above current ARR
[Expansion opportunity] progressed to [stage]
Health score moved from [current] to [target]

Anti-Patterns

Do not list only executive contacts in the relationship map — champions and day-to-day users are often more influential on renewal decisions
Do not set growth opportunity estimates without a basis — even rough ARR values prevent the plan from being treated seriously
Do not treat "no known risks" as acceptable — if no risks are identified, the plan hasn't been scrutinised honestly
Do not write 90-day actions as vague aspirations ("strengthen the relationship") — each action must specify a call, meeting, or deliverable with a named owner

Quality Checks

Relationship map identifies decision-makers, influencers, and any relationship gaps
Risks all have mitigation actions and named owners
Growth opportunities include estimated value (even roughly)
90-day actions are specific (not "have a call" — what call, with whom, to achieve what)
Success criteria are measurable at the end of the planning period

1	---
2	name: account-plan
3	description: "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."
4	---
5
6	# Account Plan Skill
7
8	Produces a structured account plan — the document that separates account managers who grow accounts from those who just service them.
9
10	## Required Inputs
11	- Account name
12	- Current ARR / revenue
13	- Contract renewal date
14	- Key contacts (names, roles, relationship strength)
15	- Products/services currently in use
16	- Known opportunities or expansion areas
17	- Known risks
18	- Planning horizon (6 / 12 / 24 months)
19
20	## Output Structure
21
22	---
23
24	# Account Plan: [Account Name]
25	Account Manager: [Name] \| Period: [Date range]
26
27	---
28
29	### Account Snapshot
30
31	\| Metric \| Current \| Target (EOY) \|
32	\|---\|---\|---\|
33	\| ARR / Revenue \| £[amount] \| £[target] \|
34	\| NPS / Health score \| [Score] \| [Target] \|
35	\| Products in use \| [List] \| [Expansion targets] \|
36	\| Renewal date \| [Date] \| — \|
37	\| Risk level \| Low / Medium / High \| — \|
38
39	---
40
41	### Relationship Map
42
43	\| Name \| Title \| Influence \| Relationship \| Notes \|
44	\|---\|---\|---\|---\|---\|
45	\| [Name] \| [Role] \| Decision maker / Influencer / User \| Strong / Neutral / Weak \| [Insight] \|
46
47	Relationship gaps: [Who we do not have access to that we should]
48	Executive sponsor: [Do we have one? If not — who could become one?]
49
50	---
51
52	### Why They Stay (Retention Anchors)
53	[2-3 specific reasons this account renews. If the list is short, that is the risk signal.]
54
55	---
56
57	### Growth Opportunities
58
59	\| Opportunity \| Product \| Est. Value \| Timeline \| Next Action \|
60	\|---\|---\|---\|---\|---\|
61	\| [Opportunity] \| [Product] \| £[value] \| [Q/Year] \| [Specific action] \|
62
63	Whitespace: What products do we have that this account does not use, and why?
64
65	---
66
67	### Risks and Mitigation
68
69	\| Risk \| Likelihood \| Impact \| Mitigation \| Owner \|
70	\|---\|---\|---\|---\|---\|
71	\| [Risk] \| H/M/L \| H/M/L \| [Action] \| [Name] \|
72
73	---
74
75	### 90-Day Action Plan
76
77	\| Action \| Why \| Owner \| Due \|
78	\|---\|---\|---\|---\|
79	\| [Specific action] \| [Why it matters] \| [Name] \| [Date] \|
80
81	Next QBR / EBR: [Date — if no EBR cadence, flag as a risk]
82
83	---
84
85	### Success Criteria
86	At end of [period]:
87	- Renewed at or above current ARR
88	- [Expansion opportunity] progressed to [stage]
89	- Health score moved from [current] to [target]
90
91	## Anti-Patterns
92
93	- [ ] Do not list only executive contacts in the relationship map — champions and day-to-day users are often more influential on renewal decisions
94	- [ ] Do not set growth opportunity estimates without a basis — even rough ARR values prevent the plan from being treated seriously
95	- [ ] Do not treat "no known risks" as acceptable — if no risks are identified, the plan hasn't been scrutinised honestly
96	- [ ] Do not write 90-day actions as vague aspirations ("strengthen the relationship") — each action must specify a call, meeting, or deliverable with a named owner
97
98	## Quality Checks
99
100	- [ ] Relationship map identifies decision-makers, influencers, and any relationship gaps
101	- [ ] Risks all have mitigation actions and named owners
102	- [ ] Growth opportunities include estimated value (even roughly)
103	- [ ] 90-day actions are specific (not "have a call" — what call, with whom, to achieve what)
104	- [ ] Success criteria are measurable at the end of the planning period
105

View all files on GitHub →

Details

Updated: Sep 23, 2026
License: MIT
Stars on the repo: ★ 1,395
Checked: Sep 24, 2026
Source: mohitagw15856/pm-claude-skills ↗
Creator: mohitagw15856 · 193 listings

View creator

Made with account-plan

Account Plan Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Account Plan Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856