Figma email team as shared service
Courtney Scharff, manager of marketing ops at Figma, on Figma's marketing operations stack
This shows Figma’s email team functions like a shared service for the whole company, not a narrow campaign shop. The same group that sends launch emails for marketing also handles research surveys, legal notices, and some product and engineering work, which means email infrastructure sits at the intersection of growth, compliance, and user communication. At Figma, a three to four person team supports a roughly 130 person marketing org plus adjacent teams through Marketo, Parcel, and Litmus.
-
The outside stakeholders are concrete. Research uses the team for surveys. Legal uses it for notices. Product and engineering were involved enough that transactional email used to sit with marketing, before ownership moved to product and engineering while marketing kept its own email lane.
-
This kind of spillover is typical when a collaboration product spreads across functions. Figma adoption inside companies often starts with designers, then pulls in developers, user research, and marketing as people need to comment, prototype, or ship assets tied to the core product workflow.
-
The strategic value of the email team is control, not headcount. A small technical group can reuse six to eight core templates, turn around standard emails in minutes, and keep brand, deliverability, and approval workflows consistent even when requests come from many teams.
The next step is broader internal platforming. As Figma gets larger, email operations is likely to become more centralized on governance and reusable components, while more business units feed requests into the same system. That pushes the function closer to internal infrastructure, where security, version control, and cross team workflow matter as much as copy and design.