account-research-brief
Skill13 starsChanged 24 days agoMITView on GitHub
Use this skill when you need to research a target company before outreach, a first call or an account plan: \"research this account\", \"what should I know about Acme before the call\", \"find a reason to reach out\". Produces a one-page account brief with what the company does, current priorities, recent trigger events, likely pains tied to your offer, the people to contact and three specific outreach angles, each with its source. Built for SDRs, AEs and founders doing B2B sales.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- volodymyrkhodonovych/claude-sales-skillstheir own version, first seen Nov 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
- volodymyrkhodonovych/claude-sales-skills★ 1same 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 repository77 other files it gives its agents.
- AGENTS.mdAGENTS.md
- abm-account-planSkill
- account-tieringSkill
- aeo-answer-optimizerSkill
- breakup-emailSkill
- buyer-persona-builderSkill
- buying-committee-mapperSkill
- buying-signal-scoringSkill
- call-coaching-scorecardSkill
- campaign-performance-analyzerSkill
- case-study-writerSkill
- churn-win-backSkill
- closed-lost-reactivationSkill
- cold-call-scriptSkill
- cold-email-sequenceSkill
- cold-email-writerSkill
- comparison-page-writerSkill
- competitive-battlecardSkill
- competitor-teardownSkill
- crm-hygiene-auditSkill
- customer-interview-guideSkill
- deal-qualificationSkill
- deliverability-auditSkill
- discovery-call-prepSkill
- domain-warmup-planSkill
- email-authentication-setupSkill
- email-copy-reviewSkill
- event-follow-upSkill
- expansion-opportunity-finderSkill
- first-line-personalizationSkill
- follow-up-email-writerSkill
- funding-signal-outreachSkill
- gtm-global-rulesSkill
- hiring-signal-outreachSkill
- icp-builderSkill
- job-change-playsSkill
- lead-list-builderSkill
- lead-magnet-builderSkill
- lead-scoring-modelSkill
- linkedin-comment-strategySkill
- linkedin-connection-noteSkill
- linkedin-message-sequenceSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- list-cleaningSkill
- lookalike-account-finderSkill
- meeting-booking-replySkill
- messaging-matrixSkill
- multichannel-cadenceSkill
- mutual-action-planSkill
- negotiation-playbookSkill
- no-show-recoverySkill
- objection-handlerSkill
- outbound-ab-testSkill
- outbound-mathSkill
- outreach-compliance-checkSkill
- pipeline-reviewSkill
- post-engagement-outreachSkill
- proposal-follow-upSkill
- prospect-research-briefSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use this before the first touch on a Tier 1 account or before any first call.
- Distinctive: line 27
Search the CRM before the web.
- Distinctive: line 36
Stop when the brief is complete.
- Distinctive: line 42
Write each as "Because <trigger>, they probably <pain>, which we solve by <outcome>." If you cannot fill all three parts, it is trivia, not …
- Distinctive: line 65
Every angle has a dated source.
- Distinctive: line 73
MUST check CRM history before external research.
- Distinctive: line 74
MUST date and source every trigger and angle.
- Distinctive: line 75
NEVER treat information older than 12 months as a current trigger.
- Distinctive: line 76
NEVER use personal information unrelated to the person's work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Use this before the first touch on a Tier 1 account or before any first call. It produces a one-page brief that answers one question: why would this company care about us this quarter?
Inputs
- Company name and domain.
- Your offer and ICP, so research stays relevant.
- What the CRM already knows: past conversations, open or lost deals, current customers in the same group.
The play
1. Check history first
Search the CRM before the web. A lost deal from last year, an existing customer in a sister company or an unsubscribed contact changes the whole approach.
2. Read the primary sources, in this order
- The company's own site: homepage claim, pricing page, careers page, newsroom.
- Job listings: the clearest public signal of priorities, budgets and tools in use.
- Leadership posts and interviews from the last six months.
- Press releases, funding announcements, earnings notes for public companies.
- Customer reviews of their product: the problems their customers complain about often become their priorities.
Stop when the brief is complete. Thirty minutes of research for a Tier 1 account, five for Tier 2.
3. Pick the triggers that matter
A trigger is a change that creates urgency: a new leader, funding, expansion, a hiring wave, a launch, a regulation, a bad quarter. Keep only triggers from the last 6 months and only those that connect to your offer. Read references/trigger-library.md for the trigger list with suggested angles.
4. Connect triggers to pains
Write each as "Because <trigger>, they probably <pain>, which we solve by <outcome>." If you cannot fill all three parts, it is trivia, not an angle.
5. Name the people
Economic buyer, likely champion and one alternate. Include title, tenure and anything they have said publicly about the problem.
Output format
Account: <name> (<domain>) | Fit: Tier 1/2/3 | CRM history: <one line>
What they do: <one sentence in plain words>
Priorities this year: <2-3 bullets, each with source>
Triggers (last 6 months): <date - event - source>
Likely pains: <2-3, each tied to a trigger or evidence>
People: <name - title - why them>
Angles:
1. <angle> - opener idea - source
2. ...
3. ...
Risks: <reasons this might be a bad fit or bad timing>What good looks like
- Every angle has a dated source. A brief full of unsourced claims is worse than no brief.
- The angles are about the prospect's situation, not your features.
- The best researchers notice what is missing: no sales leader on the team page, a pricing page that changed, a product line that quietly disappeared.
- Risks are listed. A brief that only argues for outreach is a sales pitch to yourself.
- The common mistake is summarising the company's About page. That tells a rep nothing they could not guess.
Rules
- MUST check CRM history before external research.
- MUST date and source every trigger and angle.
- NEVER treat information older than 12 months as a current trigger.
- NEVER use personal information unrelated to the person's work.
Example prompts
- "Research northwind.com before my call on Thursday. We sell warehouse scheduling software."
- "Give me an account brief and three angles for Acme Health. Tier 1, VP Operations is the buyer."
- "Research these 10 accounts and rank them by how timely outreach would be."
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.

