I’ve never been a fan of dogma – I’ll be the first to admit that I use some installed applications where I deem it necessary, this despite being an evangelist for all things cloud-y. I’m a solution focused kind of a guy and if an installed app fulfils my needs, I’ll use it. There’s nothing I like less than those who evangelize SaaS for its own sake rather than for the real benefits it brings.
It was refreshing then to have the following Twitter dialogue with a friend of mine who runs a successful SaaS business and whom one would expect to be 100% in the clouds. We were talking about the different applications one uses to run ones business and, naturally given the participants, the topic came around to what SaaS apps we actually use. Said friends perspective was;
When the cloud becomes a stormcloud eh... just been shooting the breeze with [someone] about Cloud apps. He can't believe we don't use Google for our email… We use our own Exchange server. WAAAAAAY faster than Gmail for managing and sorting 50-100,000+ emails… And if the net goes down we have a cached copy. And then you started talking about Google issues ha ha … Cloudapps are great, but each need should be strategically evaluated as to whether should be cloud or local. Risk decisions etc. We carry VERY sensitive data in emails - if saved on Google I'd have to disclose to customers we were doing that... I’d guess I use about 20% cloud apps... for the others, local still beats cloud - so a ways to go yet. Early cloud days eh…
Now this isn’t a post that seeks to create a discussion around the relative merits of specific installed applications versus their SaaS counterparts - neither is it seeking to cast doubt on SaaS as a genre (I’m an evangelist, that much should be obvious). It is however timely to focus on what my friend said, namely that every functional need should be viewed against broad strategic objectives. In his case his customers may well feel anxious about their private data being held in Gmail for example – he made a strategic choice that for that functional area the risks around SaaS were sufficiently large to justify retaining a traditional application.
It’s an eminently pragmatic approach regardless of whether the dogmatic types approve…
Post Comment