Figma vs Adobe XD: What Losing a Category Costs

On December 18, 2023, Adobe paid $1 billion for nothing. That’s the breakup fee it owed Figma when their $20 billion acquisition — agreed in September 2022, then ground down by EU and UK competition regulators for fifteen months — was finally called off. A month later, in January 2024, Adobe sunset Adobe XD, its own product in the category it had just tried to buy its way back into. And nineteen months after that, on July 31, 2025, Figma went public: priced at $33 a share, closed its first day at $115.50, a valuation around $68 billion.

I keep coming back to this story because it’s the cleanest priced example I know of a question that usually stays fuzzy: what does losing a category actually cost? Most category losses are invisible — the loser quietly pivots, the counterfactual revenue never shows up on anyone’s books, and everybody tells themselves the market was small anyway. Adobe doesn’t get that mercy. The cost of losing interface design showed up as line items: a $20 billion offer for a company it once could have out-shipped, a $1 billion fee for failing to close, and a shutdown notice for the product that was supposed to prevent all of it. The interesting part isn’t that Adobe lost. It’s that Adobe did almost everything the fast-follow playbook says to do, and lost anyway — because the fight wasn’t about features. It was about where the category lived.

The fast-follow that did everything the playbook says

Adobe launched XD in 2016, and on paper it was the textbook incumbent response. Sketch had shown there was a dedicated interface-design market outside Photoshop; Figma was a browser curiosity from a startup nobody’s procurement department had heard of. Adobe had the strongest brand in design software, the default distribution channel to virtually every professional designer on earth, and the resources to build a competent screen-design tool quickly. It did build one. XD was fast, native, and reasonably good — reviewers said so, and I remember designers around me giving it honest trials.

This is worth sitting with, because the comfortable story — “the incumbent was asleep” — is false here. Adobe was awake. It saw the category forming, entered within a couple of years of the challengers, and backed the entry with everything a challenger is supposed to fear. If fast-following with superior distribution were sufficient, this post would be about XD’s dominance.

The problem was that XD answered the question “how do we build a Sketch competitor?” — a what-to-build question — while Figma had quietly changed the answer to a different question entirely: where does design work happen? That’s a where-to-play choice, and it sits upstream of everything XD was optimizing.

Where did the category actually live?

Figma’s bet was that design’s real constraint wasn’t drawing tools — it was that design happened in files, on individual machines, visible to one person at a time. So it built in the browser, with multiplayer editing as the core mechanic rather than a feature. A URL instead of a file. Everyone in the document at once: designers, PMs, engineers, the stakeholder who would never install anything.

Notice what that did to the category definition. As long as “interface design tool” meant an app a designer installs, Adobe’s distribution advantage was decisive — it already owned the pipe to every designer’s machine. The moment the category became a place a team works, that pipe was worth much less, because the buyer stopped being an individual designer and became the whole collaboration graph around her. Figma didn’t beat XD at the category’s existing game. It moved the category to a venue where the incumbent’s biggest strength didn’t transfer. This is the sharpest version of the argument in the positioning post: the same product, filed on a different shelf, gets judged by different rules — and the deepest positioning move available is to change what shelf the whole category sits on.

And here’s the part that makes it a compounding problem rather than a feature gap: multiplayer in the browser is a network-effect mechanic. Every non-designer who touched a Figma link became a reason the next file lived in Figma. XD could match features — and it did, steadily — but it was matching features in a category whose center of gravity had already moved. You can catch up on a roadmap. You cannot fast-follow a place.

The receipt: $20 billion, then $1 billion for nothing

By September 2022, Adobe’s assessment of its own position was written in the price it offered: $20 billion for Figma — widely noted at the time as one of the richest multiples ever paid for a software company, for a business a fraction of Adobe’s size. Forget the press-release language about complementary visions. An acquisition offer at that level is an internal memo accidentally published: we do not believe we can win this category with what we have, at any feasible R&D spend, on any feasible timeline. Adobe had spent six years and its entire distribution advantage on XD, and the honest market value of that effort was that the endgame required buying the winner.

The regulators read the same memo. The EU and UK competition authorities spent over a year probing exactly the concern that a dominant design-software incumbent buying the category leader would entrench, and on December 18, 2023, the companies abandoned the deal rather than fight on. Adobe wired Figma the $1 billion termination fee. Then, in January 2024, it sunset XD — the closest thing to an official time of death a losing product ever gets. There was no reason to keep it alive; the acquisition attempt had already conceded what it was worth.

