Using Parcel with Email on Acid
Jay Oram, head of dev at ActionRocket, on intra-agency collaboration on email
This setup shows that email teams increasingly split writing from rendering checks, because the best editor and the best testing network are often different products. ActionRocket used Parcel for the day to day work of building HTML emails, clicking elements in the preview to find code, and collaborating across coders and designers, while relying on the large client preview infrastructure behind Email on Acid for inbox rendering checks. That combination let them avoid Litmus pricing limits and avoid Email on Acid's weaker editing workflow.
-
Parcel was built around the actual coding workflow. It gives a live browser preview beside the code, lets a user click an email element and jump to that spot in the HTML, and highlights table structure, which matters because many marketing emails are still built with nested tables for Outlook compatibility. That is why it replaced Dreamweaver for ActionRocket.
-
Email on Acid filled a different job. It focused on large scale inbox testing across many devices and clients, and its pricing emphasized unlimited previews. For an agency testing many client emails every month, that mattered. Litmus also offered builder and preview tools, but historically counted preview usage by plan, which made heavy testing feel expensive for this workflow.
-
This is also a sign that Parcel was moving from pure editor into infrastructure. Internal research around Parcel notes that it had become an email creation tool with testing layered in, and a Customer.io engineer described the relationship directly, saying Email on Acid uses Parcel and Parcel uses Email on Acid. In practice, that means some competitors are also partners.
Going forward, the winning email tools are likely to bundle these layers more tightly. The editor that helps a marketer or developer build faster, the preview system that shows Gmail and Outlook quirks, and the ESP connection that pushes finished code into Braze, Salesforce, or Klaviyo are converging into one workflow. The products that own that handoff will capture more of the email stack.