I am launching Relaticle here next Tuesday. It is an open-source CRM where AI agents can do real work on your data, and I want feedback on one design decision before launch day.
Relaticle has two trust levels. External agents (Claude Desktop, Cursor, any MCP client) authenticate over OAuth and write through 37 tools directly, like an API client. The in-app assistant is stricter: every write it wants to make becomes a proposal card, and a person approves or skips it record by record before anything lands.
The question I keep going back and forth on: is per-record approval the right granularity, or does it become noise once you trust the assistant? Would you want a "trust this kind of change" switch, or does that defeat the point?
If you run a CRM with any AI in it today, I would like to hear where you draw that line. The whole thing is AGPL and self-hostable, including the model via Ollama, so you can look at how it works rather than take my word for it.
Relaticle
@manukminasyan as someone who deals with messy client data all day an AI that acts as a strict proposal engine is exactly what market need. congrats for launch🙌
Relaticle
@priya_kushwaha1 Thanks, Priya! Glad this resonates with someone working with client data every day.
@manukminasyan For sure.. keep up the great work with it
@manukminasyan Congratulations on the Product Hunt launch! Wishing Relaticle a fantastic launch and lots of success ahead.
Relaticle
@charan_t_m Thanks, Charan! Really appreciate the kind words.
@manukminasyan the two differents trust level for ai actions make a plenty of sense, that could make the setup much easier for team with their own CRM architecture.
what was the challenging chat issue you had to fix during the restructure?
@manukminasyan Approval - gated AI sounds great but who approves the approver ?
Mailwarm
Can you set rules so certain fields can be automatically written while others always require approval?
Relaticle
@naimz Not currently, Naim. The assistant can update your fields, but those changes still need approval. What workflow did you have in mind?
Relaticle
@naimz @solozero I like the idea of earning autonomy over time. I’d want people to choose what it can update on its own. Which updates would you trust it with first?
Honestly, this is the kind of CRM + AI approach that makes sense to me.
I like that the AI can actually do things instead of just generating text, but you still get to approve what changes before it touches your data.
And making the whole thing open-source + self-hostable is a huge plus. Nice work!!
Relaticle
@ilya_pashayan Thanks, Ilya! I wanted the assistant to do useful work while keeping the person using it in control. Glad that came through.
This project has a solid based of Laravel that have helped me learn Laravel. I learned so much about how to setup Laravel in a professional - enterprise grade setup which alone is gold. In combination with AI - MCP, it really can turn a basic CRM into a full-fledge internal processing system, ie: an ERP.
Wish alot of success for Manuk for the launch!
Relaticle
@laurnts Thank you, Laurentius! Hearing that the codebase helped you learn Laravel means a lot to me. Thanks for the launch support!
Would love an undo trail for approved writes, not just the approve step. Excited to see where this goes!
Relaticle
@colegawin Thanks, Cole! Being able to undo a change after approving it makes sense. Approval doesn’t mean you’ll never need to take it back. Appreciate the suggestion!
RunEvr
@manukminasyan Manuk jan, congrats on the launch!
It’s great to see a CRM that isn’t just adding AI on top, but is actually designed around AI from the ground up. And the MCP compatibility is really cool stuff!
Good luck =)
Relaticle
@adana Thanks, Adana jan! Glad the AI approach and MCP stood out to you. Really appreciate you being here for the launch!
37 tools over oauth for any mcp client, and the workspace custom fields land in each agent's schema on their own. do they refresh live or only on reconnect?
Relaticle
@niveditha_patluri1 No reconnect needed, Nivy. Field changes show up the next time the agent fetches the workspace schema.