Re:Show HN: DenchClaw – Local CRM on Top of OpenClaw
by RovaAI on Tuesday March 10, 2026 @08:01AM
(#47322069)
The security concern people are raising is the right one, and I think it points to where the real value should sit in this stack.
One commenter said "the real time save is the agent pulling the right info from 5 different sources before a human writes anything" - that's exactly it. The enrichment layer upstream of the CRM is where agents can do the most good with the least risk, because it's read-only.
Giving an agent write access to your CRM + email + browser is a big trust leap. But having a script that ingests a list of company names and returns homepage, emails, phone, LinkedIn, HQ, and key contacts as a CSV - then you paste that into your CRM manually - sidesteps the whole problem. No credentials, no writes, no blast radius if something goes wrong.
The robotic email problem goes away too, because the human is still the one reviewing context and deciding what to say. The agent's job is to make sure that context is comprehensive before the human touches it.
One commenter said "the real time save is the agent pulling the right info from 5 different sources before a human writes anything" - that's exactly it. The enrichment layer upstream of the CRM is where agents can do the most good with the least risk, because it's read-only.
Giving an agent write access to your CRM + email + browser is a big trust leap. But having a script that ingests a list of company names and returns homepage, emails, phone, LinkedIn, HQ, and key contacts as a CSV - then you paste that into your CRM manually - sidesteps the whole problem. No credentials, no writes, no blast radius if something goes wrong.
The robotic email problem goes away too, because the human is still the one reviewing context and deciding what to say. The agent's job is to make sure that context is comprehensive before the human touches it.