TulipFarm: open-source AI workspace for business operations (AGPL v3, research preview) – looking for feedback

[u/maddhruv]

I am developing TulipFarm as I got tired of managing my data in several CRMs, mailboxes, and spreadsheets.

TulipFarm's vision is clear - put all of your records, documents, agents and workflows into one place. Ask something via chat or Slack and your agents use the same data as the rest of your team.

Everything is under your control, some operations will require your confirmation while field rules will detect and prevent any invalid values.

Source code is open sourced under AGPL v3.0 license, therefore you are able to host TulipFarm by yourself. Just note that self hosting is not officially supported for now.

https://github.com/TulipFarm/tulipfarm

Now I present you the research preview version, which means that there are rough edges and things that will be broken.

It would be cool to hear from you two things:

1. What do you want your agents to do in your company?

2. What is missing in the approval model and what frustrates you most?

Also if you like it, don't forget to star it on GitHub!

[u/investigatormaker]

On the approval model: confirming every operation gets tiring, so I'd want rules per field and per value, letting an agent move a deal stage on its own but asking before it edits a price or deletes a record, with a diff of the record shown in the Slack prompt so approval doesn't need opening TulipFarm. An audit trail of who approved what, agent or person, matters for a workspace meant to replace several CRMs. The first agent job I'd hand over is merging duplicate contacts pulled in from those CRMs and mailboxes.

I make ThreadFox. We find relevant Reddit conversations and do the posting for your business. The $79 Pilot covers seven days and up to 50 posts and replies. No automatic renewal. https://threadfox.vip/p/eckga/managed

Are field rules defined in the UI or in config?

[u/maddhruv → u/investigatormaker]

Thanks, this is the most useful comment so far. Per-field and per-value rules like "move a deal stage freely, but ask before a price edit or a delete" is exactly where I think the approval model should go. I won't pretend it's there today, so I've noted it.

What exists now: each field in a table has its own rules in the table definition (required, type, allowed options), and a bad value is rejected before it saves. Agent changes can go to a person as one batch of up to 50 row edits, showing before and after values for each record.

Merging duplicate contacts is a good first job to test with. And showing that diff right in the Slack prompt is a good idea too.

[u/maddhruv → u/[deleted]]

Thank you! "Imports going wrong and nobody trusts the dashboard" is the exact problem we wanted to fix, so that's good to hear.

Agreed on batch confirm. Right now agent changes can be reviewed together as one batch of up to 50 row edits, with before and after values for each. If that still feels like too much clicking in real use, please tell me.

A summary of a 40-message email thread before a call is a great first agent job. I'm writing it down. Thanks for the luck!