Clay in 2026: The Complete Guide for B2B GTM Teams
•
Clay is a go-to-market development platform: it finds companies and people, enriches them with data from 200+ providers, runs AI research on top, and pushes the result into your CRM or outreach tools. In 2026 it is worth it if you have a real list, a defined ICP, and one person who owns it. It is not worth it if you have none of those.
The thing most guides still get wrong is what Clay has become. In July 2026 Clay rebuilt its own homepage around a new claim: it is no longer a data enrichment product, it is the infrastructure GTM engineers build systems on. That is not just marketing. Clay now ships a public API, a CLI, an agent plugin, and MCP, which means your Clay logic can run without anyone opening Clay. That shift changes how you should buy it, budget it, and staff it.
What the Clay app actually does
Strip away the positioning and Clay does four things.
It finds records, through a proprietary database of companies and people you query with filters or natural language. It enriches them with a waterfall, checking data providers in sequence so if the first vendor has no verified email, it falls through to the next until something lands, and you only pay for the lookup that succeeds. It researches them, using Claygent to read websites, filings, job boards and news the way an analyst would. And it acts, writing clean records back to your CRM, firing a Slack alert, loading a sequencer, or syncing an ad audience.
Clay frames this as five primitives: data, agents, orchestration, execution, and governance. The framing is useful because it tells you what Clay is actually competing on. Not data. Clay resells other people's data at a markup. It competes on the layer that decides which data to buy, when to buy it, and what to do with the answer.
The commercial results back the positioning. Clay crossed $100M ARR in December 2025 and Sacra estimates $150M by May 2026, against a $5 billion valuation set in a January tender. Along the way it invented a job title and then made it real: the go-to-market engineer.
The two ways to run Clay, and why it matters
Almost every article about Clay describes only one of them. Buying decisions get made badly because of it.
The UI path is the one everyone knows. Open a table, paste a list, add enrichment columns, write a Claygent prompt, export. It is fast, visual, and the right place to find out whether a play works at all.
The API path is new and is where the next two years are heading. Your logic lives as a routine that runs outside the interface, triggered by your backend, a queue worker, a nightly job, the CLI, or an AI agent. Clay shipped the API and CLI in July 2026, including an agent plugin that runs inside Claude Code, Codex, and Cursor.
The practical difference is durability. A table is a document someone owns and eventually stops maintaining. A routine is a definition your whole stack calls. When a provider changes a field, you fix one routine instead of hunting through forty tables for the one still running stale logic.
What teams are actually shipping on Clay this year
Clay's feature list moves fast enough that most published guides describe a product from eighteen months ago. These five are what changed in 2026, and each one is a real build rather than a feature bullet.
Ad audiences that exclude your own customers. This is the most under-covered thing Clay shipped and the one with the clearest number attached. Most B2B ad budget goes to people who cannot buy: existing customers, open opportunities, partners, agencies. Everyone knows to exclude them; almost nobody does, because it means exporting a CSV from the CRM every week and re-uploading it before it goes stale. Clay syncs those audiences continuously from your CRM to LinkedIn and Meta instead, and enriches contacts with personal emails first, which is what makes Meta usable for B2B at all. Clay's own growth team reports LinkedIn cost per lead falling from $250 to $25, Meta match rates going from roughly 30% to over 70%, and one Meta campaign producing 200 leads at $10 each in 24 hours.
Account research agents over your renewal or closed-lost book. Opened to beta in July 2026, these are always-on agents that run across every account in a segment, reading CRM fields, Gong call transcripts and signals together, and writing structured fields back with the reasoning attached. The difference from a Claygent in a table matters: an account research agent holds memory per account, so intelligence compounds across runs instead of resetting. Point one at your closed-lost list and it tells you which accounts are worth re-opening, and keeps telling you as new signals land.
Reps calling ops-built logic from inside Claude or ChatGPT. Ops builds a function once. Reps then invoke it in plain language from the AI tool they already have open, with no Clay training at all. Clay ships this as MCP for Reps and runs it internally. It quietly solves the oldest complaint about Clay, that it is a tool reps cannot use, without retraining anyone.
A backend that calls Clay instead of a table that waits. Once your logic is a function, your own systems trigger it. A form submission, a trial signup, a support ticket, a webhook from your product, all can fire a Clay routine and get structured data back, with an optional webhook so Clay notifies you when the run finishes rather than you polling for it. The trigger lives where the event actually happens.
Whole-CRM runs that never touch a 50,000-row table. For anything large, you upload your inputs as a JSONL file and start a batch run against a function. No splitting a 120,000-contact database across three tables and keeping them in sync forever. This is the single biggest practical reason the API path exists.
Notice the pattern in four of those five. The trigger does not live in Clay. It lives in your CRM, your product, your ad platform, or a rep's chat window. That is the argument for building on routines in one sentence.
Routines: how you actually call Clay from outside
Routines are the umbrella for programmable Clay logic. There are three kinds, and the difference is only ever about where you build them.
Routine type | Where you build it | Status |
|---|---|---|
Clay-managed functions | Clay provides them | Available |
Custom functions | Clay UI | Available |
Workflows | Plugin or CLI | Alpha |
Clay-managed functions are Clay's own prebuilt jobs: work email, phone, job title, domain, employee count, revenue, tech stack, job openings, funding news. Use them for anything standard so nobody rebuilds what Clay already ships.
Custom functions are your logic, built once in the Clay UI and then exposed to everything else. Getting one callable is a five-minute job: open the function, enable API or MCP access in its details, copy the t_ id, and call it with function: in front. From there a backend service, a queue worker, an internal tool, or an agent all hit the same definition.
Workflows are the Alpha one, and the most interesting. You build them from the plugin or CLI rather than the UI, which means you can describe a multi-step play in plain language inside Claude Code and have the graph built, validated, test-run and inspected step by step. They hold agent nodes for reasoning, enrich nodes for Clay actions, and code nodes for deterministic logic. Clay's docs are explicit that Workflows avoid the 50,000-row limit that constrains tables. Being Alpha, treat them as the direction of travel rather than production infrastructure today.
The row limit is the honest reason a buyer should care about any of this. A Clay table caps at 50,000 rows on both Launch and Growth. Above that, you are either splitting tables by hand or you are on the API path.
Audiences, and where your data lives
One more layer worth understanding before you price anything. Audiences is Clay's persistent data layer: rather than a sprawl of tables, you hold your CRM and warehouse as two live lists, All People and All Companies, with one continuously updated profile per contact and account. Segments are live queries over that, so records join and leave on their own as they start or stop matching.
Two details that change plans and budgets, and that most guides miss. Sync cadence is tiered, with Enterprise refreshing every 15 minutes and Growth refreshing daily. And account research agents require Audiences to be set up first, with at least one source connected, so the agent story and the Audiences story are the same purchasing decision.
What Clay actually costs
Clay publishes four tiers: a free plan, Launch at $185 a month, Growth at $495 a month, and custom Enterprise pricing. Annual billing saves around 10%, taking Launch to $167. There is a 14-day trial with 1,000 data credits.
Since March 2026 Clay meters two things separately. Data credits buy data and AI from third-party vendors and cost a few pennies each. Actions measure orchestration, one per enrichment or execution task, at a few tenths of a penny. Clay says 90% of customers never hit their actions limit, so data credits are the number that decides your bill.
Here is the calculation nobody puts in writing. Clay's docs state a fully enriched record, meaning company and person profile plus email, phone and custom AI research, typically costs 6 to 20 data credits. Run that against the included allowances.
Plan | Monthly price | Credits included | Fully enriched records that buys |
|---|---|---|---|
Launch | $185 | 2,500 | ~125 to 415 |
Growth | $495 | 6,000 | ~300 to 1,000 |
Enterprise | Custom | 100,000+ | ~5,000 to 16,600+ |
Now compare that to how Clay positions the same plans. Growth is sold for teams enriching 1,000 to 10,000 records a month, but its included credits cover 1,000 records only in the best case, where you are bringing your own provider API keys and skipping phone numbers. Hit the top of that band and you need 60,000 credits, ten times what the sticker price includes.
This is not a gotcha. Clay lets you scale credits within a plan, up to 100,000 a month on Growth, and the March repricing cut data costs 50 to 90%. The point is that the list price is the floor, not the bill. Budget from your record volume and your credits-per-record, not from the pricing page. One-off credits bought mid-cycle carry a 30% premium, so the estimate is worth getting right the first time.
If you are planning a large sourcing build, one more number matters: Clay caps search results by plan, at 1,000,000 results a year on paid plans and 10,000,000 on Enterprise. A 50,000-account TAM build spends about 5% of a paid annual allowance.
Where Clay stops being worth it
Five situations. In every one, the answer is not "use Clay anyway."
Nobody owns it. This is the real failure mode and it shows up in the reviews. Clay holds 4.6 out of 5 across 226 G2 reviews, and the single most cited complaint, in 16 of them, is the steep learning curve. It is also the question practitioners keep relitigating in r/sales, which is worth reading before you buy. Clay rewards someone who treats go-to-market as a systems problem. Without that person you get a subscription and a folder of half-finished tables.
Your ICP is not settled. Clay makes it cheap to enrich the wrong accounts at volume. Pre-product-market-fit, that is an expensive way to stay confused. Fix targeting first, then automate it.
You need a rep-facing surface. Clay is not a CRM and reps should not live in it. MCP for Reps closes most of this gap by putting Clay behind the AI tools they already use, but the record still has to land somewhere reps actually work.
Your data model is broken. Clay enriches records. It does not fix a CRM whose objects, stages and fields do not match how you sell. Enriching a bad schema faster produces bad data faster, which is why we get the CRM data model right before wiring Clay into it.
You need a fixed, predictable line item. Usage billing is a feature when volume is deliberate and a liability when it is not. Guardrails fix it: per-table credit budgets, quality gates, conditional runs, dedupe before spend. But every one of those is a build decision, not a default you get for signing up.
None of these say Clay is the wrong tool. They say Clay rewards deliberate design and punishes drift, which is why the teams that do well with it put a named owner on it before they scale spend.
Who Clay is right for in 2026
Your situation | Verdict |
|---|---|
Under 500 accounts, static list | Free plan, revisit when the list moves |
Real ICP, nobody assigned to own it | Fix the owner problem first |
Growing outbound, one owner in place | Launch, then Growth |
CRM over 50,000 records | Growth with Audiences |
Triggers live in your product or agents | Build on functions and the API |
Regulated data, strict governance | Enterprise, with a compliance review |
The teams pulling ahead right now are not the ones with the most tables. They are the ones whose logic runs as reusable routines that their CRM, their backend and their AI agents all call. That is what "built like software" means, and it is plainly where Clay itself is heading.
Two things this guide deliberately does not cover. If you are weighing whether to build it yourself or bring someone in, that is a different question with a different answer, and it is worth reading what a Clay consultant actually builds before you decide. And if Clay is going to feed a CRM you are still choosing or rebuilding, start with the Attio and Clay integration, because the sync design constrains everything upstream of it.
Frequently asked questions
What is Clay used for?
Clay is used to find target accounts and contacts, enrich them with data from 200+ providers, run AI research on them, and push clean records into a CRM or outreach tool. B2B teams use it for TAM sourcing, inbound enrichment and routing, CRM hygiene, signal-based outbound, ad audiences, and account scoring.
How does Clay work?
You start with a list, either imported or found through Clay's database. Enrichment runs as a waterfall, checking providers in sequence until one returns a verified result, so you only pay for the lookups that land. AI research fills anything a provider cannot. The enriched record then syncs to your CRM or triggers an action.
How much does Clay cost?
Clay offers a free plan, Launch at $185 a month, Growth at $495 a month, and custom Enterprise pricing, with roughly 10% off for annual billing. Data credits are the variable cost. A fully enriched record typically consumes 6 to 20 credits, so budget from your monthly record volume rather than the list price.
Is Clay worth it for a small team?
Yes, if you have a defined ICP, a list that changes, and one person who owns the build. No, if you are pre-product-market-fit or working a few hundred static accounts. Small teams also cite cost as a real constraint on G2, so start on the free plan and prove one play before upgrading.
Does Clay have an API?
Yes. Clay shipped a public API, a CLI, and an agent plugin in July 2026. You can run Clay-managed functions and your own custom functions from backend services, queue workers, and AI agents, including batch runs over uploaded JSONL files. Workflows, built entirely from the CLI or plugin, are in Alpha.
What are the best Clay alternatives?
Apollo and ZoomInfo are the usual comparisons, but they solve a different problem: they sell you a database, while Clay sells you the orchestration layer on top of many databases. If you want verified first-party data with a rep-friendly interface, look at those. If you want programmable logic across providers, that is Clay's ground.
Sparsh Gupta, Founder of Automation Jinn and an Official Attio Expert Partner, builds AI-native go-to-market systems for seed to Series B B2B SaaS teams, from CRM architecture to the Clay routines and AI agents running on top. If you want your Clay build to survive past the demo and the credit audit, book a discovery call.
