Last week reader Chris Young of B2BSX made the following comment:
“I am interested in your perspective on how customer to customer exchange of custom development may impact both the rate of innovation in the community of companies using SAP and also the total cost of deploying and operating SAP…I see a tremendous opportunity to leverage much IP around the landscape.”
The tremendous opportunity in what Chris calls customer-to-customer exchange in the business-to-business arena (C2CXB2B, anyone?) has been apparent since the heyday of e-marketplaces in the 1990s, when so many people were awestruck by the Web’s ability to disintermediate business relationships. The idea of disintermediation was hot in B2B because people had already seen how the consumer Web successfully encroached on the turf of once-unassailable middlemen such as travel agents and brick-and-mortar stores.
I see a direct link between the e-marketplace paradigm and the Web 2.0 paradigm to which Chris is making an oblique reference in his comments. Both are do-it-yourself (DIY) paradigms that emphasize the way in which traditionally real-world interactions — such as partner discovery, negotiation, and sales — can be ported to the Web and de-emphasize the role of gatekeepers. As it turns out, however, the customer-to-customer idea behind these paradigms has had only partial purchase in the B2B world. Despite the presence of any number of startups out trying to convince VCs that the business Web will go the way of Facebook, the business world has stubbornly resisted the idea.
Salesforce.com’s AppExchange is an excellent case in point. Some years ago, Salesforce.com took a visionary direction, deciding that its future lay partly in becoming a platform for applications that customers created, shared, and sold to each other. AppExchange never did as well as its analogues in the B2C world — iTunes, for example — and Salesforce.com is still, in revenues and perception, overwhelmingly a CRM provider. To me, that proves that the time is not right for customer-to-customer exchange in the B2B world. Most of the customers still prefer dedicated mediators between themselves and the products they buy; in other words, customers want to deal with vendors, systems integrators, and consultants, but not necessarily with other customers.
If you’ve spent any time in the world of open source, it’s apparent why this is the case. When you buy something from another customer, there’s little control and less support. The fate of your module (or whatever you’ve bought) could depend on finding a long-buried technical post on some obscure open source website. Coders don’t answer phone calls. Forums are only sporadically updated and maintained. The person who created the code leaves the company. Whatever the case, the bottom line is that buying technology or technology customizations from your own peers isn’t a predictable experience. You get what you get, and a lot of enterprise buyers simply don’t want to take that shot in the dark. It’s not a good risk management move. Of course, the economics change downstream, where risk management is outweighed by budget constraints. But if you’re a larger company, why not spend the extra money getting customization straight from the vendor or from a vendor-approved partner?
I don’t necessarily agree with this dynamic, because I am an enthusiastic user of open source who loves the idea of disintermediation, but I do think that it exists, and it is the reason behind very slow enterprise adoption of customer-to-customer, Web 2.0, or any other flavor of the DIY Web. I’d welcome a debate on this topic, especially now that SAP is making noises about exposing its underlying SOA to community-designed custom mini-apps and interfaces. Leave your comments here or email them to email@example.com.