If they can find (or are given) a crack *most* individuals will use
it. If they cannot find a crack or serial number for software they
like, and do not want to pay the asking price, they will look for and
evaluate similar software which is cheaper.
Which is an argument in favor of my long-stated opinion that for a
good fraction of software (in particular, those that don't have huge
per-user support burdens), letting the user decide on the price he
wants to pay is well worth considering.
Let's say you think your software is worth $100. You don't get $50
from the guys who think it's worth $50. And you don't get $200 from
the guys whose job you just saved.
I've got a long-running service website that works on this system,
quite effectively. The question is how to translate my experience
there to non-server based apps.
I'm thinking that the way to do it might be something like this:
* Distribute the app uncrippled.
* Have it mention that they should consider "supporting the author"
* Let the user pay what they think the app is work, on a SUBSCRIPTION
basis. Paying means the nag screen goes away for a year, they get a
priority support email address, etc. Make it easy to pay - direct
links to a shopping cart, paypal, etc.
* If they don't pay, and then upgrade to the new version, the nag
screen returns.
* After a year, they get the nag screens back again.
The combination of choose-your-own-price and subscriptions might just
be the key. I've had quite a few people send me >$100 over several
years for the use of my site - $20-30 at a time. Subscriptions lower
the cost of entry.
Not for everyone, or for every product, but worth considering.
R
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
