<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Senlo</title>
    <description>The latest articles on DEV Community by Senlo (senlo).</description>
    <link>https://dev.to/senlo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F16156%2F3fe954f5-3bd4-48b3-bb88-ea01e35678de.png</url>
      <title>DEV Community: Senlo</title>
      <link>https://dev.to/senlo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/senlo"/>
    <language>en</language>
    <item>
      <title>Dunning, onboarding and win-back email benchmarks, with sources</title>
      <dc:creator>Ihor Filippov</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:58:20 +0000</pubDate>
      <link>https://dev.to/senlo/dunning-onboarding-and-win-back-email-benchmarks-with-sources-4g51</link>
      <guid>https://dev.to/senlo/dunning-onboarding-and-win-back-email-benchmarks-with-sources-4g51</guid>
      <description>&lt;h2&gt;
  
  
  Published benchmarks for dunning, onboarding and win-back emails, and how each one was measured
&lt;/h2&gt;

&lt;p&gt;Baremetrics published a benchmark in June for its dunning product: 119 US B2B SaaS companies, data for May 2026, a median recovery rate of 12.7%. Recurly's billing metrics report, built on nearly 2,000 subscription sites in 2019, gives a median of 47.6%. Both get quoted as "the" recovery rate for failed payments.&lt;/p&gt;

&lt;p&gt;They measure different things. Baremetrics divides recovered payments by the failed payments its email sequence engaged with. Recurly counts recovery over past-due invoices as a whole, which includes everything the automatic card retries fix without anyone reading an email. Retries alone account for a lot: Stunning, which has handled dunning for Stripe accounts since 2012, reports that 20 to 25% of failed payments go through when the card is retried a few times over a week.&lt;/p&gt;

&lt;p&gt;I'm writing playbooks for four email flows that most SaaS products end up with (failed payment, activation after signup, inactive users, cancellation) and wanted a public number for each, with a named company, a sample size and a stated method. I found about twenty that qualify. They're collected below with their limits. While searching I also saw the 47.6% attributed to two companies other than Recurly, so it's worth following any figure back to where it was first published.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Flow&lt;/th&gt;
&lt;th&gt;Number&lt;/th&gt;
&lt;th&gt;Source&lt;/th&gt;
&lt;th&gt;Limit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Failed payment&lt;/td&gt;
&lt;td&gt;12.7% median recovery&lt;/td&gt;
&lt;td&gt;Baremetrics, 119 US B2B SaaS companies, May 2026&lt;/td&gt;
&lt;td&gt;Only payments the dunning emails went after&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Failed payment&lt;/td&gt;
&lt;td&gt;47.6% median recovery&lt;/td&gt;
&lt;td&gt;Recurly, nearly 2,000 subscription sites, 2019&lt;/td&gt;
&lt;td&gt;All past-due invoices, retries included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Activation&lt;/td&gt;
&lt;td&gt;68% open, 16% click on a personal email&lt;/td&gt;
&lt;td&gt;PostHog, 2024&lt;/td&gt;
&lt;td&gt;Per-email metrics, no control group&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Inactive users&lt;/td&gt;
&lt;td&gt;14% returned, 29% of those paid&lt;/td&gt;
&lt;td&gt;WordLayouts, 1,200 users&lt;/td&gt;
&lt;td&gt;Founder-reported, no control&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;At cancel&lt;/td&gt;
&lt;td&gt;753 pauses, 94 coupons&lt;/td&gt;
&lt;td&gt;Wavve, 2,590 cancel attempts&lt;/td&gt;
&lt;td&gt;Published by the cancel flow vendor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;After cancel&lt;/td&gt;
&lt;td&gt;6% back by month 2, 8% by month 6&lt;/td&gt;
&lt;td&gt;One consumer subscription app, 2017&lt;/td&gt;
&lt;td&gt;No win-back effort at the time&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Failed payments
&lt;/h2&gt;

&lt;p&gt;The Baremetrics sample sent 123,810 dunning emails in the month and recovered 10,999 charges worth $1,236,764. That works out to about 11 emails per recovered payment (my division, not a figure from the report). Their sequence starts within 24 hours of the failure, and most recoveries that follow an email come after one of the first three, within the first week. An earlier version of the report said the day-13 lockout warning was usually the most valuable message. They removed that claim when later data didn't support it.&lt;/p&gt;

&lt;p&gt;Stunning's write-up, based on more than 50 million emails, adds detail on the emails themselves. Customers update their card either soon after the first email or after the third. Send time has little effect. Emails that look identical get ignored, so the subject and wording should change from one to the next. The update link should open a billing page without a login, because a password reset in the middle of the process loses people.&lt;/p&gt;

&lt;p&gt;To compare your own numbers with either benchmark, compute both rates. The query below assumes two tables, and yours will have other names. &lt;code&gt;failed_payments&lt;/code&gt; has one row per failed charge, with the time it failed and the time it was eventually paid (null if it never was). &lt;code&gt;dunning_emails&lt;/code&gt; has one row per reminder sent, with the id of the failed charge it was about. The syntax is Postgres and the query only reads.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="c1"&gt;-- failed_payments(id, failed_at, recovered_at)&lt;/span&gt;
&lt;span class="c1"&gt;-- dunning_emails(payment_id, sent_at)&lt;/span&gt;
&lt;span class="k"&gt;select&lt;/span&gt;
  &lt;span class="nb"&gt;count&lt;/span&gt;&lt;span class="cm"&gt;(*) filter (where recovered_at is not null)::float
    / count(*)&lt;/span&gt;                                         &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;overall_rate&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nb"&gt;count&lt;/span&gt;&lt;span class="cm"&gt;(*) filter (where recovered_at is not null and emailed)::float
    / nullif(count(*)&lt;/span&gt; &lt;span class="k"&gt;filter&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;where&lt;/span&gt; &lt;span class="n"&gt;emailed&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;       &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;attempted_rate&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
         &lt;span class="k"&gt;exists&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;dunning_emails&lt;/span&gt; &lt;span class="n"&gt;e&lt;/span&gt; &lt;span class="k"&gt;where&lt;/span&gt; &lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;payment_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;emailed&lt;/span&gt;
  &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;failed_payments&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;
  &lt;span class="c1"&gt;-- failures from 30 to 60 days ago, so each one had a month to recover&lt;/span&gt;
  &lt;span class="k"&gt;where&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;failed_at&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="nb"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="kt"&gt;interval&lt;/span&gt; &lt;span class="s1"&gt;'60 days'&lt;/span&gt;
    &lt;span class="k"&gt;and&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;failed_at&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;  &lt;span class="nb"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="kt"&gt;interval&lt;/span&gt; &lt;span class="s1"&gt;'30 days'&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;t&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;overall_rate&lt;/code&gt; corresponds to Recurly's definition and &lt;code&gt;attempted_rate&lt;/code&gt; to Baremetrics'. If the first email goes out at the moment of failure, the two are close. If it waits for the retries to finish, &lt;code&gt;attempted_rate&lt;/code&gt; will be much lower.&lt;/p&gt;

&lt;h2&gt;
  
  
  Activation after signup
&lt;/h2&gt;

&lt;p&gt;I found less here than for any other flow.&lt;/p&gt;

&lt;p&gt;PostHog documented seven versions of its onboarding sequence. A personal email to engineers had a 68% open rate and a 16% click rate. Personal tips for non-technical users averaged 54% and 6%. Unsubscribes were around 0.4%, and small changes to subject lines or body copy made no noticeable difference. The post has no control group and no measured change in activation.&lt;/p&gt;

&lt;p&gt;Heap sent different emails depending on which setup step a user hadn't completed, and reported that users who opened them converted about 10% better through the funnel. Users who open onboarding emails are more engaged to begin with, so this doesn't isolate the effect of the emails. Copyhackers reported roughly 3.5x paid conversions after rewriting Wistia's trial emails in an A/B test, with no sample size given.&lt;/p&gt;

&lt;p&gt;So the public data shows that behavior-based onboarding emails get opened and clicked. I didn't find a published activation lift measured against a control. To get one for your product, track the share of signups that reach your key event within 14 days, by weekly cohort, before and after the change.&lt;/p&gt;

&lt;p&gt;PostHog also stops the sequence for six weeks when a user hasn't activated after two emails.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inactive users
&lt;/h2&gt;

&lt;p&gt;These cases come from a single Freemius article of founder interviews, and all figures are self-reported.&lt;/p&gt;

&lt;p&gt;WordLayouts emailed 1,200 users six weeks after their last login. The email offered a walkthrough video, direct access to support and a trial extension, with no discount. 14% came back, and 29% of those were paying within two months. An earlier discount email from the same company had a 41% open rate, 8% clicks, and brought back 4%.&lt;/p&gt;

&lt;p&gt;Panto AI had also been sending discounts. They changed the email to name the setup step the user hadn't finished and offered help with it. About 18% reactivated and about 60% went back to paying. FB Group Bulk Poster sent 7,500 early free users a short email about what had changed in the product; 33% opened it and 10% of those upgraded.&lt;/p&gt;

&lt;p&gt;The article includes a timing table without saying whose data it is. Emailing after 2 weeks of inactivity brought back 9%, of whom 22% converted. After 6 weeks it was 18% and 41%, after 3 months 11% and 18%. Multiplied through, that is about 7 paying users per 100 emails at six weeks and about 2 at either of the other intervals.&lt;/p&gt;

&lt;p&gt;Three companies with no control groups don't settle anything, but in each of them an email with a specific next step did better than the discount email it replaced.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cancellations
&lt;/h2&gt;

&lt;p&gt;Wavve, a podcast tool, added a cancel flow with a survey and offers. In its first three months 2,590 customers started to cancel and 1,002 left the flow without cancelling. 848 accepted an offer: 637 took a two-month pause, 116 a one-month pause, and 94 a 50% coupon. 1% gave missing features or technical problems as the reason. The case study is published by Churnkey, the vendor of the flow, but it gives absolute numbers.&lt;/p&gt;

&lt;p&gt;For emails sent after a cancellation, Hannah Parvaz describes a consumer subscription app that had no win-back effort in 2017: 6% of cancelled subscribers returned by month two and 8% by month six. The best app in its benchmark group had 35% by month six. She later A/B tested a 20% discount against a 30% one, and both converted at the same rate.&lt;/p&gt;

&lt;p&gt;A 2023 survey of customer success teams found an average monthly churn of 6.9% at companies with win-back campaigns and 6.4% at companies without. That's a correlation in survey data and says nothing about cause, but it doesn't support the idea that running a campaign lowers churn by itself.&lt;/p&gt;

&lt;p&gt;Paddle says its reactivation product brings back 10 to 30% of churned customers, and Churnkey says "up to 34%". Both are vendor figures for their own tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  Numbers I left out
&lt;/h2&gt;

&lt;p&gt;Several widely repeated figures didn't meet the bar. Blog posts titled "recovers 30% of failed payments" or "activation from 18% to 41%" named no customer, sample or method. Some dunning landing pages state a "73% average recovery rate" with no detail. A "62% of failed payments are recoverable" stat and a "14.7% for a four-email sequence" stat are each attributed to a known company, and I couldn't find either at the source. "A good sequence lifts activation by 20 to 30%" appears with no source at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Small products
&lt;/h2&gt;

&lt;p&gt;With a few dozen customers there's no reason to automate these. Emailing the person whose payment failed and asking the one who cancelled for a reason takes minutes. Baremetrics did the same with every cancelling customer at a much larger size.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the templates look like as a result
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Flow&lt;/th&gt;
&lt;th&gt;Timing&lt;/th&gt;
&lt;th&gt;Stop when&lt;/th&gt;
&lt;th&gt;Measure&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Failed payment&lt;/td&gt;
&lt;td&gt;3 emails: at failure, day 3, day 7. Different subject each time, payment link without login&lt;/td&gt;
&lt;td&gt;payment succeeds&lt;/td&gt;
&lt;td&gt;recovered ÷ payments that got at least one email&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Activation&lt;/td&gt;
&lt;td&gt;only to users who haven't done the key action&lt;/td&gt;
&lt;td&gt;key event fires, or 2 emails with no reaction&lt;/td&gt;
&lt;td&gt;signups reaching the key event in 14 days, by cohort&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Inactive users&lt;/td&gt;
&lt;td&gt;about 6 weeks after last login, one specific next step, no discount&lt;/td&gt;
&lt;td&gt;any login&lt;/td&gt;
&lt;td&gt;returned within 30 days and still active 60 days later&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cancelled&lt;/td&gt;
&lt;td&gt;pause offered before the cancel; afterwards one email matched to the stated reason&lt;/td&gt;
&lt;td&gt;resubscribes&lt;/td&gt;
&lt;td&gt;returned in 30/60/90 days, by cancel reason&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These can run on a cron job and a provider's API, in Customer.io or Loops, or in a workflow tool on top of your own provider. I'm the author of Senlo, an open-source editor and lifecycle layer that works on top of Resend, Postmark, SES or any SMTP server. It ships these four flows as workflow templates, and I'm changing two of them based on the numbers above.&lt;/p&gt;




&lt;p&gt;Sources, checked on 16 November 2026: &lt;a href="https://baremetrics.com/blog/subscription-payment-recovery-benchmarks" rel="noopener noreferrer"&gt;Baremetrics payment recovery benchmarks&lt;/a&gt;, &lt;a href="https://recurly.com/research/annual-subscription-billling-metrics-report" rel="noopener noreferrer"&gt;Recurly Annual Subscription Billing Metrics Report&lt;/a&gt;, &lt;a href="https://blog.stunning.co/lessons-learned-from-recovering-over-85-million-in-failed-payments-for-stripe-customers/" rel="noopener noreferrer"&gt;Stunning, lessons from failed payments on Stripe&lt;/a&gt;, &lt;a href="https://posthog.com/blog/how-we-built-email-onboarding" rel="noopener noreferrer"&gt;PostHog, how we built our onboarding email flow&lt;/a&gt;, &lt;a href="https://heap.io/blog/how-we-used-behavior-based-onboarding-to-improve-plg-conversion" rel="noopener noreferrer"&gt;Heap, behavior-based onboarding&lt;/a&gt;, &lt;a href="https://copyhackers.com/2017/08/saas-onboarding-email" rel="noopener noreferrer"&gt;Copyhackers, Wistia onboarding emails&lt;/a&gt;, &lt;a href="https://freemius.com/blog/re-engage-inactive-users-with-win-back-campaigns/" rel="noopener noreferrer"&gt;Freemius, win-back campaigns&lt;/a&gt;, &lt;a href="https://churnkey.co/blog/how-wavve-cut-churn-by-2-over-two-months-with-better-cancellation-flows/" rel="noopener noreferrer"&gt;Churnkey, Wavve case study&lt;/a&gt;, &lt;a href="https://baremetrics.com/blog/how-we-reduced-churn" rel="noopener noreferrer"&gt;Baremetrics, how we reduced churn&lt;/a&gt;, &lt;a href="https://www.revenuecat.com/blog/growth/win-back-customers-how-to-guide" rel="noopener noreferrer"&gt;RevenueCat, how to win back lost customers&lt;/a&gt;, &lt;a href="https://www.customersuccesscollective.com/reclaiming-lost-customers-win-back-strategies-for-customer-success-managers/" rel="noopener noreferrer"&gt;Customer Success Collective, win-back strategies&lt;/a&gt;, &lt;a href="https://www.paddle.com/help/profitwell-metrics/retain/get-started/retain-reactivations" rel="noopener noreferrer"&gt;Paddle Retain reactivations&lt;/a&gt;, &lt;a href="https://churnkey.co/guides/how-to-win-back-churned-customers" rel="noopener noreferrer"&gt;Churnkey, winning back churned customers&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Senlo: &lt;a href="https://github.com/IgorFilippov3/senlo?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lifecycle-numbers" rel="noopener noreferrer"&gt;github.com/IgorFilippov3/senlo&lt;/a&gt; · &lt;a href="https://senlo.io?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lifecycle-numbers" rel="noopener noreferrer"&gt;senlo.io&lt;/a&gt;&lt;/p&gt;

</description>
      <category>saas</category>
      <category>email</category>
      <category>startup</category>
      <category>marketing</category>
    </item>
    <item>
      <title>I priced transactional email at 10k, 50k and 200k a month. The recommended plan is often the wrong one</title>
      <dc:creator>Ihor Filippov</dc:creator>
      <pubDate>Mon, 09 Nov 2026 13:58:47 +0000</pubDate>
      <link>https://dev.to/senlo/i-priced-transactional-email-at-10k-50k-and-200k-a-month-the-recommended-plan-is-often-the-wrong-3g76</link>
      <guid>https://dev.to/senlo/i-priced-transactional-email-at-10k-50k-and-200k-a-month-the-recommended-plan-is-often-the-wrong-3g76</guid>
      <description>&lt;p&gt;Every transactional email provider has a pricing page with a slider. You drag it to your volume, the page highlights a plan, and most people pick that plan. I did the same for years.&lt;/p&gt;

&lt;p&gt;This week I went through the pricing pages of Resend, Postmark, Mailgun and Amazon SES and did the math by hand for three volumes: 10,000, 50,000 and 200,000 emails a month. Two things surprised me. The plan a page recommends is not always the cheapest way to send that volume, and the cheapest provider changed its default price for new accounts this summer.&lt;/p&gt;

&lt;p&gt;Everything below is monthly billing, transactional plans only, in USD, read from each pricing page on 9 November 2026. If you read this later, prices have probably moved. The script at the end makes it easy to rerun.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Provider&lt;/th&gt;
&lt;th&gt;10k / month&lt;/th&gt;
&lt;th&gt;50k / month&lt;/th&gt;
&lt;th&gt;200k / month&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Amazon SES (à la carte)&lt;/td&gt;
&lt;td&gt;$1&lt;/td&gt;
&lt;td&gt;$5&lt;/td&gt;
&lt;td&gt;$20&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Amazon SES (Essentials, new account default)&lt;/td&gt;
&lt;td&gt;$1.60&lt;/td&gt;
&lt;td&gt;$8&lt;/td&gt;
&lt;td&gt;$32&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mailgun&lt;/td&gt;
&lt;td&gt;$15&lt;/td&gt;
&lt;td&gt;$35&lt;/td&gt;
&lt;td&gt;$200&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Resend&lt;/td&gt;
&lt;td&gt;$20&lt;/td&gt;
&lt;td&gt;$20&lt;/td&gt;
&lt;td&gt;$125&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Postmark&lt;/td&gt;
&lt;td&gt;$15&lt;/td&gt;
&lt;td&gt;$55&lt;/td&gt;
&lt;td&gt;$245&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Each number is the cheapest way to send that volume: either the plan that covers it, or a smaller plan plus overage. That second option is where the interesting part is.&lt;/p&gt;

&lt;h2&gt;
  
  
  The recommended plan overpays at 200k
&lt;/h2&gt;

&lt;p&gt;On Resend, if you drag the slider to 200,000, the page recommends Scale at $160. But Pro with 100,000 emails costs $35, and every extra 1,000 is $0.90. So 200,000 emails on Pro is $35 + 100 × $0.90 = &lt;strong&gt;$125&lt;/strong&gt;. That's $35 a month less than the recommended plan, or $420 a year.&lt;/p&gt;

&lt;p&gt;To be fair to Resend, Scale gives you more than volume: 1,000 domains instead of 10, more webhook endpoints, a Slack channel and the option of a dedicated IP. If you need those, Scale is the right plan. If you only need the volume, it isn't. One catch: overage on Resend works through pay-as-you-go, which you have to enable on a paid plan. Without it, sending stops at the quota.&lt;/p&gt;

&lt;p&gt;Mailgun has the same pattern. At 200,000, the next step on the slider is Scale with 250,000 for $215. Scale with 100,000 for $90 plus 100 × $1.10 overage is &lt;strong&gt;$200&lt;/strong&gt;. Mailgun prints overage as "from $1.10 / 1,000", so treat $200 as the page's own lower bound, not a quote.&lt;/p&gt;

&lt;p&gt;Postmark is the exception. At 200,000 the 300k step ($245) is slightly cheaper than 125k plus overage ($115 + 75 × $1.80 = $250), so the slider is right.&lt;/p&gt;

&lt;h2&gt;
  
  
  Between the steps it's even bigger
&lt;/h2&gt;

&lt;p&gt;The gaps get wide when your volume sits just above a step. Say you send 130,000 a month on Postmark Basic. The next step is 300,000 for $245. Staying on 125,000 and paying overage for 5,000 extra emails costs $115 + 5 × $1.80 = &lt;strong&gt;$124&lt;/strong&gt;. Half the price, for the same emails.&lt;/p&gt;

&lt;p&gt;Same on Resend at 60,000: Pro 100k is $35, but Pro 50k plus 10 × $0.90 is $29.&lt;/p&gt;

&lt;p&gt;The rule I use now: before upgrading, multiply the overage rate by how far over you are, and compare it to the next plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  SES is 6 to 12 times cheaper, with a new asterisk
&lt;/h2&gt;

&lt;p&gt;At 200,000 emails SES costs $20 at the classic rate of $0.10 per 1,000. That's 6 times cheaper than Resend and 12 times cheaper than Postmark at the same volume.&lt;/p&gt;

&lt;p&gt;The asterisk is new. Since 21 July 2026, new SES accounts (and accounts with no activity since June 2025) start on a plan called Essentials at $0.16 per 1,000. You can switch to à la carte at any time, but you have to know to do it. If you opened an SES account this autumn and never touched the plan settings, you're likely paying 60% more than the number everyone quotes.&lt;/p&gt;

&lt;p&gt;And SES is cheap for a reason. You get a sending API, an SMTP endpoint and a template API. You don't get a template editor, a searchable log of sent messages out of the box, or a dashboard most people would call friendly. Bounces and complaints come as events you route yourself (SNS or EventBridge), and a new account starts in the sandbox until AWS approves production access. The price difference is real, and so is the time you'll spend building what the others ship.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the price doesn't include
&lt;/h2&gt;

&lt;p&gt;The headline price is per email. These are the other lines that matter once you're in production.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Log retention&lt;/th&gt;
&lt;th&gt;Dedicated IP&lt;/th&gt;
&lt;th&gt;Free tier&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Resend&lt;/td&gt;
&lt;td&gt;30 days on all plans&lt;/td&gt;
&lt;td&gt;$30/mo add-on, Scale only, over 3,000 emails a day&lt;/td&gt;
&lt;td&gt;3,000/mo, 100 a day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Postmark&lt;/td&gt;
&lt;td&gt;45 days, up to 365 as add-on (from $5/mo) on Pro+&lt;/td&gt;
&lt;td&gt;from $50/mo, 300,000+/mo, Pro+&lt;/td&gt;
&lt;td&gt;100/mo, test only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mailgun&lt;/td&gt;
&lt;td&gt;1 day on Basic, 5 on Foundation, 30 on Scale&lt;/td&gt;
&lt;td&gt;one included from Foundation 100k, extra $59/mo&lt;/td&gt;
&lt;td&gt;100 a day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Amazon SES&lt;/td&gt;
&lt;td&gt;depends on what you build&lt;/td&gt;
&lt;td&gt;available, priced separately&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Log retention is the one I'd look at first. When a customer says "I never got the password reset", you want to see what happened to that email. With one day of logs on Mailgun Basic, you usually can't. Postmark's 45 days by default is a real feature, not marketing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The suites price by people, not emails
&lt;/h2&gt;

&lt;p&gt;If you're comparing these with an all-in-one tool, the pricing model changes completely.&lt;/p&gt;

&lt;p&gt;Customer.io Essentials is $100 a month and includes 1,000,000 emails, but only 5,000 profiles. Each extra profile is $0.009. With 10,000 users that's $145, whether you send them 10,000 emails or 500,000. Loops starts at $49 for 5,000 subscribed contacts and $99 for 10,000, with sends unlimited.&lt;/p&gt;

&lt;p&gt;So for a product that sends a lot of transactional email to a modest user base, the suites can be cheaper than they look. For a product with many users who each get a few emails, they get expensive fast. Delivery is included in both, which the provider prices above are not. I put the two models side by side in a &lt;a href="https://senlo.io/calculator?emails=200000&amp;amp;contacts=10000&amp;amp;utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=email-costs" rel="noopener noreferrer"&gt;calculator&lt;/a&gt;, where you can enter your own volume and user count.&lt;/p&gt;

&lt;h2&gt;
  
  
  When none of this matters
&lt;/h2&gt;

&lt;p&gt;At 10,000 emails a month the difference between the most and least expensive provider is $14. That's not a decision, that's a rounding error. Pick the one whose API and docs you like, whose dashboard you can debug with at 2 a.m., and whose deliverability you trust. Postmark has built its whole brand on that last part, and its price is partly paying for it.&lt;/p&gt;

&lt;p&gt;The overage math starts to matter from roughly 100,000 a month, and the SES gap matters when email is a real line in your costs or you already live in AWS.&lt;/p&gt;

&lt;h2&gt;
  
  
  The script
&lt;/h2&gt;

&lt;p&gt;Here's the logic as a small TypeScript script. It takes each plan step from the pricing page and finds the cheapest combination for a volume. Update the numbers when the pages change.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;interface&lt;/span&gt; &lt;span class="nc"&gt;Step&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;plan&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// emails a month&lt;/span&gt;
  &lt;span class="n"&gt;price&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// USD a month&lt;/span&gt;
  &lt;span class="n"&gt;per1kOver&lt;/span&gt;&lt;span class="o"&gt;?:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// USD per extra 1,000, if the plan allows overage&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;cheapest&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;emails&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;steps&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Step&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;best&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="n"&gt;monthly&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="n"&gt;steps&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;over&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;max&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;emails&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;over&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;per1kOver&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;continue&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;monthly&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;price&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ceil&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;over&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;1_000&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;per1kOver&lt;/span&gt; &lt;span class="o"&gt;??&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;label&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;
      &lt;span class="n"&gt;over&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;
        &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="sb"&gt;`${s.plan} ${s.includes / 1000}k + overage`&lt;/span&gt;
        &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${s.plan} ${s.includes / 1000}k`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;best&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="n"&gt;monthly&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="n"&gt;best&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;monthly&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;best&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;monthly&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;best&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;resend&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Step&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;plan&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Pro"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;50_000&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;price&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;per1kOver&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.9&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;plan&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Pro"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;100_000&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;price&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;35&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;per1kOver&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.9&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;plan&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Scale"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;200_000&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;price&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;160&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;per1kOver&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.8&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;cheapest&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;200_000&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;resend&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// { label: "Pro 100k + overage", monthly: 125 }&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The full version with all four providers is in &lt;a href="https://gist.github.com/IgorFilippov3/29275cb10b799254ad963174ab036279" rel="noopener noreferrer"&gt;this gist&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where your templates live is the other cost
&lt;/h2&gt;

&lt;p&gt;The cheapest provider today may not be the cheapest next year, as the SES change shows. Switching is easy if all you do is call a send API. It's hard if your templates live inside the provider, which is what I wrote about in &lt;a href="https://senlo.io/blog/moving-email-templates-off-mandrill?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=email-costs" rel="noopener noreferrer"&gt;moving email templates off Mandrill&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I'm the author of Senlo, an open-source editor and lifecycle layer that works on top of Resend, Postmark, SES or any SMTP server, so templates and automations stay in one place while the provider stays a setting. It's one way to keep the option to move. Keeping templates in your repo with react-email or MJML is another.&lt;/p&gt;




&lt;p&gt;Prices checked on 9 November 2026: &lt;a href="https://resend.com/pricing" rel="noopener noreferrer"&gt;resend.com/pricing&lt;/a&gt;, &lt;a href="https://postmarkapp.com/pricing" rel="noopener noreferrer"&gt;postmarkapp.com/pricing&lt;/a&gt;, &lt;a href="https://www.mailgun.com/pricing/" rel="noopener noreferrer"&gt;mailgun.com/pricing&lt;/a&gt;, &lt;a href="https://aws.amazon.com/ses/pricing/" rel="noopener noreferrer"&gt;aws.amazon.com/ses/pricing&lt;/a&gt;, &lt;a href="https://customer.io/pricing" rel="noopener noreferrer"&gt;customer.io/pricing&lt;/a&gt;, &lt;a href="https://loops.so/pricing" rel="noopener noreferrer"&gt;loops.so/pricing&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Senlo: &lt;a href="https://github.com/IgorFilippov3/senlo" rel="noopener noreferrer"&gt;github.com/IgorFilippov3/senlo&lt;/a&gt; · &lt;a href="https://senlo.io?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=email-costs" rel="noopener noreferrer"&gt;senlo.io&lt;/a&gt;&lt;/p&gt;

</description>
      <category>email</category>
      <category>webdev</category>
      <category>saas</category>
      <category>aws</category>
    </item>
    <item>
      <title>What it actually costs to move your email templates to another provider</title>
      <dc:creator>Ihor Filippov</dc:creator>
      <pubDate>Wed, 04 Nov 2026 16:16:09 +0000</pubDate>
      <link>https://dev.to/senlo/what-it-actually-costs-to-move-your-email-templates-to-another-provider-2162</link>
      <guid>https://dev.to/senlo/what-it-actually-costs-to-move-your-email-templates-to-another-provider-2162</guid>
      <description>&lt;p&gt;A company I used to work for sent all of its transactional email through Mandrill (now Mailchimp Transactional). Password resets, invoices, reports, notifications. We used it for years and it worked, so nobody touched it.&lt;/p&gt;

&lt;p&gt;The problem was not the sending API. The problem was where the templates lived. This post is about that, and about what I would do differently today.&lt;/p&gt;

&lt;h2&gt;
  
  
  How templates end up inside the provider
&lt;/h2&gt;

&lt;p&gt;Mandrill, like Postmark and Amazon SES, lets you store a template on their side. Your code sends a template name and a few variables, and the provider renders the email. It sounds like a good deal. The HTML is out of your codebase, and in theory marketing can edit it without you.&lt;/p&gt;

&lt;p&gt;So the first template goes there. Then the next one. A few years later every email the product sends is a template in someone else's database, and your code only knows the names.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it cost us day to day
&lt;/h2&gt;

&lt;p&gt;Two things hurt, and neither of them was the price.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Every change needed a developer.&lt;/strong&gt; The editor was there, but in practice nobody outside the dev team used it. A small copy change became a ticket. The ticket waited until a developer had time. Then the developer opened the template, made the change, tested it, and published. A one line fix could take a week, not because the work was hard, but because it had to wait in a queue.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Finding the right template was painful.&lt;/strong&gt; With a large number of templates in a flat list, searching and navigating was awful. Names were inconsistent because they had been created by different people over several years. There was no history beyond "draft" and "published", so you could not see who changed what or roll back a bad change. Opening three templates to find the one you need was normal.&lt;/p&gt;

&lt;p&gt;None of this is a Mandrill bug. This is what "templates as a provider feature" looks like after a few years.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it cost us when we wanted to leave
&lt;/h2&gt;

&lt;p&gt;Three things pushed us to look around.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The product stood still.&lt;/strong&gt; From where we sat, almost nothing changed for years. The editor, the template list and the API looked the same as when we started. We were not alone in that feeling. In 2019, during a Mandrill outage that lasted more than 30 hours, the person who opened the HN thread wrote that the service "hasn't had an update to any of its features since it merge with Mailchimp" (&lt;a href="https://news.ycombinator.com/item?id=19084834" rel="noopener noreferrer"&gt;HN, 2019&lt;/a&gt;). Meanwhile the rest of the email tooling moved on. When the tool you depend on stops moving, you start to wonder how long it will exist at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;We were locked in.&lt;/strong&gt; Mandrill is an add on to a paid Mailchimp account, so we paid for Mailchimp without using it. Templates were in Mandrill's own dialect, with their merge tags and their editor markup. The longer we stayed, the more templates there were to convert later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The price stopped making sense.&lt;/strong&gt; Mandrill sells email in blocks of 25 000 for $20, on top of a Mailchimp Standard plan from $20 a month. At 50 000 emails a month that is about $60. Resend charges $20 for the same volume, and that includes the API, webhooks and a template workflow built around code. We were paying three times more for a tool that was not improving. (Prices checked on 2 November 2026 on each provider's pricing page.)&lt;/p&gt;

&lt;p&gt;A few things surprised us.&lt;/p&gt;

&lt;p&gt;The export gives you HTML in Mandrill's dialect. Merge tags like &lt;code&gt;*|FIRST_NAME|*&lt;/code&gt; and &lt;code&gt;mc:edit&lt;/code&gt; attributes have to be rewritten for whatever renders your email next. Conditionals do not map one to one.&lt;/p&gt;

&lt;p&gt;We had never rendered our emails outside Mandrill. So there was no set of test payloads, no expected output, nothing to compare against. We had to build that first.&lt;/p&gt;

&lt;p&gt;And the real cost was never a line in the budget. It was developer hours spent on copy changes and on finding things, and nobody added those up.&lt;/p&gt;

&lt;p&gt;This is not new. In that same 2019 thread the author put the whole problem in one sentence.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Looking to change service providers soon, as soon as we figure out how to render emails to html before sending." (adnans, &lt;a href="https://news.ycombinator.com/item?id=19084834" rel="noopener noreferrer"&gt;HN, Feb 2019&lt;/a&gt;)&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If the provider renders your templates, you cannot leave until you can render them yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  To be fair to Mandrill in 2026
&lt;/h2&gt;

&lt;p&gt;Since April 2026 templates built in Mailchimp's visual builder publish straight to Transactional. The editor is better than the one we used. What has not changed is that templates still live on their side, there is still no version history, and the export is still in their dialect.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three ways to keep templates out of the provider
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Templates in the repo
&lt;/h3&gt;

&lt;p&gt;React Email, MJML or plain HTML files next to your code. You render at send time and pass &lt;code&gt;html&lt;/code&gt; to the provider instead of a template name.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;render&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s2"&gt;"@react-email/render"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nc"&gt;PasswordReset&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s2"&gt;"./emails/password-reset"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;html&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;render&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;PasswordReset&lt;/span&gt; &lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;resetUrl&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;firstName&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;/&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;provider&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;send&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;to&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;email&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Reset your password"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;html&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You get versions in git, code review and tests. Changing provider is a one file change.&lt;/p&gt;

&lt;p&gt;You pay with deploys. Every copy change goes through a developer, which is exactly the problem we had. For a small team with ten templates this is still the right answer.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Templates in your own database
&lt;/h3&gt;

&lt;p&gt;Store MJML or HTML in your database and render it yourself. Put any editor in front of it, GrapesJS, Unlayer or a plain textarea.&lt;/p&gt;

&lt;p&gt;You get editing without deploys and no provider lock in.&lt;/p&gt;

&lt;p&gt;You pay by maintaining an email editor. Versions, preview, test sends, merge tag checks, Outlook bugs. That is a product, not a feature. We looked at it and did not do it.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. A separate template layer
&lt;/h3&gt;

&lt;p&gt;A service that only does templates, versions and triggers, and sends the result through the provider you already use. Customer.io and Braze do this, plus a lot more, and charge per contact. Senlo, which I am the author of, is an open source version of this layer. It has an MJML editor, version history and triggers, and it sends through your own Resend, Postmark, SES or SMTP account. Dittofeed and Waypoint are other options in the same space.&lt;/p&gt;

&lt;p&gt;You get non developers editing emails and developers calling one endpoint with a template id.&lt;/p&gt;

&lt;p&gt;You pay with one more service to run. The honest test is simple. Do people who are not developers change your emails more than once a month? If not, option one is cheaper.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you are choosing a provider today
&lt;/h2&gt;

&lt;p&gt;Decide where the templates live before the first one is created. Make it a place you can render from without the provider. The sending API is a commodity. The templates are what you will still be untangling years later.&lt;/p&gt;

&lt;p&gt;If you have moved templates off Postmark or SES, I would like to hear what broke for you.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://senlo.io/blog/moving-email-templates-off-mandrill" rel="noopener noreferrer"&gt;senlo.io&lt;/a&gt;. Senlo is open source (AGPL-3.0): &lt;a href="https://github.com/IgorFilippov3/senlo" rel="noopener noreferrer"&gt;github.com/IgorFilippov3/senlo&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>email</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
