I somewhat agree with this post, but for me, the real beauty of Clay is that I get immediate access to a heap of data providers without having to sign up for multiple accounts. In the Claude Code scenario I need to manage tons of providers and accounts. Add on to that workflows and tables that I can share across users vs. isolated enrichments running in the command line and there's still very much a case for Clay's "middleware" layer. That said, I do love me some Claude Code for enrichment 😂
The multi-provider access without managing separate accounts is one of Clay's strongest arguments, especially when you are running waterfalls across five or six providers and the orchestration complexity is real.
The case I am making is narrower than "replace Clay entirely." For founding teams doing targeted enrichment on 50 to 200 accounts a month with one or two providers, the direct MCP stack covers the job at a fraction of the cost. At that scale the shared tables and multi-user workflows are not the bottleneck.
The interesting question is what percentage of Clay's current user base genuinely needs that layer versus paying for it out of habit.
I somewhat agree with this post, but for me, the real beauty of Clay is that I get immediate access to a heap of data providers without having to sign up for multiple accounts. In the Claude Code scenario I need to manage tons of providers and accounts. Add on to that workflows and tables that I can share across users vs. isolated enrichments running in the command line and there's still very much a case for Clay's "middleware" layer. That said, I do love me some Claude Code for enrichment 😂
The multi-provider access without managing separate accounts is one of Clay's strongest arguments, especially when you are running waterfalls across five or six providers and the orchestration complexity is real.
The case I am making is narrower than "replace Clay entirely." For founding teams doing targeted enrichment on 50 to 200 accounts a month with one or two providers, the direct MCP stack covers the job at a fraction of the cost. At that scale the shared tables and multi-user workflows are not the bottleneck.
The interesting question is what percentage of Clay's current user base genuinely needs that layer versus paying for it out of habit.