Emails.DutyLabs

I just launched a new tool to help developers implement emails in their applications faster. I’ve had to write email automation for more than 4 clients until now. The usual conversation goes like this: 1. We want you to send a suite of emails whenever some events happen. 2. I write the first version of the emails. 3. They want me to change the verbiage of almost all emails. 4. We iterate on that, we try to test the logic (which btw is very tricky and I usually change the email automation to wait a few minutes instead of a few days so we can test quickly) 5. We are satisfied with the implementation, but we don’t quite have a way to test how well the implementation behaves in terms of business returns - whether users bought something after we sent an email, whether they read the email, clicked the links, and so on. 6. We come up with some hacks to measure success. 7. We are pretty much done. After some time…. We want to add new emails/campaigns/change the verbiage. Here we go again. It quickly came into my brain that this is quite a common problem, and so, I did what any sane person would do and built an MVP in a few days. You can check it live at https://emails.dutylabs.ro. Read the full story at https://rusu.io/emails/.