·Updated ·20 min read

Email Deliverability Guide: 13 Tools, Checks, and a Safer Pilot

A practical email deliverability guide for SaaS and marketing teams: authentication, permission, provider fit, list-size pricing, and a seven-day pilot.

If you are fixing placement problems today, start with Postmark. It keeps application mail such as receipts, password resets and account alerts on its own message streams, separate from newsletters and promotions, and its entry plan is $15 a month for 10,000 emails when billed monthly. That separation is the main reason to begin there: when transactional and campaign traffic use distinct sender identities, a bad newsletter week is less likely to contaminate the password reset your customers need to receive.

Deliverability is not a provider score and it is not the same thing as an open rate. A receiving mailbox decides whether a message is accepted, placed in the inbox, routed to spam or rejected, using signals that include authentication, domain and IP reputation, recipient behavior, message consistency, list quality and policy compliance. This guide is written for a team diagnosing placement or choosing a sending stack. It does not promise an inbox outcome, because no vendor can guarantee one.

Prices in this guide are the figures shown on each vendor’s pricing page on October 7, 2026. Plans, free allowances and volume bands change, so confirm them on the linked page before you commit. Model the list size you expect in twelve months, not the one you have today, because the cheapest entry plan is often the most expensive one after a growth step.

Which tool to start with, and why

The right provider depends on the job. Transactional streams, newsletters, product lifecycle journeys and ecommerce flows have different data needs, different consent rules and different failure modes, so a single “best” tool does not exist. The comparison below gives each of the 13 providers a best-fit job, the starting price with its plan and billing basis, and the limitation that matters most for deliverability work.

ToolBest forStarting price (plan, billing)Key limitation
PostmarkTransactional streamsBasic from $15 a month for 10,000 emails on monthly billing; its free allowance is 100 emails monthlyNot a newsletter or segmentation suite
ResendDeveloper-owned application emailFree for 3,000 emails a month; Pro $20 a month for 50,000 emailsCampaign and segmentation features are thinner than a marketing suite
Twilio SendGridAPI delivery plus campaignsEssentials $19.95 a month (50,000–100,000 emails in the plan selector); free Marketing Campaigns plan up to 2,000 contactsTwo product surfaces need separate governance
MailgunProgrammable sending and eventsBasic $15 a month for 10,000 emails; free plan 100 emails a dayPreferences, campaigns and audience reporting are your work
Amazon SESAWS-based sending infrastructure$0.16 per 1,000 emails on the Essentials tier (0–10M emails a month), usage-basedYou assemble the surrounding deliverability system yourself
MailerLiteSmall-team newslettersIts no-cost tier holds 250 subscribers; Comfort is $12 a month for 500 subscribers, or $10.80 billed annuallyList-first model can limit event-heavy journeys
KitCreators and publishersFree up to 10,000 subscribers; Creator $33 a month, billed annuallyNot an application event system
MailchimpGeneral campaign operationsFree up to 250 contacts; Standard from $20 a month at the 500-contact selector, billed monthlyContact counts and tiers drive the real bill
BrevoCampaigns plus transactional and SMSFree at 300 sends a day; Starter $9 a month from 5,000 emailsConsent, suppression and billing differ per channel
Customer.ioEvent-driven SaaS lifecycleEssentials from $100 a month, billed monthlyNeeds disciplined event instrumentation
UserlistSaaS user and account messagingBasic from $10 a monthWeaker fit for commerce catalog data
KlaviyoCommerce behavior and catalogFree up to 250 profiles and 500 sends a month; Email from $20 a month for 500 profilesProfile growth and channels raise cost quickly
OmnisendEcommerce email and SMSFree for 250 contacts; Standard $11.20 a month for 500 contacts, shown with a first-three-month offerConsent and frequency rules need governance

Two reading notes apply to the table. First, the “starting price” column shows the cheapest paid entry point, not the plan most teams end up on. Second, a free allowance is not a deliverability guarantee. Free plans often have daily caps, branding, feature gates or smaller volume bands, and those limits can force an early migration in the middle of a launch.

Map the job before you choose the tool

