## Config

Config lives at `~/.config/lead-enrichment/config.json`. See `config.example.json` for full schema.

Key sections:

**enrichment.sources** — Which data sources to check (all public by default):
- `linkedin` — Public profiles via search
- `twitter` — Social activity and bio
- `github` — For technical leads
- `company_website` — About pages, team directories
- `news` — Recent mentions
- `crunchbase` — Company funding (public data)

**enrichment.depth** — How thorough to be:
- `quick` — Basic profile only (name, title, LinkedIn, company)
- `standard` — Above + social profiles + recent activity (default)
- `deep` — Above + news mentions + talking points + shared connections

**output.format** — Default output format (json/markdown/csv)

**output.include** — What to include in output:
- `contact_info` — Email attempts, phone
- `social_profiles` — All discovered links
- `recent_activity` — Posts, articles (last 30 days)
- `company_intel` — Company description, size, funding
- `talking_points` — AI-generated personalization hooks
- `raw_sources` — Source URLs for verification

**talking_points.enabled** — Generate AI talking points (requires Claude)

**talking_points.style** — Tone for suggestions (professional/friendly/bold)

**privacy.respect_robots** — Skip profiles with clear "no scraping" signals

**privacy.store_locally** — Cache enriched profiles (default: true)

## Data Sources

All sources are **public and free**:

1. **LinkedIn** — Public profiles via search (no API, respects robots.txt)
2. **Twitter/X** — Bio, recent tweets, follower count
3. **GitHub** — For technical roles (repos, activity, README)
4. **Company websites** — Team pages, About sections
5. **Google News** — Recent mentions
6. **Crunchbase** — Public company data (no API key needed for basic info)
7. **Common email patterns** — [email protected], [email protected], etc.

**Premium sources** (optional, requires API keys):
- Hunter.io — Email verification
- Clearbit — Enhanced company data
- Apollo — Direct contact info

Add API keys to `~/.clawdbot/secrets.env` if you have them. Enrichment works fine without them.

## Output Schema

Each enriched lead is saved as JSON:

## Integration with Trawl

Lead Enrichment pairs perfectly with Trawl (autonomous lead gen):

## Tips

**Email Discovery:**
- Works best when you provide company domain
- Tries common patterns (first@company, f.last@company, etc.)
- Marks confidence level (high/medium/low)
- Does NOT spam or verify via email sends (respects privacy)

**Talking Points:**
- Most valuable when enrichment depth = "deep"
- Requires recent activity data (posts, news)
- AI analyzes content for personalization hooks
- Style can be professional, friendly, or bold

**Batch Processing:**
- Use `--parallel` for speed (3-5 concurrent recommended)
- Progress saved (resume if interrupted)
- Failed leads logged to `batch-errors.json`

**Data Freshness:**
- Cached profiles expire after 30 days
- Force refresh with `--refresh` flag
- Social activity always fetched fresh

## Use Cases

**Sales Reps:**
- Research prospects before calls
- Personalize cold email sequences
- Find mutual connections or interests

**Recruiters:**
- Assess candidate backgrounds
- Find contact info for passive candidates
- Check GitHub activity for technical roles

**Partnerships:**
- Research potential partners
- Understand company context
- Find the right contact person

**Investors:**
- Quick founder background checks
- Company traction signals
- Network mapping

## Privacy & Ethics

