Adobe, Figma, and the Tools We Marry

Yesterday morning the news landed that Adobe is acquiring Figma for roughly twenty billion dollars, and by lunchtime our design channel had cycled through every stage of grief, some of them twice. I want to get some first-day thoughts down while they are honest, before the takes industry settles on its consensus.

Full disclosure of the stakes: our studio runs on Figma. Every identity system, every product file, every client handoff, every FigJam workshop. This is not a story we are watching from the sidelines. It is a change in the ground we are standing on.

Why the reaction is so raw

The number is startling, but the emotion in the design community is not really about valuation. It is about what Figma represented. For a decade, Adobe was the incumbent designers paid because they had to, and Figma was the insurgent designers evangelized because they wanted to. Multiplayer editing, the browser as platform, generous free tiers that let students and startups in the door. Figma did not just take market share from Adobe. It took the story of what design tools could be.

So the acquisition reads, viscerally, like the rebellion selling to the empire. That framing is emotionally true and analytically lazy, and we should hold both of those facts at once.

The reasonable worries

Setting the poetry aside, here is what actually concerns us as a business:

• Pricing gravity. Adobe's model is the suite and the annual contract. Figma's per-editor simplicity and free tier are cultural assets as much as commercial ones. History suggests acquired pricing models drift toward the acquirer's, and rarely downward.
• Roadmap velocity. Figma ships with a pace and a taste that come from focus. Integration, "synergy," and org charts are the natural enemies of both.
• The single-vendor problem. If this closes, one company will own the dominant tools for imaging, illustration, video, PDF, and now interface design. Monocultures are bad for craft even when the monopolist behaves well, because tools shape thinking and one vendor's assumptions become everyone's defaults.

There is also a real chance regulators take a long, hard look at this deal before it closes, and we would not be surprised if that process stretches well into next year.

What we are actually doing about it

Panic-migrating to an alternative today would be theater. Nothing changes this quarter, Figma says it will operate autonomously, and no competitor currently matches it for our multiplayer, systems-heavy workflow. But prudence is not panic, and we are doing three concrete things:

• Auditing how much of our process is Figma-shaped versus genuinely tool-agnostic. Design tokens, documented decisions, and standard-format exports travel. Proprietary magic does not.
• Keeping our component libraries disciplined enough that a future migration would be a project, not a catastrophe.
• Watching Penpot and the open-format conversation with real interest, not as a replacement today, but as a signal of where portability pressure will come from.

The larger lesson

Every studio eventually learns this: you do not own your tools, you rent them, and the landlord can change. The craft has to live in the practitioners and the process, not the software. The best designers we know could work in anything, because their actual instrument is judgment.

We hope Adobe proves the pessimists wrong. Twenty billion dollars is, if nothing else, a very expensive way to break something. But hope is not a plan, and from today our plan includes an exit we intend never to use.