Live data from Hacker News

What I Learned at Salesforce.com

medium.com

31–40 of 43 posts

Re: What I Learned at Salesforce.com

#31
post #26
post #14

Salesforce may have been a lean, mean sales ops tool back in 2004, but as the company has grown through acquisition and its own sales force has hugely expanded, it's platform is just not viable for many potential customers. 1) Implementation absolutely requires assistance from an integration partner. 2) Developing on top of it is an exercise in patience and futility. Their dev platform & APIs are inconsistent and hal…

You just described SAP.

At first I was thinking the same thing, but you can definitely go a-la-carte with SAP (one could argue there is no other way), and it is totally possible (and largely done) to build your own reasonably competent and market-priced team to maintain it. Come to think of it, SAP does provide added value when it is well-managed and tailored to your business. SAP is quite an unique beast.

Re: What I Learned at Salesforce.com

#33
post #31
post #26

Earlier quoted context omitted.

You just described SAP.

At first I was thinking the same thing, but you can definitely go a-la-carte with SAP (one could argue there is no other way), and it is totally possible (and largely done) to build your own reasonably competent and market-priced team to maintain it. Come to think of it, SAP does provide added value when it is well-managed and tailored to your business. SAP is quite an unique beast.

Well, you can definitely go a-la-carte with SF.com too, the point is that the sales people push you into kitchen-sinking it. SAP sales does this too, and usually leads to what we used to call "shelfware". I cannot tell you how many companies I worked with that had unused licenses laying around. (funny - most companies I met have no idea how many licenses to purchase..."oh we want the finance module. So we have 1,000 people in finance so gimme ummm 1,000 licenses") Also, both SF.com and SAP will add value if you use and maintain them properly. The biggest difference with Salesforce is that you don't have to manage a data center.

Re: What I Learned at Salesforce.com

#34
post #20

Earlier quoted context omitted.

> To me, Salesforce is the embodiment of the perception that many SAAS companies exist solely to support other SAAS companies, and that they bring little to no value to anyone. Make something people want. If they require assistance, have a half-baked API, sell you the kitchen sink, are prohibitively expensive and they are printing money selling sales software they are the definition of making something people want. >…

> If they require assistance, have a half-baked API, sell you the kitchen sink, are prohibitively expensive and they are printing money selling sales software they are the definition of making something people want. Life doesn't work in simple axioms like this. You're clearly not familiar with "enterprise software" if you think value = sales. I'd wager that the vast majority of SalesForce users despise it. That means…

In my experience, I don't think users hate it.

In fact, every time I talk to someone about salesforce and go "what, about that interface, huh? How bad is Salesforce!". They look at me like I'm a little loopy.

It's basically a lot better than the thing they used to have, which was nothing. And they can use it on their phone. And it hooks up to Outlook. And it does X, Y and Z other useful things that make their life easier.

The difference is that you and I can look at Salesforce and realize it's a mess of legacy and outdated interface ideas, that SOQL and Apex really fucking suck, so, so bad. But for users it's better than the Excel spreadsheet that kept getting out of synch, or the painfully clunky google sheet or whatever.

I mean, every time I look at salesforce it's a disgrace. Something as simple as basic filtering by related object values on Views is impossible. Or that the Notes hide the note behind a popup instead of showing the note in table view. Or that you can't change the layout of the entity homepages. Or that bizarre news feed interface.

And yet they've built a thing which tries to automatically get the twitter or linked in profile. It just screams of bad, bad, here-be-dragons core code which no-one dares touch.

Re: What I Learned at Salesforce.com

#35
post #14

Salesforce may have been a lean, mean sales ops tool back in 2004, but as the company has grown through acquisition and its own sales force has hugely expanded, it's platform is just not viable for many potential customers. 1) Implementation absolutely requires assistance from an integration partner. 2) Developing on top of it is an exercise in patience and futility. Their dev platform & APIs are inconsistent and hal…

> "Implementation absolutely requires assistance from an integration partner." > "If you aren't a multi-thousand user customer, Salesforce's sale folks don't take you seriously" Thanks for the breakdon. I strongly agree with both above, which I think leaves plenty of opportunity for those purely focused on SMBs where companies like Hubspot have stated they will stay. Ever heard of a 'Salesforce Developer'? I put that…

> Ever heard of a 'Salesforce Developer'?

Yes, and the good ones charge obscene amounts of money. A good niche if it interests you.

Re: What I Learned at Salesforce.com

#36
post #12

Is someone testing their MarketSpeak Generator? I absolutely hate dealing with vendors who use Salesforce.com. It's a red flag that support might be dismal. The only lesson to be taken from this is that you can build a business around a terrible product.

As someone in software support who had Salesforce "forced" upon us, I invite you to consider that it's as maddening for us as it is for the end-user. I've closed maybe 1500 tickets through SalesForce, and I find the system atrocious. Among other duties, I am in charge of maintaining the Knowledge Base for our product. SF's Knowledge article capabilities, however, are abysmal. The default formatting is atrocious, bare…

Hey if you think that's bad, we went one worse! This might make you feel better but it makes me envy your position.

In the effort to integrate two distinct factions in the business, they decided the best approach was not to find one holistic tool that works for both cases, nor unify the process across the company but to do the following crime:

Integrate an on-site established JIRA processes with cocked up Salesforce lack of processes with bidirectional escalation and updates!

So now the shitball of chaos and incompetence that is support and sales teams can directly lay turds into the development team's toolchain, not that they're any better in the majority. Likewise the other way, the developers can write internal swearing and technical information all over salesforce cases which can get published to the clients all the time...

