npm-name VS Twenty

npm-name - Check a package name's availability on npm.

Star on GitHub ⭐ - Twenty

So, today on that quest I am reviewing TwentyCRM. I have worked and heard various vendor lock-in CRMs but it was the first time, I heard an open source CRM. Thank you Open source! As soon as I hear open source, that gives a relief because you can be assured of what happens to your data. No more those vendor lock-ins and no more nightmares of your precious business data! I liked that Twenty CRM apart from paid feature had the self hosted option which gives US the freedom. As users, the freedom lies to us. So that's a plus for me!

Did you know that keeping your data in sync can boost your team's efficiency? In this article, we'll show you how to create an n8n workflow that automatically adds, updates, and deletes people data in Google Sheets whenever changes happen in the Twenty CRM dashboard. Let’s dive in!

Participating in the OSS.GG hackathon has been an exciting and enriching experience. Engaging with projects from multiple partners like Dub, Formbricks, Hanko, OpenBB, Papermark, Twenty, and Unkey offered me the opportunity to explore the vast landscape of open source. Through this hackathon, I didn’t just contribute to code; I also got hands-on experience in non-code contributions, which opened up new avenues for collaboration and learning.

In today’s digital age, keeping in touch with friends and planning meetups can sometimes feel like a chore. Enter Twenty, a social planning app that promises to make organizing hangouts with friends as simple and spontaneous as possible. After hearing so much about it, I decided to give it a try. Here’s a breakdown of my experience—from setup to my final thoughts on its overall usability and unique features.

I've been planning to use https://twenty.com/ but it's on the Todo list, so I can't comment as to how great it is.

Very cool and promising.

Currently the biggest blocker, even for simple use cases that don't have to add automation (there is no clear way to add customized automation), is the lack of permissions. Everyone has the same access to all the data!

User permissions: https://github.com/twentyhq/twenty/discussions/209

I had the opportunity to work on a github issue in an open source project to add a Github workflow that runs if some files where modified in the path packages/twenty-website and checks that the website is still building.

You should check out Twenty! https://twenty.com/ (YC S23) -- they're an OSS CRM.

I totally agree the object management UI is too clunky right now. I want to redo that set of pages, they were the first ones we shipped. Not gonna lie, idk if anyone except me and Ned are really pining to learn hotkeys for managing object schemas, since in practice we're the only ones doing that on a regular basis -- we do initial setup on behalf of our customers.

Yeah, I consider latency part of UX. We're doing some somewhat fancy stuff to reliably replicate every record into a couple of stores, each of which is optimized for different access patterns (search, get latest by ID, etc.). The big central Postgres(TM) is mostly there to be authoritative and to transactionally maintain invariants in the system.

Open Source software will never be able to monetize as well as closed-source. We might only capture 10% of the value we create. But being open source inherently creates strong network effects that tends to push towards a limited number of winners, and the addressable market in CRM is so big that it's still possible to build multi-billion dollar company while massively driving the costs down for everyone.

It's kind of like the Prisoner's Dilemma: If every company keep their software proprietary, they can all make on moderate growth/profit. But if one goes open-source, they could attract a large community, drive innovation, and potentially reap long-term profits while reducing the overall market size.

[1] https://github.com/twentyhq/twenty