Where’s the “App” in AppExchange?


Ok, ok, I’m starting to feel bad writing about Salesforce.com. Well, maybe not. Someone has to do it, right? This week is Dreamforce, where Salesforce runs ’round town tooting their own horn much to the chagrin of individuals who feel their vision isn’t so hot. In all seriousness, why do some of us not see Salesforce as the save-all answer or as a “shining star” in the industry? Well, a prior post of mine discusses the introduction of Apex as one reason, but what else? Let’s start with finding the apps in AppExchange.

AppExchange, based on my interpretation of the very clear  marketing message delivered by Salesforce, is an online market place where users can subscribe to applications built by Salesforce.com partner vendors. It is generally dubbed to be a parallel of eBay, or more appropriately iTunes, for on-demand applications. This is a great concept: a central place or “marketplace” online where an end user can subscribe to on-demand apps. Building up such a marketplace is hard work, requiring a certain self fueling network effect of attracting developers to build applications that will attract end users, thereby making the marketplace more appealing to a new set of developers. Salesforce.com is keenly aware of this, and their goals of bolstering the AppExchange probably push them to embrace the said network effect. So what sounds more appealing if you are a prospective vendor recruit: to say that you will participate in an AppExchange that has 350+ (actually, today they say 400+) applications with no qualifiers as to what an application is defined to be, or to participate in an AppExchange with an appropriate taxonomy that could yield a much smaller number? If I was considering Salesforce.com as a platform for me to develop, I would definitely hope to exist within the well established AppExchange version that has 350+ applications! Keeping the network effect flywheel spinning is important to the success of AppExchange. Making sure that the numbers are high add that much more of needed mass to maintain the momentum of that flywheel.

If we look at this “ecosystem” of 350+ applications, what is the breakdown? What might a stricter taxonomy look like? I recently compiled a list of these 350+ applications (I came up with 343, but I may have missed 8+) to do a little investigation. I found some wonderful tidbits of information. Did you know that at the time I retrieved the data (week of October 2, 2006)…

  • …24% of all listed applications were built by Salesforce.com rather than by partner vendors
  • …that 6 out of the 8 (that’s right, 75%) “Most Popular” applications are apps built by Salesforce.com and that are free.
  • …many of these apps extend the Salesforce.com main application functionality in ways that would traditionally classify the said “app” as a “plug-in” (Seriously, would anyone classify Clippy or the Microsoft Equation Editor as applications, or analogously would you buy a “song” on iTunes that was a Snare Drum Loop?)

While to some this may seem unimportant, it is in fact quite important when trying to create a metric for measuring AppExchange’s effective mass. I doubt a doctor taking your weight during a physical exam would accept 80 lbs of lead in your pants as part of your weight, which is why I look at AppExchange from this “no lead in the pants” perspective. Deducting the 24% of AppExchange entities (I will not call them “apps” until I know which are, in fact, “apps”) that are built by Salesforce.com, somewhere near 260 of the remaining AppExchange entities are built by partners. Of these vendor entities, some subset would normally be classified as true applications. (Please, do not misconstrue this as a poke at the vendors. They are exercising an opportunity, so Kudos to their efforts;-)) In addition, 75% of AppExchange’s most popular offerings share two things in common: they are made by salesforce.com and are free. While there is a certain “duh” factor associated with “free” and “popular”, one should not discount the fact that more valuable items that cost money are not outranking something of much lower value, even if it is free.

So I ask, where is the app in AppExchange? Is Apex their vehicle to allow for the permeation of the more traditional notion of “software functionality” into the AppExchange? Is their another player that can deliver something better? Only time well tell. My gut feeling is that some of these questions will be answered sooner rather than later.

Information and Links

Join the fray by commenting, tracking what others have to say, or linking to it from your blog.


Other Posts
Think Historically When Choosing a SaaS Platform
Salesforce.com’s Apex: Benioff’s Handcuffs for On Demand



Write a Comment

Take a moment to comment and tell us what you think. Some basic HTML is allowed for formatting.

Reader Comments

[…]  SF.com seems to charge  money for products to appear there,  but it seems that the partners  aren’t really making money themselves.   SaaSblogs provides a detailed breakdown. If we look at this “ecosystem” of 350+ applications, what is the breakdown? What might a stricter taxonomy look like? I recently compiled a list of these 350+ applications (I came up with 343, but I may have missed 8+) to do a little investigation. I found some wonderful tidbits of information. Did you know that at the time I retrieved the data (week of October 2, 2006)… […]

