I want to develop a software product that I envision working best as a web service that people register for. The software could also be packaged as a downloadable product that customers could install on their local servers. I'm sure my customers will largely dictate which product they want once I get it launched, but I am wondering how I should start?
From what I've seen, there's a large number of businesses that are only willing to rely on software that they can install and monitor on their own servers. Many have policies where they simply won't use a software product that resides (along with their data) on someone else's servers.
While I am going to try and make it as attractive as possible to use my product as a web service (which will include making all of their data fully exportable in an open format), should I start out offering the product as both a web service AND a downloadable product? Should I start out as JUST a web service and gauge customer reaction?
The only reason I would prefer to offer the product as a web service only is that it will reduce the amount of time I would have to spend maintaining the downloadable version, and eliminate support and development issues related to it being installed on third party servers running god-only-knows what. I'd rather funnel that time and effort into the web service. Piracy is not necessarily among my list of concerns.
What are everyone's thoughts?
You have to convince them that SaaS is the better deal - regular, automatic updates, tight security, redundant backups, and reliable access - and they won't want to consider the downloadable version.
You should prefer SaaS because you can charge them more in the long run if you get them dependent on you, in addition to reducing the setup time and effort.