Tuesday, January 15, 2008

The difference between "ASP", "On Demand", and "SaaS"

What is the difference between ASP, On Demand, and SaaS?

I am frequently asked about the difference between the terms: Application Service Provider (ASP), OnDemand, and Software as a Service (SaaS).

Simply put, OnDemand Software refers to the delivery of software over the internet on a subscription or per transaction basis. OnDemand software is created in one of two ways. The first option, (v1.0) utilizes an ASP to convert legacy software applications (software that was not designed to be deployed over the internet) and the applicable hardware to fit the OnDemand definition. The second option, (v2.0) is for Independent Software Vendors (ISVs) or SaaS Enablers to develop the software from the ground up in accordance with the SaaS concept.

On Demand or “OnDemand”

OnDemand software refers to software that is:

(1) Accessed via a commonly used protocol such as the http (web)
(2) Priced in a cost-effective manor (subscription or per transaction versus capital investment)
(3) Requires the ISV or OnDemand company to maintain the software (often with the use of service level agreements or “SLAs”)
(4) Is hosted or resides at a centralized facility
(5) Capable of of immediate quick utilization (hence “on demand”).

As stated above and clarified below, there are two ways of making software available OnDemand.

Application Service Provider (ASP)

The concept of ASPs is far from new. Non-internet ASP models evolved piror to the conception of the internet. The airline industry provides an example of a non-internet ASP concept. I recommend visiting the article found at http://computer.howstuffworks.com/asp1.htm to further understand the concept of a non-internet ASP.

ASPs on the internet were the first companies to deploy, host, and manage access to traditional software (i.e. packaged) applications to multiple clients from a centrally managed facility. The traditional software applications and hardware infrastructures were converted to allow clients the ability to access the application over the internet instead of installing the software onsite.

As a result of this new delivery method, software pricing models began to change. Now that the ASPs had full control of the software, payment could be collected on a “pay-as-you-go” or “per transaction” basis. This revolutionized the software industry mainly because customers who normally could not afford the capital investment of software could afford a subscription based model. Think of ASP’s as the version 1.0 enablers who took existing applications which where not intended to be web-accessable and made them available to clients over the web for an affordable investment.

ASPs lead the way for delivery and pricing software as a service instead of consumers purchasing a software product. ASPs have several limitations based on the development of legacy software. These limitations are what lead to the concept of building and delivering new software in the SaaS model.

Software as a Service (SaaS)

You probably have a good feeling of what SaaS is now. SaaS is a model of software delivery (all activities that make a software available for use). Software in the SaaS model is paid for on some form of consumption basis (rather than the traditional perpetual license) and the application and server side hardware infrastructure is hosted, maintained, enhanced, managed, and upgraded the SaaS provider.

Links for more information

http://www.idc.com/getdoc.jsp?containerId=33453&pageType=PRINTFRIENDLY#33453-S-0001 - IDC 2005 software as a service taxonomy and research guide. This is a great research paper for anyone interested in SaaS.

http://www.wikipedia.org/ – This is a great site to look up definitions such as OnDemand, ASP, SaaS, ISV, etc.

Saturday, January 5, 2008

The Evolution of Software Licensing

Traditionally, software licensing strategies have been dominated by the concepts of fear and piracy to embed complex licensing and/or cumbersome licensing schemes into perpetually licensed software products. This tactic has proven to be highly profitable for market leaders in this space such as Macrovision and generated strong industry wide competition and innovation from competing companies such as SafeNet, Reprise, and Agilis.

The problem with a perpetually licensed approach is that the bells and whistles embedded into these schemes are often misused by customers and create customer dissatisfaction and resentment. Complex licensing schemes are difficult to implement, hard to maintain, and difficult for customers to use. Additionally, these schemes often prevent honest customers from purchasing additional seats because it is difficult to monitor usage. Finally, companies who make use of all available licensing features often find they have created a product management nightmare.

Honest customers want to remain honest and comply with the terms of licensing agreements. Software companies want to protect revenue streams by ensuring compliance and preventing piracy, as well as expanding usage. Meeting all of these demands in the perpetual licensing model is difficult at best.

The SaaS model solves this problem by being inherently tied to the concepts of subscription and usage. The majority of SaaS applications today make use of basic username/password authentication schemes to grant access to all or some of a SaaS based application. This model is much more eloquent than having to request or reset perpetually based licensing features. In this model, the burden of license management is removed from the customer and passed onto the product management function of the SaaS provider. Successful SaaS applications build restricted access relationships into the offering and tie roles and rights to an authenticated user. Thus, when companies want to add users or subscriptions there is typically a self-service module to facilitate such requests and existing agreements or credit cards are charged appropriately without modification.

