Daniel Ayomide
← All work

04 · Data · lead sourcing

Lead-gen systems: harvesters + CRM sheet

A lead-sourcing pipeline that harvests businesses from Google Places and public registries, finds decision-makers, verifies emails and lands them in a CRM sheet.

Lead-gen systems: harvesters + CRM sheet screenshot

(a) Problem

  • A client needed 1,000 US decision-maker leads across nursing homes, nurse staffing agencies and oil and gas operators. Paid databases had thin coverage in all four niches.

(b) Solution

  • Harvest businesses from Google Places by niche and city.
  • Cross-reference public data: CMS staffing records, state licence lists, oil and gas permit filings and franchise-tax officer records.
  • Crawl company sites and guess domain patterns to find named contacts, then verify every address.
  • Deliver to a CRM sheet with a 'why they qualify' column for every row.

(c) Architecture

Google Places

businesses

Public registries

CMS, permits

Python enrichment

crawl + match

Email verification

per address

CRM sheet

qualified rows

(d) Stack

Python · Google Places API · RapidAPI · Google Sheets · Excel

(e) Result

  • 999 leads delivered across four lists, every one with an email.
  • 444 of them named decision-makers rather than general inboxes.
  • The same approach runs as a Make.com scenario for a Norwegian client, pulling companies from the national shareholder registry and enriching them with LinkedIn lookups.

(f) Gallery

Company-registry lead generation for a Norwegian client
Company-registry lead generation for a Norwegian client
Lead enrichment with LinkedIn lookups and deduping
Lead enrichment with LinkedIn lookups and deduping
Dual-pipeline lead sync with filters and routing
Dual-pipeline lead sync with filters and routing