[…] Salesforce.com, a company that has found success in providing hosted customer relationship management solutions, will likely be able to increase their value to existing customers by offering more and better ways to expand upon hosted CRM. This may include creating a thriving marketplace and ecosystem for developers who build solutions that integrate with Salesforce’s own CRM offering. Sinclair Schuller’s recent analysis of what’s available on AppExchange supports this–it’s an architecture for Salesforce plugins and extensions, not a platform for generic, hosted application development. […]

[…] Sure it seems like a kind-hearted message with success written all over it, and it is undeniably unified in its presentation.  But now couple that mantra with the technological implementation that is Apex and here is where the meat of my questions arise.  According to their own Apex landing page, Salesforce.com wants you to create the next Salesforce.com using the ”same tools that salesforce.com’s own development team uses to build” [salesforce.com].  Besides being a lot of Salesforce.com’s in one sentence, this seems like a cleverly veiled way of saying “we’ll let you build the next Salesforce.com, but no better.  And we’ll keep you from doing this by giving you only the tools that we give our own application developers (or gave them months ago)… who you may ultimately be competing with.”  Remember, a good deal of Salesforce.com’s AppExchange apps are indeed of their own making.  See, this way Salesforce.com’s own developers define a ceiling… a gaurded gate through which the ISVs they are ‘enabling’ cannot surpass them.  You see, you can’t really create the next Salesforce.com, you may be able to create what Salesforce.com is today.  Tomorrow Salesforce.com will have progressed, and then you can try to be that.  Sound fun?  Sound endless?  By bringing in developers through Apex, Salesforce.com is swallowing competition in an enterprise application market that it is certainly not abandoning.  Is Apex simply a vehicle for making sure that Salesforce.com stays ahead of the game?  After all, if you outgrow or otherwise find little need for the tools provided to you by Apex, you pretty much have to dismantle your application and start over on a different technology stack - putting you far far behind.  Sounds kind of Borg-ish to me.  Come to think of it… didn’t we talk about the risks of this thing called lock-in before?  In the case of Apex we might be talking about lock-in through assimilation!  Heck, you even have to learn the Apex language.  I rest my case. […]

Re. Sinclair’s comment;

“ Is their another player that can deliver something better” ?

Of course there will be. “Software Windows to the World” will exist! ISVs,VARs,and End Users, be they Individual, SMBs and right up to the largest of Enterprises, will not have to go anywhere else to instantly sell/rent or use software apps. - When a complete, true and simultaneous worldly accommodating SaaS enabling middleware is fully developed and offered, Google, Yahoo, AOL, Baidu etc. will jump all over this technology, as they have no “bone to pick” with tens of thousands of ISVs, as SaleForce may have.

A company offering this complete and true SaaS enabling technology will have to:

- be able to SaaS enable and post apps in days, not years, without access to the vendors code.

- Will enable the vendors to upgrade their apps without taking millions of simultaneous users off line.

- Will ensure multi-tenant users single tenant security.

- Will enable Google. Yahoo etc. to offer software programmers to click on and SaaS enable their own apps.

Scoof if you will, there is at least one company whohas thia Wholly Grail of SaaS enablement. And for you scffers - isn’t it silly that - when we look back to before the times of the www and the Internet and remember that we could only install apps on our own PC and only use these already outdate apps there, that many of us have difficulty accepting the fact that the www means sharing and that soon we will be able to do so with essentially any software program ever written.

Ted

Ted,

The days for such a platform vendor to exist are much closer than you think!

Keep tuned for more exiting news and progress about SaaS.

Abe.

While you did not say much in terms of word count, you did say a whole lot in terms of content.

You are also a much better speller than I.

Do you know of such a company that fufills all of the needs and removes all of the pain for all participants in Software as a Service?

Ted

Hi Ted,

We (Apprenda) will be releasing a technical preview of SaaSGrid soon. SaaSGrid levels the playing field when it comes to implementing SaaS offerings, act as an “operating system” for the web applications it hosts.

In terms of removing all pain for all participants, I think the primary takeaway is that having a platform in place allows for Apprenda to respond to market needs or the addition “new pains” or “new participants” in a fashion that benefits all those using it.

-Sinclair