Launch HN: Twenty.com (YC S23) – Open-source CRM
261–270 of 317 posts
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#262I worked as an implementation consultant during the 1st or 2nd generation of CRM apps back in the fist decade of this century. Then, since 2010 I became a CRM end-user, mainly of Salesforce. After all those years listening to sales people complain about workflows and broken UI/UX, I realized the perfect system for this type of user is a message driven minimal UI app. System would send email/IM to users all day long a…
What I'd like to see is an actually smart system that interfaces with data in my company, connects the dots intelligently and prompts humans for input where it requires it.
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#263AGPL is always scary. If I integrate your CRM code into my tech stack, technically I may need to make my tech open source, per AGPL. Thats dangerous.
We are unsure about the right license to use, so this is a great feedback. We had a MIT license one week ago that we know that we cannot hold on long term and we felt we were lying to the community by keeping an MIT license and changing it in one year. By using AGPL, we feel it's the right level of restriction. It's the license used by Metabase for example ( https://github.com/metabase/metabase ) that many companies…
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#264Earlier quoted context omitted.
It’s the advantage (like they said) that you don’t have to login into Salesforce. This tool slows them down, and via voice they don’t have to use the salesforce application directly. Imagine you have awesome ideas and plans and have 8 hours a day. But if you can only be productive for ~6, you’re losing a ton of time just because the tool is bad designed/planed/slow/{insert more words here}. If you want more about tha…
I just feel that "via voice" is what makes me having doubts. Almost any tool could be adapted to a "via voice" interface, but which tools will become better for it? I have a hunch that almost any custom interface on top of Salesforce would improve it.
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#265As a former CTO, almost every product I worked on had a request coming in at some point to create an internal CRM and I do believe in embedded CRMs as a software category.
There are even SaaS categories that could use some CRM-like ability (e.g. link building tools, procurement tools, debt collection, ...)
Open-source would be a good fit for that model cause you could take it in-house if you need a lot of customizations.
Some painful CRM issues I encountered:
- Pregnant funnels
when sales sets up the funnel stages in a way that leads can go back through the stages (e.g. "next meeting scheduled", "follow-up" or "offer sent") so a deal passes through the same funnel steps several times.
Not sure there is much you can do about that except for dynamically creating more stages in the funnel
- Last-stage-changed-at
Another issue is that CRMs don't keep event logs of what actually happened and just keep the last stage and when you changed that stage; this makes it impossible to analyze stage-durations and correct for cyclical stage switching (see pregnant funnel problem)
- Call quality
You would think that in 2023 voice-over-IP would be super reliable and works every time but I can guarantee you that in a 30 people sales team you will have many! complaints about call quality if you only rely on VOIP.
Always have the ability to call the salespersons' real phone number (over the traditional telco network) and then call the client once the sales person is connected. (a sort of conference call).
This kills all call quality issues as there is a fallback to dedicated phone networks.
- Call activity recording
Call activity recording is actually very important because apart from pipeline reviews, tracking sales call activity is one of the only leading predictors of sales success (it also catches lazy sales ppl).
Related to the above, some CRM's are able to record the calls with VoiP but fail to do so when real phone networks are involved.
- Cell phone masking
When using CRM calls, in hubspot and zendesk you can spoof the phone number; this is typically set to the salespersons' cell phone so the client can call back but when the client calls back the call goes unrecorded.
- Lack of IVR menus
IVR is a part of every PBX setup but they almost never play nice with CRMs; only Aircall integrates IVR menus but it relies only on VoiP and was a huge nightmare (see call quality issues).
- Treating leads and deals as separate records
It's surprisingly hard to build funnels that go from "this person filled in this field and has these UTMs parameters" to "which UTM parameter made actual money because almost all CRMs have a dual LEAD/DEAL record.
They typically destroy the lead and it becomes a contact which often has no stages anymore.
Nobody in Sales and marketing thinks about it that way though, it's more "here's a lead and then the lead progressively discloses more information"
I always think the best datamodel for a CRM is an event-sourced log with a giant json blob representing the latest stage that can be rebuilt from the event-source log.
- Outbound email chains
Most CRMs use their own email address and the main company domain to chase prospects (and setup automated email chains), which as you can expect sometimes get spam-listed; the ability to email through a separate domain and to capture replies properly is needed.
My current solution is to just ban the use of automated email chains but I've seen other companies use mailgun to create a proxied salesperson' inbox.
- Closing the loop with marketing
Google analytics and facebook has tags you can use to indicate the actual deal value of the generated lead. You can say this click led to 1k in revenue; except it's a huge pain in the ass to do this because of the lead/deal breakup and often the original contact details change as the sales person gains more trust.
Another option would be to export events to analytics tools like Amplitude so you can get a complete marketing-product-sales funnel
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#266Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#267There's a lot to do in this space. As a former CTO, almost every product I worked on had a request coming in at some point to create an internal CRM and I do believe in embedded CRMs as a software category. There are even SaaS categories that could use some CRM-like ability (e.g. link building tools, procurement tools, debt collection, ...) Open-source would be a good fit for that model cause you could take it in-hou…
- Meeting activity tracking
Meeting scheduling is kind of covered now but meeting activity tracking in CRM's hasn't caught up.
Also these types of calls and call activity is unrecorded now
This issue got worse since video calling is often the default
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#268Earlier quoted context omitted.
I just feel that "via voice" is what makes me having doubts. Almost any tool could be adapted to a "via voice" interface, but which tools will become better for it? I have a hunch that almost any custom interface on top of Salesforce would improve it.
Yes, I guess that’s the thing. The custom interface would be voice commands then.
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#269I work at a company that uses Salesforce as the system that runs the whole business. CRM barely touches on what we use it for. We use it for inventory, logistics, accounting, customer support, managing our partners (dealers), managing our suppliers... as well as sales. I spent 2 years as a Salesforce developer, and still dabble in APEX from time to time. All of that is context for what I'm about to say: Salesforce is…
I wouldn't use that as a source of inspiration, at least not on the "connectivity" end.
Re: Launch HN: Twenty.com (YC S23) – Open-source CRM
#270I work at a company that uses Salesforce as the system that runs the whole business. CRM barely touches on what we use it for. We use it for inventory, logistics, accounting, customer support, managing our partners (dealers), managing our suppliers... as well as sales. I spent 2 years as a Salesforce developer, and still dabble in APEX from time to time. All of that is context for what I'm about to say: Salesforce is…
To be honest, it sounds 100% like SAP / ABAP. A lot of terribly outdated stuff. But it can do everything you can imagine. If it can't, there's 1-2 recommended products that expand features on top of SAP. The moment your business wants to do things a way that isn't SAP's way, you completely butcher everything though. See https://news.ycombinator.com/item?id=17541092