I'm told that SalesForce has overhauled their product as of early last year. Anyone work with the new one? Is it as bad as the old one?
Still an enterprise product, and an enterprise product of dubious purpose at that, means it still can't be any good.
Anyone work with the new one?
there was a n older one?
a worse one?
i find that hard to believe.
It's an enterprise CRM, if you leave it alone with the customizations and let it do it's job it's pretty okay, if you try to force it to work in a way salesforce doesn't want to work it'll go about as well as you would expect.
I think you have a typo in the thread title. Did you mean "TRWTF"? :clippy:
Context: we're considering moving to SalesForce. I brought up that I've spoken with many engineers who had a hard time working with the product. I was told, they overhauled it to make it better.
We do have a large number of sales people to manage and a good number of cross-cutting strategies to put in place, and the tool we have helps tremendously with that... but they're looking at alternatives to doing another round of updates to our current custom tool.
ScholRLEA last edited by ScholRLEA
Context: we're considering moving to SalesForce.
Run. Run now. The fact that Shillfarce is even on the table implies that the MGT who are considering it are dangerously incompetent.
Nah, I'm not bitter or anything...
I brought up that I've spoken with many engineers who had a hard time working with the product. I was told, they overhauled it to make it better.
I could hardly have gotten worse. They could have hired Swampy to fix it and it would have been an improvement.
More seriously, while I am very, very biased on this matter, I still would say that getting involved with SFDC is not a good move, less because of the technology involved (which is mediocre but not catastrophic) than because of the company itself. SFDC is less of a company and more of a cult, very much in the mold of IBM during Thomas Watson, Jr.'s tenure. Their goal is less to provide a product and more to make you dependent on them for everything - and then hold your own software and data for ransom by blocking anything from leaving their cloud servers or inter-operating with anyone else's systems in any meaningful way. Their documentation exists mainly to make you dependent on their cert courses, while their cert courses in turn are basically just extended advertising for all their other products. Using SF at all basically means using it for everything (regardless of how well it serves that purpose), forever.
The fact that Shillfarce is even on the table implies that the MGT who are considering it are dangerously incompetent.
Just very, very new to this whole thing.
ScholRLEA last edited by
@Yamikuronue OK, that can happen, sure.
Also, I just added a bunch to my post, in a more serious vein than the original. I probably should have done it as a new post, but I'll leave it as it is for now.
we're considering moving to SalesForce.
okay, that's cool and all.
word of warning: DO NOT try to wedge your current sales process into salesforce! it WILL end badly for you if you do.
Instead change your sales process to be compatible with teh salesforce sales flow. that way yo8u will only be fighting with your sales people (what else is new?) instead of fighting with your salespeople AND the monstrosity that you have created in salesforce.
don't fight on two fronts, yanoo? that way lies only death and defeat.
HardwareGeek last edited by
svieira last edited by
Ah, Salesforce ... I used them several companies ago. Speaking just as an end-user, their whole setup is really underwhelming and needs a lot of tweak-for-fit, even if you're using it the way they want you to use it. It's much more comprehensive than a lot of other cheap CRMs out there, so that's something I suppose.
Karla last edited by Karla
We have some Salesforce projects. Our other main apps are moving to Microsoft Dynamics CRM.
SF -- I absolutely positively did not want to learn a new language that had little options in the real world.
I am not liking Dynamics thus far, never mind that we have to sit in classes that go at the speed of molasses.
ScholRLEA last edited by ScholRLEA
Part of the problem is that, IMAO, Customer Relationship Management is something of an iffy concept to begin with; it always truck me as automating the wrong aspects of customer relationships, taking consideration out of things that should require thought and panning while leaving things that could easily be automated to be done manually. However, this is a vague sense of things rather than any hard facts, so it is likely that my impression here is just wrong, or at least biased.
Another part is that CRMs, likes spreadsheets, tend to get used for everything except those things they are designed for (when was the last time you saw anyone use Excel to do a conditional projection? I'm guessing never). The whole reason that my previous company threw out thousands of lines of working Java code in favor of a half-baked, unworkable approach using SFDC was simply because Salesforce had a vaguely Java-esque programming language built into it, therefor it has to be a general-purpose development platform, right? It must have looked like a way to save time and money, and I have no doubt the SFDC con
-artistsspun it that way, but since we weren't actually using SFDC as a CRM, we ended up being given a jackhammer to use for both sawing lumber and fitting pipes.