Parcel's Early Win at Figma

This points to Parcel winning Figma before procurement caught up, which is how developer first tools often get their first real design partners inside larger companies. At Figma, a two person email team could try Parcel on free, move to paid quickly, and work directly with Avi Goldman because the immediate gain was simple, shared email code editing and feedback. Security review had not become the gating step yet because only three to four people used it.

• Before Parcel, Figma's email workflow was two people editing HTML in separate code editors, then passing files around or pulling code out of Marketo. Parcel solved a very concrete pain, shared editing, organized files, and easier collaboration, which made early adoption easy even without full enterprise controls.
  1 sacra
• The threshold for enterprise features at Figma was not company size, it was seat count and business criticality. Scharff says SOC 2 and SSO had not come up because Parcel was used by only a tiny team, and she compares that to GitHub, where tool audits appeared later as the company got bigger and centralized software oversight.
  1 sacra
• This fits Parcel's broader market position. It started as an email coding and collaboration product, not a classic enterprise suite, and Customer.io bought it in 2022 to upgrade its editor experience. Figma also kept Litmus for previewing and shared access, which shows Parcel landed first on workflow quality, not on being the all in one standard across every team.
  2 sacra 3 sacra 4 customer 5 customer

Going forward, tools like Parcel tend to spread inside companies only after they add the controls that procurement wants, or get bundled into a larger approved platform. Customer.io integration pushes Parcel in that direction. As email creation gets centralized and audited, the winners will be tools that keep the fast editor and feedback loop while also checking the security and admin boxes larger companies require.