Thursday, July 23, 2009
Survey: IBM ISV Plans for SaaS Development
We recently held a joint webinar with IBM to describe a methodology for ISVs to migrate to SaaS and cloud computing cost-effectively (you can see the recorded webinar here). The key is being able to leverage existing data and logic while moving iteratively to deliver web, SaaS and Cloud capabilities that provide the biggest value to the customer at the least cost and risk to the software developer.
During the webinar, we conducted a survey of the ISV attendees that turned up some interesting results about where ISVs are along the SaaS migration path and where they would like to be in 12 months.
We defined a SaaS maturity model with 5 levels:
Based on this maturity model, attendees first told us where they are today. The following pie chart shows how ISVs rank the maturity of their existing products. Note that over half of the ISVs put themselves at the most basic level - web-enabled application.
Next, we asked ISVs where they would like to be in 12 months. The following pie chart shows where ISVs would like to see their product offerings in 12 months. Note that the bulk of ISVs intend to deliver self-service customization, but fewer ISVs plan on moving all the way to a multi-tenant, cloud-scalable solution over the next 12 months.
Admittedly, this survey data is more anecdotal than rigorous (there were only 35 respondents). However, it is an interesting indication that ISVs are looking for an incremental methodology for migrating their applications to SaaS, rather than a big bang approach in which the ISV does a complete rewrite of their software.
Resources:
During the webinar, we conducted a survey of the ISV attendees that turned up some interesting results about where ISVs are along the SaaS migration path and where they would like to be in 12 months.
We defined a SaaS maturity model with 5 levels:
- Level 0: web-enabled. The ISV's application can be accessed through a web browser without requiring the end user to install anything on their desktop.
- Level 1: hosted. The ISV's application can be hosted without requiring the customer to install anything in their data center.
- Level 2: self-service. The end user can customize an application (e.g., configure dashboards, reports, data, workflow) without having to do any coding.
- Level 3: multi-tenant. The ISV can support multiple customers with a single application, database and security instance.
- Level 4: cloud scalable. The ISV can deploy their appplication within a cloud infrasctructure that automatically scales up and down based on load.
Based on this maturity model, attendees first told us where they are today. The following pie chart shows how ISVs rank the maturity of their existing products. Note that over half of the ISVs put themselves at the most basic level - web-enabled application.Next, we asked ISVs where they would like to be in 12 months. The following pie chart shows where ISVs would like to see their product offerings in 12 months. Note that the bulk of ISVs intend to deliver self-service customization, but fewer ISVs plan on moving all the way to a multi-tenant, cloud-scalable solution over the next 12 months.
Admittedly, this survey data is more anecdotal than rigorous (there were only 35 respondents). However, it is an interesting indication that ISVs are looking for an incremental methodology for migrating their applications to SaaS, rather than a big bang approach in which the ISV does a complete rewrite of their software.Resources:
- Click here for more about IBM's SaaS enablement program
- Click here for more about the SaaS maturity model
Labels: saas, saas development, saas migration
Subscribe to Posts [Atom]