Self-Hosted Lead Enrichment That Scores A Signup In Four Seconds

The Problem

Signups arrive with an email address and nothing else. Someone opens LinkedIn, works out whether the company is worth a call, and types what they found into the CRM. By the time that happens the lead is a day old and the record is inconsistent with every other record.

Prerequisites & Tool Stack

Everything this blueprint calls. Check you have them before you start - the usual reason a build stalls halfway is a key that takes a day to get approved.

Some links above are partner links and we earn a commission if you sign up through them. It costs you nothing extra, and it does not decide what goes in a blueprint - the self-hosted option is recommended wherever it is genuinely the better call.

What It Costs To Run

Monthly, at the volumes this blueprint was tested against. Worth comparing against what the manual version of this work costs you in hours.

Technical Breakdown

The decisions that matter, in the order you will meet them. Everything here is a thing that broke in testing before it was a rule.

const FREE_MAIL = new Set(['gmail.com', 'yahoo.com', 'outlook.com', 'hotmail.com', 'icloud.com']);
const ROLE = /^(info|support|sales|admin|hello|contact|billing)@/i;

const email = $json.email.trim().toLowerCase();
const domain = email.split('@')[1] ?? '';

return [{
  json: {
    email,
    domain,
    enrichable: Boolean(domain) && !FREE_MAIL.has(domain) && !ROLE.test(email),
  },
}];

When It Goes Wrong

The difference between a demo and something you can leave running is entirely in this table. Every row is a failure the blueprint handles explicitly rather than hoping about.

Payload Example

The record written to the CRM.

{
  "email": "dana@northwind-logistics.com",
  "domain": "northwind-logistics.com",
  "company": "Northwind Logistics",
  "headcount": 240,
  "industry": "Transportation & Logistics",
  "country": "US",
  "icp_score": 82,
  "tier": "A",
  "enriched_from": "cache",
  "enriched_at": "2026-08-21T14:02:11Z"
}