Ben, your preemptive strike is a miss. Supporters of SaaS should not be dismissing those who correctly point out that these examples point out the risks of SaaS. Instead, we should be the ones who point out that these DO show some of the risks, and then progress to explain what companies can do to mitigate the risks and what sort of due diligence can be done. Your simplistic statement about doing due diligence - and then stating you have to do it for desktop software too - is not helpful. The due diligence is vastly different for the two approaches. The reality is: with software you install, if the company shuts down, you still have the software running, and your corporate processes can continue. When a SaaS vendor shuts down, your corporate processes that were tied to that service shut down too. SaaS supporters need to acknowledge that. So, lets start talking about the implications of that vs. the implications of on-site software (not "desktop" software, because it can be server software too). We need a blog (or a wiki) where we can all contribute to documenting the risks for both approaches. That will 1. With SaaS software, you need to ask what is the implication of the tool being down for a certain amount of time, with you being able to do nothing other than apply pressure or seek legal action. What happens if the service is down for 24 hours? A week? 2. With on-site software, you need to ask what is the implication that you will need to dedicate staff and resources to maintaining and upgrading the software. What are the implications if you are a few patches behind? Will you be out of compliance with state or federal regulations? 3. With SaaS software, you need to ask what is the implication of upgrades being made at an inopportune time. What sort of advance notice does the vendor provide before implementing changes? What is their rollback plan if there are problems? 4. With on-site software, you need to ask what are the implications of the fact that the people administering the tool (your staff) are not the experts on the software? Sure, they may be extremely knowledgable, but the experts are at the software company. just a start....

Before anyone holds this up as yet another example of the risks of SaaS I thought I'd make a preemptive strike.



Post Comment