Transactional Email Costs for a Small SaaS at 500, 3000 and 10000 Emails
A transparent cost example for Resend, MailerSend, Plunk and Loops, with monthly pricing, daily-cap assumptions and calculations you can check.
A small email bill can hide an important constraint: the service must accommodate your busiest sending day, not just the monthly total. Contact-based billing and shared usage allowances also make apparently similar free plans behave differently.
Here is a worked example for Resend, MailerSend, Plunk Cloud and Loops at 500, 3,000 and 10,000 transactional messages. Published prices were checked on November 18, 2026. These are calculations from documented plans, not customer invoices or a delivery-performance test.
The workload we are calculating
Consider a hypothetical SaaS with 500 subscribed contacts and at most 500 unique recipients, all within the first 1,000 contacts where that restriction applies. Each row is a separate steady-state 30-day scenario.
- Every message has one recipient and no attachment, CC or BCC.
- All sending is transactional. There are no marketing, workflow-campaign or inbound messages consuming the same allowance.
- Free-plan scenarios send no more than 100 messages on any day, including each UTC day for Resend, and have enough allowance left in the relevant billing or rolling window.
- The account and sending domain meet the provider's production requirements.
- Prices use public USD monthly billing, excluding tax, optional services, promotional credits, trials, annual discounts and implementation costs.
- Paid scenarios assume an active plan for the whole period. They do not model mid-cycle upgrades, prorating or verification credits.
For Loops, the fixed 500-contact scenario avoids ambiguity around the free recipient boundary. At 10,000 sends, it assumes a voluntary upgrade to the entry paid tier, even though the contact count is below the free threshold.
Modeled monthly service charges
Swipe or scroll to compare all columns.
| Service | 500 messages | 3,000 messages | 10,000 messages |
|---|---|---|---|
| Resend | $0 — Free | $0 — Free, daily-cap condition applies | $20 — Pro |
| MailerSend | $0 — approved Free | $7 — Hobby | $14.50 estimate — Hobby plus overage |
| Plunk Cloud | $0 — Free | $3 estimate — all sends on paid usage billing | $10 estimate — all sends on paid usage billing |
| Loops | $0 — Free, contact and rolling-window conditions apply | $0 — Free, same conditions | $49 — entry paid contact tier |
Plan sources: Resend pricing, MailerSend plans, Plunk pricing, Loops pricing. Use the selection guide to compare capabilities alongside these charges.
How each estimate is calculated
Resend
The published Free allowance covers the first two scenarios under the stated daily and usage conditions. The 10,000-message scenario requires a paid plan; the $20 Pro tier includes 50,000 emails. No Pro overage is needed for this example. Plan definitions
The 3,000-message free case is tight: 30 days × 100 messages = 3,000, leaving no room for an extra counted send or inbound message. A workload with 150 messages on one UTC day would need a different plan or sending schedule even if the period total stayed the same. Quota accounting
MailerSend
The approved Free plan covers 500 messages. Hobby covers 3,000 within its 5,000-message allowance. For 10,000, its documented extra-usage rate gives:
$7 base fee + ((10,000 − 5,000) ÷ 1,000 × $1.50) = $14.50.
This assumes the account's configured extra-usage limit permits the sends. The Free plan does not become pay-as-you-go when its allowance runs out. Overage and billing limits
Plunk Cloud
The Free plan covers 1,000 messages. The paid-plan model charges all usage at $0.001 per email, so the other scenarios are:
3,000 × $0.001 = $3.
10,000 × $0.001 = $10.
The calculation does not subtract a free allowance from an already paid period. It also excludes usage from inbound messages or other sending types. Attachments have different credit accounting, so adding them changes this model. Billing and usage accounting · Transactional pricing explanation
Loops
The first two scenarios fit its 4,000-send rolling 30-day allowance under the fixed contact assumptions. The 10,000-message scenario uses the entry paid subscription at $49, which includes unlimited sends. The paid price depends on subscribed contacts; it is not a universal price for every business sending 10,000 emails. Billing model
When this table stops matching your bill
Recalculate when your daily peaks exceed a free limit, a message has multiple recipients, another email type shares the quota, or your contact tier changes. Also check what happens when your own spending limit is reached. A provider's per-second rate is a different constraint from its daily or monthly allowance.
A 30-day comparison is not a promise that every provider resets on the same date. Loops uses a rolling window; other services apply their own billing-period rules. Check the current account usage before relying on remaining free capacity.
Price is only one input to the decision
At 10,000 messages, Plunk has the lowest modeled service charge among these four under the specified assumptions. That result does not establish the lowest total operating cost or best delivery performance.
For troubleshooting, Resend documents 30-day email and log retention. MailerSend Hobby's activity history is shorter and complete request logs have separate plan requirements. Plunk separates request-log retention from stored message bodies. Loops provides transactional delivery metrics but does not track opens and clicks for those messages. Resend retention · MailerSend request logs · Plunk retention · Loops metrics
Use the Resend vs MailerSend comparison when choosing between those two, or inspect the individual Resend, MailerSend, Plunk and Loops details before connecting your application.