(This first appeared in Ovum Straight Talk - thought it would be interesting here too)
Many software companies in the Western markets, most frequently the US, have set out to transition their traditional software products into software as a service (SaaS) offerings. However, this has not been an easy path and many have struggled to bring products to market on time or have not been able to tackle the architectural and scalability issues that are needed to produce an effective offering - whether it is based on multi-tenancy, or not.
The technical challenges in migrating legacy to SaaS are potentially enormous, and the simple implication from those challenges is that this is also a costly exercise for the Western-market software company. This is coupled with a desire to tackle those challenges and bring SaaS products to market in the fastest time possible, as the window of opportunity for accelerated SaaS growth is in the 2008-11 window. If SaaS offerings are late in that window then the opportunity for revenue growth is greatly diminished. Of course, few companies can prudently afford to throw money at the problem either, and so need to find cost-effective ways of tackling the difficult problems. This is further amplified by the current investment climate that is seeing many investments delayed or suspended. Enter R&D outsourcing and outsourced product development.
India and other offshore outsourcing locations have a chance to really profit from the opportunity, through R&D outsourcing. R&D outsourcing and outsourced product development are not a new phenomenon. The largest names in the software market, like Microsoft and Oracle, already make strategic use of outsourced product development in the desire to control development costs, and have access to an extended resource pool - without necessarily having to grow the fixed cost base associated with a larger labour force. Many companies have emerged that are benefiting from the opportunity, such as Aspire Systems, Aditi Technologies, e-Zest Solutions, ISHIR, and Sierra Atlantic. Some centres are even being established to focus on SaaS development, such as Morph Labs in The Philippines. The companies in India, and elsewhere in the developing markets, have developed strong expertise in tackling the engineering challenges that the SaaS transition brings, both through experience and through developing intellectual property based tools and processes that make the SaaS transition more predictable. They bring repeatable engineering practices to mature standards - CMMI Level 5 et al - as table stakes, but their capabilities are rich as well as repeatable. Indian companies that can productise their SaaS re-engineering efforts will be at a definite advantage here, as they'll be able to scale their business more quickly, offer more predictable outcomes and offer keener prices.
Advice - software vendors should strongly consider outsourced product development as a way to transition their products to SaaS.
Rather than simply, or not so simply, re-engineering software on either a fixed-price, time-and-material or another common contracting route, there is the opportunity for R&D outsourcing companies to play for the long game - and aim for gain-share, where they share in the rewards when the re-built SaaS offerings are taken to market. There is even potential for the braver firms to negotiate for shared ownership and control of the SaaS assets that have been developed. The niche where the outsourced product development company is able to co-invest in the SaaS development transition, in return for shared rewards, shows very exciting potential and we expect there to be some market action in this area.
Advice - outsourced product development services firms should focus on commercial innovation and co-development models, as a way to get a share of the long-term action.
Of course, there are alternatives to the R&D outsourcing that are also potentially complementary to it. Platform as a service (PaaS) is the most frequently cited SaaS development accelerator. The thinking is simple and reminiscent of traditional ISV thinking: ISV applications should use as many elements of an infrastructure based on open standards as possible, avoiding building infrastructure components like databases, application servers and other middleware that are unique to that ISV application. That way the maximum development cost leverage is obtained and there is maximum focus on the application functionality that customers actually use. Lots of PaaS plays have begun to be placed, beyond the Salesforce.com example that most cite. Here companies like Bungee Labs, Coghead, Rollbase, and NetSuite are also PaaS players. Initial customer references such as CODA2go sound promising. However, there is a real danger of lock-in from the ISV perspective. Just like no self-respecting ISV would have targeted only a single database vendor, so no sensible ISV should tie itself to one PaaS provider - being able to switch providers is the whole point of SaaS models. Therefore standard and interoperability developments are going to be needed, otherwise PaaS will become the next proprietary lock-in of the future and one set of market concentration will be replaced by another. Net result: the market is no freer and customers don't have the wider set of choices that they hoped SaaS would provide.
Advice - although PaaS looks attractive, ISVs need to consider the lock-in implications before they commit, and carefully evaluate alternative strategies.