Per-Email vs Per-Subscriber Pricing

Per-email vs per-subscriber pricing

Disclosure: SendNeo is built by Yorker Media, the team behind this blog.

Email software usually counts one of two things: the people stored in your audience or the messages delivered to them. Subscriber pricing is easy to explain and can include a rich automation workspace. Per-email pricing follows the work you actually perform, which can be more comfortable for a large but quiet list.

Neither model is automatically cheaper. The right comparison starts with a sending pattern, then includes the features and operational work that surround delivery.

A worked example

Imagine a newsletter with 4,000 subscribers and four issues each month.

4,000 subscribers × 4 issues = 16,000 email deliveries per month

That total excludes a welcome email, a resend to a segment, or transactional mail from a related product. It is still a useful baseline. A provider that charges for contacts sees 4,000 as the main cost driver. A provider that charges for messages sees 16,000 as the main cost driver.

SendNeo’s Starter plan is $9 per month for 30,000 emails. That covers the baseline with room for welcome messages and a small resend. Its Growth plan is $19 for 75,000 when the publication grows or a product sends transactional mail from the same account.

MailCheap’s verified $19 plan includes 20,000 emails, so it also covers the baseline. Its next verified point is $39 for 75,000. MailCheap is newsletters only and supports up to three newsletters per account.

Kit’s verified Creator price is $39 monthly, or $33 yearly, at 1,000 subscribers. Its Pro price is $79 monthly, or $66 yearly, at 1,000 subscribers. Both rise with list size, so a 4,000-subscriber quote must come from the current Kit plan page. Kit’s free plan supports up to 10,000 subscribers but does not include automations. These prices show the shape of the models: subscriber count remains part of the bill even when the number of monthly issues stays at four.

Resend’s marketing pricing is also contact-based: the verified points are $40 per month for 5,000 contacts, $80 for 10,000, and $250 for 50,000, with a free tier of 1,000 contacts. Its transactional pricing is separate, including $20 for 50,000 emails on Pro. Combining those products requires comparing two budgets, not one.

The arithmetic is not the whole decision

Per-email pricing works well when your audience is large compared with your sending frequency. A 20,000-person archive that receives one issue a month creates 20,000 deliveries; a subscriber-priced product still needs to store and bill for 20,000 people. Per-email pricing can also make a seasonal publication easier to budget, because the bill rises when the publication actually sends.

Subscriber pricing can work well when the list is the product and you use automations, forms, segmentation, or paid products constantly. The provider has a predictable reason to invest in contact management, and your cost grows alongside the audience you are trying to monetize. A creator with a small but highly active list may prefer that bundled workflow.

The key is to include the second-order work. A low delivery rate from Amazon SES direct—$0.10 per 1,000 emails on the verified list price—does not include the application you must build around it. You need contact storage, forms, double opt-in, unsubscribe handling, bounces, complaints, templates, previews, schedules, archives, reporting, and support. If you already have those pieces, direct infrastructure can be compelling. If not, the software layer is part of the comparison.

A simple forecast

Write down four numbers for each month:

• active contacts;
• issues and average recipients per issue;
• automated and transactional messages per contact;
• expected new subscribers and unsubscribes.

Then calculate both totals. For the example above:

Broadcasts:        4,000 × 4   = 16,000
Welcome messages:  estimated    = 400
Small resend:      estimated    = 400
Monthly total:                   16,800

The estimates are deliberately explicit. Do not hide them in a vague “contacts” count. If 16,800 is your actual delivery volume, a 30,000-email SendNeo Starter allowance leaves room for ordinary variation. If you start sending application receipts from the same account, put those messages into the forecast and consider a higher plan before the limit is reached.

Critical mail changes the risk calculation

A plan limit is more than a price line when a product sends password resets or purchase confirmations. SendNeo keeps transactional mail and broadcasts in separate lanes. When a monthly allowance runs out, critical transactional mail and welcome or confirmation emails can continue for up to 20% more while you upgrade; only broadcasts wait. A newsletter-only service may stop campaigns and skip welcome emails at its limit.

That behavior can be worth more than a small price difference if a new user needs a confirmation immediately. Read the provider’s exact failure mode instead of comparing only the headline allowance.

Make the choice with a trial workflow

Before moving an audience, verify a domain and send a test issue. Check the one-click unsubscribe, public archive, bounce suppression, and export. Use deterministic test addresses where available, and do not test with a purchased or scraped list. If you operate an application, send a receipt and a newsletter from the same account, then inspect usage and webhooks.

SendNeo’s Newsletters guide covers audiences, CSV imports, and broadcasts. Deliverability explains list hygiene and authentication. For a creator-focused comparison, read Kit alternatives.

A fair conclusion

Per-email pricing is a better fit when sending frequency is the main source of cost and contact storage should remain unlimited. Per-subscriber pricing is a better fit when contact growth, automations, and a creator business workspace are central. Use your own issue calendar to decide. For 4,000 subscribers and four issues, 16,000 monthly emails makes the distinction visible: SendNeo Starter is $9 for 30,000, MailCheap is $19 for 20,000, and Kit’s cost follows the 4,000-subscriber tier rather than the 16,000-message count.

The best plan is the one whose limit, failure behavior, and workflow you can explain before launch.

Watch the quiet months too

The same newsletter can have a very different budget in a launch month and a quiet month. A per-email plan may fall to a lower tier when you publish less, while a per-subscriber plan continues to count every stored contact. Conversely, a large launch with several reminders can push a per-email allowance sooner than expected. Forecast the busy case and the quiet case before you choose a tier.

Also count non-newsletter mail. A membership product may send an invitation, confirmation, receipt, and password reset for each new account. Those messages are valuable, but they are still deliveries. Keeping them in the same forecast prevents a newsletter estimate from hiding the traffic that matters most.

When you compare plans, write the failure behavior beside the price. Does a broadcast wait, does a welcome message stop, and can a transactional message continue while you upgrade? A clear answer often matters more than a small difference between two monthly totals.

Keep the forecast in a small spreadsheet or text file and update it after each issue. Comparing the estimate with actual delivered and bounced counts shows whether the plan is sized for real behavior rather than a hopeful list size. That feedback is more useful than a generic pricing calculator.