Web Apps vendors should really understand the power of the business model they've chosen.
This is a work in progress that sets out to define the Software-as-a-Service (SaaS) Business Architecture. I wanted to release something now, even if it is an early version without much detail just to get it out to the world. I welcome input, but caution those commenting to temper their biases. Legacy software vendors, Open Source consulting companies, Virtualization vendors, and SaaS framework vendors are more than welcome to post, in fact, I encourage it.
However, please comment in the context of an open-minded discussion not from the angle of "we want to call ourselves SaaS and will defend the fact that our model is SaaS to keep that right." You can call your product whatever you want, even SaaS, if you would like to. The purpose of this definition is to define publicly what we at Sixteen Ventures have put together for our clients based on what we feel to be the most scalable (at a business level) and sustainable model.
Author: Lincoln Murphy (@lincolnmurphy on Twitter)