account-plan
/account-plan
Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.
- Author
- qa-aman ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 19.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.
Triggers from the description
Original author description
Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.
How it works
- Overview
- Workflow
- Anti-Patterns
- Quality Checklist
SKILL.md preview
--- name: account-plan description: > Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account. --- ## Overview Based on **"The New Strategic Selling"** by Robert B. Miller and Stephen E. Heiman. Miller and Heiman's framework established that complex B2B sales are never one-to-one - they involve multiple buying influencers, each with different priorities and different definitions of "win." Strategic Selling maps every key player in the account, diagnoses your position with each one, and builds a coordinated plan to move the account forward. ## Workflow ### Step 1: Define the account objective and timeline Write one sentence: what does winning this account mean in the next 90 days, and what does it mean in 12 months? Format: - **90-day objective**: [specific, measurable outcome - e.g., "Close initial $120K deal with [division]"] - **12-month objective**: [expansion target - e.g., "Expand to 3 divisions, $400K ARR"] - **Strategic importance**: [why this account matters - size, logo value, reference potential, or industry influence] Without a clear objective, every action in the account plan is activity without direction. ### Step 2: Map all buying influencers Miller and Heiman identified four roles in every complex sale. Every account has all four - find them. | Role | Who they are | What they care about | |---|---|---| | **Economic Buyer** | Final financial authority. One person, usually senior. | ROI, strategic fit, risk to the organization | | **User Buyer** | People who will use your product day-to-day. Often multiple. | Ease of use, workflow impact, job security | | **Technical Buyer** | Evaluates fit against technical, legal, or compliance requirements. | Risk elimination, standards, integration | | **Coach** | Your internal ally. Wants you to win. Provides intelligence. | Their own credibility and advancement | For each person you've identified, record: - Name and title - Role type (Economic / User / Technical / Coach) - Their primary win (what success looks like for them personally) - Your current relationship strength: Red (no contact / hostile), Yellow (neutral / unknown), Green (supportive) ### Step 3: Diagnose your position in the account For each key influencer, answer: - **Mode**: Are you in "Growth" mode (expanding a relationship), "Trouble" mode (at risk of losing ground), or "Even Keel" mode (stable but no urgency)? - **Response mode**: What does this person think of your solution - Overconfident, Panic, Complacent, or Realistic? Overconfidence is the most dangerous. If you rate a relationship Green without evidence of recent advocacy from that person, you're in Overconfident mode. ### Step 4: Identify red flags and strengths **Strengths** (what's working in your favor): - e.g., "Strong Champion in [department] who has budget access" - e.g., "Existing contract provides stickiness and usage data" **Red flags** (gaps that threaten the account): - e.g., "No access to Economic Buyer - all activity through mid-level manager" - e.g., "Technical Buyer is evaluating a competitor with stronger [integration]" - e.g., "Renewal in 60 days with unresolved support issue outstanding" Each red flag requires a specific action in Step 5. ### Step 5: Build the action plan For every red flag and every key influencer in Yellow or Red status, write one action. Format per action: - **Objective**: what you're trying to change - **Action**: specific next step - **Owner**: who on your team executes this - **By**: specific date Limit to 5-7 actions total. More than that is a list, not a plan. Example actions: - Objective: Gain access to Economic Buyer Action: Ask Coach to arrange 20-min exec briefing with CFO Owner: [AE] / By: [date] - Objective: De-risk Technical Buyer concern about integration Action: Schedule technical deep-dive with [your SE] and their IT lead Owner: [SE] / By: [date] ### Step 6: Define success metrics and review cadence Set two things: 1. **Success metrics**: how you'll know the account plan is working (e.g., "Economic Buyer meeting secured", "Expansion SOW signed by Q3", "NPS above 8 at next QBR") 2. **Review cadence**: when you'll revisit and update the plan (monthly for strategic accounts, quarterly for growth accounts) An account plan that isn't reviewed is a document, not a plan. ## Anti-Patterns **1. Building the plan around one contact** Bad: An account plan that lists one stakeholder and calls it done. Good: Map all four buying influencer types. If you only know one person in the account, that's the first red flag. **2. Confusing activity with progress** Bad: "We had 3 calls this month - account is healthy." Good: Progress means a buying influencer moved from Yellow to Green, or a specific red flag was closed. **3. Treating the Coach as the Economic Buyer** Bad: "Our Champion told us the budget is approved - we're good." Good: Verify with the Economic Buyer directly. Coaches report what they believe, not what's decided. **4. Static plans** Bad: Building the account plan at the start of the quarter and never updating it. Good: Review monthly. Update influencer status and red flags as new information comes in. ## Quality Checklist - [ ] 90-day and 12-month account objectives are written and specific - [ ] All four buying influencer roles identified (Economic, User, Technical, Coach) - [ ] Each named stakeholder has a relationship status (Red / Yellow / Green) - [ ] At least one person confirmed as Coach with evidence of active advocacy - [ ] Red flags are listed with a specific action assigned per flag - [ ] Action plan has 5-7 items max, each with an owner and a date - [ ] Success metrics defined - outcome metrics, not activity metrics - [ ] Review cadence is set and calendared
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · qa-aman/claude-skills | 100 | MIT |
| anthropics/knowledge-work-plugins | 100 | Apache-2.0 |
| fzfclee/consulting-skills | 100 | Apache-2.0 |
| salesforce/salesforce-skills | 95 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 35d1f88a1a02 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100sales-account-strategist
Use when Codex should act as the Account Strategist specialist from Agency Agents. Expert post-sale account strategist specializing in land-and-expand execution, stakeholder mapping, QBR facilitation, and net revenue retention. Turns closed deals into long-term platform… - 100account-management
Use this skill when managing key accounts, planning expansions, running QBRs, or mapping stakeholders. Triggers on account management, expansion playbooks, QBR preparation, stakeholder mapping, renewal strategy, upsell, cross-sell, and any task requiring strategic account… - 100key-account-pursuit-and-account-plan
Use when selecting, pursuing, or growing a strategic key account through an account plan, GRASP stakeholder map, relationship map, Account Cube expansion, value co-creation, executive sponsor, or strategic-account negotiation; use sales-discovery-and-objection-handling for a single bid's discovery. - 100abm
Account-based planning with stakeholder mapping, persona matching, and coordinated outreach strategy. Use when user says "plan for [company]", "account plan", "stakeholder map", "ABM strategy", or mentions targeting a specific named company. - 90account-health
Score a customer's health, start the renewal motion, and flag churn or expansion early. Trigger when the user asks "how's this account doing", "health check", "are we at risk of churn", "is this account ready to expand", or before a renewal or QBR. - 100customer-health
Health check on a customer account and QBR-ready prep - relationship strength, engagement trend, risk signals, value delivered, and the agenda that makes the review worth their time. Use when the user asks "how healthy is [account]", "customer health check", "prep the [account]…