
The 38% Open Rate That Wasn't Worth a Penny
Last year a mid-size SaaS team I know celebrated a 38% open rate on a weekly newsletter. They'd just migrated to a new ESP, the design looked great, and engagement metrics ticked up. Then they checked deliverability: their messages were landing in junk for a quarter of their database, watering down every downstream metric. The tools weren't the problem β the setup was. This guide is a step-by-step walkthrough of choosing and configuring an email marketing stack that actually gets delivered, segmented right, and measured accurately, rather than one that just looks good in a screenshot.

Step 1: Split Email Tools Into Three Jobs
Too many teams buy one "email marketing platform" expecting it to do everything: send bulk campaigns, run automation, score leads, and produce revenue attribution. The reality is that the category splits into three distinct jobs, and the best result usually comes from two tools cooperating, not one jack-of-all-trades.

- Bulk sending / ESP: Handles deliverability, volume, templates, and lists. This is SendGrid, Mailchimp, Brevo, Klaviyo territory.
- Automation / journeys: Trigger-based workflows, transactional messages, cart recovery. Some ESPs do this well; many bolt it on weakly.
- Analytics / attribution: Opens and clicks alone don't tell you revenue. You need event-level tracking wired into your product.
Deciding what actually belongs in your stack mirrors a broader AI marketing tools shopping problem: choose tools that own a clear job and integrate cleanly, not software that claims to do all three badly.
Step 2: Test Deliverability Before You Pay
Never buy an ESP off claimed deliverability stats. Run a real test: send 200-500 identical emails from the two finalists, then measure inbox placement with a seed-list tool. A free seed list of major providers (Gmail, Outlook, Yahoo) plus your top business domains is enough to see the difference. Tools like Mailtrap's deliverability suite and GlockApps make this practical. The ESP that lands in junk is disqualified regardless of price β no feature set compensates for messages the recipient never sees.

Step 3: Match Volume to Pricing Band
Email pricing is brutal if you misjudge scale. Most platforms price by monthly active senders plus a send volume bucket, and the jump between buckets is often 40-60%. Estimate your realistic monthly sends β campaigns plus transactional plus automations β then add a 30% buffer, and buy the bucket above that. Projecting growth matters too: renegotiating mid-year costs more than slightly over-provisioning up front. Here's how the majors price out at realistic tiers.

| Platform / Tool | Key Features | Pricing |
|---|---|---|
| SendGrid | Transactional + marketing APIs, high deliverability, granular engagement stats, SMTP relay. | Free for 100 emails/day; paid from $19.95/month for 50k email credits, transactional volume extra. |
| Mailchimp | Audience management, templates, basic automation, e-commerce integration, generative AI content. | Free up to 500 contacts/1,000 sends per month; Essentials from $13/month for 500 contacts. |
| Brevo (Sendinblue) | Unlimited contacts, send-volume-based pricing, SMS alongside email, marketing automation, A/B testing. | Free for 300 emails/day; Starter from ~$9/month for 5k emails/month. |
| Klaviyo | E-commerce-native flows, predictive analytics, email + SMS, deep Shopify/Magento sync, revenue attribution. | Free up to 250 contacts; paid from $20/month for 500 contacts with volume-based scaling. |
| HubSpot Marketing | CRM-driven segmentation, smart content, lead scoring, full funnel automation, integrated analytics. | From $20/month for 1,000 contacts (Marketing Hub Starter), scaling with contacts and seats. |
The per-send math is what matters. At 50k sends/month, SendGrid and Brevo are far cheaper per email than HubSpot, but HubSpot earns its premium when CRM segmentation is your core need. Pick the pricing model that matches your billing constraint, not the one with the prettiest dashboard.
Step 4: Wire Up Automation Correctly
Automation is where most email stacks fall apart β not because the tools can't do it, but because the trigger logic is built backward. The reliable pattern is event-first: define the product or behavior event that should fire an email (signed up, abandoned cart, hit usage threshold, churned), then attach the message. Building journey-first (start with the email copy, then hunt for a trigger) produces dead workflows nobody ever receives.

