Unifying Marketing and Transactional Email
Avi Goldman, founder of Parcel, on the email developer experience
The important point is that email software is usually bought as a patchwork, not as one system. Marketing teams often live in tools like Customer.io or Marketo, while product and engineering teams send app emails through delivery infrastructure like SparkPost. That split creates copy and paste handoffs, duplicated templates, and separate owners for what is still one customer experience, which is exactly the gap Parcel was built to close.
-
At Figma, marketing emails were built in Parcel, but transactional emails sat with product and engineering and were tested in Litmus. That is the same basic split by team and job to be done, marketing on one side, product email on the other, even inside one company.
-
Parcel’s wedge was not sending email, it was becoming the shared workspace where code, previews, comments, approvals, and reusable components live before HTML gets pushed into the sending platform. Avi Goldman describes export into Customer.io as the normal flow, and deeper ESP sync as the missing piece.
-
Customer.io bought Parcel because owning the editor lets it pull spend and workflow out of separate tools like Litmus and custom code setups. The broader strategy is to bundle creation with orchestration, data pipelines, and sending, so marketers and developers stop working in separate systems.
The market is heading toward tighter coupling between the place where teams build emails and the place where those emails are sent. The winning products will absorb the handoff, so a brand update or code fix made once can flow into every campaign and transactional message without manual export or separate team workflows.