1. 2

    Years ago now I suffered significant delivery failure for an event such that attendance was impacted. That was the last straw for me to self-host email. From time to time I do have a chance to talk to folk that use third-party transactional mail providers. From your perspective, do customers use mailswift.io because of delivery problems, your user interface, campaign tracking, or some other reason?

    1. 3

      One of the reasons why marketers fail to leverage advanced API systems like Amazon SES for sending out emails is due to the heavy programming efforts associated with on-boarding/maintenance. The cost savings are so huge by Amazon SES, that there is a clear need we felt was under served. So, MailSwift is primarily built to help folks get up and running with advanced API systems like Amazon SES (which has good deliverability) with zero coding and maintenance efforts while saving a fortune on the prices

      1. 2

        I should have looked at your website before asking my question. I hadn’t realized MailSwift was a desktop application using a third-party mail service as your delivery platform. Do you think Amazon will come eat your lunch one day or have you found a niche they’re not interested in?

        1. 2

          Our product is built with the principle of providing the ability to marketers to use advanced APIs like Amazon SES which are highly cost efficient and have good deliverability rates. Since AWS is highly focused on being an infrastructure, the likeliness of Amazon focusing on this niche is a bit less

        2. 1

          Totally agreed. I’ve had similar experiences.