Parcel modernizes email creation workflow
Avi Goldman, founder of Parcel, on the email developer experience
Email creation was a neglected workflow because teams were still building a business critical channel with the equivalent of loose HTML files, manual copy and paste, and generic web tools. The opening for Parcel was not email sending itself, but the messy production layer between design, code, review, testing, and export. That gap showed up most clearly at complex brands like Uber, at agencies, and inside lean marketing teams like Figma’s, where email work often lived across Atom, Dreamweaver, Marketo, and shared files.
-
The pain was operational, not theoretical. Early users either built internal systems, like Uber, or stitched together old tools like Dreamweaver, FTP, local editors, and ESPs. Parcel packaged software engineering habits like components, autosave, syntax help, validation, previews, comments, and approvals into one place for email teams.
-
Parcel sat in a different spot from Litmus. Litmus started from testing and previews, then added editing. Parcel started from writing and maintaining email code, then added testing. That matters because the buyer problem shifts from checking a finished email to speeding up how emails are built and updated.
-
The real unlock is shared infrastructure. With component based emails, a developer can fix a Gmail or Outlook issue once, or update a brand color once, and every downstream email inherits the change. That turns email from repeated one off production work into a maintainable system.
This points toward email creation becoming part of the broader customer messaging stack, not a side task inside a sender. As tools like Customer.io fold coding, collaboration, and delivery together, the winning products will make email behave more like modern software, with reusable components, centralized workflows, and less manual handoff between marketers and developers.