Clay: powerful, and priced in two currencies you have to watch

Clay is the strongest tool on the market for building and enriching a target list, and it is genuinely different from what came before: instead of buying one provider’s data, you chain several and take the first good answer. That approach is called waterfall enrichment, and it is why coverage on DACH contacts is meaningfully better than any single source.

It is also the tool whose bill most reliably surprises people, and that is a design consequence rather than a pricing trick. This review covers what it does, what it costs in practice, and the two things to settle before it touches real data.

What it actually does

A Clay table is a spreadsheet where each column can be a lookup, an API call, or a model prompt. You start with a list of companies or people, then add columns: find the domain, find the head of operations, check whether they use a particular tool, check for recent hiring, write a first line.

The waterfall is the core idea. A single column can try provider A, then B, then C, until one returns an answer. For German mid-market contacts, where any individual provider has patchy coverage, that is the difference between a usable list and a mostly empty one.

The second thing it does well is that a table is a workspace rather than a pipeline. You can look at a hundred rows, see what the enrichment returned, and change your mind. That sounds minor and is the reason people build things in Clay that they would never finish in code.

What it costs

The current plans are Free, Launch at $185/month, Growth at $495/month, and Enterprise on quote. Annual billing brings Launch to about $167 and Growth to about $446. Legacy plans (Starter $149, Explorer $349, Pro $800) remain available to existing customers only, until 10 April 2026.

Since March 2026, Clay bills in two currencies: Data Credits for marketplace enrichments and Actions for workflow operations. Failed lookups are no longer charged.

Clay pricing, checked July 2026

The two-currency split is the thing to understand before signing. A row that runs a full waterfall consumes roughly 10 to 25 Data Credits, depending on how many providers it has to try. The Launch plan includes 2,500 Data Credits and 15,000 Actions per month, which sounds generous until you divide: at 15 credits a row, that is around 165 fully enriched rows a month.

That maths is why reported real-world spend sits between $500 and $2,000+ a month for active go-to-market teams, well above the plan price, and why a 25-seat deployment lands in the $75,000 to $120,000 a year range once third-party data is counted. Enterprise agreements are reported between $12,000 and $154,000 a year.

None of that makes Clay expensive for what it does. It makes it a tool whose cost is a function of usage rather than of headcount, which is a different budgeting exercise and one that finance teams consistently get wrong on the first pass.

The verification list

Run the credit maths before the trial ends. Take your actual target list size, multiply by 15 credits, and compare against the plan. Do it for the monthly refresh too, not just the initial build: a list is not a one-time purchase, because B2B contact data decays at over 22 % a yearDE (auf Deutsch).

Decide what happens to the data afterwards. Clay is where the enrichment happens; your CRM is where the record lives. Teams that skip this end up with the truth in a Clay table that three people can see, which is a worse outcome than the spreadsheet it replaced.

Settle the Article 14 duty. This is the one that gets skipped. Enrichment means obtaining personal data from somewhere other than the person themselves, which triggers an information duty under Article 14 GDPR, at the latest with your first communication. That is a workflow decision, not a legal footnote, and it belongs in the sequence design.

And keep UWG separate from GDPR. Having lawfully enriched a contact says nothing about whether you may email them. In Germany § 7 UWG requires prior express consent for advertising email, with no general B2B exemption. We wrote that up in full for DACH outbound, and it is the single most common misunderstanding among teams who buy this category of tool.

Where it is the wrong tool

For a list you build once. If you need 300 companies enriched and then nothing for six months, the subscription is the wrong shape. Do it in the trial or pay a freelancer for a day.

For an automation that runs continuously. Clay is excellent at building the logic and less suited to being the thing that runs it forever. The pattern that works is: design and validate the screening logic in Clay, then move the recurring part into your orchestration layer once it is stable. That is the shape we use for a screening pipeline.

When the constraint is not data. A team that already has more qualified accounts than it can contact does not have an enrichment problem. Buying Clay in that situation produces a better list and the same number of conversations.

What we would actually use it for

Screening, not sending. Clay’s real strength is answering “which of these 2,000 companies are actually worth a person’s time” with criteria that no CRM filter can express: do they run this tool, did they post that role, does their site say this thing.

That output is a short list with reasons attached. What happens next belongs somewhere else: in the CRM, in the sequencing tool, in a chain someone owns. Keeping that boundary is what stops Clay from becoming a second CRM that nobody maintains.

Frequently asked questions