MJML component system at Zapier
Diving deeper into
Sean Kennedy, senior marketing ops analyst at Zapier, on his email development workflow
probably 99% of our emails are using our MJML style guides and everything, so we keep everything consistent.
Analyzed 4 sources
Reviewing context
Zapier is treating email like software, not like a one off marketing asset. The important shift is that the real work happens in a shared MJML component system, then HubSpot or Iterable become send pipes rather than design tools. That keeps layout, spacing, logos, and code quality under central control, which matters more once an email team grows and many people are shipping at once.
-
The operating reason is scale. Zapier grew from a two or three person email team using shared files to a seven or eight person team, where version control, overlapping edits, and uneven coding skill started creating friction. Parcel and MJML gave them a central place to manage templates and components.
-
The product reason is speed and reliability. MJML and shared components cut emails from thousands of lines of code to a few hundred, which makes debugging faster. A change to a shared component can update branding across many emails, instead of manually touching hundreds of templates during a rebrand.
-
This is also a clear line between coded systems and drag and drop systems. Zapier uses drag and drop only in limited cases, while tools like Taxi for Email are better for letting non technical teams localize or swap modules inside guardrails. Parcel and Litmus sit closer to the developer workflow, while Taxi sits closer to controlled self serve editing.
The next step in this market is tighter coupling between the source of truth and the sending platform. The winning tools will keep the central design system intact, while making it easier for non technical marketers to personalize and launch emails without breaking brand or code consistency.