The Figma Acquisition That Wasn't And What It Cost the Design Industry 🎨
By Creatives Takeover · April 22, 2026
Figma deal collapse exposed industry dependence.
In September 2022, Adobe made a move that shocked the entire tech world. They announced they were acquiring Figma, the collaborative design platform that had quietly become the default tool for product teams everywhere, for $20 billion. The design community held its breath. Developers had opinions. Founders took notes. And for fifteen months, everyone waited.
Then, in December 2023, it fell apart.
Regulators in Europe and the UK looked at the deal and saw something Adobe didn't want them to see: a monopoly in the making. Adobe already owned the creative software market. Photoshop, Illustrator, InDesign, Premiere. Adding Figma to that stack would have meant one company controlling virtually every stage of the creative and product design workflow. The European Commission and the UK's Competition and Markets Authority both pushed back, and after fifteen months of negotiations, Adobe and Figma quietly agreed there was no path forward. Adobe wrote Figma a $1 billion check just to walk away. No acquisition. No merger. Just a billion dollars and a lesson.
Here is where the story gets interesting for founders.
That $1 billion termination fee was not just a penalty. For Figma, it was a lifeline they never asked for. The company had raised $333 million in total venture funding across its entire lifetime. In a single transaction, they received three times that amount in cash, with no dilution, no new board seats, and no strings attached. While Adobe licked its wounds, Figma used that runway to double down on its independent roadmap, accelerate product development, and position itself for what came next.
In July 2025, Figma filed for its IPO and listed on the New York Stock Exchange under the ticker FIG. The market responded. The stock climbed. By the time the dust settled, Figma's market cap was sitting at $62 billion. Adobe, the company that tried to buy them for $20 billion, had effectively watched $37 billion in value walk out the door. The acquisition that was supposed to strengthen Adobe ended up financing its most formidable competitor.
So what does this teach founders?
The first lesson is about the danger of building to be acquired. Adobe wanted Figma because Figma had already won. The product was better, the community was loyal, and the growth metrics were exceptional. Figma was not built to be sold. It was built to solve a real problem for real teams, and the acquisition offer was a consequence of that, not the goal. When you build with an exit as the north star, you optimise for the wrong things. When you build for the user, the outcomes take care of themselves.
The second lesson is about independence as a competitive advantage. Fifteen months of acquisition uncertainty could have paralysed Figma. Hiring slows down when a deal is pending. Product roadmaps stall. Teams get distracted. But Dylan Field, Figma's CEO, kept the company moving. They shipped features, retained talent, and maintained momentum even while regulators debated their future. The founders who survive the messy middle are the ones who stay focused on the product regardless of what is happening around them.
The third lesson is one that most founders underestimate. Regulators are now a strategic variable, not just a legal formality. The era of Big Tech buying its way out of competition is closing. Antitrust scrutiny is real, it is global, and it is accelerating. For startup founders, this is actually good news. The platforms that would have absorbed your company five years ago are now being forced to compete with you instead. That changes the game entirely. You have more room to grow, more time to build, and a more level playing field than any generation of founders before you.
Adobe's story here is not one of failure in the traditional sense. It is a masterclass in what happens when a company stops innovating and starts acquiring. When your growth strategy depends on buying the competition rather than outbuilding it, you are already signalling something to the market. And the market, eventually, notices.
Figma did not need Adobe. It turned out Adobe needed Figma far more than Figma ever needed them.
Build something people need that badly. The rest tends to follow.