home / skills / eyadsibai / ltk / lead-research

This skill helps identify and qualify potential leads by researching ICPs, target accounts, and outreach strategies to prioritize sales opportunities.

npx playbooks add skill eyadsibai/ltk --skill lead-research

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.0 KB
---
name: lead-research
description: Use when "finding leads", "sales prospecting", "target companies", "business development", or asking about "ideal customer profile", "lead qualification", "outreach strategies"
version: 1.0.0
---

<!-- Adapted from: awesome-claude-skills/lead-research-assistant -->

# Lead Research Assistant

Identify and qualify potential leads by analyzing your product and finding target companies.

## When to Use

- Finding potential customers for your product
- Building company lists for partnerships
- Identifying target accounts for sales
- Researching companies matching your ICP
- Preparing for business development

## Workflow

1. **Understand** - Analyze your product/service
2. **Define** - Create ideal customer profile
3. **Research** - Find matching companies
4. **Score** - Prioritize leads by fit
5. **Strategize** - Provide contact approaches

## Ideal Customer Profile (ICP)

Define your target by:

| Attribute | Examples |
|-----------|----------|
| Industry | SaaS, Fintech, Healthcare |
| Company Size | 50-200 employees |
| Location | Bay Area, US, Global |
| Technology | Uses AWS, Python, etc. |
| Growth Stage | Series A, Profitable |
| Pain Points | Problems your product solves |

## Lead Scoring Criteria

Score 1-10 based on:

| Factor | Weight |
|--------|--------|
| ICP Alignment | High |
| Signals of Need | High |
| Budget Availability | Medium |
| Timing Indicators | Medium |
| Competitive Landscape | Low |

**Signals of Need**:

- Job postings for relevant roles
- Tech stack indicators
- Recent news or announcements
- Growth/funding indicators

## Output Format

```markdown
# Lead Research Results

## Summary
- Total leads found: [X]
- High priority (8-10): [X]
- Medium priority (5-7): [X]

---

## Lead 1: [Company Name]

**Website**: [URL]
**Priority Score**: [X/10]
**Industry**: [Industry]
**Size**: [Employee count]

**Why They're a Good Fit**:
[2-3 specific reasons]

**Target Decision Maker**: [Role/Title]
**LinkedIn**: [URL if available]

**Value Proposition for Them**:
[Specific benefit for this company]

**Outreach Strategy**:
[Personalized approach]

**Conversation Starters**:
- [Specific point 1]
- [Specific point 2]
```

## Finding Lead Signals

Look for:

- Job postings revealing tech stack/needs
- GitHub repos showing tool usage
- Recent funding announcements
- Company blog posts about challenges
- Conference speaking or sponsorships
- Technology partnership announcements

## Outreach Strategies

### Cold Email

- Reference specific company context
- Lead with value, not features
- Include relevant social proof

### LinkedIn

- Connect with personalized note
- Engage with their content first
- Reference mutual connections

### Warm Introduction

- Identify mutual contacts
- Ask for specific introduction
- Prepare context for introducer

## Best Practices

- Be specific about your product's value
- Run from your codebase for automatic context
- Provide detailed ICP constraints
- Request follow-up on promising leads
- Generate CRM-ready CSV exports

Overview

This skill helps you identify, qualify, and prioritize sales leads by analyzing your product and matching it to target companies. It guides you through defining an ideal customer profile, researching companies that fit, scoring prospects, and crafting outreach approaches. Use it to generate CRM-ready lead lists and tailored messaging for outreach. The goal is to turn product context into actionable prospecting workflows.

How this skill works

I start by extracting product attributes, value propositions, and target outcomes you provide. Then I help define an ideal customer profile (industry, size, tech stack, stage, geography, pain points) and search for companies matching those constraints. Each candidate is scored on ICP alignment, signals of need, budget/timing, and competitive context, and I produce prioritized lead entries with decision maker suggestions, value props, and outreach strategies. Outputs are formatted for easy import into CRM or to use directly in email/LinkedIn sequences.

When to use it

  • When building a list of potential customers for a new product or feature
  • When targeting accounts for outbound sales or account-based marketing
  • When qualifying and prioritizing inbound interest by fit and timing
  • When researching companies that match your ideal customer profile
  • When preparing tailored outreach and conversation starters for business development

Best practices

  • Provide a concise product summary and top three value outcomes to sharpen matching
  • Specify ICP constraints clearly: industry, company size, tech stack, location, and growth stage
  • Prioritize signals of need (job postings, funding, product launches) over loosely related attributes
  • Ask for CSV/CRM-ready export and include key fields: score, decision maker, tags, and notes
  • Test outreach templates with small batches, iterate based on reply and conversion rates

Example use cases

  • Create a prioritized list of 50 SaaS companies using AWS with 50–200 employees in the US
  • Find fintech startups post-Series A that recently hired engineering leads and likely need observability tools
  • Build a partner outreach list of healthcare platforms integrating with specific EMR systems
  • Produce personalized cold email and LinkedIn primers for high-priority accounts
  • Convert research output into a CRM-ready CSV with scores and outreach notes

FAQ

How are leads scored?

Leads are scored 1–10 based on ICP alignment, signals of need, budget/timing indicators, and competitive landscape, with ICP and need weighted highest.

What signals indicate a high-priority lead?

High-priority signals include recent funding, relevant job postings, public product changes or complaints, tech stack alignment, and explicit mentions of pain your product solves.