Their chat api expects headers that they do not include in cors allowed headers, we had to write a proxy just for this.
Salesforce as a company is a terrible experience.
Had many incidents because of their bad practices or lack of knowledge or incompetency.
When you codify your business processes, actual code is going to be needed as well. Enter Apex and heroku.
Slack is a way for SFDC to codify another part of your business processes—communication.
That said, SFDC does a lot of things that fairly give it a bad rap. Their developer experience is really bad, their apps are not that great, and lightning is still not adopted at many companies years after its release.
I don't understand what this means at all. Let's say I make pies. My sales process is I go to grocery stores and try to get them to carry my pies. My marketing is I buy commercial time on the local tv station. How do I codify this into a SaaS product?
Every time someone at your company uses your phone system to call a customer, it is auto-logged in Salesforce. Every email is logged. Every sale, every transaction, every interaction.
Now when "Bob the amazing Sales Guy" leaves you have a central repository of every contact he's made in every company he's worked with on your behalf. This means you build institutional knowledge instead of tribal knowledge.
So now lets say a couple years have gone by, and you want to publish a white paper on pie consumption, so you hand the project off to your research and analytics team. Thanks to Salesforce they have knowledge of every person your company has ever contacted about pies, and therefore have a great jumping off point to start with interviews for the whitepaper.
The reason I don't call it a sales lead tool is that is about 10% of their use case now. They've expanded significantly and companies use them for just about everything.
Salesforce is a SaaS because it’s in the cloud. The first company to take a big het on the Cloud, in fact.
If you’re still confused, then spend an hour or so reading their marketing literature and kicking the tires in their free Developer Orgs. Simple as.
The developer experience is sadistic, but Lightning is the worst. It takes forever to load basic information because it all has to cycle through JS callbacks. Try opening a link (or a bunch!) in a background tab: it doesn't load anything until you're actually looking at the tab.
Are there no better ways to automate sales and marketing?
Once you start using Salesforce, do all of your leads get stuck in the platform, or can you export them and do your own analytics queries? How deep is their lock-in?
> Slack is a way for SFDC to codify another part of your business processes—communication.
It feels too freeform to be automated. It's just chat with a so-so search interface.
SFDC has one of the most robust APIs I've seen...you can export pretty much everything. I actually really enjoy working with the soql rest API, because it's simple, effective, and discoverable.
The lock-in is instead in their integrations. It is almost guaranteed that there won't be another platform that has all of the integrations you need, so you stick with SFDC. You add more integrations over time and the lock-in deepens.
To some extent, as a business owner or CRO, you want the data to be stuck in Salesforce. The price of Salesforce is small compared to the cost of salespeople maintaining their own relationships directly with clients -- and then potentially walking away.
Along they way they've bought a ton of companies that do various enterprisey things. Now they're a one stop shop to run everything a business might need.
It's hard to tell if Salesforce has been a positive for Heroku for keeping it alive, or a negative for mismanaging the company, since we don't know what they would have done if they stayed independent and had to actually compete. But I'm pretty sure if they were still independent and had to compete in the market with only the features they have right now, they would likely be out of business. There's very little reason to choose Heroku these days, and I say that as someone who has code running in production on Heroku's platform.
The product is stable, there's a ton of new features (like pipelines), and can't imagine starting a serious project and not using Heroku.
Heroku still doesn't have any data hosting options. You have to go to a third party for this.
Heroku doesn't have any static site hosting options. You have to go to a third party.
But the biggest problem I have with Heroku's model is how much I need to pay. I've been a Heroku customer for years and I'm still not exactly sure what a dyno is. And if I get it wrong, I can have auto-scaling... but only if I'm paying a minimum of $250 per month. Now that's not a lot to big companies, but for bootstrappers that's insane. And I only get 2.5GB of RAM for that $250/mo? And if I'm using microservices, every service costs me a minimum of $25/mo, $250/mo if I want auto-scaling on those services.
Like I said, Heroku is great and I use it in production and pay them money every month, but man if it's not stuck in 2015. Luckily so is my application so I don't have too many issues except for the ridiculous cost even as EC2 is dramatically cheaper now than it used to be (does Heroku support Graviton? I don't think it does), but PaaS in general is "the old way of doing cloud" and Heroku is becoming less relevant every day.
Suppose that we said that Salesforce (or JIRA) itself is fine, except for those sites that have implemented it poorly. Would that be an example of the One True Scotsman fallacy?
(I mean the question honestly. I'm not 100% I properly understand that fallacy's definition.)
If there’s something missing all you need is either time or budget to have it built.