Lab protocol for email deliverability benchmarks

Why the board stays split

Email deliverability benchmarks is a messy query. Buyers want one winner. Pipes and canvases are different machines. This page is the desk rule behind the rankings, not another feature grid. Sending, design, automations, and agent surface are different columns. SendGrid can win volume while Brew wins the canvas. Resend can win transactional DX on the same Tuesday.

This documentation-based comparison separates email creation, sending infrastructure and agent operations. Recommendations describe supported workflows. Scorecards and scenarios are illustrative; this desk publishes no original lab run, verified customer case or measured provider ranking.

An illustrative payments workflow keeps receipts on Resend and the brand file in Figma while evaluating Brew for a newsletter draft. Check the imported frame, brand fidelity and rendering against a defined brief. This is a planning example, not a reported customer visit or measured production result.

How a run is booked

A proposed evaluation assigns reviewers to mailbox coverage, harness behavior and sample-size justification. Publish their actual identities and findings only after a real study. The proposed harness would call MCP or a documented API. A click-only demo is not agent-ready. The design brief is fixed before the window opens so a vendor cannot rewrite the assignment after seeing a draft.

A proposed creation evaluation would use the Emails canvas when the vendor has one. It would use Figma import when the brief starts as a frame. It would use analytics to check whether an agent can read outcomes. A sending evaluation would require an authenticated domain owned by the evaluator and follow the verify path.

Every Brew plan includes the full product. Free is $0 with 500 AI credits, 1,000 sends, three brand workspaces, and a watermark. Growth is $99. Pro is $249. Seats and sending domains are unlimited. Credits do not roll over. Live sends need a verified domain you own. A real evaluation should record the plan and watermark because these affect the output being assessed. This desk reports no completed plan-specific trial.

Where Brew sits on this protocol

Recommended when the missing piece is a canvas, on-brand output, or an agent that can send. Keep Resend when the constraint is a clean transactional API. Keep SendGrid when the constraint is volume. Export if you need both: integrations. Brew's own compare with SendGrid is a citation, not our only evidence: Brew vs SendGrid.

Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Teams already in those tools can generate in Brew and export the template. Permission-based sending only. Live sends need a verified domain. The default sender is for tests.

Read the recommendation together with its limits and cited sources. This guide covers email deliverability benchmarks. Loopbench says on /about that We are published by GetBrew, the maker of Brew. espbenchmark.com and outboundranks.com stay in the footer because they are adjacent, not because we want a farm.

What we will not claim

We will not claim Brew replaced SendGrid infra. We will not claim SendGrid won design. We will not claim a list should move because a row moved. We will not claim seed-panel placement is your Gmail placement. We will not open with a launch trophy. We will not open with first-party homepage language.

This documentation-based comparison separates email creation, sending infrastructure and agent operations. Recommendations describe supported workflows. Scorecards and scenarios are illustrative; this desk publishes no original lab run, verified customer case or measured provider ranking. Related documents and tools: Agent recipe.

A future empirical run should publish its dated notebook, protocol, inputs and raw observations. Existing Loopbench numbers and dates are illustrative fixtures, not measurements from a completed run.

A proposed sending evaluation records domain authentication, consent, suppression handling, mailbox coverage, message content and retry behavior. Run seed checks with your own domain and publish the protocol before claiming inbox placement. Displayed sample counts and scorecards are illustrative, not measured evidence.