GTM Revenue Intelligence and Lead Enrichment Data Engine Spec

Role: Enterprise Data Architect specializing in Go-To-Market and Revenue Operations infrastructure.

Context

• Core CRM Target: {{primary_crm}}
• Third-Party Enrichment Providers: {{enrichment_sources}}
• Daily Lead Ingestion Rate: {{lead_ingestion_rate}}
• Predictive Scoring Model Runtime: {{scoring_model_runtime}}
• Reverse-ETL Sync Cadence: {{sync_frequency}}
• Central Warehouse Target: {{warehouse_target}}

Task

Construct a resilient, low-latency technical architecture specification for a B2B Revenue Intelligence Engine that ingests {{lead_ingestion_rate}} leads, executes waterfall enrichment across {{enrichment_sources}}, scores opportunities in {{scoring_model_runtime}}, and synchronizes state between {{warehouse_target}} and {{primary_crm}}.

Method

1. Specify the webhook intake gateway and schema validation tier for inbound prospect touchpoints.
2. Architect an asynchronous waterfall enrichment orchestration layer querying {{enrichment_sources}} based on confidence thresholds and cost constraints.
3. Design deduplication, account matching, and fuzzy resolution algorithms linking incoming contacts to parent entities.
4. Specify the feature transformation and inference pipeline running on {{scoring_model_runtime}} for propensity-to-buy scoring.
5. Detail the landing schema, transformation models, and audit tables within {{warehouse_target}}.
6. Architect the reverse-ETL sync engine to push prioritized records to {{primary_crm}} at {{sync_frequency}} cadence.
7. Formulate circuit-breaker and retry mechanics for external API limits and CRM rate thresholds.

Constraints

• Architecture MUST implement dynamic circuit breakers across {{enrichment_sources}} to prevent quota exhaustion and runaway costs.
• MUST NOT block inbound lead capture on downstream enrichment API latencies.
• PII data masking and encryption in transit/rest must meet enterprise security standards.
• Account matching must provide deterministic confidence scores before writing updates to {{primary_crm}}.

Output format

Present the technical specification using the following mandatory sections:

1. Executive Architecture Topology & Data Life Cycle
2. Ingestion Gateway & Rate-Limiting Specification
3. Waterfall Enrichment Subsystem & Cost Control Design
4. Identity Stitching & Account Association Logic
5. Machine Learning Scoring Runtime Architecture ({{scoring_model_runtime}})
6. Warehouse Layer ({{warehouse_target}}) & Reverse-ETL Sync ({{primary_crm}})
7. Resilience, Failure Modes, and Throttling Strategy Target length: 1200-1600 words.

Self-review

• Confirm all 6 variables ({{primary_crm}}, {{enrichment_sources}}, {{lead_ingestion_rate}}, {{scoring_model_runtime}}, {{sync_frequency}}, {{warehouse_target}}) are explicitly addressed in system interfaces.
• Verify that waterfall priority logic handles third-party timeout scenarios without dropping pipeline data.
• Confirm schema definitions account for schema drift in enrichment payloads.