Skip to main content

Scott Sehlhorst on SaaS

On his Tyner Blain blog, Scott Sehlhorst has a richly informative entry on software as a service (SaaS). What makes his treatment of the topic noteworthy is his focus on practical customer benefit rather than on the hype that typically surrounds SaaS.

Based on Scott's entry, here is how I boil down the problems with licensed software that SaaS solves for customers:
  1. Deployment time and expense. When a new version of the software comes out, it can take considerable time and money to roll the software out, especially in an enterprise environment. With SaaS, upgrades require little or no deployment time or expense for the customer.
  2. Administration time and expense. Typically, when software is installed at an enterprise site, administrators monitor and manage the installation to ensure it is functioning properly. With SaaS, the provider handles site administration.
  3. Lack of accessibility. If the software is installed locally on individual computers, and a customer needs to use software when she is traveling, she must bring a computer with the software installed or rely on installation on other computers. With SaaS, the service is available remotely via the web or another mechanism.
There are other subtle benefits to SaaS. Yet perhaps I've also omitted some major ones?

UPDATE: Paul Young has some additional thoughts.


Scott Sehlhorst said…
Roger, thanks very much for the shout-out! And great summary. One thing about accessibility - in some ways, you're robbing Peter to pay Paul. You trade the need to access a computer with the software locally installed for the need to have access to the SaaS server (remotely). You need an internet connection. This is changing in interesting ways, between Google Gears, Adobe Flex, and other approaches to allow for disconnected use of traditionally always-connected applications.
Dugg said…
We have found that our large customers are switching to our SaaS applications to avoid specific certifications such as PCI/DSS, GLB, HIPAA and others that can require thousands of hours and millions of dollars to bring their own application environments up to snuff.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio