When Adobe’s proposed acquisition of Figma ended without a deal, the news raised a practical question for designers and businesses: what happens to the tools they rely on when a major technology merger falls through? Figma remained independent, while Adobe continued developing its own creative and collaboration products. For teams choosing software, the episode is a reminder to look beyond headlines and consider how competition, product roadmaps, and workflow needs shape day-to-day work. A detailed look at the failed acquisition offers useful context for understanding the stakes.
Why the proposed deal mattered
Adobe announced plans to acquire Figma in 2022, in a transaction valued at approximately $20 billion. Figma had become a prominent browser-based platform for interface design and real-time collaboration. Adobe, already a major supplier of creative software, saw an opportunity to bring the product into its portfolio and expand its reach in collaborative design.
The deal attracted regulatory scrutiny in the United States, the United Kingdom, and the European Union. Competition authorities examined whether combining the companies could reduce competition in digital design tools. In December 2023, the companies mutually ended the agreement after concluding there was no clear path to regulatory approval. Adobe agreed to pay Figma a termination fee of $1 billion under the deal’s terms.
The outcome did not mean that Figma’s product disappeared or that Adobe’s existing applications stopped competing. Instead, both companies continued as separate businesses, with each able to set its own priorities. The episode also showed how regulators can influence technology markets when a proposed merger might affect customer choice and future innovation.
What it means for designers and businesses
For users, the immediate priority is not predicting which company will dominate. It is choosing tools that support the work at hand. A product’s interface, collaboration features, file compatibility, learning curve, and total cost can matter more to a team than the corporate ownership behind it.
Figma’s browser-centered approach makes it convenient for distributed teams to work together on shared designs. Adobe’s broad creative ecosystem can be useful for organizations that move between interface design, illustration, photography, video, and other media. These descriptions are not a rule that one product suits every team: organizations should test their actual workflows, check current plan details, and confirm that files can be handed off in the formats they need.
It is also sensible to avoid building a process around a single feature or vendor without considering alternatives. Keep source files organized, document design decisions, and make sure more than one team member understands how projects are structured. Those habits make it easier to adapt if pricing changes, a product evolves, or a company changes its direction. They also reduce disruption when new collaborators join.
Competition can shape product development
When two suppliers compete for the same customers, each has an incentive to improve its products, explain its value, and respond to user feedback. That can lead to better collaboration tools, more integrations, or new ways to hand designs over to developers. Competition does not guarantee that every update will benefit every customer, but it gives teams more than one option when evaluating software.
For product managers and business owners, the failed acquisition is a useful case study in the uncertainty of technology strategy. A merger announcement is not the same as a completed transaction. Until a deal closes, customers and partners should treat major product changes as possibilities rather than certainties. It is wise to follow official product updates, maintain exportable project files, and review vendor commitments before making a long-term investment.
Design choices connect to the wider digital experience
Design software is only one part of delivering a digital product. A polished interface still needs dependable development, useful content, and a site or application that performs well on different screens. Small businesses planning a new web presence should define the project scope before choosing tools: page count, custom features, content responsibilities, and approval steps all affect the work involved.
Those decisions also influence the schedule. A simple informational site with prepared copy and images is usually less complex than a custom site with integrations, online payments, or extensive original content. For a practical overview of the factors involved, Osdire explains how long a business website may take to build. Thinking through the timeline early can help a business coordinate design, development, and review without treating launch day as the only milestone.
Make decisions around needs, not headlines
The Adobe-Figma deal ended, but the larger questions it raised remain relevant: how much choice should customers have, how do creative products evolve, and how can teams avoid unnecessary dependence on one platform? There is no single answer for every organization. Comparing tools against real tasks, preserving portable work, and planning for implementation are practical steps that remain useful regardless of which companies merge or compete.
For designers, the best response to industry uncertainty is a flexible workflow. For businesses, it is to connect software decisions to clear project goals and user needs. That approach keeps attention on the quality of the work—and gives teams room to adapt as the technology landscape changes.
