Block-based vs code-first email workflows
Sean Kennedy, senior marketing ops analyst at Zapier, on his email development workflow
The real divide here is between tools that let marketers assemble approved blocks, and tools that let email specialists actually engineer the system underneath. Taxi for Email sits closer to a controlled drag and drop layer, where a team prebuilds modules and other users rearrange them. Parcel goes deeper into the coding workflow, with MJML support, collaborative editing, versioning, and component based development that make it behave more like an email IDE than a template picker.
-
Taxi is strongest when a central team wants to lock brand rules into reusable modules, then hand campaign creation to less technical marketers in many regions or business units. That is why agencies use it for global brands that need local teams to swap language, images, and links without touching raw HTML.
-
Parcel is built for teams already writing email code, especially in MJML. The workflow is closer to VS Code for email, with shared editing, code level components, and previews around the codebase. That fits Zapier's setup, where the core problem was version control, QA, and keeping a growing team on one design system.
-
Litmus overlaps with both, but from a different starting point. Its center of gravity is review, approvals, and inbox testing, not component driven email production. In practice, teams often pair Litmus with a coding workflow, while Parcel tries to collapse coding, review, and preview into one workspace.
The market is moving toward hybrids that start with locked components and add more review and deployment plumbing around them. The winners will be the products that let non technical teams self serve safely, while still giving technical owners one place to manage code, brand rules, approvals, and handoff into the ESP.