3 ms·
Simple. Justify—in honest, person-to-person language, not marketing bullshit—why you deserve to keep receiving money. If your product involves continual resour
by _zzaw 4y ago
Simple. Justify—in honest, person-to-person language, not marketing bullshit—why you deserve to keep receiving money.
If your product involves continual resource usage—runs on your servers, offers personal support, continually updated info, etc—then yeah, you're providing value in exchange for money. I despise subscriptions, but I have no problem paying for someone else's resources that I'm using.
But if your product runs on my resources, you do not deserve to be paid any more than once. I'm sorry, but it really is that simple. I have no problem paying a fair price, or paying for additional upgrades. I do have a problem paying for you to sit back and do nothing, and that's what software subscriptions essentially are. People don't like greed. That's a feature, not a bug.
If you still want to try to milk people, though, I think the hybrid model is the way to go. When I'm considering an app, the first thing I look at is pricing; if it's a sub, I close the window and never look back. If it's a one-time price, I'll genuinely consider whether the product is worth it. If it's a reasonable price, I might even impulse-buy it.
So I think beyond being unethical, the subware pricing scheme is probably losing you potential customers that you aren't even aware of.
- MathMonkeyMan 4y agoCareful. This perspective lends to [SaaSS][1]. We _could_ give you the software and have it run on your machine, but then we couldn't justify charging a subscription. So, we'll give you a thin client, run the software on our hardware, and be sure to charge you much more than our costs. As a bonus, we can change the behavior of the software at any time without your knowing. [1]: https://www.gnu.org/philosophy/who-does-that-server-really-serve.en.html https://www.gnu.org/philosophy/who-does-that-server-really-s...