🗺️ Architecture

GTM Stack Map

The integrative view of the revenue stack. Capture + enrichment on the left, systems of record in the center, engagement + BI on the right, and the AI GTM build layer underneath. Click any node for the full definition, data flows, and notes.

System of Record
Capture & Routing
Enrichment / Call AI
Engagement & Reasoning
BI & Visualization
Reporting & Output
AI GTM · Secondary
● AI GTM Systems — Secondary / Evolving
Build layer writes back into core systems
INBOUND & CAPTURE
ENRICHMENT & CALL AI
SYSTEMS OF RECORD
ENGAGEMENT & REASONING
BI LAYER
OUTPUT
Meetings + contactsCustomer signalsEnrichmentCall dataOps stateLifecycle triggersDeal + contact ctxAgent outputsSubscription xrefARR / MRRHS dataOps viewsExec reportingForecast baseDeployProxyApp Cards APIAgent alertsAgent state

💡 Scroll horizontally to pan · Click any node for full definition, data in/out, and integration notes

How to read this diagram

  • Dashed lines are raw data flows (integration syncs, routing). Solid lines are active transforms and writes.
  • ⚑ Flagged nodes are load-bearing systems — HubSpot, Stripe, Clay, Sybill, Claude. If these break, the revenue engine stops.
  • The pink band at the bottom is the AI GTM build layer — secondary today but increasingly where RevOps ships leverage.
  • Upward curved wires from the AI layer show how custom agents write back into the core systems (HubSpot, Slack, Claude reasoning).