Completions

Capture-demand swarm · Lead-Scoring + Routing Agent · Firmographic-enrichment skill · Build pillar · Published June 4, 2026

How to build firmographic enrichment + lead routing for multi-location operators

This guide explains how to architect the firmographic-enrichment skill on the lead-scoring-routing agent end-to-end at multi-location franchise + multi-store scale: per-portfolio per-lead per-canonical-multi-vendor-enrichment-waterfall + per-real-time-enrichment + per-data-freshness-spec + per-cross-vendor-deduplication + per-confidence-scoring + per-territory-matching + per-account-based-marketing-routing + per-SLA-enforcement + per-portfolio audit-trail.

Engage the lead-scoring-routing agentSee the 32-agent swarm

What you will build

  • Per-portfolio per-canonical-multi-vendor-enrichment-waterfall across per-Tier-1 (Apollo + ZoomInfo + Clearbit / HubSpot Breeze Intelligence) + per-Tier-2 (Cognism + Lusha + LeadIQ) + per-Tier-3 (Hunter + RocketReach + People Data Labs + Coresignal) with per-field-waterfall-fall-through-rule (Tier-1 attempt-first + Tier-2 on miss + Tier-3 on miss + cost-budget stop-rule) + per-field-vendor-accuracy-rank (firmographic = Apollo-first, technographic = Clearbit-first, intent = Bombora/6sense/Demandbase-first, contact = ZoomInfo/Lusha-first).
  • Per-canonical-real-time-enrichment — per-form-submission-trigger + per-CRM-record-create-trigger + per-vendor-latency-spec (Tier-1 under 500ms + Tier-2 under 1500ms + Tier-3 under 3000ms) + per-async-batch-enrichment-fallback-when-real-time-budget-exceeded.
  • Per-canonical-data-freshness-spec — per-firmographic-field 90-day staleness + per-contact-field 180-day staleness + per-technographic-field 365-day staleness + per-stale-field re-enrichment trigger + per-stale-field vendor rotation.
  • Per-canonical-cross-vendor-deduplication via per-domain + per-DUNS-number + per-LinkedIn-company-URL + per-tax-ID-EIN resolution + per-cross-vendor-field-conflict-resolution (Tier-1 wins on firmographic + Tier-1 wins on employee-count + most-recent-update wins on contact + highest-confidence wins).
  • Per-canonical-confidence-scoring per-field (Tier-1 vendor 95% + Tier-2 vendor 85% + Tier-3 vendor 75% + cross-vendor-agreement bonus + data-freshness penalty) + per-low-confidence-field-flag-for-human-review.
  • Per-canonical-territory-matching — per-franchisee-territory-spec (ZIP-code list + DMA list + radius from store pin + state list + county list) + per-lead-address-to-territory match + per-territory-conflict-resolution (overlap routes to closest store + overlap routes to highest-priority franchisee + uncovered routes to corporate marketing) + per-FDD-compliance-attestation.
  • Per-canonical-account-based-marketing-routing — per-account-tier-spec (Tier-1 strategic 300-target + Tier-2 named 1,500-target + Tier-3 target 5,000-target) + per-SLA (Tier-1 = 1-hour + Tier-2 = 4-hour + Tier-3 = 24-hour) + per-routing-rule (Tier-1 to VP-Sales + Tier-2 to Sales-Director + Tier-3 to SDR-team) + per-SLA-violation alert + escalation + per-SLA-compliance-dashboard.

Why per-vendor-Apollo-Enrichment-single-account breaks at multi-location-franchise scale

Per-vendor-Apollo-canonical-Enrichment ships per-account per-lead per-firmographic-field primitive. Per-vendor-ZoomInfo + Clearbit + Cognism + Lusha + Hunter + RocketReach + LeadIQ + DiscoverOrg + People Data Labs + Coresignal + LeadFeeder-canonical-single-account ship per-vendor per-native enrichment primitives.

At 1-territory-1-marketing-team scale per-account per-lead per-firmographic-field primitive is enough. At 200-territory-200-franchisee scale per-multi-vendor-waterfall-not-single-account + per-field-vendor-selection-rule + per-data-freshness-spec-90-day-180-day-365-day + per-cross-vendor-deduplication-via-company-resolution + per-confidence-scoring-per-field + per-territory-matching-per-franchisee-radius-ZIP-DMA + per-ABM-routing-per-account-tier + per-SLA-enforcement-per-lead-status.

Per-cross-vendor-enrichment-fragmentation + per-data-staleness-blind + per-cross-vendor-conflict-resolution-blind + per-confidence-scoring-blind + per-territory-overlap-conflict-resolution-blind + per-ABM-tier-routing-blind + per-SLA-enforcement-blind.

The operator-side architecture above per-vendor-enrichment primitive is canonical-multi-vendor-waterfall + per-real-time-enrichment + per-data-freshness + per-cross-vendor-deduplication + per-confidence-scoring + per-territory-matching + per-ABM-routing + per-SLA-enforcement + per-routing-audit-trail.

What is in market today

Per-platform per-firmographic-enrichment-vendor

Apollo.io, ZoomInfo, Clearbit (HubSpot Breeze Intelligence), Cognism, Lusha, Hunter.io, RocketReach, LeadIQ, DiscoverOrg, People Data Labs, Coresignal, Adapt.io, UpLead, Seamless.AI, Surfe (formerly Leadjet), Datanyze. Per-account per-lead per-firmographic-field. Per-canonical-multi-vendor-waterfall-canonical-per-field-vendor-selection-canonical-cross-vendor-deduplication is not the primitive.

Per-platform per-intent-data-vendor

6sense, Demandbase (ABM-platform-tier), Bombora, G2 Buyer Intent, TrustRadius Trust Signals, LeadSift (Foundry), Intentsify, MRP Prelytix, NetLine Buyer Engagement, KickFire. Per-account per-account-intent-score. Per-canonical-multi-vendor-intent-canonical-cross-vendor-deduplication-canonical-Tier-rank-routing is not the primitive.

Per-platform per-CRM-routing-platform

Salesforce + Salesforce Sales Cloud Round Robin, HubSpot Sales Hub, Outreach, Salesloft, Chili Piper, LeanData, RingLead (ZoomInfo OperationsOS), Distribution Engine (NC-Squared), Lane Four (formerly Distribution Engine). Per-account per-routing-rule per-territory. Per-canonical-territory-FDD-compliance-canonical-multi-territory-overlap-resolution-canonical-account-tier-SLA-enforcement is not the primitive.

Per-platform per-data-warehouse

Snowflake, Databricks, BigQuery, Redshift, Synapse, ClickHouse, Firebolt, MotherDuck. Per-account per-table per-row. Per-canonical-per-lead-enrichment-audit-trail-immutable-storage-canonical-SOC2-canonical-GDPR-export is not the primitive.

