Lead Enrichment — Multi-Source Data Completion

Enrich CRM contact records by filling missing fields from multiple sources. Works with DuckDB workspace entries or standalone JSON data.

Sources (Priority Order)

1. 1. LinkedIn (via linkedin-scraper skill) — name, title, company, education, connections
2. Web Search (via websearch tool) — email patterns, company info, social profiles
3. Company Website (via webfetch) — team pages, about pages, contact info
4. Email Pattern Discovery — derive email from name + company domain

Enrichment Pipeline

Step 1: Assess What's Missing

Step 2: Prioritize by Value

• - High priority: Missing email (needed for outreach)
• Medium priority: Missing title/company (needed for personalization)
• Low priority: Missing education, connections count, about text

Step 3: Enrich Per Record

For each record with gaps:

If LinkedIn URL is known but other fields missing:

1. 1. Use linkedin-scraper to visit profile
2. Extract: title, company, location, education, about
3. Update DuckDB record

If LinkedIn URL is missing:

1. 1. Search LinkedIn: {name} {company} or INLINECODE1
2. Verify match (name + company alignment)
3. Store LinkedIn URL, then scrape full profile

If Email is missing:

1. 1. Find company domain (web search or LinkedIn company page)
2. Try common patterns:

1. 3. Optionally verify with web search: INLINECODE6
2. Check company team/about page for email format clues

If Company info is missing:

1. 1. Web search: "{name}" "{title}" or check LinkedIn
2. Fetch company website for: industry, size, description, funding

Step 4: Update Records

Bulk Enrichment Mode

For enriching many records at once:

1. 1. Query all incomplete records from DuckDB
2. Group by company (scrape company once, apply to all employees)
3. Process in batches of 10-20 records
4. Report progress after each batch:

   Enrichment Progress: 45/120 leads (38%)
   ├── Emails found: 32/45 (71%)
   ├── LinkedIn matched: 41/45 (91%)
   ├── Titles updated: 38/45 (84%)
   └── ETA: ~15 min remaining
   

1. 5. Save checkpoint after each batch (in case of interruption)

Enrichment Quality Rules

• - Confidence scoring: Mark each enriched field with confidence (high/medium/low)

• - Never overwrite existing data unless explicitly asked
• Flag conflicts: If enriched data contradicts existing data, flag for review
• Dedup check: Before inserting LinkedIn URL, check it's not already assigned to another contact

Email Pattern Discovery

Common corporate email formats by frequency:

1. 1. first.last@domain.com (most common, ~45%)
2. INLINECODE9 (~20%)
3. INLINECODE10 (~15%)
4. INLINECODE11 (~10%)
5. INLINECODE12 (~5%)
6. INLINECODE13 (~3%)
7. INLINECODE14 (~2%)

Strategy:

1. 1. If you know one person's email at the company, derive the pattern
2. Search web for INLINECODE15
3. Check company team page source code for mailto: links
4. Use the most common pattern as fallback

Output

After enrichment, provide a summary:

CODEBLOCK3

DuckDB Field Mapping

Standard field names for Ironclaw CRM objects: