JSON Raises Marketer Skill Floor
Sean Kennedy, senior marketing ops analyst at Zapier, on his email development workflow
The real bottleneck in modular email systems is not writing HTML, it is teaching non technical marketers to think like software users. Zapier had already centralized more than 200 templates into reusable Parcel components, so the next problem became passing structured inputs into those components. Once a teammate has to type fields, values, and arrays in JSON like syntax, the workflow stops feeling like drag and drop email building and starts feeling like filling out code parameters.
-
This is the tradeoff behind design systems for email. A shared component lets one edit update logos, colors, or layout everywhere at once, which removed the old process of manually changing more than 200 live templates during Zapier's rebrand. But that centralization only works if the team can reliably feed each component the right inputs.
-
Other teams describe the same pattern. Sinch uses JSON inside Parcel to switch brands, colors, typefaces, and footers across multiple email products. That shows why JSON appears at all, it is the control layer that turns one component into many variants, but it also raises the skill floor for marketers who know email HTML and not data structures.
-
The alternative tools Zapier considered, like Taxi for Email, are built around this exact handoff problem. Agencies use them to package a component library so local marketers can swap copy, images, links, and language without touching underlying code. The market is moving toward safer forms and controls on top of components, not asking more marketers to learn JSON directly.
The next step for email tooling is turning structured component inputs into normal product UI. The winning products will keep the power of reusable code underneath, but expose it as forms, dropdowns, and guided choices so marketing teams can self serve without needing to read or write JSON at all.