How the architecture is built

  1. Per-portfolio per-canonical-multi-vendor-enrichment-API-substrate. Per-Apollo-API + per-ZoomInfo-API + per-Clearbit-HubSpot-Breeze-Intelligence-API + per-Cognism-API + per-Lusha-API + per-LeadIQ-API + per-Hunter-API + per-RocketReach-API + per-People-Data-Labs-API + per-Coresignal-API canonical-multi-vendor.
  2. Per-portfolio per-canonical-per-field-waterfall-fall-through-rule. Per-Tier-1-attempt-first + per-Tier-2-on-miss + per-Tier-3-on-miss + per-cost-budget-stop-rule canonical-fall-through.
  3. Per-portfolio per-canonical-per-field-vendor-accuracy-rank. Per-firmographic-Apollo-first + per-technographic-Clearbit-first + per-intent-Bombora-6sense-Demandbase-first + per-contact-ZoomInfo-Lusha-first canonical-accuracy-rank.
  4. Per-portfolio per-canonical-real-time-enrichment-trigger. Per-form-submission + per-CRM-record-create + per-Tier-1-under-500ms + per-Tier-2-under-1500ms + per-Tier-3-under-3000ms + per-async-batch-fallback canonical-real-time.
  5. Per-portfolio per-canonical-data-freshness-spec. Per-firmographic-90-day + per-contact-180-day + per-technographic-365-day + per-stale-field-re-enrichment-trigger + per-stale-field-vendor-rotation canonical-freshness.
  6. Per-portfolio per-canonical-cross-vendor-deduplication. Per-domain + per-DUNS + per-LinkedIn-company-URL + per-tax-ID-EIN canonical-company-resolution.
  7. Per-portfolio per-canonical-cross-vendor-field-conflict-resolution. Per-Tier-1-wins-on-firmographic + per-Tier-1-wins-on-employee-count + per-most-recent-update-wins-on-contact + per-highest-confidence-wins canonical-conflict-resolution.
  8. Per-portfolio per-canonical-per-field-confidence-scoring. Per-Tier-1-95-percent + per-Tier-2-85-percent + per-Tier-3-75-percent + per-cross-vendor-agreement-bonus + per-data-freshness-penalty + per-low-confidence-flag-for-human-review canonical-confidence.
  9. Per-portfolio per-canonical-per-franchisee-territory-spec. Per-ZIP-code-list + per-DMA-list + per-radius-from-store-pin + per-state-list + per-county-list canonical-territory.
  10. Per-portfolio per-canonical-territory-conflict-resolution + FDD-compliance. Per-overlap-routes-to-closest-store + per-overlap-routes-to-highest-priority-franchisee + per-uncovered-routes-to-corporate-marketing + per-FDD-compliance-attestation canonical-territory-routing.
  11. Per-portfolio per-canonical-account-tier-spec + per-SLA-spec. Per-Tier-1-strategic-300-target + per-Tier-2-named-1500-target + per-Tier-3-target-5000-target + per-Tier-1-1-hour-SLA + per-Tier-2-4-hour-SLA + per-Tier-3-24-hour-SLA canonical-tier-SLA.
  12. Per-portfolio per-canonical-per-account-tier-routing-rule. Per-Tier-1-routes-to-VP-Sales + per-Tier-2-routes-to-Sales-Director + per-Tier-3-routes-to-SDR-team canonical-routing.
  13. Per-portfolio per-canonical-SLA-enforcement + per-routing-audit-trail. Per-SLA-violation-alert + per-SLA-violation-escalation + per-SLA-compliance-dashboard + per-lead-ID + per-enrichment-vendor-chain + per-per-field-source-vendor + per-per-field-confidence + per-territory-match-resolution + per-account-tier-assignment + per-routing-decision + per-routing-timestamp + per-SLA-status + per-conversion-outcome + per-CSV-export + per-SOC2-export + per-GDPR-data-subject-access-request-format-export + per-immutable-storage.

Frequently asked questions

What is firmographic enrichment + lead routing for multi-location operators?

Firmographic enrichment + lead routing runs per-portfolio per-lead per-canonical-multi-vendor-enrichment-waterfall + per-canonical-real-time-enrichment + per-canonical-data-freshness-spec + per-canonical-cross-vendor-deduplication + per-canonical-confidence-scoring + per-canonical-territory-matching + per-canonical-account-based-marketing-routing + per-canonical-SLA-enforcement + per-canonical-routing-audit-trail. Per-canonical-multi-vendor-enrichment-waterfall runs per-canonical-Tier-1-vendor-spec (per-Apollo + per-ZoomInfo + per-Clearbit-HubSpot-Breeze-Intelligence per-canonical-Tier-1) + per-canonical-Tier-2-vendor-spec (per-Cognism + per-Lusha + per-LeadIQ per-canonical-Tier-2) + per-canonical-Tier-3-vendor-spec (per-Hunter + per-RocketReach + per-People-Data-Labs + per-Coresignal per-canonical-Tier-3) + per-canonical-per-field-waterfall-rule (per-firmographic-fields-Apollo-first + per-technographic-fields-Clearbit-first + per-intent-fields-Bombora-6sense-Demandbase-first + per-contact-fields-ZoomInfo-Lusha-first per-canonical-field-waterfall) + per-canonical-per-vendor-cost-spec + per-canonical-per-vendor-coverage-spec + per-canonical-per-vendor-accuracy-spec. The per-platform firmographic-enrichment vendor category includes Apollo.io, ZoomInfo, Clearbit (HubSpot Breeze Intelligence), Cognism, Lusha, Hunter.io, RocketReach, LeadIQ, DiscoverOrg, People Data Labs, Coresignal, LeadFeeder, 6sense, Demandbase, Bombora, Adapt.io, UpLead, Seamless.AI, Surfe (formerly Leadjet), Datanyze.

