Figma Resisted Adobe's Bundlenomics
How Figma defied Adobe's bundlenomics
Adobe learned that a free add on does not beat a tool that designers treat as their home base. Figma won because the work itself lived there, in one browser file where designers, PMs, engineers, and marketers could all edit, comment, inspect history, and hand work off without exporting files. That made Adobe XD feel like an extra app inside a larger bundle, not the place where product design actually happened.
-
In practice, companies often kept paying for both stacks. One design leader described 35 to 40 Figma users at Lime while still having Creative Cloud access, and said no one used XD. Another company had about 14 Adobe Creative Cloud seats, 10 Figma users, and zero XD users.
-
The product gap was concrete. Figma replaced local files, sync headaches, and design exports with multiplayer editing in browser, shared libraries, version history, comments, and developer handoff. That turned Figma from a drawing tool into the source of truth for product decisions, which is a much stickier role than a bundled substitute.
-
Adobe still kept the broader budget because Figma was not a Photoshop, Premiere, or After Effects replacement. That meant Adobe could not force a winner take all bundle. Instead, enterprises treated Figma as a premium must have for product design and Adobe as the required suite for adjacent creative work.
The next phase is bundle versus bundle on Figma's terms. Once Figma proved designers would not switch just because XD was included, the path forward became adding products like FigJam and other cross functional tools that turn a design beachhead into company wide workflow ownership, while Adobe keeps defending the broader creative suite around it.