Clay's New Account Agents Feature Is Two of Its Own Products Fusing Together

Clay’s newest feature, Account Agents in Workflows, is really two of its prior product bets converging into one. The company announced the feature — now in open beta across its Enterprise, Growth, and Launch plans — as a way to embed AI agents directly inside GTM workflows: instead of writing conditional logic for every trigger across a limited set of data fields, an agent evaluates an account’s full context (CRM records, call transcripts, email activity, product usage) and decides what action is actually worth taking. Clay frames the shift plainly: “from writing conditional logic for every trigger to agents that hold a goal and decide what’s worth acting on.” Every agent run logs its input, output, timing, cost per record, and reasoning, and the four use cases Clay ships with — routing inbound demos by trial history, evaluating whether outbound signals warrant action, synthesizing win-loss reasoning from Gong calls for closed-lost re-engagement, and scoring accounts against full account state rather than firmographics alone — all depend on agents that remember what they found last time.

That persistence is the same differentiator Clay built a month earlier into Account Research Agents, which it launched explicitly to solve the problem that standard “Claygents” restart their context on every run: Account Research Agents instead maintain compounding account intelligence over time, pulling from the same Gong transcripts, CRM records, and buying signals, and writing synthesized findings back into the CRM automatically. And the branching, auditable orchestration layer Account Agents in Workflows runs on top of is Clay Workflows itself, the visual, graph-based “building primitive” Clay called its biggest interface shift since the original spreadsheet-style table, the same system its own Growth team used to replace an 81-column lead-routing table with a single MCP-driven workflow.

Put together, Account Agents in Workflows isn’t a new capability so much as Clay wiring persistent account memory into branching workflow logic — the two building blocks it spent the prior month shipping separately, now fused into the product its GTM customers actually touch day to day.