The Price of Plugins
Page: 1
Recent posts in this topic
Hi all -
I haven't bought aC 1.0 yet - just waiting a bit longer for documentation etc. But I was thinking about plugins that will enhance the product... and then I started thinking about pricing of plugins... I realise that 3rd party plugins may or may not have a price tag attached to them, but what about "aC/a51 Development" produced plugins?
Do you guys have thoughts on if you'll be charging for plugins? if so is there a ball park figure? (i understand price would vary as per plugin) ...or would plugins most likely be free - like a bonus incentive for purchasing aC? (or a mixed bag?)
I haven't bought aC 1.0 yet - just waiting a bit longer for documentation etc. But I was thinking about plugins that will enhance the product... and then I started thinking about pricing of plugins... I realise that 3rd party plugins may or may not have a price tag attached to them, but what about "aC/a51 Development" produced plugins?
Do you guys have thoughts on if you'll be charging for plugins? if so is there a ball park figure? (i understand price would vary as per plugin) ...or would plugins most likely be free - like a bonus incentive for purchasing aC? (or a mixed bag?)
I have been wondering the same, a fair answer would be to link plugin price with the feature list / complexity of the plugin. It will be hard to give a price range without giving some example.
Lots of people want to import their basecamp projects, now that's an example. It would seem the basecamp API is not well documented, it might take time to build the plugin. Another example, the outlook plugin (like vTiger has). I don't care about it, but big corporation might care. Another one : let's say you need to have a CRM module, this would mean lots of dev hours and would most likely be pricey.
Remember that each time you build a plugin or module, you have to take into consideration the market : how many people are likely to buy it ? Price won't be the same if it's 100 or 1 000 or 10 000... The more a feature set is specific, the less people you can sell it to. I guess most highly specific features will be done internally.
My 2 cents...
Lots of people want to import their basecamp projects, now that's an example. It would seem the basecamp API is not well documented, it might take time to build the plugin. Another example, the outlook plugin (like vTiger has). I don't care about it, but big corporation might care. Another one : let's say you need to have a CRM module, this would mean lots of dev hours and would most likely be pricey.
Remember that each time you build a plugin or module, you have to take into consideration the market : how many people are likely to buy it ? Price won't be the same if it's 100 or 1 000 or 10 000... The more a feature set is specific, the less people you can sell it to. I guess most highly specific features will be done internally.
My 2 cents...
The best way to predict the future is to invent it
------------------------------------------
Apache 2.2.8 - MySQL 5.0.45 - PHP 5.2.6 | Debian 4.0 (Etch)
------------------------------------------
Apache 2.2.8 - MySQL 5.0.45 - PHP 5.2.6 | Debian 4.0 (Etch)
