Files
pm-claude-skills/exports/windsurf/pm-sales/account-plan/account-plan.md
T
mohitagw15856 036511ab3e Windsurf + Aider targets, MCP server, and demo placement (#33)
Broadens both reach (more tools) and content types (an MCP server), continuing
the multi-platform story.

Windsurf + Aider:
- build-exports.mjs gains two platforms: exports/windsurf/*.md (workspace rules,
  trigger: model_decision) and exports/aider/*.md (conventions for `aider --read`).
  Now 5 platforms (ChatGPT, Gemini, Cursor, Windsurf, Aider).
- install.sh + bin/cli.mjs install both (windsurf -> .windsurf/rules, aider ->
  .aider/skills with a --read hint); generated README index is excluded from copies.
- One-line windsurf-install.sh / aider-install.sh wrappers for parity.

MCP server (new content type):
- mcp/server.mjs — zero-dependency stdio MCP server exposing list_skills,
  search_skills, get_skill. Published as a second bin (pm-claude-skills-mcp).
  Logs to stderr; reads bundled skills/ at startup. mcp/README.md documents
  client config.

Also: README hero "See it in action" demo placement (ready to swap in a GIF;
recording guide in web/docs-assets/README.md), Works-With table + exports +
install docs updated, CHANGELOG Unreleased. package.json files/bin updated.


Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px

Co-authored-by: Claude <noreply@anthropic.com>
2026-06-17 23:15:38 +01:00

105 lines
3.4 KiB
Markdown

---
trigger: model_decision
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)
## 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