Most deliverability failures start with a mismatch between the job and the platform. A team sends password resets through a newsletter tool because it was the first account created, then wonders why a campaign complaint spike delays account mail. Another team buys an event-driven lifecycle platform for a product that only sends a monthly digest. The table below turns the decision into a short lookup. Read it as a starting filter, then test the shortlist against your own data model.

If you need…PickBecause
Receipts, resets and alerts through an APIPostmarkMessage streams keep transactional mail distinct from campaigns and expose delivery events
Code-first sending with a free starting pointResendThe send path from application code to rendered email is short, and the free allowance covers early volume
An established API and a campaign surfaceTwilio SendGridBoth products sit under one account, but only if sender identities and suppression are governed
Delivery webhooks and validation in your stackMailgunEvent callbacks and validation are built for engineering-owned pipelines
The lowest per-message cost inside AWSAmazon SESUsage pricing per 1,000 emails suits high volume, provided your team owns the rest
A small newsletter with forms and simple automationsMailerLite or KitPublishing, forms and sequences are the core workflow, not event processing
Campaigns with a familiar editor and many integrationsMailchimpEditor, automations and integrations matter more than event context
Campaigns plus transactional and SMS from one vendorBrevoOne relationship covers several channels, with separate rules to configure for each
Lifecycle messages driven by product eventsCustomer.io or UserlistJourneys respond to activation, usage and plan changes rather than a manually maintained list
Purchase-aware store email and SMSKlaviyo or OmnisendCatalog, cart and order data drive segmentation and timing

The non-negotiable authentication checks

Authentication is the first deliverability control you own completely. It does not depend on a recipient’s mood or a campaign’s copy. Start with SPF. Publish one SPF record for each sending domain that covers the senders you actually authorize, because multiple SPF records do not combine and the SPF standard limits the number of DNS lookups a record may trigger. A record that has accumulated unused includes from old vendors is a common cause of failures, so review it whenever you add or remove a sending service.

Next, configure DKIM. Each provider gives you a selector and a public key to publish in DNS. After publishing, send a test message and confirm the signature validates against the domain in the visible From address. Alignment is the point that teams often miss: a message can pass a check on a technical domain while failing to align with the address the recipient sees.

Then add DMARC. Begin with a monitoring policy and a reporting address so you can discover legitimate senders you have forgotten about. Read the aggregate reports for a few weeks, fix alignment failures, and only then move toward an enforcement policy. Enforcing too early can block legitimate mail from a forgotten service, so treat the move from monitoring to enforcement as a deliberate change with a named owner. Where the risk and volume justify it, keep marketing traffic and application traffic on clearly owned subdomains so that each stream can be authenticated, monitored and suspended independently.

Google’s email sender guidelines and Microsoft’s sender support guidance describe mailbox-provider expectations. Use them as policy references, then confirm your own DNS by checking the published records independently rather than trusting a dashboard that says “verified”.

Permission, suppression and complaints

Authentication proves who is sending. Permission decides whether the message should be sent at all, and mailbox providers respond strongly to recipients who report mail as unwanted. Use permissioned acquisition with a visible sender identity and an easy unsubscribe path. Keep subscription types separate, so a person who wants product updates is not automatically enrolled in promotions. Record the source, the timestamp and the subscription type for each contact, because an unlabeled list cannot be defended when a complaint arrives.

Do not infer marketing consent from a receipt, a password reset or an account creation unless your legal and product basis is clear. Transactional mail and marketing mail carry different expectations, and a platform that imports every address into one list makes that distinction easy to lose. Suppress hard bounces and complaints promptly. Make re-engagement measurable, and stop sending to cold cohorts that never open or click rather than hoping they will recover.

Suppression must survive a tool change. A platform can expose suppression events, but your team still owns the data contract. The common failure is a unsubscribed address that reappears in a second system after a sync or a fresh import. Before you send to any imported list, compare its counts with the source, confirm that unsubscribes and complaints are included, and keep a single authoritative suppression list that every sending service reads from.

Measure the right failure

Track accepted, deferred, bounced, complained, unsubscribed and, where a provider offers it, placement or reputation signals. Opens are noisy. Image blocking, privacy features and rendering differences all distort them, so an open-rate drop is a prompt to investigate rather than proof of spam placement. Replies, clicks to a fixed destination and conversions are usually more reliable indicators of engagement.

