SaaS v ASP – the business difference

by admin on July 16, 2006

in Cloud Computing/SaaS

John Clough of BDO raised a question behind AccountingWEB’s walled garden (sorry James) which has the makings of a lively debate. “What’s the difference between ASP and SaaS?” There is a lot of misinformation floating about among professionals on this topic so now is as good a time as any to offer an explanation. Here I’ll talk about the business promise of SaaS and pose the question: Does ASP offer any of this?

In my view SaaS’ technical underpinning offers the tantalising promise of changing the way business is done. Today, we tend to operate in departmental silos but the opportunity to meld and aggregate information from different systems using SaaS style offerings can change the way you work and the results you achieve.

If I think about WinWeb (a client), they’re bringing together a set of related business critical applications to make SMB’s lives easier using SaaS as a delivery mechanism. They offer components as modules you can tack into the base application. Each part fulfills a specific need and is addressed accordingly. They are, in effect, creating a platform for business. They can offer the accounting module for free to single users because they see other services as having a clear business value that customers will likely pay for. I agree.

Twinfield (another client), is looking at a range of options that splice their accounts app to CRM. They may well end up offering a mix and match approach where the customer chooses the best route for their business. That’s an interesting way of delivering choice.

When I look at how I work today – no on premise network, no cabling everywhere, no network management, no application management. In other words, a good 30% of my time cost has evaporated, allowing me to concentrate on things that matter.

Instead, I have a clutch of applications running elsewhere but accessible through browser tabs with automatic notification of information updates. I’m changing my billing to a service that automates the follow up I need but with manual over-rides. It’s set up with triggers so I don’t have to worry about debt collection. I have a shared space where I can easily work collaboratively with clients. I have another service that allows me to centralise document creation and storage but which allows me to provide secure access to clients on an individual or group basis. I can field multiple IM conversations with Skype.

At a different level, my interaction with people has fundamentally changed. All the services I use have a social dimension that allows me to discover new information about topics of interest at almost zero effort on my part. The only effort I need to put in is to add to the various discussions in which I’m interested. It pays enormous dividends. A simple example. Many sites have a list of sites the site owner likes. That provides me with an easy way to discover new people who have interesting things to say. I can change my lists any time I wish or any time my information preferences change. That’s happened many times over the last 10 months. It allows me to enrich information.

All of that’s a far cry from having a discrete accounts app, email, file storage, word processor etc etc. that are disconnected and require a lot of PC horsepower. And it’s a far far cry from having a single application hosted on my behalf as would be the case in an ASP accounting scenario. I’m no longer tethered to specific networks but can flit from place to place, depending on what I need to do at the time.

We’ve only scratched the services surface and I see massive opportunities for professional accountants. A pity the incumbent vendors have yet to appreciate the business opportunities. Anytime you guys want to engage – feel free. You all know where I am.

Does ASP offer any of these advantages? For those that want a dive into the technical differences, which serve as the jumping off point for the business discussion I’d recommend checking out what Phil Wainewright has to say about SoSaaS.

PS: This is an open ended, evolving thought stream. As I say, we’re barely scratching the surface.

Technorati Tags: ,

Comments have been disabled for this post.
Sort: Newest | Oldest

Thomas

I am pretty much with you on this one. I see SaaS as not just a rebranding of ASP in its entirety but more a demarcation of one form of ASP to to be able to place it in juxtaposition with other forms of ASP, most often the hosted provision of off-the-shelf boxed software a la Online50.

Some pundits have taken to defining ASP as limited to this latter category. Others have come up with the term SOSaaS (Same old SaaS) to describe hosting boxed apps, which makes Online 50 a form of SaaS which I find really confusing!

The following article has some interesting comments from some of the providers in the industry who are as entitled as any to pass comment on what they should be called:

http://www.aspstreet.com/archive/d.taf/what,show/l...

Alan

Thomas -- I see where you're coming from and I don't have a problem with that.

A lot of peeps get confused on this. I'm putting a stake in the ground. It may not be the best but it helps focus the mind. The way I see it: technical underpinning>business model>process change>customer benefit

Another thought - APS can still be batch but struggles to be real-time. SaaS has definite potential to be event driven as it is, by its nature and in MY definition, real-time.

SF.com could not do what they do if they followed a Corio style model. It's why IBM has a massive consulting business. They confuse it more by referring to certain hardware bundling deals as 'on demand.'

I still dont see a real difference, it is a way to rebrand ASP, and sweep
The technical changes Cote mentions about are not unique to SaaS, but they make it easier to deliver on the promises that were made in the heady days of ASP.

just look at the confusion in this post
http://blogs.zdnet.com/BTL/index.php?p=2513

It is the same thing, SaaS is just the trendier twin. It is that cute juxtaposition of lower and uppercase and daring to have a 4 letter acronym in a 3 letter world. Maybe I should write my name ThomaS.

I've kicked the same basic question around quite a lot over the past year. As much as I'd like to come up with a "real" answer, the one I always come back to is technological: ASPs were GUI-heavy, SaaS is web app based. SaaS usually has web services and WS-*, while ASPs had binary APIs or funky plain text ones.

Like I said, I'd like a better answer, but that's what I come back to every time.

We are getting closer than ever to launch ebdex Document Exchange. At entry level it could be used as a document generation engine. It has an Inbox and Outbox. Company A can generate an invoice on-line and post it to Company B. This service is offered free. Real value comes when your accounting/ERP/CRM is connected to the exchange. Then you can post an invoice (or any other structured document with supporting documents) from your system to ebdex Document Exchange for your customers to collect from their Inbox. A copy is retained on-line in your Outbox. In this case, we charge you for the transaction. Transaction fee is cheaper than a cost of a stamp. Maximum benefit comes when we can deliver that document to recipient's system directly, thereby automating document transmission and processing at recipient end. Depending on the size of organisation, recipients can save a significant operating cost in accounts payable function. Whilst this all sounds simple (it is simple except my developers disagree) there are complexities involved in exchanging documents with legacy systems. Most systems sold to date still use very old technologies..This is another SaaS business. One of our challenges is to connect up with NetSuite, Twinfield and others. If you use webservices, the job is relatively easy.

Previous post:

Next post: