agentleFS
akachandan1akachandan1/proofstack/skills/sales/account-research/SKILL.md

account-research

Skill0 starsChanged 7 months agoMITView on GitHub

Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

Files
SKILL.md

Account Research

Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                     ACCOUNT RESEARCH                             │
├─────────────────────────────────────────────────────────────────┤
│  ALWAYS (works standalone via web search)                        │
│  ✓ Company overview: what they do, size, industry               │
│  ✓ Recent news: funding, leadership changes, announcements      │
│  ✓ Hiring signals: open roles, growth indicators                │
│  ✓ Key people: leadership team from LinkedIn                    │
│  ✓ Product/service: what they sell, who they serve              │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + Enrichment: verified emails, phone, tech stack, org chart    │
│  + CRM: prior relationship, past opportunities, contacts        │
└─────────────────────────────────────────────────────────────────┘

Getting Started

Just tell me who to research:

  • "Research Stripe"
  • "Look up the CTO at Notion"
  • "Intel on acme.com"
  • "Who is Sarah Chen at TechCorp?"
  • "Tell me about [company] before my call"

I'll run web searches immediately. If you have enrichment or CRM connected, I'll pull that data too.


Connectors (Optional)

Connect your tools to supercharge this skill:

ConnectorWhat It Adds
EnrichmentVerified emails, phone numbers, tech stack, org chart, funding details
CRMPrior relationship history, past opportunities, existing contacts, notes

No connectors? No problem. Web search provides solid research for any company or person.


Output Format

# Research: [Company or Person Name]

**Generated:** [Date]
**Sources:** Web Search [+ Enrichment] [+ CRM]

---

## Quick Take

[2-3 sentences: Who they are, why they might need you, best angle for outreach]

---

## Company Profile

| Field | Value |
|-------|-------|
| **Company** | [Name] |
| **Website** | [URL] |
| **Industry** | [Industry] |
| **Size** | [Employee count] |
| **Headquarters** | [Location] |
| **Founded** | [Year] |
| **Funding** | [Stage + amount if known] |
| **Revenue** | [Estimate if available] |

### What They Do
[1-2 sentence description of their business, product, and customers]

### Recent News
- **[Headline]** — [Date] — [Why it matters for your outreach]
- **[Headline]** — [Date] — [Why it matters]

### Hiring Signals
- [X] open roles in [Department]
- Notable: [Relevant roles like Engineering, Sales, AI/ML]
- Growth indicator: [Hiring velocity interpretation]

---

## Key People

### [Name] — [Title]
| Field | Detail |
|-------|--------|
| **LinkedIn** | [URL] |
| **Background** | [Prior companies, education] |
| **Tenure** | [Time at company] |
| **Email** | [If enrichment connected] |

**Talking Points:**
- [Personal hook based on background]
- [Professional hook based on role]

[Repeat for relevant contacts]

---

## Tech Stack [If Enrichment Connected]

| Category | Tools |
|----------|-------|
| **Cloud** | [AWS, GCP, Azure, etc.] |
| **Data** | [Snowflake, Databricks, etc.] |
| **CRM** | [e.g. Salesforce, HubSpot] |
| **Other** | [Relevant tools] |

**Integration Opportunity:** [How your product fits with their stack]

---

## Prior Relationship [If CRM Connected]

| Field | Detail |
|-------|--------|
| **Status** | [New / Prior prospect / Customer / Churned] |
| **Last Contact** | [Date and type] |
| **Previous Opps** | [Won/Lost and why] |
| **Known Contacts** | [Names already in CRM] |

**History:** [Summary of past relationship]

---

## Qualification Signals

### Positive Signals
- ✅ [Signal and evidence]
- ✅ [Signal and evidence]

### Potential Concerns
- ⚠️ [Concern and what to watch for]

### Unknown (Ask in Discovery)
- ❓ [Gap in understanding]

---

## Recommended Approach

**Best Entry Point:** [Person and why]

**Opening Hook:** [What to lead with based on research]

**Discovery Questions:**
1. [Question about their situation]
2. [Question about pain points]
3. [Question about decision process]

---

## Sources
- [Source 1](URL)
- [Source 2](URL)

Execution Flow

Step 1: Parse Request

Identify what to research:
- "Research Stripe" → Company research
- "Look up John Smith at Acme" → Person + company
- "Who is the CTO at Notion" → Role-based search
- "Intel on acme.com" → Domain-based lookup

Step 2: Web Search (Always)

Run these searches:
1. "[Company name]" → Homepage, about page
2. "[Company name] news" → Recent announcements
3. "[Company name] funding" → Investment history
4. "[Company name] careers" → Hiring signals
5. "[Person name] [Company] LinkedIn" → Profile info
6. "[Company name] product" → What they sell
7. "[Company name] customers" → Who they serve

Extract:

  • Company description and positioning
  • Recent news (last 90 days)
  • Leadership team
  • Open job postings
  • Technology mentions
  • Customer base

Step 3: Enrichment (If Connected)

If enrichment tools available:
1. Enrich company → Firmographics, funding, tech stack
2. Search people → Org chart, contact list
3. Enrich person → Email, phone, background
4. Get signals → Intent data, hiring velocity

Enrichment adds:

  • Verified contact info
  • Complete org chart
  • Precise employee count
  • Detailed tech stack
  • Funding history with investors

Step 4: CRM Check (If Connected)

If CRM available:
1. Search for account by domain
2. Get related contacts
3. Get opportunity history
4. Get activity timeline

CRM adds:

  • Prior relationship context
  • What happened before (won/lost deals)
  • Who we've talked to
  • Notes and history

Step 5: Synthesize

1. Combine all sources
2. Prioritize enrichment data over web (more accurate)
3. Add CRM context if exists
4. Identify qualification signals
5. Generate talking points
6. Recommend approach

Research Variations

Company Research

Focus on: Business overview, news, hiring, leadership

Person Research

Focus on: Background, role, LinkedIn activity, talking points

Competitor Research

Focus on: Product comparison, positioning, win/loss patterns

Pre-Meeting Research

Focus on: Attendee backgrounds, recent news, relationship history


Tips for Better Research

  1. Include the domain — "research acme.com" is more precise
  2. Specify the person — "look up Jane Smith, VP Sales at Acme"
  3. State your goal — "research Stripe before my demo call"
  4. Ask for specifics — "what's their tech stack?" after initial research

Related Skills

  • call-prep — Full meeting prep with this research plus context
  • draft-outreach — Write personalized message based on research
  • prospecting — Qualify and prioritize research targets

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.