SaaS Fans

Data Aggregation

Ok, I know I said I wouldn’t talk much about the benefits of SaaS because we want to focus instead on design and implementation in this blog, but there is one important benefit that is often overlooked and under appreciated; data aggregation. Inherent data aggregation is unique to SaaS, and can only really be accomplished efficiently with a multi-tenant model.

Data is quickly becoming a valuable asset. Many companies base their entire business models on the quantity and quality of their data. But in order for that data to have real value, it needs to be aggregated, analyzed, and presented in a meaningful way. Vendors/ISVs of SaaS applications are sitting on loads of data entered by thousands of customers. With a multi-tenant model, this data is already aggregated and ready to be mined, analyzed, and presented. Of course, one of the challenges is that the data must be “de-identified” and “anonomized” before it can be presented, but this is a relatively simple process.

Imagine for a moment a SaaS application for grocery stores. Many different grocery stores use this application to track and manage their inventories. Now, suppose that one of the grocery stores (maybe from a large chain or maybe a “mom-and-pop” store) wants to compare its restocking times for specific items against other grocery stores of similar size and geographical location. Well, this grocery store is in luck because the software vendor has provided, as one of the benefits of this inventory management SaaS application, a de-identified report comparing restocking times, in aggregate, of each store with other (competing) stores. Basically, this equates to an industry “trend analysis” report, but it is much more relevant, timely, and trusted because the data is real-time, localized, and generated directly from the source. Other types of companies, such as healthcare providers, could benefit from comparing results of their surgical procedures against a de-identified, aggregated group of similar providers. This powerful feature can provide a compelling advantage for a company to “purchase” a multi-tenant SaaS application over another type of application.

Another opportunity for the SaaS vendor is to sell rights to view and mine data to 3rd party companies. With the right tools, 3rd party companies can have access to robust trending data and possibly even discover new trends that haven’t been previously considered within the vast amounts of data.

And, why not consider placing ads within the SaaS application itself, like FaceBook does? SaaS vendors could lower the fees they charge in exchange for the acceptance of ads (just like Gmail). These ads could be highly targeted based on the data that has been aggregated and analyzed behind the scenes.

One possible hangup in this whole strategy is that customers want to “own” their data. This is understandable. But, there is no reason why customers wouldn’t agree to let their vendors use their data in an anonomized and de-identified manner, for legitimate business purposes, especially when it provides value back to the customers.

So, wake up SaaS vendors/ISVs to the inherent data aggregation benefits of your mutli-tenant SaaS applications!

There is only ONE attribute that differentiates a SaaS application from all other types of applications. That attribute is multitenancy. Multitenancy (multi-tenancy) can be an intimidating word, but all it really means is that the underlying database uses a single schema (model) for all customers. Data is separated logically (as opposed to physically) and there is typically a single code set. Below are illustrations of this concept.

But what about the fact that SaaS applications are browser based and hosted? Well, other single-tenant applications can have those same attributes, so they are not differentiators. In fact, in one of my prior companies, we had trouble with competitors claiming they were “browser based” and “hosted”. We tried to differentiate ourselves based on the fact that we were multitenant (multi-tenant), but it was difficult when our competitors threw around terms that are often used to describe SaaS applications.

So, what is the most popular multitenant application?  Well, probably Facebook. Millions of people log in to the same database (yes there might be multiple servers hosting a huge database but you know what I mean). There is a single database schema (i.e. structure) for all customers and a single code set. Each person has his/her own little customized page and can make changes without affecting other pages. This is a classic SaaS application.

Since multitenancy is THE differentiating factor for SaaS applications, we are going to spend a lot of time on the subject in the SaaS Fans blog. And, have no fear SaaS fans. Multitenancy offers such as compelling advantage to software vendors/ISVs that it merits its own unique software classification (i.e. SaaS).

Hi, I’m Matt. I am a big fan of the SaaS (Software-as-a-Service) delivery model for Internet-based applications. I have spent the past 6 years designing and building web-based (SaaS) applications for various companies and I have gained some practical knowledge that I would like to share.  So, I decided to start this blog.

My vision for SaaSFans.com is that it will be a source of “best practices” and practical knowledge on designing, building, and deploying SaaS applications. We will rarely discuss the benefits and drawbacks of SaaS (there are plenty of other blogs for those discussions). Instead, we assume that you have already embraced the SaaS model and just need some help to get started on actually turning your vision into reality.

Other than the information provided here and any feedback that I can provide, if you would like some help actually building your SaaS application my company Surge (www.surgeforward.com) can help.

So, to all you SaaS fans out there, let’s share our ideas and turn our SaaS visions into reality. My plan is to post tasty morsels of SaaS knowledge at least every week so check back frequently.