Domain Lead Scoring and ICP Enrichment

Domain Lead Scoring and ICP Enrichment scores company websites against your ideal customer profile and returns agent-ready lead qualification data. It is built for AI sales agents, prospecting workflows, CRM enrichment, and outbound prioritisation when you have domains but need fit scores, reasons, disqualifiers, website evidence, and a recommended next action.

Use cases

• Score a list of domains before importing leads into a CRM.
• Prioritise outbound lists by ICP fit.
• Give an AI sales agent structured lead qualification context.
• Add evidence-backed fit reasons and disqualifiers to prospect records.
• Build a lightweight enrichment step before deeper paid enrichment.

Use this Actor when

Use this Actor when you already have one or more company domains and a short ICP description, and you want a first-pass lead score with transparent reasons.

Do not use this Actor when

Do not use it as the sole source of truth for buying intent, revenue, headcount, funding, or private company facts. It scores public website signals only.

Input

{
  "domains": [
    "https://scaleupsystems.co"
  ],
  "icpDescription": "B2B companies selling services or software, with clear growth or lead generation needs.",
  "maxPagesPerDomain": 2
}

Output

The Actor writes one record per domain to the default dataset. Typical fields include:

• domainOrUrl
• fitScore
• fitBand
• reasons
• disqualifiers
• suggestedNextAction
• profile
• profile.evidencePages
• profile.contactPaths
• profile.confidence

Agent workflow

1. Pass a small batch of domains and an ICP description.
2. Read scored records from the default dataset.
3. Route high fit leads to outreach, medium fit leads to manual review, and low fit leads to deprioritisation.
4. Use reasons and disqualifiers to explain the decision in downstream automations.

Limitations

• Scoring is based on website text and visible contact/conversion paths.
• Thin or blocked websites can produce low-confidence results.
• The score should guide prioritisation, not replace human sales judgement.

Pricing and runtime

This MVP uses bounded website fetches and compact JSON output. Keep batches small for agent workflows; increase only after validating result quality.