Thank you. It would come down to execution.

One way to solve that is to track "scene releases" [0] and download the releases for software you think could become keygen.sh customers. Then reverse engineer the cracks or patches and document the process. Next, show how keygen.sh would have prevented this cracking technique. Now you have original content that will help you sell keygen.sh.

A byproduct of this will continuously give you ideas on how to improve keygen.sh.

It is very important to note that keygen.sh or any licensing platform will ever be uncrackable but if you can delay the time software gets cracked by a week or two then it could possibly translate into more sales for the keygen.sh customer.

At the end of the day, it is on the keygen.sh customer to sell their product and keygen.sh to delay the release of a crack for it.

[0] https://torrentfreak.com/27-years-of-warez-scene-release-inf...

>Then reverse engineer the cracks or patches and document the process.

Sounds prohibitively work intensive in the extreme.

There could be ways to automate the process [0] with machine learning [1].

[0] https://www.cuckoosandbox.org/

[1] http://www.covert.io/research-papers/security/Automatic%20An...