Skip to main content

SaaS is going Mainstream



image Source: Wikipedia, the free encyclopedia
The headline depicts my impression from a Research Note written by Burton Group's analyst, Craig Roth. The Research Note describes and analyzes the results of a new SaaS survey conducted by Burton Group and Ziff Davis Enterprise.
It is not just a survey. Some of the participants were asked to explain their answers. The explanations provide another layer of understanding: Why (explanations) in addition to What (the answers).
Some of the findings are in accord with my expectations (I assume that my expectations are not very different from expectations of other people who read articles on SaaS), but there were also findings I would not expect to find.
It should be noted that all the 318 participants reside in USA and Canada, therefore extrapolating the conclusions to other parts of the globe could be misleading.


Reasons for implementing SaaS
The obvious reason is cost reduction, but a lower cost was not the most frequent reason for interest in SaaS applications. The most related reason was "No in-house Maintenance", which could be positively correlated with lowering costs.
Surprisingly, the second, third and forth frequent answers are more related to Agility than to lowering costs (Shorter roll out time, Usable anywhere via internet, Faster improvement cycles).
Reasons for avoiding of SaaS implementations
As expected the leading reason for not implementing SaaS was Security risks. However, those who implemented SaaS experienced rarely Security breaches occurrences.
The second frequent reason was Unavailability in case of inability to connect by the internet.
and the third frequent reason (less customizable) also fit to my expectation.
The surprising findings are the low frequency of citing "Less functionality". I would also expect to find integration between SaaS and Data Center applications to be cited frequently. However, that was not what Burton Group and Zif Davis Enterprise found.
Applications
The most popular SaaS applications are Web Conferencing and CRM. CRM is expected to be used frequently due to SalesForce.com effect. As expected, applications used for SaaS are applications which are standalone (e.g. HR, Surveys, e-mail) and are less used as connected systems.
Least cited applications were ERP applications.
Charging Model
I expected that the preferred charging model would be related to usage and or capacity, but actually most of the participants preferred Flat Fee Enterprise Model.
Probably, this model would be more expensive than charging by Usage and/or Capacity models.

My Take In my opinion the bottom line of the survey done by Burton Group together with Ziff Davis Enterprise is very clear: SaaS is going Mainstream.
The following bullets include my view of the surrey's results:
  • Agility is a leading reason for selecting SaaS applications. This finding illustrates the similarity between SaaS and SOA, which is driven by the quest for Agility.
  • The old Service Bureau charging models of the 60s are still valid. Service Bureau Customers preferred a simple and stable charging model over a more accurate and complex charging model. I do think that more flexible models are better fit for Cloud Computing. It looks as if SaaS consumers are not yet able to adapt Out of the Box thinking and therefore stick to the Data Center Enterprise License model.
  • The issue of integration between local and SaaS applications was lacking from the list of reasons to avoid SaaS usage. This issue matters more to large Enterprises and especially for Business Intelligence purposes.
Why is this reason lacking from the list?
Is it because SaaS implementations are not yet mature?
Is this reason (Integration), which was not cited, at list a partial explanation of more benefits realization
by SMBs than by Large Enterprises?
  • Types of applications implemented by SaaS model is a key issue. Core Systems implementations is an indicator of SaaS Maturity. Burton Group's analyst thinks it is not yet matured. The low rate of ERP usage sustains his view. NetSuite was the first company to offer SaaS based ERP. Other companies will probably follow NetSuite.
  • Even though, SaaS is not matured it is going Mainstream. The majority of enterprises deploy SaaS applications. Mainstream technologies should not be confused with Mature technologies. Mature technologies could become non Mainstream e.g. pre-relational databases like IMS or Adabas. A very good example of Immature Mainstream technology is Enterprise Client/Server Integrated Development Environments (IDEs) in the middle of the nineties.
  • Burton Group's analyst Craig Roth concludes that SaaS is immature. The immaturity is manifested in the type of applications used frequently in SaaS model. Maturity will be manifested by more frequent use of SaaS model for Core Applications such as ERP.

Labels:

Comments

Post a Comment

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...
16 comments
Read more

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...
11 comments
Read more

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...
8 comments
Read more