3 ms·
I like the "crm.json" image. We definitely want to work on doing something modular like this. I also wanted to price differently than by seat initially. Becaus
by iFelix 3y ago
I like the "crm.json" image. We definitely want to work on doing something modular like this.
I also wanted to price differently than by seat initially. Because CRMs tends to be the source of truth for the whole organizations, and usually teams like customer support are left out because it's not worth paying a license for them to just read the information the sales have put in, while it would be useful. But we didn't find a better way to price in the end. Pricing by usage feels off since there is no cost associated to usage (a user that logs more activities is not going to cost us more). How would you charge then?
Noted for email automation / lead enrichment!
- primitivesuave 3y agoIf you look at medical EMRs (essentially a CRM where patients are customers and salespeople are doctors) there is a similar situation as the CRM market, where a few big players dominate the scene with crappy software and feature creep (i.e. Epic = Salesforce). Based on the clean UI you have so far, you're definitely on the way to building a better user experience for CRMs, but at the end of the day you have to sell this to a salesperson, just like people selling better EMRs have to sell to hospital administrators who don't care how great the code is. Consider an organization spending $10k/year on HubSpot. They're also spending at least a million a year on salaries/commissions for their sales staff. Optimizing software costs addresses 1% of the total spend, while making sales people more efficient optimizes the other 99%. In general, if your target customer is sales management, I would pitch support/customization contracts to streamline sales organizations when you're picking up initial customers. This would also likely bring you perspective on the wide range of customizations out there.