7 ms·
The biggest mistake a competitor can make is thinking Salesforce is a CRM. They may sell themselves as one, but that is just to get a foothold in a company's sa
by paxys 3y ago
The biggest mistake a competitor can make is thinking Salesforce is a CRM. They may sell themselves as one, but that is just to get a foothold in a company's sales system. Salesforce actually sells (1) an ecosystem that lets your company connect to any other software out there and (2) a platform on which you can build...basically anything. These two together ensure that every one of their customers is 100% locked in and will continue to pay whatever Salesforce asks for all eternity. The actual CRM part (basically tables of data with a UI) is trivial, and not really their "special sauce" that you can disrupt with something shinier.
- nickstinemates 3y agoSalesforce is basically the OS for your company.
- DaiPlusPlus 3y agoWhat's SAP then?
- nickstinemates 3y agoAn OS for Finance :)
- jarym 3y agoAn OS for bleeding companies dry
- alemanek 3y agoA virus
- vxNsr 3y agoSame thing, as is servicenow, they're all cloud platforms angling to be the "Company OS" all coming at it from different angles. Salesforce comes in at the sales side of things, SAP invades as a finance app, and ServiceNow begins their encroachment as an IT ticketing system, but they all wanna be THE only cloud platform your company needs.
- phkahler 3y agoIt seems like a good solution would have clean interfaces between various pieces so they can be easily replaced. Sales, purchasing, payroll, HR, and IT stand out to me, but there may well be others.
- LrnByTeach 3y agogood to know what these "Company OS" stands for > Salesforce comes in at the sales side of things, > SAP invades as a finance app, and > ServiceNow begins their encroachment as an IT ticketing system, but they all wanna be THE only cloud platform your company needs.
- iFelix 3y agoGood summary! And Microsoft through the Productivity apps? (Word, Excel...)
- vxNsr 3y agoSure but Microsoft isn’t really offering a coherent solution for general company data and processes. They have the power platform, but because there’s no happy path, best practices, laid out it requires a lot more buy in from actual engineers who don’t have a lot of love for nocode platforms. It’s totally feasible to build a IT ticketing system in power platform. And then to build a sales/CRM solution and then also build a bunch of analytics and compliance and such for finance, but because Microsoft doesn’t have the barebones platforms there it’s a lot more work to stand up, and you end up maintaining a very custom product that is totally dependent on Microsoft not suddenly changing their pricing or deciding to kill the platform due to lack of revenue. At that point you may as well just build your own thing in actual cloud products instead of depending on the “baby proofed cloud”.
- e12e 3y ago> Sure but Microsoft isn’t really offering a coherent solution for general company data and processes. Do you have a moment to talk about our Lord and Savior Dynamics 365? > Microsoft Dynamics 365 is a product line of enterprise resource planning (ERP) and customer relationship management (CRM) intelligent business applications https://en.m.wikipedia.org/wiki/Microsoft_Dynamics_365 https://en.m.wikipedia.org/wiki/Microsoft_Dynamics_365
- esafak 3y agoYou can say the same thing (lock in) about any product that has migration costs. If everybody thought that way nothing would get built. I say to Felix: just do it, but think about these problems. Fortunately there is a whole field of business devoted to this problem: go-to-market strategy. Target a niche, offer a compatible product, offer a significantly better product, offer a different product, offer a cheaper product ... the options are endless.
- marpstar 3y agoRight, but the bigger the organization, the larger those costs. Think of a city of Los Angeles switching to a new system for tracking their public works department versus a township of 3,000 people. Smaller orgs are much more tolerant to this. New orgs start small and don't need something huge like Salesforce immediately; they need something usable.
- DaiPlusPlus 3y ago> You can say the same thing (lock in) about any product that has migration costs. If everybody thought that way nothing would get built. Not all "migration costs" are the same: to quote General Turgidson, "It is necessary now to make a choice, to choose between two admittedly regrettable, but nevertheless distinguishable, postwar environments: one where you got twenty million people killed, and the other where you got a hundred and fifty million people killed." In the case of software migration costs, the cost of migrating away from a proprietary application-platform with zero-to-little code and data portability, will be orders of magnitude higher than the cost of migrating away from a proprietary infrastructure-as-a-service platform. This isn't anything new: while Cloud-y platforms like SalesForce present even higher barriers to exercising our rights to data-sovereignty than what we had previously with SAP (because at least with SAP you can defenestrate the machines), it's all too similar to the 4GL vs. SQL wars of the 1990s. I honestly can't think of any orgs from then that regrets betting on a SQL-based RDBMS, while there are still companies out there depending on FoxPro, Progress, or worse... This is also why I flat-out refuse to use Firebase. Another hidden-cost of 4GL-like systems is that eventually they run-out-of-steam: hype fades and the vendor becomes stagnant and/or can't attract the best minds in the industry to design and build the platforms they expect others to use, so they lose whatever advantages they might have had which justified their proprietary nature - or an even more insidious version, whereby too many slow-moving companies become dependent on a particular platform that the platform's vendors have to intentionally hold-back the platform to avoid imposing too many fast-moving potentially breaking-changes (Java comes to mind...).
- marpstar 3y agoAccurate. The licensing (and the "kill switch") at a previous job were controlled entirely via Salesforce. Our app would "phone home" regularly to check which features are being paid for and we'd toggle them on and off in our app accordingly. I had, at the same company, been asked to evaluate building Salesforce apps (using the custom programming language they provide) and contrasting that with building new apps on our own metadata-driven platform. Developers hate it, business people love it. It won't be going away for lack of paying customers, that's for sure.
- collinc777 3y agoApex is nightmare fuel
- chologrande 3y ago100% - having to submit code server side to just get compilation results is the worst development loop I've ever experienced.
- iFelix 3y agoI'm really eager to get to the point where we can work on CRM extensibility and developer experience. We're hoping to bring traditional web development workflows and not re-invent anything. We opted for a multi-tenant infrastructure for the cloud hosted version so there will be some additional challenges to make it work in that context!
- iFelix 3y ago100% agree. And we are not there yet. But I feel like open source is the best answer to 1 (building an ecosystem of integrations), and that it will also allow us to build a better platform for developers (2): why learn Aura components/Apex when you already know and can use Typescript/React?
- solarkraft 3y agoA "real" development stack might enable users to build actually good experiences. The custom (proprietary) stacks I've seen so far have always been pretty "meh", lacking features, community and tooling, resulting in not-great DX and making building some features something between very hacky and impossible.
- btown 3y agoAn open-source core is only part of it, because different users will need different data models for different business domains. One of the biggest challenges here will be: how can you allow tenants to run arbitrary plugins that (a) execute arbitrary sandboxed server-side code, and (b) can store arbitrary new data models and custom fields within your instance's centralized storage alongside the canonical model types, in a way that allows for indices, foreign key constraints, and derived materialized fields? If you solve this and provide a great developer experience, including free sandbox accounts and a payments stack so that developers can sell plugins without needing to ever operate their own infrastructure, with namespacing to avoid compatibility problems between apps, then the ecosystem will come.
- charlesTwenty 3y agoThat's a very good point. In the early stage, we were thinking about a single tenant architecture which would make this questions way easier. However, I am a strong believer in multi-tenant architectures as they allow to scale while mutualizing the resources (I personally think it's single tenant at scale is non-sense in term of ecology) and we will invest into maintaining a multi-tenant architecture. So, as we go through the multi-tenant path, what you say is very relevant and will be challenging. Regarding custom entities and custom fields, we plan to introduce a flexible data table backed by a meta-data, quite close to what salesforce is doing ; this article is gold about how they built it: https://architect.salesforce.com/fundamentals/platform-multitenant-architecture https://architect.salesforce.com/fundamentals/platform-multi.... In short, you have a data table (uuid, objectid, tenantid, field1, ..., fiel500) where fields are VARCHARs and you build your own engine on top of that. This comes with a lot of challenges such as performances (indexation), typing (we lose Typescript/GraphQL power obviously as we deal with flexible data modeling) Regarding plugins that we want users to be able to create and to activate on the marketplace without vetting, here is the way we see it right now: 1) Front-end: serve a dedicated JS depending on what workspace you are on. Rebuild this JS when you activate / update a plugin 2) Back-end: we will need to execute the code in a separate environment. We were thinking about serverless lambdas for the cloud version and keep it local on the main server for self-hosting ; kind of allowing two drivers (lambdas + local) to execute plugin code in the codebase but using lambdas only on the the cloud). Would love to chat a bit more about it. We will likely open a Github discussion thread in the upcoming weeks about this specific topic) so we can get the feedback from anyone interested into it
- SystemOut 3y agoReplace Salesforce and CRM with ServiceNow and ITSM and it's a similar story. They call it "Land and Expand". There's a reason they have a 99% or so renewal rate.
- scrapcode 3y agoServiceNow can't be worse than BMC Remedy... I hope.
- andy_ppp 3y agoI think of Salesforce like an octopus that puts immovable tentacles into the organisation that are almost never removed. It provides as much opportunity to be misused as possible!
- mattfrommars 3y agoThe 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.
- _ktx2 3y ago> 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 how Larry got his blood money.
- mattfrommars 3y agoOh yes. I definitely use WorkDay. Interesting, never knew WorkDay is created by Salesforce. We are a very M$ bias company, hence, no slack.
- paxys 3y ago
- samanator 3y ago> The actual CRM part (basically tables of data with a UI) is trivial Although I agree with the general sentiment, I disagree with this. I've tried out over 100 low-code ui builder over the past year (including creatio,Corteza,ERPNext,Baserow,tadabase,appsmith,nocodb,mathesar,bubble, etc.) and so far none of them have perfected "excel like ease with the power of a database". If anyone has any suggestions, (that's not on my list https://docs.google.com/spreadsheets/d/15Pg6y11JscBMK-PK06f7CK7TI0UQ4xBIGytG1flXsEY https://docs.google.com/spreadsheets/d/15Pg6y11JscBMK-PK06f7... ), please let me know!
- iFelix 3y ago2 competitors which I think are getting things right on the UI front are Attio [1] and Folk [2]. It's not as powerful as Salesforce and the data structure is very loose, but they have done a good job with the user-experience. They are not open source though. [1] https://attio.com https://attio.com [2] https://www.folk.app https://www.folk.app
- gervwyk 3y ago
- epberry 3y agoThe salesforce object model/API is actually pretty reasonable and easy to work with. Their UI is horrible but the Lightning version is fast at least.
- tootie 3y agoIt's more than that. If you look around the market at any sort of data, BI marketing automation, payments or a dozen other verticals and every single one of them will have a first-class integration with Salesforce extolled on their homepage. A business running Salesforce is like a business that speaks English.
- rtpg 3y agoI feel like people don't appreciate enough that Salesforce is selling a... Smalltalk OS that everyone shares access to. It's nifty!
- arethuza 3y ago"The biggest mistake a competitor can make is thinking Salesforce is a CRM" A lot of CRMs seem to evolve into general purpose platforms - Salesforce and MS Dynamics being the ones I am familiar with.