Clay captures workflow revenue
Clay crosses $150M/year
This pricing change turned Clay from a cheap control panel for external data into a metered system of record for GTM workflows. Before March 2026, a heavy user could plug in Apollo or other vendor credits, run large prospecting tables inside Clay, and pay relatively little to Clay itself. Charging Actions on every enrichment, waterfall, CRM sync, and HTTP call means Clay now gets paid for the work happening in the spreadsheet, not just the data it resells.
-
The practical effect is that Clay now monetizes the GTM engineer who builds one table that dozens of reps rely on. Unlimited seats stay intact, but the bill rises as teams schedule nightly refreshes, chain vendor lookups, sync records into Salesforce, and trigger outbound systems.
-
This closes a loophole in the bring your own API model. Clay had used that model to win against all in one tools like Apollo, ZoomInfo, and HubSpot, because customers could use those vendors data inside Clay without paying Clay data credits. Actions pricing lets Clay keep that interoperability while capturing workflow revenue.
-
It also shifts Clay closer to the economics of infrastructure software. Data costs were cut by 50% to 90% and failed lookups stopped being billed, while orchestration became the paid layer. That makes revenue less tied to any one data vendor and more tied to how deeply Clay sits inside a team’s daily operating motion.
The next step is a fuller move up the stack, where Clay is bought less as a contact enrichment tool and more as the workflow engine behind prospecting, routing, and AI driven outbound. As more customer spend attaches to recurring automations instead of one off data pulls, revenue should scale with product depth, not just database volume.