Email innovation via workflow compression
Avi Goldman, founder of Parcel, on the email developer experience
The real innovation is workflow compression, not new email formats or new sending rails. Email teams still do work that web and design teams solved years ago, like reusing components, pushing one style change across hundreds of assets, and separating copy edits from code fixes. Parcel’s bet is that bringing design system discipline into email makes the whole function faster, more reliable, and easier to share between marketers, designers, and developers.
-
Parcel is taking familiar web software patterns and applying them to email. Components let a team define a button, footer, or layout once, then reuse it everywhere with variables for brand, language, or content. That matters in email because many teams still duplicate old HTML files and manually patch each send.
-
The practical bottleneck is not writing code, it is keeping email assets synced with the sending platform. Both internal interviews and user workflows point to the same pain. a team can update a component centrally, but if exports into Marketo or Customer.io are still manual, the biggest efficiency gain is left unfinished.
-
This is also why Parcel and Litmus feel different in practice. Litmus is strongest when a team wants inbox previews and QA. Parcel is strongest when a team wants an IDE for email, shared components, and faster iteration. That split mirrors the market, testing versus authoring.
The next step is email becoming just another design system surface inside customer messaging platforms. As deeper sync arrives, the winning products will let one team update a component once, then propagate that change across campaigns, transactional messages, and eventually adjacent channels from the same source of truth.