Litmus is the right answer to a question we don't try to answer. Email QA Agent is the right answer to a question Litmus deliberately doesn't cover. Most teams that take this product seriously will run both.
Litmus answers: "Will this email render correctly across 100+ inboxes? Will it pass spam filters? Are the authentication records set up?" That's deliverability and compatibility. It's the question your IT-adjacent ops lead cares about. Litmus does it better than anyone.
Email QA Agent answers a different question: "Does this email follow our team's brand and content checklist? Is the hero 640x250? Does the personalization token have a default? Are the UTMs on every Seequent-domain link? Did the requester use the right footer for an operational versus marketing send?" That's content QA against a per-team rule pack. Litmus deliberately doesn't do this because the rule pack is different at every company.
Different layers of the stack. Same workflow. Most marketing-ops teams should run both.
| Litmus / Email on Acid | Email QA Agent | |
|---|---|---|
| What it tests | Rendering across 100+ inboxes, deliverability, spam filters, accessibility, load time, link validity | Content against your team's checklist: image dimensions, padding, font sizes, UTM presence, default tokens, footer correctness, spelling, custom rules per client |
| Where the rules come from | Universal email-client compatibility standards | Your team's brand + content guide, encoded as a versioned JSON rule pack |
| Where feedback shows up | Litmus dashboard (separate tool your team has to learn) | A structured comment in your project management tool (ClickUp, Asana, etc.), addressed to the requester by name |
| Tuned per client | No, same checks for everyone | Yes, every client gets a custom rule pack |
| Catches "send the wrong audience" | No | Yes (Phase 2 with Marketo API) |
| Catches typos and missing tokens | Partial (link-level, not content) | Yes |
| Catches Outlook-specific rendering bugs | Yes, this is the core product | No, we don't try to do this |
| Catches DMARC / DKIM auth issues | Yes | No |
| Pricing entry | $199 / mo (Plus tier, 2026) | $7,500 starting (fixed-scope pilot, 4 to 6 weeks, then retainer) |
| Buying motion | Self-serve SaaS | Pilot-first with Innovative Group, then handoff or retainer |
Here's the honest read. Litmus is excellent at what it does. We use it ourselves. They built the rendering-and-deliverability layer better than anyone, and they built it once for the whole industry. That's the right architecture for that problem.
The reason there's white space for Email QA Agent is that Litmus deliberately stopped at compatibility. They don't audit your team's checklist because every team's checklist is different. Hero image 640x250 here, 800x300 there. The Spanish first-name token defaults to Hola at one client and Mi amigo at another. The "preferred language NOT Portuguese, Spanish, Russian" trick for English audience targeting at Seequent doesn't apply at HubSpot.
Per-team rule packs are a category of work Litmus deliberately can't take on at scale. We can, because we encode each client's checklist as a versioned JSON file, build the agent on top, and post the result into the project tool the team already lives in. We're the layer below.
The teams that need both are the same teams that send 50+ emails a quarter through the same junior-then-senior review chain, where the senior reviewer is currently spending half her week on rule-based feedback. Litmus catches none of that. Email QA Agent catches all of it.
In a healthy marketing-ops workflow, Email QA Agent runs first. The requester sends a Marketo send-sample to our inbox. The agent posts the rule-pack feedback to ClickUp in 30 seconds. The requester fixes the easy stuff. Then the email goes through Litmus for rendering and deliverability checks. Then the senior reviewer sees a clean email and signs off.
Reversing the order works too, but it's wasteful. Running Litmus on an email that has 9 content errors means you'll re-run it after the requester fixes them. Email QA Agent first, Litmus second, senior reviewer third. The funnel narrows in the right order.