For SaaS companies that have considered the product management aspects of subscription or metered consumption before deploying their SaaS application, this is a wonderful model for facilitating additional usage and/or subscribers. For those companies that have not thought through subscription access, there is a strong market need for the development of a SaaS based subscription management service that assists SaaS companies in managing and developing subscriptions within their SaaS applications.

Nevertheless, the SaaS based licensing model provides an eloquent evolution for license management.

Sunday, December 23, 2007

SaaS Advantages - The Customers Perspective

Why would you or your company consider using software deployed as a service, i.e. Software as a Service (SaaS)? There are numerous resources and discussions on the web about the advantages and disadvantages of utilizing SaaS as an alternative to purchasing a perpetual license. If you would like further insight on SaaS and its evolution, please see The difference between “ASP”, “OnDemand”, and “SaaS”.

Ultimately, the customer has the upper hand! These days, competition within the software industry is fiercer than ever. Software products and services are plentiful. With the abundant number of available solutions, clients are likely to find software for their needs delivered in both the traditional “product” model and the on demand SaaS “pay and use now” model. In some cases, SaaS providers have a hybrid model allowing customers the ability to choose from SaaS or software as a product. With this approach, clients can move from one delivery model to the other as the need arises. This hybrid approach may seem slick, but challenges arise and clients may find additional costs associated with data migration, scalability, and additional user training.

Why should the customer choose SaaS?

Choosing SaaS instead of a perpetual license has many advantages for both the small and large business. Small businesses typically can earn the highest return on investment utilizing SaaS. They benefit from technology that, originally, only larger businesses could afford or develop. Below are the top five reasons why a customer of any size can benefit from software as a service. Each of the benefits listed below are integrated. For example, the customer is up and running quickly. This is a benefit on its own, but at the same time, a fast deployment will reduce cost of system implementation for the customer. In summary, SaaS allows customers to speed implementation, minimize implementation expense and risk and overcomes in-house IT infrastructure.

1. Price!

The traditional delivery of software is almost always considered a capital or “upfront” investment. With the SaaS model, the customer pays as they consume the software. This helps by removing the barrier of entry for individuals who would not ordinarily be able to afford the software. The new pricing model also helps organizations using SaaS to appropriately budget software costs for future consumption. Unlike traditional software that can have significant hidden costs (additional modules, large setup fees, or additional hardware) the SaaS model has few up-front unknowns. (Note: Customers should still be aware of integration and scalability costs!) The number one benefit of SaaS is that the cost associated with building (or purchasing) and maintaining the SaaS solution is spread over a number of customers. This leads to shared costs and subsequent reduction in the cost of the software per customer.

2. Up and running quickly!

With SaaS or OnDemand software, onsite hardware or software installation is not required (in some situations minor installations may be required). Customers are up in running in hours or weeks instead of months or years (hence the name “OnDemand”). Following a configuration period, the user is typically “up and running”. Due to the nature of the SaaS delivery, users can typically run a free trial before purchase. A free trial can cut down on the amount of time it takes to complete the due diligence phase of purchasing software, which leads to a shortened implementation timeline.

3. Low risk!

Since users rent versus own the software, they are typically in a “pay-as-you-go” or “per transaction” pricing structure. There are almost always Service Level Agreements (SLA) that allow the customer to back out of the contract if the SaaS provider does not meet the agreed upon service requirements. If the software turns out not to fit the customer, the customer can “opt out” before they spend too much money. (Be aware that even with SaaS, there are several additional costs such as change management, training, integration, and setup).

4. Reduced IT headcount!

Due to the nature of SaaS, customers can use the software with thin client technology. This means that software no longer needs to be installed on PCs, which significantly cuts down on IT involvement. For the most part, customers do not have to worry about hardware, database support, scalability, uptime, reliability, or platforms. Since the SaaS provider is responsible for hosting, managing, and enhancing the software application, the customer can reduce and reallocate (or remove) the amount of IT staff and dollars to other areas. IT professionals, much like surgeons, are usually highly compensated and very specialized. By building software to fit the SaaS model, customers can eliminate specialized IT infrastructure for the application and its respective supporting applications. SaaS providers often have more application experience than in-house staff, leading to more quality software applications. Since the SaaS provider is responsible for providing these resources, each resource can be highly utilized and paid for over several customers.

5. Security & Data backup!

SaaS providers utilize more stringent security measures than the customer would. The SaaS model means that costs are shared amongst all the users, therefore there are typically more resources and funds to allocate to security than if one organization had to do this on their own. This applies to data backup, since the SaaS provider is also responsible for ensuring the safety of the data. There are more resources, so regular audits and detailed plans are used to ensure the safety of the data.

Links

Does anyone buy software any more by James Maguire? check here