[boberoni]

Congrats on launching to HackerNews! First step on a journey of many.

Some Feedback:

- The biggest words on the landing page are "Behavioural Email Tool" but I don't know what this means. Maybe I'm not in your market.

- As I read through what Plunk does, it sounds more like "email automation". However, Plunk is not like other email automation because... (insert your wildest dreams)

- Your pricing is too low. In the wise words of patio11, "Charge more!" For a detailed guide to pricing SaaS and how to think about your pricing, check out patio11's writing on the Stripe blog[1]

- There's a typo in your free plan: it should be "1 seat", not "1 seats".

- Don't offer "Amazing Support" on your free plan. Reason (1) is that users on the free plan tend to squeeze the most support out of you, and they're not even paying you. You can reach out to help them if you want, but don't promise support to free users. Reason (2) is that adding support is a good incentive for a serious business to upgrade to the pro plan. If I'm a business who's success/revenue relies on Plunk for my success, I surely would upgrade from a plan without support to one with support.

[1] https://stripe.com/atlas/guides/saas-pricing

[driaug]

Thank you very much for this incredible feedback, very kind of you!

I have already made some minor changes (fixed the typo and moved dedicated support).

Tomorrow I will be looking into altering the copy because I do understand what you are saying and have heard the same feedback about the term "behavioural email tool"from a couple of people!

Thank you very much for linking Stripe Atlas' guide, seems really helpful and in-depth!

[mind-blight]

+1 for "I don't know what that means". I think I'm the target demographic, but I don't feel like can effectively compare the pros and cons of this product with something like MailChimp with the information available on the site.

I'd love to see a clearer breakdown of the features: - how come I trigger an event instead of sending an email directly? It seems like a neat abstraction with a lot of potential, but I haven't found the reasoning behind it in the site. - what can I do with workflow automation? Can I do complex logic based on multiple events? Can I do branching logic? Etc. - why wouldn't a larger company choose you? What's missing that's present in a more established product, and what advantages do you give over that product? I'm assuming cheaper and simpler, but I'd love to get a better idea about the now specific tradeoffs.

Overall, it seems like a really cool idea . I have a project in mind that I may use it for

[ru552]

Pretty good feedback here. Learned a thing or two myself.