Using Clay for recruiting

Clay is a sales enrichment and automation tool, and it is a good one. Recruiters started using it because nothing in hiring gave them the same control over lists and messages. It works, up to the point where hiring stops being a list problem.

Start for free Book a demo

$100 of credits on us. No card required.

The short answer

That was a reasonable move. Sales tooling was five years ahead on lists, enrichment and outreach.

Built forHiring: candidates, evaluation, coordination

Finding peopleBuilds the list from my own index of the open web

Judging peopleDeterministic scoring against your bar, evidence attached

The difference in one table

	Clay	Laidback
Built for	Go to market: leads, enrichment, sequences	Hiring: candidates, evaluation, coordination
Finding people	Enriches a list you supply	Builds the list from my own index of the open web
Judging people	Formulas and prompts you write	Deterministic scoring against your bar, evidence attached
Setup	Tables, waterfalls and credits per role	One sentence in a channel
Sending	Automated sequences	Drafted by me, approved and sent by a human
After the reply	Out of scope	Scheduling, panel chasing and ATS updates

Three places a Clay recruiting stack runs out

You can only enrich who you can already see

The list still starts from a profile database, so you get the same people everyone else gets, with better data attached.

Every role is a rebuild

The table, the waterfall and the prompts are tuned to one search. The next role is another week of setup, usually by the one person who understands it.

Nothing owns the middle

Replies, scheduling, panel chasing and pipeline updates land back on a human, which is where most of the hours actually go.

Where Clay still wins

If you want total control over data operations, or you run recruiting and sales prospecting from one system, Clay is genuinely powerful and I am not trying to be that.

#hiring-ops

Weronika

We built a whole Clay table for sourcing. It took a week to set up.

Laidback

And it will need rebuilding for the next role, because the enrichment waterfall was tuned to this one.

Laidback

The deeper issue is the input. Clay enriches people you already found. It cannot find the engineer whose evidence is a repository and no profile.

Enrichment is not discovery

What people ask when they already run Clay

Can we keep Clay for sales and use you for hiring?

Yes, and most teams do. They are different jobs. Nothing here asks you to change your go to market stack.

We already built the tables. Is that wasted?

No. Keep them running while you test me on one role, then compare who each approach actually found and who replied.

Where does your candidate data come from?

My own index of the open web: repositories, portfolios, publications, personal sites, company writing and talks, plus the candidates already sitting in your ATS. Profiles are built from what people ship rather than from a licensed snapshot every vendor buys.

Do we have to rip anything out to try you?

No. Keep your current stack, give me one open role and compare the shortlists. I sit on top of your ATS rather than replacing it.

It still treats a person as a record to enrich. Hiring needs a judgement about whether someone can do a job, made the same way twice, with the reasoning shown.

On the independent people search benchmark I score 97.80 out of 100. The method and every scored query are published on the benchmark page.

Built-in taste, not a general model pointed at hiring

Anyone can wire a model to a search box. What makes me good at this is the recruiting judgement, skills, workflows and memory that arrive with me on day one.

I read potential, not keywords

Titles lie and stacks change. I look at what someone shipped, who they shipped it with, and how fast they grew into the work.

Every call comes with its evidence

You get the commit, the talk, the customer they carried, the line in the release notes. If I cannot show why, I do not claim it.

The same rubric, every candidate

Your bar becomes a written rubric I apply the same way on Monday and on Friday, so a shortlist is comparable instead of moody.

You can argue with me

Disagree with a score and I show the reasoning behind it, then carry your correction into the next batch.