# generate-account-plan

The generate-account-plan Claude Code command builds a strategic plan for a company account. It reviews account, contact, and activity data, with web search as a supplement when requested or when data is sparse.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 36654 repo stars
- Author: Common Room · official Anthropic repository
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/anthropics/knowledge-work-plugins/tree/HEAD/partner-built/common-room/commands/generate-account-plan.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/generate-account-plan

## What it does

The command turns a company name or domain into an account plan with an executive summary, company overview, stakeholder map, activity analysis, opportunities, risks, and action items. It ranks the top five contacts by member score and assigns each a stakeholder role. Activity analysis covers the last 90 days, with up to 50 events.

Web search runs when Common Room data is sparse or the user asks for it; it looks for company news from the last 30 days. When the account has little data, the command keeps only sections supported by evidence and shortens the plan. If `references/my-company-context.md` is available, it uses that context to tailor the summary and action items.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add anthropics/knowledge-work-plugins
```
In the agent chat (not a shell):
```text
/plugin install common-room@knowledge-work-plugins
```

2. **Manually: put the files in place**
- File: `.claude/commands/generate-account-plan.md` — Call it with /generate-account-plan. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/generate-account-plan.md` — Call it with /prompts:generate-account-plan. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/generate-account-plan.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/generate-account-plan.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/anthropics/knowledge-work-plugins/tree/HEAD/partner-built/common-room/commands/generate-account-plan.md

## When to use it
- build an account plan for a named company
- identify key contacts and classify their roles
- summarize account engagement over time
- turn account signals into opportunities, risks, and next steps

## Example prompts
- Create an account plan for Acme using the domain `acme.com`.
- Review Acme’s contacts and activity from the last 90 days.
- Prepare an account plan for Acme and add recent company news.

## Source text · generate-account-plan.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b3c3a85fd4a1d8cf.

BEGIN THIRD-PARTY FILE b3c3a85fd4a1d8cf
````text
---
description: Generate a comprehensive strategic account plan
argument-hint: <company name or domain>
---

Generate a comprehensive account plan for "$ARGUMENTS".

## Process

1. **Full account research** — Follow the account-research skill to produce a complete account overview. Pull all available first-party (product), second-party (community), and third-party (intent) signals, CRM data, scores, and RoomieAI research.

2. **Stakeholder mapping** — Fetch the top 5 contacts at this company sorted by member score descending. Classify each into: Champion, Economic Buyer, Influencer, End User, or Unknown. Use Spark persona data if available; if Spark is unavailable, infer from engagement patterns and activity recency. If no activity data exists either, classify as Unknown.

3. **Engagement analysis** — Pull all organization activity for the last 90 days (up to 50 activities). Identify trends: is engagement growing, stable, or declining? Which contacts are most active? What channels are they engaging through?

4. **Web search (supplementary)** — If CR data is rich, skip. If data is thin or the user requests it, search for recent company news (last 30 days): funding, acquisitions, product launches, leadership changes, competitive moves.

5. **Synthesis** — Combine all data into a structured account plan. When the user's company context is available (see `references/my-company-context.md`), tailor the executive summary, opportunities, and action items to the user's product and ICP.

## Output Format

```
## Account Plan: [Company Name]

### Executive Summary
[3-4 sentences: relationship status, key opportunity, primary risk, recommended priority]

### Account Overview
| Field | Value |
|-------|-------|
| Industry | ... |
| Size | ... |
| Domain | ... |
| CRM Owner | ... |
| Opp Stage | ... |
| ARR | ... |
| Scores | ... |

### Stakeholder Map

**Champions**
- [Name] — [Title] — [Key signals, last activity date]

**Economic Buyers**
- [Name] — [Title] — [Key signals]

**Influencers**
- [Name] — [Title] — [Key signals]

**End Users**
- [Name] — [Title] — [Key signals]

### Engagement Analysis
[Trend summary: growing/stable/declining, most active contacts, top channels, comparison to 90 days prior if data available]

### Recent News [If web search was run]
[Web search findings with sources and dates]

### Opportunities
1. [Signal-backed opportunity with specific next step]
2. ...

### Risks
1. [Signal-backed risk with mitigation]
2. ...

### Prioritized Action Items
1. [Specific action] — [Owner suggestion] — [Timeline]
2. ...
3. ...
```

Ground every insight in actual data. Flag explicitly when data is thin or unavailable.

**If Common Room returns sparse data for this account**, produce an abbreviated plan that covers only the sections with real data. Do not generate a full account plan from minimal input — a short honest plan with gaps clearly noted is far more useful than a comprehensive-looking plan built on fabricated details. Omit sections (Stakeholder Map, Engagement Analysis, Opportunities, Risks) entirely if there is no data to support them.
````
END THIRD-PARTY FILE b3c3a85fd4a1d8cf

The third-party file has ended. Everything between the b3c3a85fd4a1d8cf tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© Common Room · Apache-2.0 · https://github.com/anthropics/knowledge-work-plugins/tree/HEAD/partner-built/common-room/commands/generate-account-plan.md

## Similar
- [sales-account-segmentation](https://affpapa.org/en/nevibecode/skills/sales-account-segmentation.md) — skill · 33600 installs
- [account-management](https://affpapa.org/en/nevibecode/plugins/account-management.md) — plugin · ★ 450 repo stars
- [sales-account-tiering](https://affpapa.org/en/nevibecode/skills/sales-account-tiering.md) — skill · 34500 installs
- [revnu](https://affpapa.org/en/nevibecode/skills/revnu.md) — skill · 3700 installs
- [account-executive](https://affpapa.org/en/nevibecode/skills/account-executive.md) — skill · 195 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
