Show HN: I turned my email automation tool into a full-fledged email platform (useplunk.com)
Around 10 months ago, I published a tool I made (https://news.ycombinator.com/item?id=32229278).
I was scouring the market for an affordable and easy-to-use email automation tool, to no avail. The solution? I decided to just build it myself.
Since then, I've added the ability to send transactional and broadcast emails, threw out the subscription pricing and turned it into a usage-based model, etc. In short, turned it into a full-fledged email platform designed for SaaS.
With this post, I would like to share my learnings, findings... Ask any question and I'll answer it to the best of my ability.
Thanks to the feedback of the HN community, I was able to turn this into something that I am still proud of every single day. A sincere thank you from my side.
10 comments
[ 2.5 ms ] story [ 35.1 ms ] thread- Transactional: one-time emails, sent through an API on-demand (e.g. password resets, magic links...)
- Automations: Repeatable sequences such as onboarding flows with delays and follow-ups
- Broadcasts: Emails sent to a segment of contacts (e.g. newsletters, changelogs...)
You do have something covered at https://www.useplunk.com/use-cases but a lot more could be added.
Thank you so much for the interaction and feedback.
Plunk is a great example of an end-to-end SaaS application. I would be interested to know if you used a particular framework to implement the multi-tenant SaaS capability when building Plunk?
Thanks,
Mustafa.
https://vercel.com/docs/concepts/projects/domains