And yes we're doing the same with the knowledgebase but we're pushing it and release notes from JIRA into it.

Now I'm no fan of JIRA the money-sink by any means, as a guy who supported it for a number of years, but neither platform is a good match for a well established company devoid of any reasonable processes and going through a rapid reinvention phase.

Ugh.

Re: What I Learned at Salesforce.com

#37
post #14

Salesforce may have been a lean, mean sales ops tool back in 2004, but as the company has grown through acquisition and its own sales force has hugely expanded, it's platform is just not viable for many potential customers. 1) Implementation absolutely requires assistance from an integration partner. 2) Developing on top of it is an exercise in patience and futility. Their dev platform & APIs are inconsistent and hal…

> "Implementation absolutely requires assistance from an integration partner." > "If you aren't a multi-thousand user customer, Salesforce's sale folks don't take you seriously" Thanks for the breakdon. I strongly agree with both above, which I think leaves plenty of opportunity for those purely focused on SMBs where companies like Hubspot have stated they will stay. Ever heard of a 'Salesforce Developer'? I put that…

"Salesforce Developer/Architect" here.

My enterprise domain knowledge is far more valuable than my technical skills, and Salesforce is just a more fluid vehicle for delivering this value compared to traditional on-premise solutions from Oracle, SAP, and IBM.

Sure, the upstart CRM vendors have better UIs, but they aren't the real competition.

Salesforce is executing a classic innovators dilemma strategy of acquiring these upstarts (desk.com) and allowing them to operate independently in the SMB space as an on-boarding ramp to the enterprise-scale solution.

Re: What I Learned at Salesforce.com

#38

Earlier quoted context omitted.

> "Implementation absolutely requires assistance from an integration partner." > "If you aren't a multi-thousand user customer, Salesforce's sale folks don't take you seriously" Thanks for the breakdon. I strongly agree with both above, which I think leaves plenty of opportunity for those purely focused on SMBs where companies like Hubspot have stated they will stay. Ever heard of a 'Salesforce Developer'? I put that…

> Ever heard of a 'Salesforce Developer'? Yes, and the good ones charge obscene amounts of money. A good niche if it interests you.

yup, a great niche. Possibly even one of the best bang for buck certifications.

Re: What I Learned at Salesforce.com

#39
The amount of negative comments in this thread is as suspected when one brings up enterprise software to the world of HN where the community prefers "clean canvas" to draw the ideal world and call it elegant piece of art.

I would suggest people to view Salesforce from the perspective of the business users (or check this comment as well: https://news.ycombinator.com/item?id=9184356)

The place I work for at the moment uses Salesforce and we're paying lots of money to them (company with 100 people employees, balanced between engineering, support, sales/bdr, marketing, hr). I've never heard our Sales/SE/Support complained about Salesforce. In fact, they continue to find better tools/vendors inside Appexchange that can help them to be more productive closing Sales.

Our software integrate with Salesforce to some extend w.r.t to tracking customer acquisition, license, and retention. I can't complain. Salesforce is better than any other Enterprise software I've dealt with before.

I had a chance to talk to the CTO of Salesforce1 yesterday while he was demo-ing the Salesforce1 platform on his iPhone. He showed me how Sys-Admins (sys-admins of Salesforce themselves) can write a small "module" that can be deployed and visible inside the Salesforce1 mobile app immediately.

That's probably one of the few "enterprise" mobile apps I've seen so far where you can allow your customer to develop a small-modular-app to be deployed within the _same_ Salesforce1 mobile app but only visible to your Organization (or to certain group/role within your Organization).

Our customers purchased our solution (we are an APM company) to monitor their Salesforce instances because they need a 3rd-party to ensure Salesforce does not break their SLA. (We're talking about Fortune 500 company that signed $10m contract with Salesforce; Salesforce will be held accountable if they break SLA).

I asked him how Salesforce test Salesforce itself (the whole thing, that big ball of mud if you want to call it that way). He went off and explain how they rigorously test the whole system in details. That includes testing the mobile app... and testing the "custom app" within Salesforce ecosystems.

So I got curious and asked him further: how do you test those custom apps written by the customers? His replied was as follows:

1. When the customer sign up, they agree to let Salesforce run test-automation of their custom app

2. Salesforce tries their best to educate "Salesforce Developer" to write automation test that will be executed as part of Salesforce update/deploy cycle

3. If the customer/vendor does not do that (or write tests that don't test properly), it's their fault.

That's insane! I've never seen an enterprise software company go that far!

During the event, I get the impression that Salesforce cares a lot of automation, automation testing, and to ensure "things don't break". Can't say the same thing with Facebook even though they're developing lots of "cool" cutting edge tech. But then again, Salesforce customers force Salesforce to not break things or else refund...

TLDR: Salesforce as an enterprise company is pretty good compare the rest. HN community is definitely not the target market so it's natural to see negative comments.

Re: What I Learned at Salesforce.com

#40

Its funny seeing Salesforce get knocked on here. I've been working with it quite a lot. They deliver two upgrades with new features every year that are deployed in minutes for each customer, and in nearly all cases, previous features and APIs and customer customisations continue to be supported. To be able to extend and extend and extend like that without breaking, their core codebase must be incredibly well engineer…

Check my comment somewhere here as to how they ensure things don't break upon update.

PS: Salesforce1 is their new platform that bridge web and mobile. It's not just one or two thing. It's everything. It's how they build Salesforce...

Post reply on HN