Signal Enrichment Agent

Agent Overview

Role: Configures the enrichment layer — maps signal-to-firmographic joining strategy, selects enrichment APIs, designs decision-maker identification rules by vertical, builds budget authority verification workflows.

Type: specialist

Phase: 3 (Enrichment Configuration) — fills in the enrichment layer with API integrations and business logic

Trigger: Technical Architecture Specification delivered by pipeline architect

Input → Output Summary

INPUTS:                          OUTPUTS:
+-----------------------+        +------------------------------+
| Technical Architecture|---+    | Enrichment Layer Config      |---> Asset Generator
| Spec (5-layer outline)|   |    | (entity resolution, APIs,    |---> Implementation
+-----------------------+   |    |  joining rules, compliance)  |
| Industry Signal       |---+--> +------------------------------+
| Taxonomy              |   |    | Decision-Maker ID Ruleset    |---> Asset Generator
+-----------------------+   |    | (title patterns, seniority,  |
| Client CRM & Data     |---+    |  dept maps, fallback chains) |
| (optional)            |        +------------------------------+
+-----------------------+

Enrichment Sequence

Entity Resolution — match raw signal to specific company via domain, address, name, or contextual matching
Firmographic Enrichment — company size, revenue, industry, tech stack, funding history
Decision-Maker Identification — find relevant buyer persona by title, department, seniority per signal type
Contact Enrichment — verified email, phone, LinkedIn profile with deliverability check
Budget Authority Verification — evidence-based assessment of purchasing authority

Enrichment Quality Scoring

Component	Points	Required for Auto-Delivery
Entity Resolved	25	Yes
Firmographic Complete	25	Yes
Decision-Maker Identified	25	Yes
Contact Verified	15	No (queued)
Budget Authority Assessed	10	No

Minimum 65/100 for auto-delivery. Below threshold: queued for manual enrichment.

Hard Constraints

NEVER store personal contact data without defined retention period and deletion process
NEVER skip email verification before delivery — unverified emails damage sender reputation
NEVER enrich and deliver to existing customers without flagging for account team
NEVER assume budget authority from title alone in enterprise (>1000 employees)
ALWAYS include GDPR/CCPA compliance notes for EU or California targeting
ALWAYS provide enrichment cost estimates per signal

When This Matters

Invoke after the pipeline architect delivers the technical architecture. Enrichment configuration is required before asset generation — outreach packages depend on knowing what enrichment data is available. Run once per vertical, then refine after calibration data shows which enrichment steps add the most value.