I’ve several posts comparing and contrasting SaaS and software. So far, the thread consists of:
- SaaS vs. Software: The Release Cycle for SaaS is Usually (Not Always) Faster
- SaaS vs. Software: Their Licensing Needs to Be Integrated
- SaaS vs. Software: SaaS Has a Built-In Usage Feedback Loop
- SaaS vs. Software: The Pros and Cons of SaaS Pricing
I’ve had four comments on the pricing post so far, and I thought it would useful to comment on some of the comments:
I had pointed out that SaaS’s pay-as-you-go model avoided the big cost bumps that software often has and might make companies complacent and not rethink their purchase. One reader said, “I disagree with “point 4″ and think that SaaS actually provides MORE opportunities to rethink and evaluate the purchase. I think it is a great benefit that many cloud solutions have user ratings, reviews and comments capabilities built in, which allow companies to have to work less hard to “hear” what their users are saying.” Another reader felt that because SaaS was less capital-intensive, it would be easier to switch solutions.
I’m not sure about these points. While empowered users may use comments and tell their IT departments what they think about their SaaS solutions, I sometimes talk to IT departments who, truthfully, don’t care what their users think–or really even know what a typical day for a user is. Many IT departments care a lot about keeping the ERP and CRM systems running, but pay scant attention to how information workers collaborate. So while users may signal that they want a better or different system, some IT departments will just ignore them. In fact, many SaaS solutions got their start because disgruntled departments were tired of being ignored by IT, and went out and bought their own.
Not all IT departments behave this way; I’ve also talked to a lot of enlightened shops as well. Some are amateur anthropologists and follow users around for days, trying to figure out what systems would help them do their jobs better.
But when all is said and done, I think many IT shops are driven by the bottom line, and reconsider switching systems only when they turn expensive, not when they’re dysfunctional for the business. It’s easy to measure expensive; it’s not always easy to measure dysfunctional.
However, a SaaS application that stores tons of data that companies want to take with them (e.g., an online collaboration system such as IBM LotusLive, Google Apps, or Microsoft BPOS) I think is a different case. Furthermore, if there’s an embedded data model or taxonomy, it’s a lot of work to recreate that in a new system. I’m hoping that it does become easier to switch with SaaS, especially as standards make things more interchangeable. However, at this point some SaaS vendors will charge customers to extract/convert their data, and I don’t think we’re yet in the “easy switch” era–at least not across the board.
Finally, a reader commented, “The well stated points in this article aren’t so much a comparison of SaaS vs Software, as much as they are a comparison of a perpetual license vs. a subscription license.” Fair point. I can’t think of anything that’s actually preventing software vendors from moving to the subscription license model. I wish they would–it would give them a better feedback loop. At the moment, many vendors think their software is a rousing success due to large sales; but sometimes when I talk to clients I find out it’s actually shelfware. True, falling support revenue is something of a proxy for poor software, but moving to a subscription model would make vendors really pay attention as to whether they’re continuing to deliver business value to their customers.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.