What, exactly, does a SaaS provider look like? This quirky need of mine for clear definitions stems back to the 90s. I was writing up a network switch report when a key vendor, who was well known for its extremely fast bridges, called and said they were changing the names of the bridges to network switches and wanted to have them included in the report. I developed a red, itchy rash and a penchant for definitions that very afternoon. But I digressâ€¦
A pure SaaS provider has the following characteristics:
1. Organization and Culture
A pure SaaS vendorâ€™s organization and culture focuses on subscription-based customer service excellence. The company seeks to maximize value for its clients by delivering application performance and utilization above what can be obtained internally.
The SaaS vendor uses monitoring and analysis to determine specific application performance service quality such as availability, response times and security. However, unlike other software delivery models (ASP, MSP, ISV) the SaaS vendor also measures which applications and application elements are being used. This information provides customers with real usage information and the ability to trim costs. Surely, an ongoing value proposition for firms of all sizes.
2. Physical Infrastructure
This is a big one. There are numerous ASPs, MSPs, and ISVs masquerading as SaaS vendors. When data centers, rack space, servers and revision levels creep into the conversation, you know you are not dealing with a pure SaaS vendor.
A SaaS vendor operates at the Application Layer. Their value is in delivering applications faster, better, cheaper. Some even seek to deliver enterprise applications to non-traditional devices such as smartphones.
The physical level infrastructure should never, ever, nada, nope, never come up in a SaaS conversation. If it does, the vendor is probably transitioning from one of the other business models noted above. Data centers and hosting are outside the core competencies of pure SaaS vendors. They partner for this important expertise.
3. Application Specifics
A SaaS provider builds its applications and users purchase a base + add-ons for customization. In this manner, a SaaS provider is able to leverage its intellectual property most effectively. Other models, such as ASPs, use off-the-shelf applications and client customization is long and expensive.
Application usability. Usability is super simple from a SaaS provider. The applicationsâ€™ UI is designed to be intuitive without needing any training. That intuitive UI model is not shared by commercial applications and frequently requires a professional services engagement to get the user community up to speed. In addition, traditional applications are client-server based. See infrastructure issues, above, but also note that applications delivered via SaaS are Web 2.0 centric.
Application upgrades and enhancements. A SaaS provider will use agile or some other form of rapid application upgrades and enhancements. Changes can occur very quickly and often will occur many times a month. The customer can elect to adopt the enhancements or not on an as-needed-basis. No need to state the pain of upgrades, revision levels and enhancements for commercial applications running in a client-server environment.
A pure SaaS vendor provides customers a substantial amount of value, including billing based on usage, an important attribute as firms seek to control and trim costs. The emphasis is on the application, the component of IT that actually drives business, not the physical infrastructure. Be sure your firm knows what it is buying into as it explores the benefits of using SaaS.
You can find me at: