Is it the economy? Is it just bad timing, irrespective of the economy? Was the functional idea flawed? Is the "give away the razor" idea flawed? All these questions come to mind as I read on June 12 that Flowgram (about which I posted last fall) has announced that it has
" decided to terminate the Flowgram service as of the end of the month (June 30th, 2009). The service received excellent reviews and had an enthusiastic core user base. However, we were not able to demonstrate (especially in these economic times) that Flowgrams would ever be prevalent enough for us to adequately monetize the business, either though ads or subscriptions.
The demise of Flowgram, created by Abhay Parekh (who had a good track record of founding and building IT companies), follows the much publicized collapse of Coghead in February 2009. Coghead's intellectual property and some assets were purchased by SAP.
There are three generic lessons to be drawn by IT management and staff in these software-as-a-service company corporate failures. You have to vigilantly monitor all three if you depend on such on-demand/cloud-based/SaaS services (pick your buzzword), even from such well-funded firms as Google with its gmail and other aspects of Google apps. They are:
On the first issue, you get what you pay for, as they say. But as I wrote last December in The ERP/SaaS Conflict Is a Myth:
"SaaS-delivered ERP has been popular in health-care delivery, community banking, professional services, construction and other services industries since - since back when we called it timesharing.
Most is subscription-based, but some such as construction-oriented software is sponsor-supported, and there is no reason these models will not continue to work as well as they have for decades.
The second factor is to determine how critical the SaaS-based functionality is to your enterprise. Videos and PowerPoint-like presentations like Flowgram enabled are probably never going to be that critical. As I wrote on December 8, 2008, there are in fact many functions that are better served by IT-enabled business services -- and I suspect, but not based on any market research, that videos are one of them. If you were depending on a service such as Coghead's as an application development platform, even for situational applications, the criticality level goes up a notch. Now you run the risk of having to redo months of development work depending on how the SaaS-based platform service worked. At the highest threat level, when it comes to your core applications, there's nothing to say that such applications cannot go SaaS. But I don't think that approach will be accepted until the Facebook generation takes over IT.
As for the third issue, protecting your investment in IT done over the ether is the most important thing to watch. There are not only the almost weekly reports of Gmail outages, but there is the issue of losing the information the SaaS service "stores" for you. It's that information that is key, not the enterprise software that processes and manipulates it. When it comes to your core applications, there's nothing to say that such applications cannot go SaaS. But just as with on-premise core applications, you want to have backups on your backups. To the extent you are doing app development or something less core in the cloud, you want to have the same kind of versioning control and check-in/check-out back up as with on-premise development. Even for mundane things such as Powerpoint presentations, make sure you keep the information in standard file formats so that you can get at them in the future with another application if need be. That's true even if you use an IT-enabled business service to develop the information.
This is all common sense, of course. But it takes an unfortunate business failure every so often to remind us. Flowgram is working hard to encourage all its users to get their presentations off its servers so that the users do not lose their information.