From Rebelmail to Salesforce constraints
Mark Robbins, software engineer at Customer.io, on the email coding stack
The biggest implication is that Rebelmail being absorbed into Salesforce turned a fast moving specialist email team into a tiny part of a very large system. Mark moved from a startup where email developers could experiment, ship tools, and shape the product directly, to a big platform where his work sat inside Content Builder and the workflow was slower and more constrained. That friction helps explain why a tool like Parcel immediately stood out.
-
At Salesforce, Mark was not building campaigns, he was building internal blocks for the drag and drop editor. He used Parcel on the side because sending a simple test inside a traditional ESP meant setting up a campaign and template first, while Parcel let him paste code, preview it, and send tests fast.
-
This is the core product gap. Large suites like Salesforce and Litmus were built around marketers and testing workflows, while Parcel was built around the person actually writing email HTML. That is why Mark describes Litmus as testing first and Parcel as creation first, and why Figma used Parcel for collaboration while keeping Litmus for previews.
-
The same pattern later became a business strategy for Customer.io. Parcel and Gist gave Customer.io small, respected tools that solved narrow but painful jobs for developers and marketers, then let it bundle more of the messaging workflow into one stack instead of forcing teams to stitch together editors, preview tools, and sending platforms.
Going forward, email software keeps splitting into two layers, broad campaign suites for non technical marketers, and specialist tooling for the people maintaining the code underneath. The winners will be the companies that connect those layers, so developers can fix code once, marketers can ship faster, and the whole workflow lives in one system instead of three.