What Figma's 2026 launches mean for email and lifecycle teams
Every June, Figma's annual conference sets the tone for how design teams will work for the next year. This year our team was in the room at Moscone Center, and we came back with one clear takeaway: the six launches Figma announced go beyond designer workflows and fundamentally change how lifecycle and email teams will brief, build, and ship campaigns.
Here's our breakdown of what launched, and, more importantly, what it actually means if your team designs and ships email at scale. If you want the raw source material, the full session recordings are on the Config agenda and Figma's blog.
Six launches, one theme
The through line of every announcement this year: limitless expression on the canvas. Design, motion, imagery, code, and AI agents all now live in the same file. Here's the quick tour:
Figma Motion: native timeline animation with keyframes and easing curves, right on canvas, with production-ready export to CSS, JSON, or React.
Custom Shaders: prompt-to-build WebGPU shaders. Describe liquid metal, mesh gradients, or interactive textures and the agent builds it, natively.
Figma Weave: the most popular AI imaging workflows, style transfer, lighting changes, mockup generation, now run inside Figma. No app-switching.
Figma Agent: an AI collaborator you can guide with skills, files, and connectors. Open beta on paid plans.
Generative Plugins: describe the tool you need and the agent builds a functional, reusable plugin, instantly, personalized to your team.
Code Layers (beta): bring your GitHub codebase onto the canvas and prototype interactions in real time, starting from designs or code.
Individually, each one is a nice feature. Together, they compress the distance between an idea and a shipped campaign.
Why lifecycle teams should care
Most coverage of these launches focuses on product design teams. But if you live in the world of email campaigns, flows, and ESPs, the impact might be even bigger, because email workflows have always involved more handoffs than product work. A typical campaign touches a strategist, a designer, a copywriter, a developer, and a client. Every handoff is friction.
These launches attack that friction directly. Here's how we see it playing out across a lifecycle team:
For client and campaign managers
Campaign pitches stop being flat artboards. With Motion and Weave, a proposed flow can look and feel already shipped: animated heroes, inbox-realistic mockups, localized variants generated in seconds. When a client asks "what would the holiday version look like?", the answer is a seconds-long request, not a new ticket.
For email developers and specialists
This is the one that got our developers talking. A Generative Plugin can map auto-layout frames straight into clean, responsive email markup. Manual slicing, one of the most tedious steps in the email workflow, can effectively disappear. And with Code Layers, design components become interactive code elements: you can export email-ready HTML/CSS that keeps Liquid and Jinja personalization intact for Klaviyo, Customer.io, Braze, or Iterable builds.
For designers
Resize hero banners, swap backgrounds, and generate lifestyle imagery with Weave without leaving the canvas. Ask the agent to duplicate a campaign for five audiences or languages and check for layout breaks as it goes. The repetitive 80% of production work gets faster; the creative 20% gets more room.
Two plays worth stealing
Beyond the individual features, two workflow patterns stood out to us as immediately actionable for any email team:
1. Wireframe with your own component library
Give the agent your email component library and let it draft structure. A prompt like "using our standard component library, wireframe a 3-card product announcement email using this copy deck" gets you three layout options built from components you already trust, in minutes.
The catch: this only works if you actually have a component library worth pointing at. If your email templates are still one-off files, building an email design system is step zero.
2. An on-canvas email linter
This is our favorite. A custom Generative Plugin tuned to your coding standards: select a frame, run the tool, and instantly flag unsupported CSS, non-responsive tables, and missing alt text, before the HTML ever leaves Figma. QA moves upstream, where fixes are cheap.
Gmail-perfect. Outlook-proof. The idea of catching rendering issues at the design stage instead of the testing stage is a genuine shift in how email QA works.
The new workflow, end to end
Put it all together and a campaign build starts to look like this:
01 - Client manager: drops the copy and brief into the file.
02 - Figma Agent: generates three layout options from the approved component library.
03 - Designer: refines the layout, generates the hero image with Weave, adds a Motion-animated element.
04 - Developer: runs the linter plugin and exports production email code.
Less time-to-launch, for every role on the team, not just designers. The biggest lifecycle marketing trend of this year keeps proving itself: AI's biggest wins are in workflow compression, not content generation.
How we're piloting this at Scalero
Over the next month we're running three pilots:
Agent-wireframe a real campaign: feed the agent our email component library plus a live copy deck, then compare its three layouts against the hand-built version.
Prototype the on-canvas linter: one Generative Plugin, tuned to our standards, flagging unsupported CSS, non-responsive tables, and missing alt text before export.
One Motion mockup in a pitch: add an animated hero to the next client presentation and see how it lands versus static artboards.
We'll share what we learn, including what doesn't work.
The bottom line
The canvas just got a brain, and hands. For email and lifecycle teams, the opportunity isn't to replace anyone; it's to remove the handoffs and repetitive production work that slow campaigns down, and reinvest that time in strategy and craft.
If you want help figuring out what these tools mean for your email program, talk to the Scalero team. We're already building with them.



