What happened
Clay detailed the change in its own product changelog, the Product Roundup for the week of September 14, published September 21. Functions let a team turn any enrichment setup into a reusable, savable step — Clay's changelog specifically flags a one-click path to migrate private Recipes to user-managed Functions. The same release shipped self-serve sign-in and Auto Top-Ups, which auto-refill credit balances once they drop below a 250-credit minimum. The retirement of Public Recipes matters more than the addition: that library was where outbound and RevOps teams browsed to copy a working waterfall-enrichment setup or a specific data-provider chain instead of building one from scratch. Functions are workspace-wide and auto-installed, signaling Clay wants standardized, governed enrichment logic inside a company rather than ad-hoc templates copied from the public community.
Why Clay Functions is a workflow-governance move
MagnetizeX builds founder visibility systems for B2B firms.
Clay crossed $150 million in ARR in May 2026, up from roughly $30 million in 2024, largely by becoming the default enrichment layer for outbound teams stitching together dozens of data providers per lead. That growth created a real support problem: thousands of workspaces running copied Public Recipes that broke silently when a source provider changed its API, with no owner responsible for fixing them. Functions push enrichment logic into something a RevOps lead can version, name, and maintain like code, rather than something an SDR copy-pasted once and never touched again. For a growing outbound team, that's the difference between a prospecting stack that degrades quietly and one someone is actually accountable for.
- Audit any workflow built from a copied Public RecipeCheck your Clay tables this week for enrichment steps sourced from the old Public Recipes library; those Recipes are being retired, and a silently broken enrichment step will quietly degrade lead quality without triggering an obvious error.
- Convert your best working logic into a Function nowUse Clay's one-click migration to turn any private Recipe your team relies on into a Function before the old system is fully deprecated, so the logic survives the transition and stays editable by whoever owns your outbound stack.
- Assign an owner to your enrichment logicTreat Functions as shared infrastructure with a named owner in RevOps or growth, the same way you'd assign ownership to a CRM field mapping, since Clay is now making workspace-wide reuse the default rather than a one-off table trick.
By the numbers: Clay reported $150 million in ARR as of May 2026, up from roughly $100 million in November 2025 and about $30 million in 2024, a more than 260% year-over-year increase, per Sacra research.
What to do this week
Open your Clay workspace this week, filter your tables for any enrichment step built from a Public Recipe or column template, and migrate the ones you actually rely on into Functions using Clay's one-click tool before the old library disappears entirely. If you've never used Clay's enrichment layer for outbound, this is a reasonable week to trial it, since Functions make it easier to copy a working setup from a teammate without inheriting an unowned mess.