Twenty: A Modern open-source CRM
github.com
github.com
When I meet a CRM salesperson, and they're like our software will do whatever you want and we will create it, you have to read between the lines and translate it. What they really mean is "Our software isn't designged to work for most general use cases, implementation will require a team of really expensive developers to create and maintain, we will tell you we are making custom fitting "cuture" software and you will be sending us a boat load of money for the rest of your company's life if it works or you will burn a giant pile of money until it doesn't work.
This isn't my first rodeo. If you have to extensively customize the software then the cost of the software will end up being moot and the cost of the people to run it will end up costing a fortune forever.
I believe Dante wrote a book on the subject…
Even those won't be specialized enough, a legal firm that handles corporate megers and acquisitions has very different processes from one that does class action litigation or criminal defense. Successful CRMs are not opinionated, but are customizable - requiring an army of consultants to deploy and an internal role to support. Small companies may be coerced to using opinionated processes (quickbooks + whatever process the part-time bookkeeper wants), but every medium-sized enterprise or larger is a snowflake
They can't be that different from one another that they would require bespoke software, other than an off-the-shelf solution for criminal defence lawyers? Or is there sufficient difference e.g. state to state that this would never work?
1. https://www.salesforce.com/uk/solutions/industries/business-...
The good reason is even within an individual industry each company is different enough that the software needs to be extremely customizable or there will be too much adoption pain required. I don't think opinionated does it when you would need to enforce change across large swathes of people. I have seen this tried and be an expensive failure across more than one organization where malicious compliance basically killed multimillion-dollar rollouts of this kind because people simply weren't prepared to change their workflows. I've seen the CTO of a very large organization first instruct, then ask, then plead, then beg for people to adopt the CRM that had been installed at great cost all to no avail.
The bad reason is that lots of big software companies (but definitely CRM people like Salesforce) rely on big consultancy firms to sell their product. Consultancy do that because they "don't sell software, they sell solutions", meaning they come in and do the implementation etc. They wouldn't do this if they didn't get the sweet sweet billable hours, so your software better be customizable up the wazoo for them to be interested in being your sales army.
And then piled on top of that, salesforce have created an ecosystem of developers who do the customization. So if you're a small bank, you might want ncino to do your loan workflows etc. That means Ncino are selling salesforce everytime they sell their product etc.
It sounds like they want you to pay for developers to help develop their unfinished crm system and the benefit you will receive is the crm system will be completely customized for your business.
Personally, my experience is that large software like CRM can be very very expensive and very very risky in the sense that you become dependent on the people you hire for it and those people can start out or become very very expensive. But most developers I know many of whom are on hacker news believe they can churn out a CRM quickly all they need is javascript, a server and a database.
After all, they just want to re-implement their current, CRM solution (which is terrible, and is why they want to buy a new one in the first place) in the new fancy CRM.
This isn't my first rodeo either, and in my experience, most firms have at least a few idiosyncratic rules and process that they aren't willing to change just to conform to the limitations of software.
If you build opinionated software, your customer base will be limited to businesses that either already operate according to the assumptions you've baked in to your design, or else have the resources to implement their own solutions -- at higher complexity than customization -- to compensate for what's missing from yours.
We're currently rewriting the backend and will ship a new version on October 30 that will be much more powerful (with a flexible data model)
Also please fill the demo with at least 10.000 to 100.000 items - it makes no sense showing your software with five data items, it looks like a demo for some home work then. We want to see how it behaves with millions of data.
We'll work on a real demo environment with a lot of records, we just haven't prioritized it yet. Right now it's not really a demo environment, but a real account that happens to be provisioned with a few example records. Putting more records wouldn't really make sense (you have to delete those records manually to start using the CRM).
I would assume that their point is that this would demonstrate that the system doesn't break down if you fill it with more than a handful of entries. Would be a shame if it grinds to a halt after using it for a few years.
And demo data != initial starting state
There are still a lot of things we need to develop to be at feature parity with big players but we are shipping fast and we will get there!
It's the open source circle of life. The same thing will happen to Twenty in a number of years. Things to watch out for: someone launches a competing hosted version of thr CRM.
— deleting my previous comment -
As for the cloud version, I replied here: https://news.ycombinator.com/item?id=37808121
TLDR is that the cloud version hasn't been our primary focus yet and we put a high pricing on purpose that is not the final pricing, while we figure out the good pricing strategy. As of today everything is free without any limitation, we don't enforce any limit. And when we rollout the real pricing, it will be more compelling
I've noticed previously in life that if I don't correct an allegation, people will just assume the to-me-obvious-falsehood is true by my silent assent. I didn't know that I, too, fall for this stuff despite being aware of the problem.
Your pricing page says pretty much the opposite and is quite confusing — it literally just shows “Free” vs. “Grow” and no option for self hosting made clear
removing those limits in an open source alternative doesnt help that crowd
but yeah there’s definitely a sliver of an audience that can do system design and wont just roll out their own microservices and database
We will focus on a narrower scope and try to do it very well instead of going into that many directions
Github says Agpl license.
Then the pricing page says 100 contacts for community support, is that for hosted version?
Why not have a "self hosted option" on pricing page that probably doesn't have limits unlike hosted one?
We definitely need to work on that page!
The actual pricing will likely be significantly lower. Initially we thought of introducing a pricing system that's more aligned with the value created (with a generous credit system, based on number of actions taken), because we found that Salesforce charges by seat but in large orgs most of the seat companies pay for are unused, so the incentives aren't aligned. I'm not sure we'll go this way because people also want a simple and predictable pricing they can understand.
Or put everything free and have your own dedicated service, with your infra and support. Look at Sentry. Everything is open source. They are making a lot of money. Not everybody wants to run Sentry on their own infra. Same with CRM.
Storybook here: https://storybook.twenty.com
When it's mature enough we'll isolate this into a UI lib anyone can use
Honest question: Why?
We've made the bet to invest on a tailored design for our components. Using an existing UI library is a strength to use robust components and move faster, but I've always struggled to customize it.
There is always a point where you want something custom that is not supported by the library and you start hacking into it. On previous projects, I've almost always used existing UI libraries. For Twenty, this is a long term project and the initial burden of creating UI components vs customizing existing ones will be marginal on the long run.
IMO, if you have strong design requirement (and you have enough resources ofc), don't go with UI librairies ; I take as much inspiration as I can from them, I may fork one but I would not hack their API
Using external libraries gives some early velocity, but most of the good looking libraries are incomplete and most of the complete ones are boring (material / bootstrap)
What is CRM Why use CRM?