Why does per-vendor-Apollo-canonical-Enrichment-canonical-single-account break down at multi-location-franchise scale?

Per-vendor-Apollo-canonical-Enrichment ships per-account per-lead per-firmographic-field primitive. Per-vendor-ZoomInfo + per-Clearbit + per-Cognism + per-Lusha + per-Hunter + per-RocketReach + per-LeadIQ + per-DiscoverOrg + per-People-Data-Labs + per-Coresignal + per-LeadFeeder-canonical-single-account ship per-vendor per-native enrichment primitives. At 1-territory-1-marketing-team scale per-account per-lead per-firmographic-field primitive is enough. At 200-territory-200-franchisee scale per-canonical-multi-vendor-waterfall-enrichment-canonical-not-single-account + per-canonical-per-field-vendor-selection-rule + per-canonical-data-freshness-spec-canonical-90-day-canonical-180-day-canonical-365-day + per-canonical-cross-vendor-deduplication-canonical-via-company-resolution + per-canonical-confidence-scoring-canonical-per-field + per-canonical-territory-matching-canonical-per-franchisee-canonical-radius-canonical-ZIP-canonical-DMA + per-canonical-ABM-routing-canonical-per-account-tier + per-canonical-SLA-enforcement-canonical-per-lead-status.

How does per-portfolio per-canonical-multi-vendor-enrichment-waterfall + per-real-time-enrichment work?

Per-portfolio per-canonical-multi-vendor-enrichment-waterfall runs per-portfolio per-canonical-Tier-1-vendor-API (per-Apollo-API + per-ZoomInfo-API + per-Clearbit-HubSpot-Breeze-Intelligence-API per-canonical-Tier-1) + per-canonical-Tier-2-vendor-API (per-Cognism-API + per-Lusha-API + per-LeadIQ-API per-canonical-Tier-2) + per-canonical-Tier-3-vendor-API (per-Hunter-API + per-RocketReach-API + per-People-Data-Labs-API + per-Coresignal-API per-canonical-Tier-3) + per-canonical-per-field-waterfall-fall-through-rule (per-Tier-1-attempt-first + per-Tier-2-on-miss + per-Tier-3-on-miss + per-cost-budget-stop-rule per-canonical-fall-through) + per-canonical-per-field-vendor-accuracy-rank (per-firmographic-Apollo-first + per-technographic-Clearbit-first + per-intent-Bombora-6sense-Demandbase-first + per-contact-ZoomInfo-Lusha-first per-canonical-field-accuracy-rank). Per-canonical-real-time-enrichment runs per-canonical-form-submission-trigger-real-time-enrichment + per-canonical-CRM-record-create-trigger-real-time-enrichment + per-canonical-per-vendor-latency-spec (per-Tier-1-under-500ms + per-Tier-2-under-1500ms + per-Tier-3-under-3000ms per-canonical-latency) + per-canonical-async-batch-enrichment-fallback-when-real-time-budget-exceeded.

What does per-portfolio per-canonical-data-freshness-spec + per-cross-vendor-deduplication + per-confidence-scoring do?

Per-portfolio per-canonical-data-freshness-spec runs per-portfolio per-canonical-per-field-freshness-spec (per-firmographic-field-90-day-staleness-budget + per-contact-field-180-day-staleness-budget + per-technographic-field-365-day-staleness-budget per-canonical-freshness) + per-canonical-stale-field-re-enrichment-trigger + per-canonical-stale-field-vendor-rotation. Per-canonical-cross-vendor-deduplication runs per-portfolio per-canonical-company-resolution-spec (per-domain-resolution + per-DUNS-number-resolution + per-LinkedIn-company-URL-resolution + per-tax-ID-EIN-resolution per-canonical-company-resolution) + per-canonical-cross-vendor-field-value-deduplication + per-canonical-cross-vendor-field-conflict-resolution (per-Tier-1-wins-on-firmographic + per-Tier-1-wins-on-employee-count + per-most-recent-update-wins-on-contact + per-highest-confidence-wins per-canonical-conflict-resolution). Per-canonical-confidence-scoring runs per-portfolio per-canonical-per-field-confidence-score (per-Tier-1-vendor-confidence-95-percent + per-Tier-2-vendor-confidence-85-percent + per-Tier-3-vendor-confidence-75-percent + per-cross-vendor-agreement-bonus + per-data-freshness-penalty per-canonical-confidence) + per-canonical-low-confidence-field-flag-for-human-review.

