4 ms·

Your customers are going to ask if it's cheaper to buy your library or build out the functionality on their own. If I were pricing this, I'd try to be at the hi

Your customers are going to ask if it's cheaper to buy your library or build out the functionality on their own. If I were pricing this, I'd try to be at the highest number possible where the answer to that question is a no-brainer. Personally, I'd do a fixed one time fee for each major version of the library. Another option is to scale your pricing based on your customers' revenue like Unity does (minus the subscription part). Smaller companies can get a better deal on your software, but when they cross a threshold of annual revenue, then they pay more.

JohnFen 7y ago
> Another option is to scale your pricing based on your customers' revenue I don't scale the pricing in an overt way, but I have been known to reduce the fee for small companies or individual developers if they ask. Also, if I think a particular customer would give me additional benefits (such as increased exposure or clout), I have sometimes cut the rate in exchange for permission to advertise their use of my library.