account-planning
Skill2 starsChanged 25 days agoMITView on GitHub
Build a point of view and a strategic account plan for a target account, or find and rank expansion opportunities inside an existing one. Use this skill whenever a seller says "build an account plan", "give me a POV on [account]", "account strategy for [account]", "find expansion in this account", "where can we grow this account", "whitespace at [account]", "what's our plan for this account", or is preparing to go after a new logo or grow a current customer. It pulls context from Loop first (falling back to CRM, call transcripts, and email), builds a POV on what is changing, maps the stakeholders and the opportunities by executive priority, and drafts the first outreach. Prefer this over a blank-page account plan any time a seller needs a strategy for winning or growing an account.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- open-gitagent/enterprise-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- open-gitagent/enterprise-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- call-follow-upSkill
- call-prepSkill
- champion-enablementSkill
- competitive-displacementSkill
- deal-advancementSkill
- manage-upSkill
- multithreadSkill
- one-page-business-caseSkill
- qbr-prepSkill
- sales-playsSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Loop first: If the Loop MCP (https://mcp.fluint.io/mcp) is connected, use it first.
- Distinctive: line 39
No Loop? Detect what is live and fall back: Do not assume a vendor. In parallel:
- Distinctive: line 41
Call transcripts (Salesloft, Gong, Clari, Chorus, Fathom, Fireflies.
- Very specific: line 53
Read references/frameworks.md (POV + strategic vision).
- Distinctive: line 56
Add the 3-year, board-level vision you are guiding them toward.
- Very specific: line 67
Read references/frameworks.md (Opportunity map + whitespace).
- Distinctive: line 96
Rank by exec priority, not by product fit: Follow the money and the mandate.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Account Planning
What this does
Turns an account into a plan you can run: a point of view on what is changing, the opportunities ranked by executive priority, the stakeholders who own them, and the first message to build momentum.
Two modes, same plan:
- New target account: build the POV and the opening plan to break in.
- Existing account: find the whitespace (adjacent teams, new initiatives, unaddressed problems) and rank where to grow next.
The deliverable is a strategic account plan plus a first outreach message.
Step 1: Lock the target and pull context
Loop first. If the Loop MCP (https://mcp.fluint.io/mcp) is connected, use it first. Pull the
account, any deal, the contacts, and prior meeting activity. For an existing account,
pull current footprint: who uses you, what problem you solve, how they get value. Loop
already fuses CRM, calls, and emails, so start there.
No Loop? Detect what is live and fall back. Do not assume a vendor. In parallel:
- CRM (HubSpot, Salesforce, Attio, Pipedrive) = account record, contacts, current footprint.
- Call transcripts (Salesloft, Gong, Clari, Chorus, Fathom, Fireflies; or via Clay / Deepline) = stated priorities.
- Email (Superhuman, Gmail, Outlook) = the working relationship and recent signals.
- Public research = leadership changes, launches, earnings language, hiring.
Set the mode: new account, or expansion in a current one.
Missing a source? Flag it, and make the gap a move. Mark it inline as [MISSING: ...] and continue. Every gap gets the single highest-leverage way to close it: the one question, to the one person, at the next touchpoint. Not "get more data."
Who can actually say yes? Name the people with the power to approve this, or to block it, and mark whether they are engaged yet. Power is often not in the room. If the deciders are absent or untouched, that is the headline, not a footnote.
Step 2: Build the POV
Read references/frameworks.md (POV + strategic vision). Research what is changing at the
account that creates a greater need for what you do. Write the point of view: the shift, the
recommended strategy you uniquely enable, the outcomes they unlock, and the cost they avoid.
Add the 3-year, board-level vision you are guiding them toward. Lead with a real signal, not a
generic claim.
Step 3: Map stakeholders and the compelling event
Identify the top contacts to target, their org influence, and their #1 goal, with a short value soundbite for each. Name the compelling event: the executive pushing a strategic goal, the internal project supporting it, the milestone and date they are working toward.
Step 4: Build the opportunity map
Read references/frameworks.md (Opportunity map + whitespace). Lay out the top 2 to 3
opportunities, each tied to an executive priority, with: why change / why now, their current
state, the use case and your right to win, the future-state outcome, and a high-level plan
(key influencers, intros needed). For an existing account, rank by impact and ease of entry,
and check the three whitespace signals: product whitespace, stakeholder whitespace, and
customer-health signals.
Step 5: Draft the first outreach
Draft the first message based on the top opportunity, built to be forwarded. For expansion, draft the champion ask: a short note asking your existing champion to introduce you to a new stakeholder, easy for them to forward.
The deliverable
Produce the account plan using the skeleton in references/output-templates.md:
- POV (the shift, the strategy, the outcomes) plus the strategic vision
- Compelling event (the executive priority, the project, the date)
- Key contacts (org influence, #1 goal, soundbite)
- Opportunity map (top 2 to 3 by exec priority, ranked for expansion)
- First outreach (the opening message, or the champion intro ask)
The operator's read
Before you hand it over, add the part a summary cannot: the one thing an experienced operator would notice that the data does not show on its own. The non-obvious risk. The stakeholder who matters more than their title. The deal that is not what it looks like. The strength that is quietly a trap. One or two sentences of judgment, called out plainly. Anyone can produce the map. This is the read.
Operating principles
- Lead with what is changing. A problem matters when it blocks a priority they own.
- Rank by exec priority, not by product fit. Follow the money and the mandate.
- Right to win, stated plainly. Why you, for this use case, at this account.
- Every plan ends in a first move. The plan is worthless without the outreach.
- Voice guard. Anything the buyer will read opens with their words, from the call or their own materials, in the first line. Banned openers: "Great connecting," "As discussed," "I wanted to follow up," "Hope this finds you well," "Circling back." If a sentence would survive being pasted into a different deal, it is too generic. Cut it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

