It will be, for many, the end of a error that has too often wrongly cast software vendors in the role of evil perpetrators of bad technology, while sucking billions of dollars out of IT budgets and frustrating attempts at deriving cost-effective value out of enterprise software. In that role, the SIs wont be missed by anyone. But their exit from the enterprise applications scene, or a least a diminution of their role, will also be the end of a major channel for big software vendors like SAP and Oracle, and a major source of revenue for everyones favorite coopetitor: IBM.
In other words, SaaS promises to upend one of the time-honored fixtures of the enterprise software world, and do so in a way that will be highly disruptive for the vendors. But as disruptive as it might be for vendors, the demise of the SIs would spell a great day for the end-user community. As long as SaaS is there to take their place.
Dont get me wrong, we will still need the expertise in integration and customization that only SIs can bring to the table. With vendor products still more generic than specialized, the added competitive edge that customization can bring will still require some intervention on the part of SIs. But the classic big implementation project the ones that cost anywhere from two to ten times the software license cost are clearly on the way out. And none too soon, in my book.
What is ironic about the whole mess is how laissez-faire laissez screw-up, really most vendors have been about what SIs have been up to lo these many years. This despite the fact that every ERP failure lands the vendors name in the headlines, while the real culprit is the implementation partners mismanagement, greed, and incompetence (often in cahoots with IT and business management at the customer site, to give bad credit its due.)
Next page: Am I being too harsh?
As someone who has reviewed dozens of failures over the years, its clear that the times in which bad software killed a project are virtually non-existent. Whats more common is the projects were poorly run, that specifications werent translated in to a workable system, go-live took place before the data transfer was verified and the users trained: All of which gave the appearance that the main goal of the SI was to latch on to the client and suck as much revenue out of the project as possible, while hopefully leaving things messed up enough to guarantee the project extensions and modifications that could turn the project into an annuity for the SI.
Am I being too harsh? Even when things have gone remarkably well, and the majority of project have been successful, the cost burden of the traditional SI implementation has hampered attempts to get total cost of ownership under control and deliver a genuine return on investment. Again, this isnt just the SIs fault, the vendors have been colluding with them along these lines for years. To the mutual benefit of all. But if you look at the money pot that has flowed into enterprise software over the years, too much, way too much, has ended up with the SIs certainly with respect to the value they have been able to deliver.
So heres to SaaS and its upending of one of the worst things about enterprise software. Marc Benioff of Salesforce.com has definitely exaggerated when he talks about SaaS representing the end of software. But SaaS is definitely heralding the end of the SI, at least with respect to bloated projects that fail to deliver anything but excessive costs. Their demise will be a good thing, even if it means that the vendors have to find a new channel for selling high-end projects to big companies. Its time for the industry to move beyond these issues, and I for one wont miss those over-priced implementations one little bit.