Dreamforce05, Seismic Shift
It’s very rare that you get clean demarcations between historical eras. Maybe the asteroid hitting the earth 65 million years ago was such an event but I wasn’t there to experience it so I can’t tell you. Monday September 12, 2005 will go down as a deep line in the sand identifying the before and after in the enterprise software industry. It was the day that Siebel agreed to be acquired by Oracle and coincidently the day that Salesforce.com opened up its Dreamforce user conference in San Francisco.
The two events were like bookends and this is as much about Oracle as it is about the rivalry between Salesforce.com and Siebel because in one day Oracle conceded any pretense of being a leading software industry innovator while Salesforce.com happily crowned itself. In all cases, the driving factor was not so much technology as it was business model and finance. Let me explain.
Oracle has been dominant in application development for a long time. Since the 1980’s, first its database and later its tools and its enterprise business applications set the standards for how computing is done for big companies. Oracle ultimately spawned numerous software companies — Siebel and Salesforce.com among them — that essentially followed the same model of building large suites of software that enterprises would spend millions to license and millions more to configure, customize, install and train end users to operate.
But the model was getting old. It was challenged by Salesforce.com more than five years ago and the upstart company with the brash slogan of “The end of software” got away with its challenge turning itself into one of the fastest growing software companies and a public company in only six years. Meanwhile, Oracle, Siebel and all the others were content to play the part of lumbering dinosaurs.
Monday changed all that: on that day Salesforce.com presented to the market its second major disruptive innovation in enterprise software when it announced Appforce and ApplicationExchange, two products that would definitively put an end to the tedious and expensive way we have come to believe enterprise software can and should be built.
Briefly, Salesforce announced that its users and partners could now use the Salesforce.com architecture to their hearts’ content to build any applications they want. More importantly, Salesforce.com through its ApplicationExchange lets all of these people evaluate, rate and purchase applications made by others for their own use within the hosted service. All applications built this way have the same underlying database, operating environment, look, feel, and security. And they can be manipulated and customized using the tools used to build them.
For the first time in history application software development does not require a heavy investment in infrastructure, all that’s needed is a PC with an Internet connection and a browser. With such a low barrier to entry we can reasonably expect to see a swarm of new applications hit the market developed by people on the other side of the planet in economies with very different — read lower — measures of fair value for work. But it also means that if you have a garage or a spare room and a PC you can be in business too.
It is equally important to observe that with an online marketplace for enterprise software — which is effectively what the ApplicationExchange is — the cost of selling and marketing software will also come down significantly. “Frictionless” sales and marketing are words that come to mind here. Fewer people will be required to do the work so emerging software companies will not require the same amounts of money they once did and that will have a profound effect on the venture capital community.
While we’re at it, the systems integration community is in for a shock of its own. Salesforce.com demonstrated how applications developed independently using its platform technology could integrate — automatically — with whatever else a customer is using from the vendor. Translation: you can take a test drive of new software with your own data at your leisure; there will be no more elaborate demos and proofs of concept.
The New Software Economy
In short, Salesforce.com introduced the world to a whole new software economy on Monday, the same day Oracle gave up on innovation and a week after Microsoft more or less did the same. Talk about inflection points. At Dreamforce, Salesforce.com CEO, Marc Benioff, compared Oracle to Computer Associates (CA) the company that bought up a number of mainframe software companies at the end of the mainframe era. CA’s strategy was to simply milk the maintenance stream until customers upgraded to client-server systems. Now, Oracle, the company that led the charge into the relational database era and client server computing, finds itself in a similar position.
You might ask why companies, like Oracle and Microsoft, which are full of smart people, would take such predictably suicidal turns. And while the answers are numerous and complex, I think you need to look closely at business models and the financial community. Companies are founded on certain assumptions about how they make money (business model) and how much they can make (margin). The traditional client server model which is dying has a built in expectation of revenues and margins and so does the on-demand model. Unfortunately, the financial community simply wants to know how well your model worked in the 90 day period just ended. In that way the decline of a business model is like boiling a frog.
But each successive model in this industry has offered orders of magnitude lower costs to the buyer — and lower margins for the vendor. Ultimately, I think it’s far easier for a company to burrow in and milk an installed base than it is to change its model and re-educate the public markets about the realities of doing business in a new era.
So rather than smooth transitions from one era or style of computing to another, we have seismic events like we saw on Monday. Don’t look for everything to change literally over night; these things can take years — client-server took a decade. There’s still work to be done building out the model, Salesforce.com is not the only player, and it may not ultimately be the one that gets all the way to the goal line. On the other hand, a decade might be far too long. I started writing about this new model two years ago in a white paper called “The New Garage” and I was very surprised at how quickly yesterday arrived.
You must be logged in to post a comment.
If we are talking about what’s great about Salesforce.com, do we discuss the method of delivery (subscription) or content (how well this tool works in implementing the CRM vision). All the industry buzz seems to be about the method of delivery. Salesforce promises low cost, seamless and trouble free implementation. From my experience, the difficulties associated with getting a CRM project up and running have nothing to do with the method of delivery, but everything to do with transforming company culture.
This is a good point and one I agree with. Software is still a challenging undertaking. The reader suggests that implementation partners are a key to the solution, and they are, and I think we’ve seen companies like Accenture making pacts with Salesforce for implementation work. But the fact remains that because Salesforce is easier to use, there will be less need in some cases for assistance and more line of business people will be ablet to customize applications without going to IT for help.
salesforce undoubtedly has a strong model which appeals to a huge number of companies – ourselves included. 75% of our staff have salesforce licences and it provides a 360 degree view of our business.
all great… NOT QUITE. Just because the software is easy to “install” – pay the $50/month. However, what is missed by many (most) is that you still need to run the implementation project which means involving business users in how the business should change to take advantage of salesforce, configuring salesforce.com, training the users on the new processes. In short – change management.
Without this the application will not be used correctly, consistently and you will fail to get a ROI – just like Siebel, but a lower cost.
This “no implementation” problem is rife at salesforce clients as the licence churn is high. The larger the client the bigger the problem. Cisco – their flagship client is stalling… http://ideas-warehouse.blogspot.com/2005/09/salesforcecom-hits-adoption-challenges.html
The answer – sign-up implementation partners who make money for implementation consulting…
The trick is enabling these thousand points of lights. Let the people who know what they want create what they need – without barriers to infrastructure. The icing on this cake lets them sell it to other who has the same need. How cool is that? Have you been to doctor’s office lately? These folks are slave to expensive highly specialized software that is not very intuitive to use, and impossible to integrate with other software stack they depend on. Imagine all the doctors you visit can easily access all health information about you, with your consent. This is just one example of highly specialized sector that can benefit from a doctor who decides to write up an app on appexchange, and make it available for other docs. Imagine how many needs are out there that we do not know of. Imagine the possibility. Way too cool!!!!
I like the electricity metaphor. As with a lot of things in business, I suspect the new electric motor simply replaced the water wheel purely for economic reasons. In other words, the investment had to be written off before fundamentally different and better approaches took hold.
In this situation, we have an infrastructure-less infrastructure so it could be that we will see much faster write-off and new adoption. I wonder if anyone at Oracle is thinking about this?
Yes, I agree that Oracle’s purchase of Siebel looks like a grainy VCR replay of CA’s strategy 15+ years ago. It even applies to the personalities: Charles Wang was unpopular then, and Larry Ellison carries that same mantle today.
A combination of on-demand and Web services are brutally reshaping how software is developed and delivered. To use another historical analogy, it’s similar to the shift in the U.S. from water to electrical power. When mills used rivers to generate power, the technology was a big behemoth of a water wheel that transfered power via belts and pulleys. When electicity came along, it awhile — about 50 years in fact — for companies to get away from that centralized view. Initially, businesses just put in an electric engine where the water wheel was and turned the same belts and pulleys. Only after awhile did they realize that the power topology had shifted: that they could put electic motors wherever they needed.
Like before, I think habit will be the greater constraint than the technology — but it sounds like Appforce and AppExchange will wake some people to rethink their habits.