Earlier quoted context omitted.
Sure! We want to build something flexible where users can define their own custom objects and fields. We were thinking about leveraging Hasura that's already providing a flexible graphql API based on metadata which is exactly what we need / will need to build in the future. However, there are three reasons that pushed us to go through a different way: 1) We want to build a cloud version which is multitenant (I person…
The multitenant sharing of one large table with uuid seems rather crazy.
Launch HN: Twenty.com (YC S23) – Open-source CRM
171–180 of 317 posts
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#172Earlier quoted context omitted.
Sure! We want to build something flexible where users can define their own custom objects and fields. We were thinking about leveraging Hasura that's already providing a flexible graphql API based on metadata which is exactly what we need / will need to build in the future. However, there are three reasons that pushed us to go through a different way: 1) We want to build a cloud version which is multitenant (I person…
The multitenant sharing of one large table with uuid seems rather crazy.
I might be missing your point and I'm far from being a database expert. Would you give me more details about what challenge you have in mind?
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#173This looks very promising. Excited to see how Twenty develops over the next years! I think they key is to nail the data model and make sure replicating stuff from people's products and matching it with outside conversations (email, phone etc..) works smoothly
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#174Looks interesting, i think i'll give it a try. BTW your Github readme says: A CRM that ban self-hosted for free, on your own network and close to your data sources. You might want to correct that one :)
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#175Earlier quoted context omitted.
Sure! We want to build something flexible where users can define their own custom objects and fields. We were thinking about leveraging Hasura that's already providing a flexible graphql API based on metadata which is exactly what we need / will need to build in the future. However, there are three reasons that pushed us to go through a different way: 1) We want to build a cloud version which is multitenant (I person…
Ah, yep that makes complete sense if you want to per-tenant schemas. My app is multi-tenant but all have the same schema. We use a customer_id column that's matched against the JWT's customer_id token to ensure that no data is shared inadvertently by a dev missing adding a WHERE clause. Thanks for the SF link, that's quite interesting. It seems bonkers to me to throw away all the advantages of the RDMS but you can't…
> Interesting, I will look into that, thank you!
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#176We are currently evaluating CRM packages. This is probably a bit too in development for me to recommend but I'll let you know our internal requirements so you have one extra data point in the market. Phone integration is huge for us. We need the CRM to respond to an incoming call by bringing up the contacts details if it recognises the number. We also need a log that the cal began, was answered by, and how long it la…
You should evaluate close.com if not already. They have all the features you mentioned. We use them for sales for our business.
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#177Interesting how you choose typescript?
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#178Earlier quoted context omitted.
The question is why are they so successful in doing this. Why do organizations by default use Salesforce. I have never used nor worked at an organization that is built on top of Salesforce. Just a regular web dev.
> I have never used nor worked at an organization that is built on top of Salesforce. You probably do. Salesforce has all kinds of different products from Slack to Mulesoft and Tableau. Salesforce starts their pipeline by solving one problem, making that work well from a business ROI perspective, and then they pitch you on another and another and another with package pricing. This is basically the Oracle model and ho…
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#179Before me, there was an attempt to migrate to Dynamics CRM but our current CRM we've being developing for 15 years has so many custom rules/quirks/etc. eventually they abandoned the attempt because of the huge scope and the difficulty to reimplement millions of lines of custom logic in a proprietary CRM.
Before I joined the team, the CRM's development didn't follow best practices and now it's very hard to maintain and update, due to architectural problems aka "big ball of mud". Another issue is that it was not designed to be extendable, every small rule the business comes up with is hardcoded in the code, and so there's no way to configure things somewhere in the UI with least amount code possible.
So if I was to migrate our CRM to an open source engine/core, the following is a list of things I would want to see:
1) good modular internal design/API so that it was possible to easily add custom complex logic/flows
2) design/API which is extendable and doesn't have hardcoded logic/doesn't assume your company's flows
3) allows to configure as much as possible from the UI
4) an ecosystem of plugins/some sort of marketplace, with, again, solid, standardized API
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#180Earlier quoted context omitted.
> I have never used nor worked at an organization that is built on top of Salesforce. You probably do. Salesforce has all kinds of different products from Slack to Mulesoft and Tableau. Salesforce starts their pipeline by solving one problem, making that work well from a business ROI perspective, and then they pitch you on another and another and another with package pricing. This is basically the Oracle model and ho…
Workday is not Salesforce. The rest, yes.