Hello, currently we're struggling with a pricing model for our Gorilla3D framework (https://www.diggets.com).
Hello, currently we're struggling with a pricing model for our Gorilla3D framework (https://www.diggets.com).
The developer edition will be free, but for published products, built with our framework, we have to demand money.
We would appreciate, if you take your time to select an option. This would really help with the decision.
1) Monthly fixed fee per developer (without any further costs)
2) Monthly fixed fee per company (without any further costs)
3) A fixed component suite price
4) A participation model, f.e. ~3-5% on retail price
Thanks for joining.
The developer edition will be free, but for published products, built with our framework, we have to demand money.
We would appreciate, if you take your time to select an option. This would really help with the decision.
1) Monthly fixed fee per developer (without any further costs)
2) Monthly fixed fee per company (without any further costs)
3) A fixed component suite price
4) A participation model, f.e. ~3-5% on retail price
Thanks for joining.
Bill Meyer You're right! In case of an subscription model, developers do every month need to have the feeling , that it is worth paying.
ReplyDeleteWhat comes in mind to me, is the fact of maintenance. Having one time sale price and unavoidably many different version out there, we surely have much more effort to hotfix older versions. Rather than having everybody in a subscription and always allow them to download the newest version with all fixes.
I am always a big fan of a subscription model.
ReplyDeleteEric Berger I forgot to mention that you can also utilise any beta tester you may have. They can add in many ways, eg. ask them politely to prepare a white paper, an example code, write a blog and of course you can offer the product in discount
ReplyDelete