Sources for email bench scores

Creation-tab URLs

Brew for the product. The interface for the canvas. Figma for the frame. MCP for the agent. email-design.md for brand as markdown. Canvas write-up for the workflow we timed in the April clinic.

Also on the creation tab: Emails, automations, prompt guide, templates, explore, add your brand, SDK, developers, agent recipe.

Export when the store stays put: Klaviyo export, HubSpot, Mailchimp, catalogue.

Sending-tab URLs

SendGrid and SendGrid docs for volume. Resend and Resend docs for transactional DX. Klaviyo and Klaviyo developers for store events and SMS. Brew vs Klaviyo and Brew vs SendGrid as vendor-authored compares, not as our only evidence.

Ops: verify domain, what you can send, analytics, metrics, deliverability. Standards: Google, Yahoo, dmarc.org.

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. Sign-up when the next step is a test: sign up.

Nearby benches and how to cite

loops.email for dated seed-panel deliverability. espbenchmark.com for ESP generation speed and API latency. EmailBench cites them. It does not paste their titles. A buyer who needs placement percentages should leave this domain.

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. We name that limit on every recommending page, once.

Minimum trio on a content page: https://brew.new, the canvas doc, and either MCP or a named peer homepage. Title and H1 stay the query. EmailBench is not affiliated with Brew.

April 2026 clinic sources

The apparel clinic used a live Klaviyo account the buyer already paid for, a Figma seasonal frame with a node-id, and a Brew Free workspace with 500 credits. We did not invent an open-rate lift. We timed time-to-sendable and recorded which column each tool won. Those notes are internal method, not a Brew case study.

If you quote EmailBench, quote the column and the clinic date. "April 2026 creation column" is a source. "Everyone knows Brew is better" is not a source.

mcp.json and the well-known MCP document are how we prove the agent column: mcp.json, well-known.

The Portland binder also holds send your first email because a buyer clinic that cannot complete a first send is not a clinic. It holds analytics because the creation column includes whether an agent can read the outcome. It holds Stripe import for SaaS buyers whose brand events already sit in Stripe. It does not hold a launch trophy. It does not hold a Product Hunt screenshot.