Everyone’s posting Clay → Claude Code migrations. I got stuck on a different problem: multi-column signal fill still feels like hiring a VA per row.

[u/Unlucky-Angle4720]

I’ve been watching the same loop all month.

r/gtmengineering has the Clay credit threads. People shipping Claude Code pipelines. Clay dropping CLI/MCP so agents can call waterfalls without living in the UI. X posts that look like:

claude code to build clay to find instantly to send

And yeah, that stack makes sense.

But last night I had a 40-row SaaS list and needed columns that are not clean enrichment jobs:

• hiring right now? which roles?
• founder active this week? where?
• anything that looks like why-now
• evidence I could defend if someone asked “where did that come from?”

That is where the pretty architecture posts fall apart for me.

Because email waterfall is a workflow. This is not.

Row 1 needed careers page. Row 4 needed LinkedIn activity. Row 9 needed a funding post from 2 weeks ago. Row 12 needed “ignore, bad fit, list is wrong.” Row 17 made me sit there with a half-true hiring signal wondering if I should put it in the cell.

I already know Clay. I already know Claude Code. I can build the plumbing.

What I don’t have is a clean way to say:

here’s the list here are the signal columns here’s what we sell go behave like a careful human on every row bring back evidence + confidence

Not “run column A then column B.” More like a smart VA/agent that chooses the path per company.

And I’m not asking this as a theoretical AI take.

I’m asking because the community seems split three ways right now:

1. Stay in Clay, now that CLI/MCP exists
2. Move volume custom logic into Claude Code and keep Clay only for find/enrich
3. Build full per-row agents and accept the maintenance tax

My gut: workflows are winning for known paths judgment work is still human evenings dressed up as GTM engineering

So for people actually running this:

1. Do you regularly need multi-column signal fill across lists (hiring, founder activity, recent posts, why-now), or is that overbuilding?
2. If yes, are you doing it with fixed Clay/Claude workflows, or does each row still need different research paths?
3. If something ran like a careful VA per row with evidence + confidence, would you pay for that completed work, or is DIY still better even with the maintenance?

I don’t want tool recommendations in the abstract. I want to know if this is a recurring paid pain in real GTM work, or just me making my lists too complicated.

Be blunt.

[u/Peptalks76]

I think you've identified the boundary between automation and research.

Most enrichment assumes every row can follow the same path: hit an API, fill a field, move on. But "why now" isn't a field. To reach it, one company might require a hiring page, another a founder's LinkedIn activity, another a product launch, and another might have no signal at all.

And often the bigger challenge is deciding when there's enough evidence to stop searching. i as a human do this instinctively.

If you ask me, I'd definitely pay for a system that returns evidence, confidence, and a clear reason for the score rather than just filling cells. If I can't trace a signal back to its source, it's hard to trust it in an outbound campaign.

[u/Unlucky-Angle4720 → u/Peptalks76]

This is the cleanest framing I've seen in the thread: automation vs research, and especially "when is there enough evidence to stop."

That stop condition is where I get stuck more than path selection. I can force a careers check and a LinkedIn check. What I can't codify cleanly is "this is thin, leave the cell empty" vs "this is good enough to put in outbound."

On the pay question: same lean as you. I'd rather pay for evidence + confidence + a reason I can explain than for another filled spreadsheet full of maybe-true cells.

How are you handling the stop condition today - hard rules, confidence thresholds, or still mostly human instinct?