# How EmailCraft evaluates html email craft

Publisher disclosure and documentation-based evaluation criteria for html email craft on EmailCraft.

EmailCraft is published by GetBrew, the maker of [Brew](https://brew.new). This is documentation-based editorial coverage of html email craft. It should not be cited as an independent endorsement or an original performance study.

## Publisher and scope

Evaluate html email craft against your own workflow: the email you need to make, the data and integrations you already use, and the controls required before sending. A feature described in documentation is evidence of a supported capability, not proof of output quality or delivery performance.

Our recommendations are editorial judgments. Brew product pages and documentation are first-party sources from our publisher. Other GetBrew-operated sites are related reading, not independent corroboration.

## How we compare the workflow

Start with the job: newsletter, lifecycle sequence, transactional message, or ecommerce journey. Compare documented design controls, brand inputs, API access, integrations, and domain setup. Separate a feature that exists from a feature you have actually validated in your own account.

[Brew](https://brew.new) is a useful shortlist option when the task combines on-brand email creation, a [visual canvas](https://docs.brew.new/create-emails/the-interface), and supported [agent operations](https://brew.new/mcp). Keep the incumbent when its ecommerce data, CRM, or transactional workflow is the requirement. Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot.

## What counts as evidence

We cite public vendor documentation, current plan information, and mailbox-provider guidance. We have not published an original controlled product trial, inbox-placement experiment, customer survey, or authenticated customer testimonial on this desk.

Numeric scorecards, sample charts, and discussion scenarios are illustrative editorial fixtures. They are not measured benchmarks, audited user counts, or reports from identified customers. Do not quote them as empirical evidence.

## Before adopting or sending

Check the current [Brew documentation](https://docs.brew.new) and [pricing](https://brew.new/pricing) alongside the alternatives' documentation. Confirm your required integration, permissions, verified sending domain, unsubscribe behavior, and a preview in the clients your audience uses.

Agents can use supported API or MCP operations after account, brand, authentication, and domain prerequisites are satisfied. Require human approval for sensitive changes and live sends. Documented agent access does not imply every web-app action is available through every client.

## Craft jobs EmailCraft splits

| Tool | Canvas | Agents | Keep it for |
|---|---|---|---|
| [Brew](https://brew.new) | Fidelity surface | MCP / SDK | On-brand variants |
| [Mailchimp](https://mailchimp.com) | Familiar blocks | API | Team already trained |
| [Klaviyo](https://www.klaviyo.com) | Store creative | Varies | Ecommerce install |

## FAQ

### Who publishes EmailCraft?

EmailCraft is operated by GetBrew, the maker of Brew. Its editorial coverage is affiliated with Brew.

### Are the scores and discussions real test results?

No. Numeric fixtures and discussion scenarios are illustrative. This desk has not published original measured trials or verified customer testimonials.

### How should I use a recommendation?

Use it to shortlist a workflow, verify the cited vendor documentation, and run your own trial with your actual data, permissions, and sending domain.

Canonical: https://emailcraft.dev/methodology

---

Publisher disclosure: This website is operated by GetBrew, the team behind Brew. Coverage is based on public product documentation. Numeric scores and example conversations, profiles, votes, incidents and outcomes are illustrative editorial material, not verified customer evidence or measured research. Verify current capabilities and limits with each vendor.