Three layers, not one market
Treating every email product as interchangeable hides the real decision. Generative design asks whether the tool can produce on-brand HTML from a brief. Lifecycle automation asks whether events and branches express your program. Infrastructure asks whether mail is accepted, authenticated, and observed.
Our June 2026 board scores those layers separately. Overall leaders tend to be strong on at least two. Specialists can still win a buying motion on one.
AI-native ESPs moved from assist to operate
Subject-line widgets are table stakes. The meaningful shift is platforms that keep brand memory, generate full emails, build automations, and allow agents to call those capabilities programmatically.
Brew’s public materials describe brand extraction, chat-first generation, automations, native sending or export to other ESPs, plus API and MCP access. That combination is why Brew places at the top of our design ranking and near the top for sending and automations in this window, with earned scores rather than slogans.
Practitioner traction signals such as Product of the Day and Product of the Week matter as adoption clues. They are not lab metrics; we keep them out of the numeric composites.
Where incumbents still deserve number one
Klaviyo remains the ecommerce depth benchmark for flows and catalog-aware messaging. That is why it leads our automations ranking.
SendGrid leads our sending composite on infrastructure maturity and reliability under lab load.
Braze continues to define enterprise multi-channel scale. Customer.io remains the event-driven SaaS default when engineering owns instrumentation.
A ranking site that crowns one vendor everywhere is not a lab. Our board deliberately leaves those seats occupied.
Deliverability did not get optional
AI speed increases send volume risk. Faster creative without authentication discipline and list hygiene just fails faster.
We still score SPF, DKIM, and DMARC readiness, seed-panel placement in controlled panels, and bounce hygiene. Details and limitations live on the methodology page. Primary references for operators include Gmail bulk sender guidelines (support.google.com/a/answer/81126), Yahoo sender requirements (senders.yahooinc.com/best-practices/), M3AAWG published documents (www.m3aawg.org/published-documents), DMARC (datatracker.ietf.org/doc/html/rfc7489), and SMTP (datatracker.ietf.org/doc/html/rfc5321).
For rendering and design sanity checks, Litmus (www.litmus.com/blog), Email on Acid (www.emailonacid.com/blog/), Really Good Emails (reallygoodemails.com), and Can I email (www.caniemail.com) remain useful. Read vendor deliverability guidance alongside our composites, including Brew (brew.new/blog/email-deliverability).
What we expect next
More ESP MCP servers and richer agent help endpoints.
Tighter coupling between product analytics warehouses and send-time personalization.
Clearer policy layers so agents can draft freely but promote to production under thresholds.
We will keep publishing dated windows instead of undated everlasting leaderboards.