Introducing Mailclerk

Noah & Greg

Posted 1.1.21

Email is ubiquitous. As one of the oldest web technologies, email is used by over four billion people, it has been treated as a legally binding contract, and email security has been central to recent political scandals. We feel the significance of email in our lived experience as well. We receive notification and confirmation of major events via automated emails like large purchases, college admissions, changes to medical records, and more.

For most businesses, email is the primary way to maintain a relationship with their customers when they are not actively using their product. (In other words, most of the time!) The average web application sends hundreds of thousands of emails per month. Yet, the standard practices for designing and sending these emails hasn’t changed much in the last decade.

Application emails are more complex for businesses to deploy than marketing emails because they require a deeper integration within a codebase. Product managers, marketers, operations and support specialists, as well as other business stakeholders who cannot modify the codebase end up disempowered to iterate on these emails. They also tend to have limited visibility into email performance. Meanwhile, developer time is used on email-related tasks that might be better handled by others on their team. Customer experience and businesses’ bottom lines suffer.

We’ve run into these problems countless times working within a variety of organizations and have had to create custom tools to solve these problems each time. Now, we’re building Mailclerk to make it easier for anyone on your team to have control over your application emails.

Mailclerk provides flexible, powerful, and easy-to-use tooling that:

  • Makes it easy for non-developers to create and iterate on automated emails, ensuring the content of these emails are always up-to-date and easy to understand.
  • Gives your customers more control over which emails they want to receive, so they don’t just unsubscribe from all of them.
  • Allows your whole team to gain better visibility into how your users are interacting with your application via email.
  • Triggers emails with perfect timing and completely accurate data, so you can create a more "magical" customer experience.
  • Saves developer time by automatically generating code snippets for an API that follows a simple standard: "JSON in, email out."
  • Gives you freedom to easily swap out delivery services, so you can more easily troubleshoot issues and generally decrease bounce rates.

You can think of Mailclerk as a layer, similar to a content management system, that can be added to any web or mobile application. Within this layer, we provide functionality, analytics, and the education necessary for everyone on your team to maximize the benefits of high-quality email for your organization.

As we build Mailclerk, we plan to model good business practices at every opportunity. We rely heavily on open source software projects, and are already contributing back to the community. We plan to produce freely available educational content, on this blog and beyond. We’re also launching with a partnership with Stripe Climate, where 1% of your subscription will be automatically contributed to projects that remove CO₂ from atmosphere. And, perhaps most importantly, we take the performance and reliability of Mailclerk very seriously.

We’re excited to have you as a part of it. Join the waitlist. Follow along on the blog, Twitter, and Instagram. And if you have any questions, you can just shoot us an email:

-Noah & Greg 📬 🚀

Interested in early access?