Everyone's Buying Clay. Almost Nobody's Ready For It.

There's a myth making the rounds in GTM circles this month: Clay now has an agent that builds plays for you, so you don't need anyone on your team who really knows Clay.

It's an easy conclusion to reach. It's also wrong, and teams that act on it are about to spend a lot of money learning why.

Clay is a great tool. I'm not arguing about that. I'm arguing that the newest features make the ownership question more important, not less.

What actually changed

At Sculpt, Clay's annual conference in San Francisco on October 8, the company showed an agent-first way to build: you describe the outcome you want, and an agent plans, runs and improves the play. It also pushed Clay Workflows, a visual canvas for multi-step plays that can branch, loop, run code and call agents, into beta for every user. That sits on top of Audiences, which pulls CRM records, call recordings and product usage into one data layer, plus Sequencer and Ads for running outreach and campaigns.

That's a serious platform. Clay has more than 17,000 customers and raised a $115M Series D at a $7.1B valuation, so it isn't going anywhere. If you run GTM, you will be asked about it.

But look closely at what those launches do. They make it faster to build. None of them make it easier to own what you built.

Easier to build is not easier to own

My view hasn't changed with the new features: Clay needs a dedicated owner. The reason is the kind of work people do in it. Clay workflows aren't one-off lists. They're running systems. Tables refresh, enrichments fire, agents make calls, and the results get written back into your CRM and marketing automation platform on a schedule.

Anything that runs on a schedule and writes to your system of record needs someone watching it. Your ICP shifts. A territory gets carved up. A data provider's coverage drops. A field gets renamed in Salesforce and a sync quietly starts failing. Every one of those means going back in to modify, update or fix what's already live.

An agent that builds a play in ten minutes doesn't change that. If anything, it makes it worse. When building is that fast, you end up with more running workflows than anyone can keep track of, and nobody who fully understands how they were put together.

The pricing makes the same point. Clay now meters two things separately: Data Credits for data pulled from its provider marketplace, and Actions for platform work like enrichments, AI calls and exports. CRM auto-sync is only on the Growth plan, which starts at $495 a month. Two meters running down independently is exactly what goes wrong when nobody owns the tables.

Clay amplifies what's already there

AI doesn't fix your foundation. It speeds up whatever is already there. Point Clay at a CRM with a defined ICP, clean account data and clear routing, and your team gets faster. Point it at duplicates, blank industry fields and accounts no one has touched in two years, and you get bad outreach, sent at scale and stamped back into Salesforce looking legitimate.

Clay's own sales leadership is saying something close to this. Announcing a partnership with Marketbridge this month, Clay's Global Head of Sales put it this way: "Enterprise teams do not need more signal, they need help taking action." The bottleneck isn't access to data. It's the process and the people who turn data into action.

The wider AI market shows the same pattern. Gartner expects more than 40% of agentic AI projects to be canceled by the end of 2027, mostly because of rising costs and unclear business value. The model is rarely the problem. The problem is that nobody defined what the project was for or who would run it.

Where Clay actually sits in your stack

A lot of the confusion comes from treating Clay as the center of the stack. It isn't. In most companies, Clay is the middle layer. It pulls from your marketing automation platform, your CRM and your other data sources, runs a workflow on top of that data, and writes the result back to your system of record, which is usually the CRM.

That means Clay is only as good as the systems on either side of it. If the CRM is the source of truth and nobody trusts the CRM, Clay writing into it doesn't build trust. It just gives you more records nobody believes.

If you're not ready, do this instead

"Don't buy it yet" isn't the same as "do nothing." My advice is the same as for any tool. Before you look at Clay, write down three things:

What's broken. The specific gaps in your process: leads that sit unrouted, accounts with no firmographics, reps hand-entering call notes.

What's manual. The workflows your team runs by hand every week that should be automated.

What has to connect. The tools those workflows touch, and where the output needs to land.

If that list points to Clay, because Clay solves those problems and connects to the tools you rely on, then ask the second question: do you have someone with MOps, RevOps or GTM engineering skills who can manage Clay and own it? Not someone who can set it up in a sprint. Someone who will still be maintaining it six months from now.

If the answer is yes, buy it. You'll get far more from it than the team that bought it because everyone else did. If the answer is no, the first investment isn't the license. It's the person.

Build backward, then buy

Start with the end goal and work backward: define the outcome, map the process, clean the foundation, name the owner, and only then pick the tool. If the tool turns out to be Clay, great. The new agents will make your owner much more productive.

They just won't replace your owner.