Break every metric down by mailbox provider, stream, sending domain, cohort and template. A single aggregate bounce rate hides the stream that is failing. Do not apply a universal “safe” bounce or complaint threshold without considering your provider, list source, traffic mix and each provider’s reporting definitions. The right threshold for a purchased list and for a signup form on a documentation site are not the same, and treating them as equal is how teams end up with a clean dashboard and an unhappy inbox.

The 13 tools, one by one

The profiles below follow the same structure: the audience the tool serves best, what it does well for that audience, where it falls short, its price with the plan and billing basis, and a link to the vendor’s pricing page. None of these profiles is a ranking. A tool that is a poor fit for one job can be the right choice for another.

Postmark

Best for: teams that need transactional email to stay distinct from promotional campaigns. Receipts, account alerts and password resets are the core use.

What it does well: the message-stream model makes ownership and debugging clearer. A developer can trace a message from the application event to the delivery outcome, and template changes can be reviewed as a normal part of the codebase.

Where it falls short: it is not a replacement for segmentation, editorial campaigns or product-led nurture. If you also send newsletters, you need a second system or a carefully separated stream plan, along with a preference model that both systems respect.

Price: Basic from $15 a month for 10,000 emails, billed monthly. Pro starts at $16.50 a month and Platform at $18 a month for the same 10,000-email entry point. The free plan covers 100 emails a month with no overages. Check volume bands and add-ons on the Postmark pricing page.

Resend

Best for: developer teams that want an API-first path from an application event to a rendered email, with templates owned by engineering.

What it does well: the send path is short and the developer workflow is direct. Webhooks report events back into your system, so bounce and complaint handling can be part of the normal application code.

Where it falls short: campaign segmentation and preference management are thinner than in a dedicated marketing suite. Marketing plans are priced by contacts and sit beside the sending plans, so confirm which product surface covers each kind of message before you move anything.

Price: Free for 3,000 emails a month, with a daily cap and up to 3 domains. Pro is $20 a month for 50,000 emails, and Scale is $90 a month for 100,000 emails. On the marketing side, the free plan covers 1,000 contacts and Pro marketing is $40 a month at 5,000 contacts. See the Resend pricing page for current bands.

Twilio SendGrid

Best for: organizations that want an established email API and a separate campaign surface under one account, with engineering and marketing sharing the same provider.

What it does well: the integration surface is broad and the platform has a long operating history. The Email API and Marketing Campaigns can be run as separate workflows, which suits a split model where transactional delivery is owned by engineering and broadcasts are owned by marketing.

Where it falls short: two product surfaces create blind spots. Sender identities, unsubscribe groups, suppression synchronization and template ownership all need written agreement, or the same person can receive a suppressed message through the other product.

Price: Essentials is $19.95 a month for 50,000 to 100,000 emails in the plan selector, and Pro is $89.95 a month for 100,000 to 2.5 million emails. Marketing Campaigns has a free plan for up to 2,000 contacts and 6,000 emails a month. The Email API free trial allows 100 emails a day for 60 days. Compare both plan families on the Twilio SendGrid pricing page, because they are priced differently.

Mailgun

Best for: engineering-led teams that treat email as programmable infrastructure and need delivery events, validation and failure handling inside their own stack.

What it does well: delivery webhooks and API control over domains and sending give engineers direct access to accepted, deferred, bounced and complained states. Email validation is available as a separate service, which helps clean addresses before they reach a sending plan.

Where it falls short: preference management, campaign authoring and audience reporting remain your responsibility, so you will usually pair it with another system for newsletters.

Price: the free plan allows 100 emails a day. Basic is $15 a month for 10,000 emails, Foundation is $35 a month for 50,000 emails and Scale is $90 a month for 100,000 emails, with the Foundation and Scale prices applying after the first month. Model validation, domains and retention on the Mailgun pricing page.

Amazon SES

Best for: teams already operating in AWS that are willing to own the surrounding deliverability system, including DNS, identity configuration, event processing and monitoring.

What it does well: pricing is usage-based per 1,000 emails, and the service composes with other AWS building blocks. For high-volume application or bulk sending, the per-message cost is easy to model.

