The SaaS product is targeting a very specific audience so my current version of the landing page[1] assumes that the user knows what a (web)hook is.

I am an author of an open-source self hosted tool named webhook[2] and it has validated that the problem I had, others have as well and that there are users who need an incoming server that would execute their code.

Main problems with my open-source tool is that managing all these hooks is PITA. If you have more than 5 hooks, you'll start getting lost in your JSON configuration. Providing a web interface in the open-source tool would clash with my philosophy of doing one thing and doing it well. Additionally, I would like to monetize this, and that's the reason I am launching a SaaS which does what my open-source tool does, improves on the pain points the tool has and also adds some additional features such as concurrency execution management, etc...

Is the SaaS version worth anything to the users? The time will tell, but I believe it is.

Any suggestions on what to add/remove to the current landing page that would help you decide my SaaS is worth your time.

Second thing: how would I go to market my product. The problem it's solving might look trivial, but the implementation has some tricky parts. Especially ones dealing with the concurrent executions. :-)

Thanks in advance!

[1] https://www.hookdoo.com/ [2] https://www.github.com/adnanh/webhook