Email as a Software Surface
Mark Robbins, software engineer at Customer.io, on the email coding stack
Email is becoming a real software surface, not just a copy paste task. As teams send more complex, branded messages across more products and regions, they need the same kind of component system and shared workflow that web teams already use. In practice that means developers define reusable building blocks once, marketers swap in copy and links, and fixes to broken code or brand changes flow across every email without rebuilding each one by hand.
-
The old workflow was usually a code editor, HTML files, and manual paste into an ESP like Marketo. Parcel won by turning email creation into a shared workspace with previews, validation, comments, and reusable components, which is much closer to a lightweight IDE than a drag and drop builder.
-
The main competitive split is creation versus testing. Parcel is strongest when a team is actively writing and maintaining email code. Litmus is strongest as a preview and testing layer. At Figma, marketing builds in Parcel while other teams still keep Litmus for separate transactional testing workflows.
-
The bigger opening is inside the sending platform. Both Mark Robbins and Avi Goldman point to the same bottleneck, once a component is updated, teams still have to export and sync HTML into the ESP. Deeper integration removes that handoff and turns components into live infrastructure for every campaign.
This points toward email tooling looking more like modern frontend tooling. The next step is a shared design system for messages, tied directly to journeys, analytics, asset hosting, and send systems, so one source can generate every version of a campaign and keep it current automatically across channels.