$ man orchestration

Orchestration

The meta-pattern. How Clay, Exa, email tools, MCPs, and CRMs chain together into a complete workflow. Not one tool — the connective tissue between all of them.

every tool in a GTM stack does one thing well. Clay enriches. Exa researches. Instantly sends. HubSpot tracks. but none of them know about each other by default. orchestration is the layer that makes them work together — the routing logic, the data handoffs, the trigger conditions, the quality gates. without orchestration, you have 6 tools and 6 separate workflows. with orchestration, you have one pipeline. I learned this the hard way. I used to run each tool manually and move data between them with CSV exports. now the orchestration layer handles it: signal fires → Clay enriches → Exa researches → Instantly sends → HubSpot records. the tools didn't change. the orchestration did.

my orchestration layer lives in Clay + MCP servers + Python scripts. Clay is the hub — it receives signals (web reveals, list imports, manual adds), runs qualification and enrichment, and syncs downstream. MCP servers let Claude monitor everything from one conversation — check Smartlead stats, search Exa for intel, post to Slack. Python scripts handle batch operations that Clay can't — like running Exa enrichment across 73 companies with rate limiting and deduplication. the orchestration pattern for a typical campaign looks like: signal trigger → Clay table → company qualification prompt → persona enrichment → Exa research (icebreakers + signals) → email enrichment → MX routing → platform sync (Instantly or HeyReach) → CRM sync (HubSpot). each step has a quality gate. if a company scores below threshold, it stops. if Exa finds no signals, it flags for manual review. orchestration isn't a tool — it's the architecture.