Quote:
Originally Posted by farkedup
I've had a few open source projects and simply put you won't have anybody capable of handling support until it becomes popular, it can't become popular without support so if you won't get help with support until its popular you're sitting there supporting people who haven't paid you a dime crossing your fingers that others will come and help with support....
If support is the problem jack up your prices. Its better to get fewer sales and higher profit margins. Modify your support so that the first month is free and then charge after that. I'm going to change my support from what is currently stated as lifetime down to something considerably less than that.
I've also been steadily raising my prices. When I was in the testing stages I was giving it out left and right, then I jacked my prices up as the product improved. I'm planning on having a few different pricing tiers, have lifetime support, copyright removal and installation at a high price and go all the way down to an at least partially encoded system and release a few addons.
I'm also putting out a free system that ONLY supports embed codes and will have some paid addons for that once I get a chance to cleanup some things in that system which I coded most of it over 2 years ago and it was used by some of my arcades back in the day.
|
open source works if you use the model of pay per incident support in fact when you are starting out and the script is not popular you actually make more money
after a little while when the script becomes popular people will jump in and offer support for your script at a lower price (since they can see the problems)
the key is to make it clear about the pay per incident / custom mod pricing up front
there are dozens of examples of this model working from the very big (red hat to the very small phplists)