Add it up as a cost accounting, which is what makes this story unusual. Losing the category cost Adobe: the direct XD investment (never disclosed, six-plus years of it), a $1 billion fee with nothing attached, the strategic vacuum TechCrunch politely called “a big hole to fill,” and — the largest line, the one that never appears on a balance sheet — the category itself, at whatever it will be worth over the next twenty years. Which brings us to the market’s estimate of that last number.

What the market said the category was worth

On July 31, 2025, Figma priced its IPO at $33 and closed the first day at $115.50 — roughly $68 billion, more than three times what regulators had blocked Adobe from paying. And the S-1 underneath that pop is the part I’d actually put in front of a team, because it shows what category leadership does to the numbers rather than just the narrative: $821 million in trailing-twelve-month revenue, the most recent quarter growing 46%, with 132% net dollar retention. (You’ll see “$912M ARR” quoted around this filing — that’s an analyst annualization of the quarter, not a number the S-1 states.) FY2025 revenue came in at $1.056 billion, up 41%.

That NDR figure is the compounding thread of this whole story made visible. Net dollar retention of 132% means Figma’s existing customers alone — before a single new logo — grow revenue 32% a year, because the multiplayer mechanic keeps pulling more seats, more teams, more of the org into the file. That’s not a sales motion; that’s the where-to-play bet from 2013 still paying out in 2025. Category leadership compounds precisely because the winner’s product mechanics and the category’s definition are the same thing. XD never had access to that loop, not because its team was worse, but because the loop lived in the browser and XD, structurally, didn’t.

The uncomfortable lesson for anyone sitting on incumbent-scale distribution: distribution is an advantage inside a category definition. It is close to worthless across one. Adobe could put XD in front of every designer alive. It could not make the design conversation happen inside a desktop file.

The same movie, currently screening

If this feels like a period piece, it isn’t. The same shape is playing out right now in AI coding tools. GitHub Copilot is the incumbent’s product with incumbent distribution — 20 million-plus users per Microsoft’s FY2025 10-K, riding the world’s default developer platform. Cursor made the Figma move: instead of shipping a plugin into the incumbent’s venue, it forked the entire editor — a fresh where-to-play bet that the AI-native workflow needed to own the whole surface, not rent a sidebar. The trajectory, with the caveat that these are company-reported figures: from $1 million to $500 million ARR in roughly 24 months, $1 billion by November 2025, $2 billion by February 2026.

I’m not claiming the ending is written; self-reported ARR deserves its hedge, and Microsoft has more moves left than Adobe had. But the structure rhymes exactly: an incumbent with overwhelming distribution defending the current definition of the category, and a challenger betting that the category is about to live somewhere else. Adobe’s story is what the receipt looks like when that bet resolves against you. It starts with a competent fast-follow, and it ends with you paying a billion dollars for the privilege of not acquiring the company you could have out-built a decade earlier.

Put it to work

1. Ask where your category will live, before asking what to build in it. Write down the venue assumption your product depends on — the desktop, the file, the plugin, the app store, the individual seat — and then ask what happens to your biggest advantage if that venue shifts. Adobe’s distribution answered “how do we reach designers?” perfectly; the category quietly changed the question to “where do teams work?” and the advantage didn’t transfer.
2. Read acquisition offers — yours or competitors’ — as strategy confessions. When an incumbent offers a category-defining multiple for a challenger, it is publishing its own internal assessment that building lost. If you’re the incumbent, run that assessment before it costs twenty billion to admit: could our fast-follow win even with our distribution, or is the category’s center of gravity already somewhere our strengths don’t reach?
3. Price the loss honestly, including the invisible line. Adobe’s cost wasn’t the $1 billion fee; it was $1 billion plus years of XD investment plus a category the market later valued at $68 billion on IPO day. When your team debates whether defending a category is “worth the investment,” put the category’s compounding value — Figma’s 132% NDR is what that looks like — on the same slide as the build cost. The build cost is always the smaller number.

Further reading

• Figma’s S-1 and investor filings (investor.figma.com / SEC EDGAR) — the primary source for the $821M LTM revenue, 46% quarterly growth, and 132% NDR figures; the NDR discussion is the category-compounding argument in tier-1 form.
• TechCrunch, “Adobe has a big hole to fill after the $20B Figma deal falls through” (December 18, 2023) — contemporaneous account of the termination, the $1 billion fee, and what the collapse left Adobe without.
• Contrary Research’s Cursor company report — the fullest public account of the Cursor trajectory and the fork-the-editor bet, with the company-reported ARR milestones and their caveats.
• Microsoft’s FY2025 10-K — source for the 20M+ Copilot user figure, and worth skimming for how an incumbent frames a category it currently defines.