3 ms·
> It does not seem wise to charge a fixed one time fee of a few hundred bucks Maybe you could make the one-time price higher? I've seen some critical libraries
by actionowl 7y ago
> It does not seem wise to charge a fixed one time fee of a few hundred bucks
Maybe you could make the one-time price higher? I've seen some critical libraries cost several thousand dollars, and it was worth it in time saved.
- geoah 7y agoI would have to agree with this. In the days when .NET was top dog and GitHub was not still a thing people spent insane amounts of money for libs that would save them time. Per client, per developer, per "seat", per core, anything you can think of someone charged for it. Telerik is the one that comes to mind, but they mostly did dev-oriented stuff. The pay-more-once scheme always seemed the most easy choice for companies I worked for, as they wanted to be able to sell products that they couldn't easily keep charging for after the sale.
- JohnFen 7y agoThis is my approach with my own libraries (and it's what I look for in libraries I buy from others). I would rather pay four or five figures one time than to have to put up with making regular payments over time. In part for convenience, but mostly to avoid nonsense like registration keys and the like, and I prefer not to ask my customers to deal with things that I'm not willing to deal with myself. That said, as a small businessperson I have considerable flexibility. If a customer really wants a lease option, I can easily accommodate that.