account-plan
$
npx mdskill add mohitagw15856/pm-claude-skills/account-planProduces a structured account plan — the document that separates account managers who grow accounts from those who just service them.
SKILL.md
.github/skills/account-planView on GitHub ↗
--- 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) ## 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] ## 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
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign 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.
- ab-test-plannerDesign 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.
- accessibility-auditGenerate 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.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.
- architecture-decision-recordCreate an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.