Last week was my last week at Clay. I am so proud, and a little surprised, at how far the spreadsheet outbounding tool I started using 4 years ago has come. Clay is now the default AI GTM platform, the category leader and category creator for GTM Engineering, and used by the biggest companies in the world to build more automated and nimble GTM motions. It’s 40X bigger by revenue, 30X bigger by valuation and 20X bigger by employee count than when I joined 2.5 years ago. And just like I joined coming from a Clay customer, I am leaving and going back to a Clay customer. I’m very excited to use Clay in a large production environment. I expect to develop new techniques for growth and push GTM Engineering further into the frontier. Along the way, I’ll certainly be posting (or at least replying “for sure” on everybody’s posts). To my fellow Claymates: thank you all for everything. You mean the world to me. Ay keep Clay creative✌️
Everett Berry
GTM Leadership at Anthropic · 2mo ago
I'm the Head of GTM Engineering at Clay. Here's every tool in our GTM tech stack for 2026: what we're building, what we're buying, and how we put it all together.
We’ve tried to be intentional about buying best in class tools but building where we can get a unique advantage by doing so. I’ve marked ⭐ on pieces of our stack that are either Clay or internally built.
We follow the “build on Clay” principle where we use Clay as infrastructure for many parts of our stack, but rely on end solutions for displaying data or providing interfaces.
Our two biggest investments are Terra (our rep command center) and Quartz (our pricing agent). Building these tools aligns with our principles because how our reps work and how we price are two highly unique areas where the internal context we have beats what a vendor could do.
But as you can see, the majority of our stack is bought - proof of the narrative violation that “we’re going to use AI to build everything internally”.
Marketing
- Inflection - lifecycle / campaigns / notifications
⭐ Clay Ads - ad audiences
- LinkedIn / Meta / Google - ad execution
- Webflow
- Ploy - website conversion
Prospecting
- LinkedIn Sales Nav - manual prospecting
- Exportly - Clay workflows in browser
- Gong Engage - sequencing / ops triggered sequences
⭐ Clay Sequencer - rep triggered sequences
⭐ Terra / Terra MCP (internal rep UI) - signals, 1P data, call prep, ROI calculator
Data
- Snowflake
- Fivetran
- Segment
⭐ Clay Audiences
Enrichment
⭐ Clay
A…
Everett Berry
GTM Leadership at Anthropic · 2mo ago
GTM Engineers - I spent 7 days building workflows with the Clay API and MCP. Here's what I built, what worked, what didn't, and step-by-step how to videos for you to build them yourself (bookmark this!!)
Day 1 - live building a prospecting workflow from Claude Code. A simple “resequencing” workflow, described with a prompt and built inside of Clay by Claude. https://lnkd.in/gB42r_zX
Day 2 - exploring every command in the API and how to turn the Clay UI you are used to into a programmatic infrastructure layer. https://lnkd.in/gcjVvvzw
Day 3 - field marketing with codex. Enriching event leads and asking about the data without ever seeing the data or Clay’s UI. https://lnkd.in/gnn6eSea
Day 4 - vibe coding a rep UI. Got a little cooked for having some stale data in here. Also kicked off a broader debate about whether companies should build custom UIs for themselves. My take? Companies are already doing this and will continue down this path. https://lnkd.in/gwpUHxtw
Day 5 - fix my vibe coded app. I didn’t tell Claude to validate the contacts. Rookie mistake but easily fixed. https://lnkd.in/gKMjHW2m
Day 6 - revops observability dashboard for an inbound router using the Clay API. Getting metadata and reporting from our API is slept on. https://lnkd.in/gacihfxZ
Day 7 - calendar inspection for sales leadership and leader tools using Clay MCP in ChatGPT. https://lnkd.in/gADPE8Sd
My overall takeaway is that GTM Engineers are very safe in their roles. Some mistakes I made large…
Everett Berry
GTM Leadership at Anthropic · 2mo ago
Christian over at UserGems 💎 just ROASTED me for the data being stale in my vibe coded rep UI demo yesterday. Very fair callout Christian, let’s talk about why this happened and fix it.
Firstly, I was more just trying to show that you can hit Clay APIs from a web frontend but obviously I should validate the data - after all what kind of GTM Engineer am I to just ship things without looking at 😉
So what happened? When I asked Claude to “find contacts” I gave no additional instructions to it. So it naively hit Clay’s people search endpoint to find anyone who ever worked at Ramp and list five people.
Oops.
Happily, since Christian and others are actually looking at what I built, we can just go back into Claude Code and fix this.
In fact in my video you can see exactly that. I’m telling Claude I got called out for this and asking it to 1) narrow the title search for revops and 2) validate that we are pulling current employees.
It identifies the problem in my code right away and then sets about adding contact validation to my workflow.
While this fix took about 10 minutes Christian makes an additional more subtle point: you shouldn’t build custom tools when you can rely on one solution to give you a rep UI and all the fresh data you need.
On this point my experience is just wildly different with customers that have very poor data and very custom needs but hey it's a big market.
There we go: my unexpected DAY 5 Clay API post. DAY 4 which got me in hot water linked below.
Everett Berry
GTM Leadership at Anthropic · 7w ago
The adoption of GTM Engineering in industries outside of tech is happening slowly but surely - inline with the adoption of modern demand gen practices.
