Adjust the SharePoint Srvr licensing model (& its requirements) to be compatible with making available an ISV product on SaaS business model
The current licensing model isn't friendly at all if you're thinking on making your SharePoint product available as a Cloud SaaS.
To go Cloud, this must needed change must occur so that the SharePoint (and its ecosystem required products) licensing model to fit well with SaaS business models without an obscene entry cost in licensing that crushes your initial investment as an ISV.
We have this product that we developed, and it requires SharePoint Server.
We’ve been considering for some time now the possibility of making our product also available as a SaaS.
However, as SharePoint Server is a requirement – the available licensing options pose a direct problem to this business model when you start onboarding customers.
1 comment
-
Jay
commented
My upvote is to align the product (SharePoint) licensing cost with the service (365) licensing cost. As it stands the only reason I can see is doing this is to drive customers away from their product and into alternatives such as OpenText, Drupal, Joomla etc. (wikipedia has a nice list to start evaluating alternative products)
