Seat design dictated Figma tool choice
Diving deeper into
Courtney Scharff, manager of marketing ops at Figma, on Figma's marketing operations stack
you can share a login and you can't do that with Parcel
Analyzed 4 sources
Reviewing context
This reveals that seat design, not editing quality, decided who used which tool inside Figma. Parcel handled the core job for the small marketing team, writing and updating email HTML in one shared workspace. Litmus stayed in the stack because product and engineering only touched email occasionally, and a cheaper, separate testing space mattered more than pulling every occasional reviewer into Parcel.
-
Figma split the workflow by job. Marketing used Parcel as the main editor and no longer needed Atom. Litmus was kept for inbox rendering checks on new templates and for transactional email changes owned by product and engineering.
-
That made pricing and access control practical issues. Figma had only three to four regular Parcel users, but broader engineering access would have required extra seats. Litmus positioned its enterprise plan around unlimited seats and usage, which fits occasional cross functional reviewers better.
-
The product distinction also mattered. Parcel was built around coding, live browser preview, and optional paid inbox previews. Other email teams describe it as closer to an email IDE, while Litmus is treated as the stronger dedicated testing layer when a team mainly wants previews and QA.
The likely direction is further separation between an editor seat and a reviewer seat. Tools that win this market will let a small specialist team build emails in a developer style workspace, while giving larger groups cheap or free ways to preview, comment, and approve without buying full coding seats.