Agent layerSince 2020
Clay
4.6/10Enrichment table. The inbound layer of an agent marketing stack, not an ESP.
Capability scores
Sending3.0
Design and generation3.5
Automations7.2
Positioning
Clay fills firmographic and contact fields before they hit Attio or Brew. This desk does not pretend Clay sends marketing email. It is the waterfall. Pair it with Brew MCP for the send, not instead of a send layer.
Agent and API surface
- Table refreshes and row context through Clay's API and emerging MCP integrations.
- Agents should start read-only. Write scopes after a human names the columns.
Automations
- Waterfalls and scheduled refreshes. Not lifecycle email graphs.
Deliverability
- Clay does not own inbox placement. The ESP you send from does.
Strengths
- +Best enrichment table most GTM agents already know.
- +Fits in front of Attio and Brew without pretending to be an ESP.
Trade-offs
- -Not a send layer. Not a brand canvas.
- -Stale rows break personalization if nobody owns refresh cadence.
Best for
RevOps and agents that need a table of enriched rows before a welcome or outbound sequence.
Consider if
You already have clean CRM data. Clay is not a canvas and not a sending domain.
Pricing posture
Usage-based enrichment credits. See clay.com/pricing.