Discussion

Search code, repositories, users, issues, pull requests...

dandaka: Can my agents (powered by NanoClaw or Claude Code) use the CRM without installing OpenClaw codebase?

kumar_abhirup: This is an OpenClaw framework, so it installs / relies on your existing OpenClaw codebase. I think there has been a ton of requests on Claude Code support, someone has been working on a PR for exactly this, I'll update you here if it ships.

bluepeter: > sales automation, lead enrichment, biz dev, [...] linkedin outreach,Sigh.

kumar_abhirup: It also does all or most knowledge work there is, the goal is for it to be smartly be able to do anything you ever do on your machine.

auvira_systems: Love the choice of DuckDB for the local storage layer;it's incredibly underrated for building high-performance, analytical client-side apps. I’m doing something similar with IndexedDB for a financial IDE (AccIQ), and the everything is a file/local approach is the only way to get that sub-10ms "IDE feel". How are you handling the memory footprint when DenchClaw starts ingesting larger HubSpot/Notion exports into the local DuckDB instance?

davexunit: Combining OpenClaw with sensitive personal data is a recipe for disaster.

shafyy: > It has a CRM focus because we asked a couple dozen hard-core OpenClaw users "what do you actually do", and it was sales automation, lead enrichment, biz dev, creating slides, linkedin outreach, email/notion/calendar stuff, and it's always painful to set up.Fuck me, it's going to get worse before it gets better, isn't it?

spiderfarmer: At what point does this become an AI powered spamming machine?

strongpigeon: One on hand, this is genuinely cool. On the other end, this is the final nail in cold outreach's coffin.

articsputnik: I just use plain-text files for my CRM in Obsidian [1]. Works great if you are a solo founder only.[1] https://www.ssp.sh/brain/managing-my-business-with-obsidian/

dickiedyce: ... or disastrous comedy?

jadbox: That's a simple but useful set up, thanks for sharing.

ftkftk: In response maybe we should design TCPAclaw. It is specialized in honeypotting all of the random cold call spam, tracks down the source of unsolicited contacts; including registration state, legal contacts, and registered agent(s). It then drafts and sends a TCPA letter and waits for one of two things to happen: Either a $500-$1500 check arriving in your mailbox, or the demand deadline elapses. In case of demand deadline elapse, TCPAclaw files a small claims suit in the appropriate court of jurisdiction.Fight fire with fire.

dickiedyce: I'm in.

jadbox: That's... not a bad idea. The downside is the bot would be doing a lot of these and false-positives would be... embarrassing (like a real investor outreach).

dang: I've taken that bit out of the text above. See https://news.ycombinator.com/item?id=47314105 for more.

dang: I've taken that bit out of the text above - I originally advised Kumar to put it in there (it's actually from the opening of the demo video), but in hindsight, I should have known it would backfire with the HN audience.

kumar_abhirup: The way imports work in DenchClaw is a bit unconventional, when you tell it to "import my HubSpot", the agent literally opens your browser (using the copied Chrome profile), navigates to HubSpot, triggers the export, and then ingests the downloaded files into the workspace DuckDB. So the bottleneck isn't really a fat in-memory ETL... it's more like processing a CSV/JSON export file on disk.For the DuckDB side specifically: we shell out to the duckdb CLI binary for every query rather than embedding it in the Node process. So each operation gets its own memory space and dies when it's done. the web server at localhost:3100 stays lean regardless of what you're ingesting. DuckDB's out-of-core execution also means it can handle datasets larger than available RAM natively, which is one of the reasons we picked it over SQLite.For really large exports (think full HubSpot instance with 100k+ contacts), the practical limit is more about the browser export step than DuckDB. HubSpot itself chunks its exports, and we process those chunks as they land. The DuckDB insert is the fast part.Honestly for CRM-scale data, even a large sales org's full HubSpot, DuckDB eats it for breakfast. Where it would get interesting is if someone tries to throw analytics-scale data at it, but that's not really the use case. Would love to hear how IndexedDB holds up for you at scale in AccIQ, different trade-offs for sure.

iamacyborg: > The way imports work in DenchClaw is a bit unconventional, when you tell it to "import my HubSpot", the agent literally opens your browser (using the copied Chrome profile), navigates to HubSpot, triggers the export, and then ingests the downloaded files into the workspace DuckDB.What’s stopping the agent from doing literally any other thing in HubSpot? You know, small stuff like editing/deleting records, sensing emails, launching marketing campaigns, deleting reports, etc.

kumar_abhirup: Our HubSpot import seed skills have strong always on prompts for asking user before doing any action, and it knowing where to click. For actions faster than browser, the skill also knows how to use hubspot cli.Ideally for these pursposes, I would ALWAYS use Claude Opus 4.6 for this stuff, personally I have never seen it do unintended things to that extent.Also, when the browser opens you can supervise it doing the thing, since you can see what its doing, you can always stop it if it ever goes wrong.

jscottmiller: Become? I believe that’s the point.

operatingthetan: Cold calling is not 'spam' because it is essentially done by a human. This is no different than an email spam network. So now this will just become email / linkedin spam done by corporations? I guess we turn up the filters now?

richwater: Just because a human gets paid to sit at a computer calling random people doesn't absolve them of a spam title.

operatingthetan: I agree that it is spam of a sort, but I don't think that's how it's generally portrayed. If biz dev and sales are just spammers then we should reclassify them and shun those types of posts.

zikani_03: Nice, this seems interesting. I don't use Obsidian (I use Logseq) but this has given me a couple of ideas for a CRM I am building (it's currently in a Personal Relationship manager phase which I've found useful for about a year or two).Thanks for sharing.

jesse_dot_id: OpenClaw opens a wide attack surface on your digital life that cannot be remediated so long as hallucinations and prompt injection remain unsolved problems. Anything built on top of it is equally insecure and probably even more insecure.I really don't want to yuck anybody's yums or step on dev work that I had nothing to do with, because I've been there and I know it sucks, but OpenClaw is barely secure enough to even play with in a sandbox. Giving it private information about your real business and real business contacts feels like an absolutely insane thing to do.At best OpenClaw is like a toy... if the toy was a gun and it shot real bullets. This feels like playing Russian roulette with your livelihood.

olq_plo: Great, thanks for making me Google what CRM means in this context. Neither your post nor your website explains the acronym.

zachrip: This is a pretty widely known acronym

Lalabadie: Looking at that star graph: Since OpenClaw became a thing, I can't help but conclude that Github interest/popularity metrics have become useless signals.

jesse_dot_id: Especially considering this project is 2 days old and has 580 stars. 500 seems like it would be a nice round number if one were to purchase bot engagement. Not confident enough to make that claim directly, but something about this project doesn't sit right in general.

kumar_abhirup: Bruh it's not botted, the 500 stars came from Garry Tan's viral tweet.

kumar_abhirup: Sorry! It's basically a database for normies.

ancientcap: the crm isnt the hard part, the hard part is that most sales teams have a workflow problem disguised as a tooling problem. local first is smart but id focus on opinionated defaults for pipeline stages because thats where 90% of founders building their own crm get stuck, they model their process wrong then blame the software.