What does per-portfolio per-canonical-territory-matching + per-account-based-marketing-routing + per-SLA-enforcement do?

Per-portfolio per-canonical-territory-matching runs per-portfolio per-canonical-per-franchisee-territory-spec (per-ZIP-code-list + per-DMA-list + per-radius-from-store-pin + per-state-list + per-county-list per-canonical-territory-spec) + per-canonical-per-lead-address-to-territory-match + per-canonical-territory-conflict-resolution (per-overlap-territory-routes-to-closest-store + per-overlap-territory-routes-to-highest-priority-franchisee + per-uncovered-territory-routes-to-corporate-marketing per-canonical-conflict-resolution) + per-canonical-territory-FDD-compliance-attestation. Per-canonical-account-based-marketing-routing runs per-portfolio per-canonical-account-tier-spec (per-Tier-1-strategic-account-300-target + per-Tier-2-named-account-1500-target + per-Tier-3-target-account-5000-target per-canonical-account-tier) + per-canonical-per-account-tier-SLA-spec (per-Tier-1-strategic-account-SLA-1-hour-response + per-Tier-2-named-account-SLA-4-hour-response + per-Tier-3-target-account-SLA-24-hour-response per-canonical-SLA) + per-canonical-per-account-tier-routing-rule (per-Tier-1-routes-to-VP-Sales + per-Tier-2-routes-to-Sales-Director + per-Tier-3-routes-to-SDR-team per-canonical-routing). Per-canonical-SLA-enforcement runs per-portfolio per-canonical-per-lead-status-SLA + per-canonical-SLA-violation-alert + per-canonical-SLA-violation-escalation + per-canonical-SLA-compliance-dashboard.

What does per-portfolio per-canonical-routing-audit-trail + per-lead-scoring-routing-agent-canonical-bundle do?

Per-portfolio per-canonical-routing-audit-trail runs per-portfolio per-canonical-per-lead-canonical-audit-record (per-lead-ID + per-enrichment-vendor-chain + per-per-field-source-vendor + per-per-field-confidence + per-territory-match-resolution + per-account-tier-assignment + per-routing-decision + per-routing-timestamp + per-SLA-status + per-conversion-outcome per-canonical-audit-record) + per-canonical-audit-trail-export-CSV + per-canonical-audit-trail-export-SOC2-compliance-format + per-canonical-audit-trail-export-GDPR-data-subject-access-request-format + per-canonical-audit-trail-immutable-storage. Per-lead-scoring-routing-agent-canonical-bundle integrates the firmographic-enrichment skill with sibling skills on the same agent: per-canonical-lead-enrichment (sibling, parent commercial pillar at /lead-enrichment) + per-canonical-bant-scoring (sibling, downstream consumer of enrichment for BANT qualification) + per-canonical-firmographic-enrichment (sibling, this skill) + per-canonical-multi-location-bant-lead-scoring (sibling, downstream consumer for per-location lead-scoring).

Engage the lead-scoring-routing agent

Per-portfolio per-canonical-multi-vendor-enrichment-waterfall + per-real-time-enrichment + per-data-freshness-spec + per-cross-vendor-deduplication + per-confidence-scoring + per-territory-matching + per-account-based-marketing-routing + per-SLA-enforcement + per-portfolio audit-trail shipped as the orchestration layer above your existing per-firmographic-enrichment-vendor + per-intent-data-vendor + per-CRM-routing-platform + per-data-warehouse primitive.

Book a scope callBrowse the 32-agent catalog

Related reading