The blog · GTM Systems · 7 min
What did Clay Sculpt change for GTM teams and solutions partners?
Clay launched an agent-first way to build, Workflows and an Inbound SDR Agent, with marketing as its new buyer. The operator matters more; the partner question stays open.

Clay launched 13 new features at Sculpt 2026, and three of them show where the product is going: an agent-first way to build, Workflows, and an Inbound SDR Agent. Together they move Clay toward what it calls a self-learning revenue engine, with marketing as its new buyer. For GTM teams, that confirms a direction the market was already taking: the tool matters less each year, and the operator and the system around it matter more. For solutions partners, the place in Clay's next chapter is still open, and what Clay does over the next year will settle it, not what anyone said on stage.
What did Clay launch at Sculpt 2026?
Clay launched 13 new features at Sculpt in San Francisco on October 8, 2026, the day after its Partners Day, in front of 2,000 attendees. Three of them carry the story. Source: Clay, Sculpt recap: Building the self-learning revenue engine, 2026
| Launch | What it does | Status at Sculpt |
|---|---|---|
| An agent-first way to build | You give Clay an outcome, such as a campaign into ICP contacts at high-intent health tech companies. An agent plans and runs it using Knowledge Hub, Clay's living record of your ICP, personas and positioning, then recommends changes from the results | Available to Sculpt attendees, rolling out through early access |
| Workflows | A visual canvas where every step can branch, loop, run code or call an agent. Plays can be described in natural language, traced record by record and run across millions of records, with results written back to Audiences, Clay's data layer | In beta for all Clay users |
| Inbound SDR Agent | Clay's first agentic seller. Qualifies inbound leads in a voice conversation, demos the product in a sandbox, and learns from the call recordings of your best sellers | A preview, with a waitlist for pre-beta partners |
What does a self-learning revenue engine mean for GTM teams?
A self-learning revenue engine, in Clay's framing at Sculpt, is a system where executing campaigns is the easy part and the edge comes from how fast a team learns from its results. We agree, and it matches how we already work with marketing teams. The Demand Compass is our two-axis read of a market: every account scored on Brand Awareness and Readiness to Buy, which gives four quadrants (Cold, Nurture, In-Market and Sales-Ready) and one move for each. We map a team's market first, then track those accounts, and the people inside them, on both axes, with an activation layer on top that acts at every stage of the buying journey.
The learning loop is familiar too. Every week, DemandCompass measures which signals preceded real conversations and proposes a change to the weights, and nothing is applied until a person approves it. Clay describes the same pattern for Knowledge Hub: learn, propose, accept.
Why is marketing Clay's new buyer, and what changes?
Marketing is Clay's new buyer because, at Sculpt, the focus moved from the person who builds (the operator, the GTM engineer, the founder with a free afternoon) to the marketing team, and Clay now has a whole team built around it, Clay for Marketing. A marketing team buys an outcome, not a canvas. That changes what has to sit around the product: someone to deploy it, someone to run it, someone to answer for it every Monday.
A marketing team buys an outcome, not a canvas.
It is the gap we hear from the marketing leaders we work with. One said it on a call, and many have said it since: "I've done this a million times. I know what great looks like. The frustration is I can't execute it alone." We built our offer around that sentence, so seeing Clay arrive at the same buyer read as validation of a bet we had already made.
Is Clay becoming a product with a forward deployed team?
A forward deployed model pairs a product with a team that implements and operates it inside the customer's own environment, and from where we sat at Sculpt, that is the direction Clay is taking. Many of the people Clay has hired are GTM engineers, and the shape looks like software plus people who deploy it inside the customer.
It is the model we run at a smaller scale: DemandCompass is the product, we operate it, and Clay runs inside it. Two companies of very different size landing on the same shape is not a coincidence. Software alone leaves the client to run it, and a team alone leaves campaigns that stop when the retainer does.
What does growing up mean for a company moving this fast?
Growing up, for a company like Clay, means keeping its pace of change while carrying more customers, partners and roadmap with every decision. Clay today is a different product from the one shown at the first Sculpt, and it deserves credit for changing that much. A lean team can change its mind on a Tuesday. A larger company carries everyone along with every change. Size does not decide this either way; it makes speed a deliberate choice instead of a default, and Clay will have to keep choosing it.
If operators can build these systems themselves, what is the tool for?
Experienced GTM operators can now build comparable systems on other stacks or in-house, and that is the tooling market maturing, not a verdict on any one product. Clay is still excellent at what it does best: the enrichment waterfall, the breadth of data providers, and building a workflow fast.
What a tool does not settle is who runs it and what the system remembers. Clay is software you operate. What we found building DemandCompass is that the hard part comes after enrichment: knowing what changed since last Monday, letting old evidence expire under the Decay Rule, and not depending on one person's memory of how it all works, the single point of failure. In one of our deployments, 829 signals were captured in a quarter, 150 reached a person, and 82 percent were filtered out on purpose. That layer is where we put our work, and Clay is an ingredient in it. Source: automate rev.ops., The Demand Compass, chapter 18
So the question for any team is whether to build, buy software, or adopt a product with a deployed team on top. All three are legitimate.
| Option | What you get | It fits when |
|---|---|---|
| Build in-house | The system, and the job of running it | You have an operator you intend to keep |
| Buy software | A tool your team operates | Someone on the team has the hours to be the system every week |
| A product with a deployed team | The system running in your own stack, with people who operate it | You need it working before you can hire for it |
Where do solutions partners fit in Clay's next chapter?
Solutions partners do not yet know their place in Clay's next chapter, and what Clay does over the next year will settle it. Clay has said it will look after its partners as its focus shifts toward larger customers, and we take that at face value. What we do not have yet is a measure to hold it against, so these are the three things we will be watching:
- A partner path into larger accounts.
- A shared view of the roadmap.
- A way for partner-built systems to count.
We do not know how this plays out, and we would rather say that than guess. Clay created this category, and the partners who grew with it helped build it. The market is big enough for all of us, and B2B companies need help turning new tooling into revenue. For now, the honest takeaway for partners is: we will see.
Related questions
Should a marketing team adopt Clay's agent-first way to build now?
It is available to Sculpt attendees and rolling out through early access, so most teams will reach it over the coming months. Decide first who reviews what the agent recommends each week, because the learning only pays off when someone accepts or rejects the changes.
Is automate rev.ops. a Clay partner?
Yes. We are a Clay Solutions Partner, and Clay runs inside the systems we build and operate for clients, alongside DemandCompass.
What is a forward deployed team?
A team that implements and operates a product inside the customer's own environment, instead of handing over software and leaving. The system keeps working when one person is out.

