What is Clay, and how does it fit into GTM engineering?

Clay is a data enrichment and workflow tool for go-to-market teams. You work in a table where each row is a company or person, and each column can pull data from a provider, run an AI research step, score the row or draft a message. Clay's own site describes the product as infrastructure to get any data, run agentic workflows and launch GTM plays.

What is Clay used for?

Clay's homepage lists the jobs GTM teams build on it. The most common are:

• TAM sourcing, which means finding every account in your market in one place
• Enriching, scoring and routing inbound leads
• Scoring leads on intent and engagement signals
• Personalized outbound campaigns
• Keeping CRM records complete and current
• Turning target accounts into ad audiences
• Automating rep research, call prep and follow-ups

How does Clay work?

Three parts of the product do most of the work.

• Data marketplace. Clay says one contract gives you access to more than 200 data and AI vendors, so you don't need a separate account with each provider.
• Waterfall enrichment. Clay checks several providers in sequence until one returns a valid match. It's most often used for work emails and phone numbers, and Clay says you can waterfall any data point.
• Claygents. These are Clay's AI agents. A Claygent takes inputs, follows your instructions and writes a structured output, which suits web research and finding data no provider sells.

How does Clay fit into GTM engineering?

Clay's homepage says "GTM engineers build on Clay," and for many teams it's where a list gets built and enriched. If you're new to the term, start with what GTM engineering is and what a GTM engineer does.

Jordan Crawford describes the change in three eras on the Blueprint homepage.

1. The SDR era. Teams grew revenue by hiring more reps, buying a list and dialing.
2. The workflow era. A specialist ran Clay, enrichment APIs and multi-step workflows. Results improved, but one person and one tool became a single point of failure.
3. The current era. Teams can work with every internal and external data point about their customers and prospects. The hard part is knowing what to ask the AI to build.

Where Clay helps and where it doesn't

The tool is only as good as the question you point it at. Enriching a firmographic list with more firmographics doesn't change the outcome. Enriching it with data that shows a specific, current problem does. That's the idea behind a Pain-Qualified Segment.

Here's a simple example from the Blueprint homepage. A typical message to a crane rental company says "I help crane rental companies improve fleet utilization" and asks for 15 minutes. The message Blueprint builds names a specific crane with no DOT transit permit on file, points to a permit just filed to install wind turbines half a mile away, and offers an intro to the foreman. A Clay table can hold columns like those. Someone still has to decide that permits are the data worth looking for.

Jordan's experience with Clay

Jordan Crawford has advised Clay since 2021. He's listed in Clay's expert directory as a product expert, enterprise partner and educator, with expertise in GTM systems, signals and triggers, lead sourcing and local lead generation.

He also built AutoClaygent, a Claude Code tool and course that writes Claygent prompts, tests them against real data and scores the results until the output matches your judgment. Many of his current builds now run in Claude Code, and he publishes them as he goes in On the Edge.

His view is that Clay works best as one part of a system that starts from why your customers bought. Pick the problem first, find the data that proves it, then use Clay or Claude Code to build the list. You can see finished examples in the Blueprint Showcase.