For teams whose automation runs on behavioral triggers from their product, treat the ESP's event API as your primary interface. If you're deep in AI-assisted messaging, there's a specific category worth reading on AI email assistants that handles drafting and personalization at scale.
Step 5: Design Templates That Don't Break Deliverability
Modern emails are HTML, and that HTML affects whether you get flagged. The practical rules: single column under 680px, plenty of plain-text alt, no heavy image-to-text ratio (aim over 60% text), and proper DKIM/SPF/DMARC alignment on your domain. Most ESPs give you a standard template, but the value is in customizing with real content hierarchy β subject line, preheader, one clear CTA, then a text footer. A library of tested templates is one of the most underrated assets; a starter set of strong ones is a common topic in our write-up on .
Step 6: Set Up Attribution So You Can Kill What Doesn't Work
Open rates are table stakes. The email metrics that matter for ROI are click-through-to-revenue, list churn, and revenue per send. That requires either the ESP's native revenue tracking (Klaviyo's strength) or a UTM + product-analytics pipeline. Set this up before launching any campaign, or you'll spend weeks guessing which emails drove real pipeline. Teams that treat email as a revenue unit rather than a blast-out do measurably better, and the analytics side is covered further in AI marketing analytics.
The Practical Launch Order
- Confirm your sending domain's DKIM/SPF/DMARC records are correct (do this first β it's the #1 deliverability killer).
- Run the seed-list deliverability test against your top two ESP finalists.
- Set up a simple welcome automation from product events before building any campaign.
- Send one low-volume campaign, check inbox placement and spam complaints.
- Wire UTM attribution, then scale volume to your projected bucket.
Teams that follow this order consistently avoid the "we have the tool but emails go to junk" failure mode that plagues most migrations.
Common Setup Traps Worth Avoiding
- Buying by dashboard feature list instead of by deliverability test result.
- Undersizing volume buckets and eating overage charges every month β the budget leak nobody budgets for.
- Ignoring DMARC alignment, which silently depresses inbox placement across every campaign.
- Automation built journal-first β workflows that only fire when someone remembers to trigger them manually.
For teams that also send regular automation and want to reframe the whole stack as part of a coordinated marketing engine, the broader picture of marketing tooling is covered in this guide, and automation-specific patterns in .
For more, check out: .
FAQ
Why does my email land in spam even though the ESP has great deliverability claims?
Usually it's your domain's authentication: missing or misaligned SPF/DKIM/DMARC, or a domain with a poor sending reputation from previous practices. Deliverability is per-domain, not per-ESP. Fix authentication records, warm up the sending domain with gradual volume, and verify with a seed list before blaming the tool.
How do I choose between volume-based and contact-based pricing?
Volume-based (Brevo, SendGrid) suits senders with large send volumes relative to contacts, like transactional-heavy apps. Contact-based (Mailchimp, Klaviyo) suits teams that email a growing list frequently but may send high-touch campaigns. Estimate both your contact growth and monthly sends, then price both models; whichever is lower for three of your next four quarters wins.
Can one ESP handle both transactional and marketing email reliably?
Yes, but treat them as separate sending categories: transactional (password resets, receipts) needs API speed and high deliverability, while marketing needs templates, segmentation, and analytics. SendGrid and Mailchimp handle both, but you should keep separate sending sub-domains and reputations for each so a marketing spike never throttles your transactional delivery.
How do I know if an AI drafting feature actually improves results?
Run a controlled A/B: send half your list the AI-drafted subject or body and half your regular copy, keeping everything else equal. If the AI variant doesn't beat your control on your real target metric (click-through or revenue, not just open rate) across two rounds, skip it. Use AI where you're weak β subject-line volume β not where your team already shines.
What's the fastest way to improve deliverability without changing ESPs?
Verify DKIM/SPF/DMARC alignment, purge inactive and hard-bounced contacts (a 200+ day inactive list drags you down), standardize on one plain-text + one image-light template, and drop any sender name that triggers complaint thresholds. Fixing those four routinely lifts inbox placement by double digits within a month. If you also run a bilingual audience, re-target in the right language β our guide on θ₯ιθͺε¨εTool covers the Chinese side of the same stack.