How to Choose an Email Service Provider for B2B (2026)

#01What category of ESP fits you?

Our view: most B2B SaaS teams end up with a CRM-native hub for lead nurture and a product-messaging platform for in-app behaviour, or one of the two with good sync. Decide which system owns which email, and never let both send the same type of message.

#02What requirements should you write?

Write requirements as user stories with data sources:

• "When a trial user approves their first invoice in the product, start the activation flow within 15 minutes." (Source: product event.)
• "Exclude contacts whose CRM deal stage is Closed Won from nurture." (Source: CRM, synced at least hourly.)
• "Send the newsletter only to contacts with consent or soft opt-in recorded." (Source: consent fields, lesson 3.)
• "Report clicks and conversions by flow and by email." (Source: ESP plus GA4.)

Checklist

#03What should you ask vendors?

1. How do you add List-Unsubscribe and List-Unsubscribe-Post, and are they DKIM-signed?
2. How are unsubscribes synced to our CRM, and how fast?
3. How do you filter Apple MPP and security-scanner opens and clicks?
4. What happens on your shared IPs when another customer causes complaints?
5. Can we export all data, including engagement history, if we leave?
6. Where is data stored, and which sub-processors are used?
7. How is pricing calculated: contacts, sends, or events? What happens to price when the list grows?
8. What deliverability support do we get during onboarding?

#04How do you run a proof of concept?

Pick one real flow, ideally your trial onboarding or webinar follow-up. In the trial account:

1. Authenticate a test subdomain (custom DKIM and return-path).
2. Send real product events or CRM fields for 20 to 50 internal test contacts.
3. Build the flow with branching on an event.
4. Check headers in Gmail and Outlook.com.
5. Unsubscribe a test contact and time the sync to the CRM.
6. Pull a report of clicks and conversions and compare with GA4.

#05How do you score options?

Score each 1 to 5, multiply by weight, and write one sentence per score explaining it.

#06How do you migrate?

1. Inventory every flow, template, form, list, field and integration.
2. Decide what to drop. Migrations are a chance to retire dead flows.
3. Authenticate the new ESP on your domain and subdomains.
4. Move data with consent fields, suppression lists, unsubscribes and engagement history.
5. Rebuild templates and test in major clients and dark mode (lesson 13).
6. Warm up by moving the most engaged segments and transactional-like lifecycle flows first (lesson 7).
7. Run in parallel briefly, with clear rules about which tool sends what.
8. Switch forms and integrations, then freeze the old tool. Keep read access for reporting history.

#07Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Figures are illustrative, not benchmarks.

Ledgerline uses an SMB all-in-one ESP. It cannot trigger on product events, so trial onboarding is a fixed daily drip that ignores what users do.

Walkthrough

1. Requirements: seven user stories, four of them product-event triggers.
2. Category: product-messaging platform for trial and customer lifecycle, CRM-native hub for lead nurture and newsletter.
3. Proof of concept: two vendors each run the trial onboarding flow with 30 internal test users.
4. Scoring: Vendor 1 scores 4.1, Vendor 2 3.6 (illustrative). Vendor 2's unsubscribe sync took over an hour.
5. Ownership rule: product-messaging platform sends anything triggered by product behaviour; CRM hub sends everything else. Shared suppression synced both ways.
6. Migration: suppression list first, then flows, over nine weeks.

#08Common mistakes

• Picking from a feature comparison grid before writing requirements.
• Two tools both sending onboarding emails.
• Forgetting the suppression list during migration.
• Underestimating engineering work for events.
• Choosing on price per contact without modelling growth.

#09Try it yourself

Write five user stories for your email programs with the system that holds each piece of data. Score your current ESP against the checklist. If it fails two must-haves, draft a shortlist of two categories to evaluate.

#10Quick quiz

1. What should you migrate first? Answer: The global suppression list.

2. Name two must-have deliverability features. Answer: Custom DKIM and return-path, and RFC 8058 one-click unsubscribe headers.

3. Why write requirements as user stories? Answer: They expose the data source and trigger each email needs.

4. Where does cold outbound belong? Answer: A separate sequencing tool on separate domains.

#11What should you check before the next lesson?

• Requirements written with data sources.
• Current ESP scored against the checklist.
• Ownership of each email type assigned to one tool.
• Suppression list exportable.

Previous: Domain warm-up and list hygiene · Next: Segmentation and personalisation

Or return to the Email Marketing for Marketers track.

Related: Lifecycle, onboarding and nurture flows · Gmail, Yahoo and Outlook sender requirements · n8n CRM and HubSpot workflows

#12Common questions

Should a SaaS company use its CRM's email tool or a separate ESP? If your CRM's marketing module can trigger on product events and handles your volume, staying in one system reduces sync problems. Product-led SaaS with many behavioural triggers often needs a product-messaging platform connected to the CRM.

What matters most when choosing an ESP? Whether it can use your data for triggers and segments, whether it supports authenticated sending with RFC 8058 one-click unsubscribe, how it handles consent and suppression sync, and whether your team can actually run it.

How long does an ESP migration take? Plan six to twelve weeks for a B2B program with flows, including authentication, template rebuilds, data sync, warm-up and parallel running.

Do I need a separate tool for cold outbound? Yes. Cold outbound belongs on separate domains in a sequencing tool built for it, never in your marketing ESP.