When the Tools You Build Start Competing With the People You Hired to Build Them
Figma has spent the last several years quietly acquiring small design and AI-focused teams – not always for their products, but for their talent. These acqui-hires were a bet on the future: bring in the engineers and researchers who understand generative interfaces, AI-assisted design workflows, and machine learning pipelines, then let them shape what Figma becomes. The logic was sound at the time. But Figma’s own AI rollout is now creating a strange internal tension, where the native tools the company is shipping are starting to do exactly what those acquired teams were brought in to help figure out.
The collision isn’t dramatic or public. There are no reported walkouts or internal memos circulating on X. But the structural problem is real: when a company acqui-hires for specific expertise and then automates the core questions that expertise was meant to answer, what exactly are those teams still solving for? That question is becoming harder to avoid at Figma.
What Figma’s AI Push Actually Does
Figma’s AI features – rolled out progressively through its design, prototyping, and Dev Mode tools – are focused on collapsing the gap between idea and execution. Auto layout suggestions, AI-generated UI components, first-draft wireframes from text prompts, and code generation tied directly to design layers are all either live or in active development. Each of these capabilities sits squarely in the territory that small, specialized AI design startups were originally carving out for themselves before getting absorbed into larger platforms like Figma.
The bet Figma is making is that native, deeply integrated AI tools will outperform anything a bolt-on acquisition can deliver. A wireframe generator that lives inside Figma’s canvas, with full access to your component library, your design tokens, and your existing file history, will always be more useful than a standalone tool that exports into Figma as a second step. That argument is hard to refute from a product standpoint. Where it gets complicated is on the human side of the equation.
The Acqui-Hire Math Gets Messy
Acqui-hires work on a simple assumption: you are buying time. The market for specialized AI engineering talent is thin, the competition to hire it is intense, and building the expertise from scratch takes years. So companies pay a premium to skip that line. Figma has done this, as have virtually every major product company with a serious AI roadmap. The acquired teams are folded in, their original products often sunsetted or quietly wound down, and their attention is redirected toward the acquirer’s larger ambitions.
The problem is that acqui-hire value decays. The knowledge gap that made a small team worth acquiring in the first place narrows as the acquiring company’s own internal teams catch up – or as the underlying models and tooling that powered the acquired team’s edge become commoditized. In Figma’s case, the acceleration of general-purpose AI capabilities through foundation model providers has compressed that timeline significantly. What felt like proprietary expertise in AI-assisted interface generation two years ago now looks a lot more like applied prompt engineering on top of widely available APIs.
There is also the question of product vision overlap. When Figma ships a native feature that directly addresses the problem an acquired team was originally brought in to explore, that team’s mandate effectively shifts. They may move into adjacent territory, get absorbed into broader platform work, or quietly find themselves redundant to the core roadmap. None of these outcomes are the kind of story Figma would put in a press release, but all of them are plausible inside a company moving this fast.
The morale dimension matters too. Engineers who join through acqui-hires typically do so with some expectation of seeing their original work or vision carried forward. When the acquiring company instead builds around them – not with them – the psychological contract frays. Retention risk in these situations is real, and in a talent market as competitive as AI infrastructure and design tooling, losing key people from acquired teams after their retention windows close is a meaningful cost.
Figma’s Broader Strategy Isn’t in Question – Its Execution Is
None of this suggests Figma is mismanaging its AI strategy at the product level. The features being shipped are substantive, and the integration advantage Figma holds over standalone competitors is genuine. For the vast majority of its user base – product teams at mid-to-large tech companies, solo designers, frontend developers working in Dev Mode – the AI additions are making an already dominant tool significantly more capable.
The question is whether the acqui-hire approach was the right vehicle for getting there, or whether Figma could have built most of this organically and deployed that acquisition capital differently. That calculus is easy to second-guess in hindsight, which is why most companies don’t bother revisiting it publicly.
The Wider Pattern Across Design and Dev Tools
Figma is not alone in this dynamic. Across the broader design and developer tooling space, companies that made talent acquisitions specifically to accelerate AI capabilities are now contending with the same structural tension. The foundation models got better faster than most product roadmaps anticipated, and the work of integrating AI into existing products turned out to require less specialized knowledge than the acqui-hire thesis assumed. It required distribution and deep product integration – things large incumbent platforms already had.
This is partly why the value in developer tooling is consolidating around platforms with the largest installed bases and the tightest integrations with existing workflows. Vercel’s approach to frontend infrastructure illustrates the same underlying logic: own the workflow context, and AI features become far stickier than any standalone tool could manage. Figma is applying that same thinking to design, and it is working at the product level, even as it creates internal friction at the organizational level.
Startups building AI-native design tools today are navigating a more difficult path than their predecessors did two years ago precisely because Figma is now shipping what those predecessors were pitching to investors. A design AI startup looking for an acqui-hire exit in 2025 is essentially hoping that Figma – or a competitor like Canva or Adobe – has a gap in its native roadmap that the startup happens to fill. That gap is getting narrower with every product update Figma ships. The acqui-hire window, at least in design AI, may already be mostly closed – and some of the teams Figma already bought are sitting inside that realization right now.
