If you hook them now, at least some of them will push for your product to be adopted at their future companies.Ĥ) Improve the product on a regular basis. Not everyone who's going to want to use this is necessarily a professional developer flush with cash (yet). If customers need to consult with their lawyer to find out if they're in compliance or not you've done something wrong.ģ) Offer a cheap(er) personal license. Make it less than that for an individual developer.Ģ) Don't offer too many types of licenses. Many companies have a purchase size above which they need a PO. You talk about zero friction development all the time, apply that to purchasing.ġ) Price it reasonably. My best advice to you is to make it easy/desirable for people to buy it and treat the ones who do buy it with respect. There's also only one of you, and many of them. You can very easily dump huge amounts of time/brainpower into trying to come up with clever ways to protect it, and they'll crack it anyway, probably in less time than it took you to protect it in the first place. If people want to steal your software, they'll find a way. I don't think you should spend much time on licensing at all. Those range from being able to use a license on several machines, support floating licenses and removing a license from a machine. I got requests from users regarding the licensing. Now, just to make things more complicated. I got some advice in the matter from friends, which I am very grateful for, if not for the fact that this is so depressing. More than that, in order to produce a good licensing story, you need to invest a lot of time writing some tricky code so hackers would have harder time breaking this. That didn’t work out, and I now find myself in the position of having to writing the licensing infrastructure for NH Prof.Īny second that I put into the licensing infrastructure is a second that I can’t put into actually making the product itself useful. Initially, I bought a licensing component. For NH Prof, I need to have some licensing solution so people would be reminded that after 30 days of using the trail, they should pay.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |