Closed APIs Suck: An Open Letter to Salesforce 5
Dear Salesforce,
I've been doing some work with you lately, and I was hoping to hook into you using your APIs to automatically insert some of our leads. Unfortunately, I can't. Despite the fact that you have a full API, it seems that you've chosen to restrict API access to "Enterprise Edition" and higher level accounts, and at my office we only have a "Group Edition" account.
I've been trying to think of a good reason why you would do this. I'm doing my best to lock our small but growing business into using Salesforce. Why wouldn't you want that to happen? I'm trying to tie myself intimately into your infrastructure. I'm trying to make it impossible to extract myself from being your customer down the road, but you're thwarting my attempts at every turn.
Think of how it would increase my switching costs if something better comes along. I would have to tell whoever is pushing us to adopt the new application, "Sorry, if we switch we'll have re-engineer our app." It would set the bar much, much higher. Also, it would only help your case for sticking around if I could say "You know all of that cool stuff that our app does with Salesforce, it'll all be gone if we switch over."
So come on Salesforce, how about making both of our lives easier and opening things up. I'm sure that some high-up executive there is telling you that there are a bunch of good reasons not to. I'm here to tell you that that person is wrong. Open up and this relationship will be better for both of us.
Thanks in advance,
Kurt
Well said. A API seems like a horrible thing to cripple for the lower-end versions of a product. I had a similar situation with StarTeam several years ago. They did give us an API, but the JavaDocs were incomplete and they refused to provide source code to the API's public interfaces and classes. This made it quite difficult to use. It's not like we asked for source to internal implementation details.
I would talk with your account executive. I work in a shop that integrates Rails apps with Salesforce (our clients are all on Enterprise though), and our account executives have always been reasonable when it comes to addressing the artificial limitations that Salesforce puts on their editions.
I've worked in-depth with the SF API as well as a number of others and agree with you 100%. The irony is that a UI requires so much more hardware, code, and support, than an API. Yet, companies continue to treat APIs like a 'feature' rather than what they should be - a minimal requirement.
I recently left a company that charged thousands for its API. The Integration Team had 2 people and the support team had a few dozen. It really made me scratch my head (still does!)
The subject of this blog post was the entire reason I started the "ThoughtsOnSalesforce.com" blog.
Salesforce.com is filled with people especially at the C-level who only ever think about "What's in it for ME?" and to them, every customer touchpoint is a point at which they can attempt to grab some money off the table instead of realizing how giving some things away can provide a much larger benefit. Sad, because if they were more longsighted they could have become the Microsoft killer; as is I predict they will be little more than a footnote in time.
After over a year with my Salesforce.com-related blog, however, I just got so fed up with Salesforce.com that I sold the blog and moved to SugarCRM, and haven't looked back.
I'm so miserable about this (lack of availability of API outside of Enterprise). Have read Mike's blog and agree. I have a killer app but unwilling to build it if I can only sell it to my customers who are willing to "upgrade" their Salesforce account to get it.
Not sure how firmly the heels are dug in, and I understand having to add value to justify Enterprise pricing ...but big opening for competitors.
SugarCRM (whatever that is) ... here I come....