This skill only uses **publicly available data**. It:
- Respects robots.txt and rate limits
- Does NOT scrape private profiles or paywalled content
- Does NOT send verification emails (won't spam your leads)
- Does NOT store data if privacy.store_locally = false
- Provides source URLs for transparency

**Be a human:** Just because you CAN enrich someone doesn't mean you should spam them. Use this for genuine, personalized outreach.

## Data Storage

Enriched leads are stored at `~/.config/lead-enrichment/data/leads/`:

# By name + company
./scripts/enrich.sh --name "Sarah Chen" --company "Acme Corp"

# By email
./scripts/enrich.sh --email "[email protected]"

# By LinkedIn URL
./scripts/enrich.sh --linkedin "https://linkedin.com/in/sarahchen"

# Output to file
./scripts/enrich.sh --name "Sarah Chen" --company "Acme Corp" --output sarah-chen.json

# With talking points
./scripts/enrich.sh --name "Sarah Chen" --company "Acme Corp" --talking-points

# From CSV (columns: name, company, email, linkedin_url)
./scripts/batch.sh --input leads.csv --output enriched/

# From JSON array
./scripts/batch.sh --input leads.json --output enriched/

# Process with concurrency
./scripts/batch.sh --input leads.csv --parallel 3

# Export as JSON (default)
./scripts/export.sh --format json enriched/*.json > leads.json

# Export as Markdown (readable)
./scripts/export.sh --format markdown enriched/*.json > leads.md

# Export as CSV (CRM import)
./scripts/export.sh --format csv enriched/*.json > leads.csv

# Pipe to your CRM
./scripts/export.sh --format json enriched/*.json | \
  curl -X POST https://your-crm.com/api/leads -d @-

{
  "lead_id": "sarah-chen-acme-corp",
  "enriched_at": "2025-01-29T10:30:00Z",
  "input": {
    "name": "Sarah Chen",
    "company": "Acme Corp"
  },
  "profile": {
    "full_name": "Sarah Chen",
    "title": "VP of Engineering",
    "company": "Acme Corp",
    "location": "San Francisco, CA",
    "bio": "Building the future of...",
    "photo_url": "https://...",
    "social_profiles": {
      "linkedin": "https://linkedin.com/in/sarahchen",
      "twitter": "https://twitter.com/sarahchen",
      "github": "https://github.com/sarahchen",
      "personal_site": "https://sarahchen.com"
    }
  },
  "contact": {
    "emails": [
      { "address": "[email protected]", "confidence": 0.85, "verified": false },
      { "address": "[email protected]", "confidence": 0.60, "verified": false }
    ],
    "phones": [],
    "preferred_channel": "email"
  },
  "company": {
    "name": "Acme Corp",
    "domain": "acmecorp.com",
    "industry": "SaaS",
    "size": "51-200 employees",
    "description": "AI-powered...",
    "funding": "Series B ($25M)",
    "tech_stack": ["React", "Node.js", "AWS"],
    "recent_news": [
      {
        "title": "Acme Corp raises $25M...",
        "url": "https://...",
        "date": "2025-01-15"
      }
    ]
  },
  "intelligence": {
    "recent_activity": [
      {
        "type": "twitter_post",
        "content": "Excited to announce...",
        "url": "https://...",
        "date": "2025-01-20"
      }
    ],
    "job_change_signal": false,
    "shared_connections": [],
    "interests": ["AI", "startups", "engineering leadership"]
  },
  "talking_points": [
    "Reference their recent Series B — congrats and ask about growth plans",
    "Mention mutual interest in AI/ML engineering",
    "Their tech stack (React/Node) aligns with your solution"
  ],
  "sources": [
    "https://linkedin.com/in/sarahchen",
    "https://twitter.com/sarahchen",
    "https://acmecorp.com/about"
  ],
  "confidence_score": 0.88
}

# Trawl finds leads, enrichment researches them
trawl sweep.sh                    # Discover leads
trawl leads.sh list --json |      # Export qualified leads
  jq -r '.[] | "\(.name)|\(.company)"' |
  while IFS='|' read name company; do
    ./enrich.sh --name "$name" --company "$company"
  done

# Or automate it via config:
# trawl config: "post_qualify_action": "enrich"

~/.config/lead-enrichment/
├── config.json                 # User configuration
├── data/
│   ├── leads/                  # Enriched profiles (one file per lead)
│   │   ├── sarah-chen-acme.json
│   │   └── john-smith-techco.json
│   ├── cache/                  # Temporary data (30-day expiry)
│   └── batch-runs/             # Batch processing logs
└── exports/                    # Generated exports