Where it falls short: SES does not give a marketer a campaign operating model. You need an owner for IAM permissions, DKIM, bounce and complaint processing, CloudWatch visibility, quotas and any production-access request. Adjacent AWS services are billed separately.

Price: $0.16 per 1,000 emails on the Essentials tier for 0–10 million emails a month, with Pro at $0.22 and Enterprise at $0.23 per 1,000 in the same band. For example, 10,000 emails at $0.16 per 1,000 comes to 10 × $0.16 = $1.60 a month before adjacent costs. Eligible new AWS customers can receive up to $200 in credits. See the Amazon SES pricing page for regional details.

MailerLite

Best for: small teams that publish newsletters, run forms and maintain a few straightforward automations, with a marketer who owns the work from signup to send.

What it does well: the path from signup to campaign is short, and forms and publishing are simple to set up. For a single-audience newsletter, the list model keeps consent and unsubscribes easy to understand.

Where it falls short: a list-first workflow can become limiting for event-heavy SaaS lifecycle logic or complex permissions across several teams. If your messages depend on product state, the list will become a poor proxy for what a person has actually done.

Price: MailerLite's free allowance is 250 subscribers and 2,500 emails monthly. Comfort starts at $12 a month on monthly billing, or $10.80 a month billed annually, for 500 subscribers; Power starts at $25 a month, or $22.50 billed annually, at that tier with unlimited monthly emails. Larger bands are on the MailerLite pricing page.

Kit

Best for: creators and publishers whose core unit is a broadcast, a sequence, a tag or a subscriber relationship. The decision usually starts with editorial ownership and audience growth.

What it does well: the free plan includes unlimited email broadcasts, tagging and segmentation for up to 10,000 subscribers, which makes it useful for early publishers. Creator adds visual automations and sequences, and Pro adds deliverability reporting.

Where it falls short: Kit is not an application event system. Product telemetry, account-level data and complex transactional separation usually require integrations or a second provider. Automations and sequences start on a paid plan, so check that the features you plan to use are included.

Price: Creator is $33 a month when billed annually, and Pro is $66 a month when billed annually. The free plan is available up to 10,000 subscribers. Paid plans include a 14-day free trial with no credit card required. Confirm subscriber bands and features on the Kit pricing page.

Mailchimp

Best for: general campaign teams that value a familiar editor, conventional automations and a broad integration ecosystem. It suits recurring campaigns with several stakeholders.

What it does well: the editor and integrations lower training friction, and the automation options cover common welcome and nurture patterns. Many teams already know how to run it.

Where it falls short: the model is contact-led rather than event-led, and the contact count drives cost. Inactive records, feature tiers and send allowances can make the real bill and the real workflow less obvious than the entry price suggests.

Price: Mailchimp's free allowance is 250 contacts and 500 sends monthly. Standard starts at $20 a month at the 500-contact selector with up to 6,000 emails; 2,501–5,000 contacts are listed at $100 monthly for up to 60,000 emails, and 5,001–10,000 at $135 for up to 120,000. See the Mailchimp pricing page for current bands.

Brevo

Best for: teams that want campaign email, transactional delivery and SMS under one vendor relationship, with a send-volume model that suits a large but lightly mailed audience.

What it does well: the free plan allows 300 sends a day for up to 100,000 contacts, and the paid plans combine campaigns, transactional mail and SMS in one account. That consolidation can simplify a small stack.

Where it falls short: each channel has its own consent, suppression and billing questions. The free plan’s daily limit can block a launch, and the difference between Starter and Standard matters once automation and A/B testing are needed.

Price: the free plan allows 300 daily sends. Starter is $9 a month from 5,000 emails with no daily sending limit, and Standard is $18 a month from 5,000 emails with automation, A/B testing and advanced reports. Professional starts at $499 a month for 150,000 to 10 million monthly sends and up to 2 million contacts. The yearly toggle on the pricing page carries a discount, so compare both views. Use the Brevo pricing page for current bands.

Customer.io

Best for: product-led SaaS teams whose messages depend on activation, usage, billing or other stable product events, rather than a manually maintained list.

What it does well: journeys respond to product state, so a message can change or stop when a user activates, downgrades or churns. Event context is the main reason to choose it over a list-based tool.

Where it falls short: instrumentation, identity resolution, data retention and QA become production responsibilities. Without a shared event vocabulary between engineering and marketing, the journeys will be hard to trust. Pricing scales with profiles, so a growing product should model its next profile band early.

Price: Essentials starts at $100 a month. Profile-based Essentials prices are $145 a month at 10,000 profiles, $235 at 20,000, $325 at 30,000, $415 at 40,000 and $505 at 50,000 or more, all billed monthly. Eligible early-stage companies that have raised under $10 million can receive 12 months free through the Startup Program. Check the Customer.io pricing page for eligibility and current bands.

Userlist

Best for: SaaS teams that need product-qualified segments and customer education without adopting a broad CRM. It fits when the important distinction is account, user, plan or product state.

What it does well: the model is oriented toward SaaS users, companies and plans, and in-app messages sit alongside lifecycle email. For a team that already keeps user and account identities consistent, the setup is comparatively direct.

Where it falls short: it is a weaker fit for catalog merchandising and for infrastructure-only delivery. The team must keep user and account identities consistent, because the segments are only as good as the underlying data.

Price: Basic starts at $10 a month and Professional at $12 a month. The pricing page also lists $149 a month for Basic at up to 10,000 users and $349 a month for Professional at up to 10,000 users. Enterprise is priced with custom message limits. Confirm tracked-user limits and feature scope on the Userlist pricing page.

Klaviyo

Best for: commerce brands whose relevance and deliverability depend on catalog, browse, cart, order and customer-value data.

What it does well: purchase-aware segmentation and flows make timing and content depend on store behavior. When store events are timely and identities are resolved, a marketer can explain why a flow sends and when it must stop.

Where it falls short: profile growth and optional channels increase cost, and data quality decides how relevant the messages are. Poor catalog sync or duplicated customer records will show up as wrong messages, not just as a bill.

Price: Klaviyo's free allowance is 250 active profiles and 500 email sends monthly. Email plans start at $20 a month for 500 profiles, $60 for 2,500, $150 for 10,000 and $400 for 25,000, billed monthly; SMS is separate. See the Klaviyo pricing page for current profile bands.

Omnisend

Best for: small and mid-sized ecommerce teams comparing email and SMS with ready-made store journeys, such as cart recovery and post-purchase sequences.

What it does well: store-oriented templates and flows reduce setup time, and email and SMS sit in one place. The coordination between browse, cart and order triggers is the main advantage for a store with a modest team.

Where it falls short: consent and frequency rules across email and SMS need careful governance, and SMS pricing scales by country and volume. Teams often underestimate how many channels a single profile can receive.

Price: the free plan includes 250 contacts, 500 emails and 500 web push notifications a month. Standard is $11.20 a month for 500 contacts and 6,000 emails, shown with a 30% offer for the first three months. Pro is $41.30 a month for 2,500 contacts with unlimited monthly emails, and SMS starts at $0.007 per message. Check the Omnisend pricing page for the offer terms.

What it costs at three list sizes

Pricing units differ between these tools. Some charge by contacts, some by profiles or subscribers, some by monthly emails and some by usage. The table below compares what each provider lists for three sizes, and each cell states its own unit. Where a provider does not publish a price for a size on the pricing page, the cell says so rather than estimating one. Prices are monthly unless a cell says otherwise.

ToolSmaller listMiddle listLarger list
Mailchimp (contacts)500 contacts: Standard $202,501–5,000 contacts: $100 (up to 60,000 emails)10,001–15,000 contacts: $230 (up to 180,000 emails)
MailerLite (subscribers)Up to 250 subscribers: free500 subscribers: Comfort $12 monthly, or $10.80 billed annuallyPricing on request for larger subscriber tiers
Brevo (monthly emails)5,000 emails: Starter $95,000 emails: Standard $18150,000 emails: Professional $499
Kit (subscribers)Up to 10,000 subscribers: freeCreator $33 when billed annuallyPro $66 when billed annually
Klaviyo (profiles)500 profiles: Email $202,500 profiles: Email $6010,000 profiles: Email $150
Omnisend (contacts)500 contacts: Standard $11.20 (offer rate shown)2,500 contacts: Pro $41.30Pricing on request beyond the Pro band
Customer.io (profiles)10,000 profiles: Essentials $14520,000 profiles: Essentials $23540,000 profiles: Essentials $415
Userlist (users)Basic from $10Basic $149 at up to 10,000 usersProfessional $349 at up to 10,000 users
Postmark (monthly emails)10,000 emails: Basic $1550,000 emails: Basic $55125,000 emails: Basic $115
Resend (monthly emails)3,000 emails: Free50,000 emails: Pro $20100,000 emails: Scale $90
Twilio SendGrid (monthly emails)2,000 contacts and 6,000 emails: Marketing Free50,000 emails: Essentials $19.95100,000 emails: Pro $89.95
Mailgun (monthly emails)10,000 emails: Basic $1550,000 emails: Foundation $35100,000 emails: Scale $90
Amazon SES (monthly emails)10,000 emails: $1.60 (10 × $0.16)50,000 emails: $8.00 (50 × $0.16)100,000 emails: $16.00 (100 × $0.16)

Read the table with three cautions. Amazon SES and the other usage-based services exclude adjacent infrastructure, so the email line is only part of the monthly cost. Mailchimp, Klaviyo and Customer.io prices can jump at a band boundary, so a list that grows from 4,900 to 5,100 contacts can move to a different row. Finally, the cells show list-size bands as published. If a band boundary is close to your current size, model the next band before you commit to an annual term.

Setup and migration checklist

Moving a sending stack is the riskiest moment for deliverability, because domains, DNS records, suppression lists and templates all change at once. Work through the checklist below before the first live send from the new platform. Each row ends with a condition you can check, so the team does not rely on memory.

StepWhat to doDone when
1. Inventory sendersList each domain, subdomain, stream, sending service and its ownerEvery sending service has a named owner
2. Publish SPFKeep one SPF record per sending domain that covers only authorized sendersOne record exists, with no duplicate records and no stale includes
3. Configure DKIMEnable keys in each provider and publish the selectors in DNSTest messages show a valid signature aligned with the From domain
4. Publish DMARCStart with a monitoring policy and a reporting addressAggregate reports arrive and someone reads them on a schedule
5. Separate streamsUse distinct subdomains for transactional and marketing mail where the volume or risk justifies itEach stream has its own sender identity and suppression rule
6. Import suppression firstMove hard bounces, complaints and unsubscribes before importing any active contactsSuppressed counts in the new system match the source
7. Verify webhooksConfirm bounce, complaint and event callbacks reach your systemA test event appears in the log of each system that needs it
8. Dry-run the exitExport contacts, consent history and templates from the new platformA complete export has been opened and checked, not just downloaded

Migrate in cohorts rather than all at once. Start with the most engaged contacts who gave clear consent, watch the provider-level signals for a week, and only then bring in the older or colder segments. Keep the old platform running in a read-only or paused state until the export is verified, because a rushed cutover is where consent history goes missing.

A seven-day deliverability pilot

Run a short pilot before committing a team or a budget to a new stack. Use a permissioned cohort, keep customer-facing sends in test or holdout mode, and define the outcome in advance. The pilot is not meant to prove that a vendor guarantees inbox placement. It is meant to prove that your team can authenticate, send, observe, suppress and recover correctly.

  1. Day one: inventory domains, streams, senders, consent types and owners, and write them down.
  2. Day two: publish or verify SPF, DKIM and DMARC, and separate streams where the volume justifies it.
  3. Day three: send transactional, campaign and lifecycle test messages, and save the headers, rendered output and provider event identifiers.
  4. Day four: trigger duplicate, late, bounced, complained, unsubscribed and converted states, then check the suppression logs and journey exits.
  5. Day five: compare delivery signals for Gmail, Outlook and Yahoo test accounts, and record them by provider, stream and cohort instead of as one aggregate rate.
  6. Day six: model the current list size and the next growth milestone against the official pricing pages, including contacts, sends, seats, channels and overages.
  7. Day seven: decide, document the remediation needed, or stop the migration. Record a pass or fail scorecard, a rollback plan and a named owner for each open issue.

A scorecard for a deliverability review

Use this scorecard at the end of the pilot and again each quarter. Each area has a pass condition and a red flag. A single red flag is a reason to investigate, and a pattern of red flags is a reason to reconsider the stack.

  • Authentication. Pass when every authorized sender aligns and DMARC reports are reviewed on a schedule. Red flag when an unknown service sends from the same domain.
  • Permission. Pass when source, timestamp, subscription type and opt-out are inspectable for each contact. Red flag when a receipt, an account or purchased data is treated as marketing consent.
  • Reputation operations. Pass when bounces, complaints and changes are monitored by provider and stream. Red flag when a sudden drop is explained only by open rate.
  • Suppression. Pass when unsubscribe, complaint, hard bounce and conversion exits are tested in every system. Red flag when a suppressed address can be re-added by another system or a fresh import.
  • Portability. Pass when contacts, consent, templates, events and suppression have a tested export path. Red flag when the vendor holds the only copy of critical consent or event history.

How to choose between two tools that both pass

When two tools both pass your checklist, the decision should rest on the job, the cost at your next milestone and the effort your team would otherwise spend by hand. Start by confirming that each tool can separate the streams you need, can read a single suppression list, and can export contacts and consent history without a support ticket. A tool that fails any of those three conditions is not a candidate, however attractive its interface.

Then compare the cost at the list size you expect in twelve months, using the official pricing page for each tool. A cheaper entry plan can become the more expensive option once a band boundary is crossed. Where a stronger tool removes manual work your team already does, such as webhook plumbing for billing events or a suppression list kept in a spreadsheet, count that saved effort as a real cost difference, because it is the cost you will otherwise pay in incidents.

Finally, ask how exports work before you sign, not when you leave. Request a sample export of contacts, consent history and templates, and check whether the file contains the subscription type and source for each contact. Those fields are what allow you to defend a list after a complaint, and they are the first thing lost in a poorly planned move.

Frequently asked questions

Does a reputable provider guarantee inbox placement?

No. Providers can offer infrastructure, authentication guidance, feedback processing and monitoring, but recipient mailbox providers make their own decisions. Your consent, content, sending pattern, list quality and domain reputation still matter, and no vendor can honestly promise an inbox outcome.

What is the difference between SPF, DKIM and DMARC?

SPF lists the servers allowed to send for a domain. DKIM adds a cryptographic signature to each message so that the receiver can confirm it was not altered and was signed by an authorized key. DMARC tells receivers what to do when a message fails alignment with the visible From domain, and it sends you reports so you can see who is sending on your behalf. You need all three for a reliable setup, and DMARC depends on the other two being aligned.

Should transactional and marketing mail use separate providers?

Sometimes. Separate providers or separate streams can isolate ownership and reputation risk, but they add integration and suppression work. Decide from your traffic volume, your tolerance for failure, the team that owns each kind of mail and the consequences of a campaign problem reaching account-critical messages.

Do I need a dedicated IP address?

Not automatically. A dedicated IP adds control and responsibility, including consistent volume and a warm-up period. Many teams are better served by a reputable shared pool until their volume, policy requirements and operational maturity justify dedicated infrastructure. Ask the provider for its current thresholds rather than relying on a universal number.

What should I check first if messages start landing in spam?

Segment the symptom by mailbox provider, stream, domain and recent change. Verify SPF, DKIM and DMARC alignment, inspect bounces and complaints, pause questionable acquisition sources, review recent volume and protect your most engaged recipients while you investigate. Do not switch providers until you know whether the failure comes from data, policy, authentication, content or reputation.

Are the prices in this guide final?

No. The figures reflect each vendor’s pricing page on October 7, 2026. Plans, free allowances, band boundaries and promotional offers change. Confirm the current price on the linked pricing page before you sign, and model the list size you expect after your next growth step.

Can I move a list to a new tool without losing consent history?

Yes, if the export includes the source, timestamp and subscription type for each contact, and if suppression is imported before any active contacts. Never import a list that omits unsubscribes or complaints. Compare the new system’s counts with the source, keep the old platform readable until the export is verified, and retain the consent record outside any single vendor.