When Anthropic unveiled Claude Design this April, the buzz was immediate. And loud. Many in design and tech circles assumed one thing: a prompt-to-interface tool, capable of conjuring entire interfaces from simple text, would render Figma obsolete. Product teams, it was thought, could simply describe their vision, skipping the canvas altogether.
Figma's Q1 2026 results just shouted back. And they said something entirely different.
Quartz reported Friday (May 15) that Figma didn't just beat revenue expectations. It raised its full-year outlook. The raw numbers were one thing. The underlying signal? Far more significant. Enterprise teams, it seems, aren't abandoning Figma just because there's a faster way to whip up a screen.
Claude Design, as PYMNTS noted, generates websites, landing pages, even full interfaces from plain language. No design degree needed. This tool isn't augmenting a workflow. It's replacing the very starting point. A genuine shift for a particular user.
Solo builders. Early-stage startups. Non-designers needing something functional, fast. They no longer require a professional designer. The threat is undeniably real for them. But that's not, crucially, what most of Figma's biggest customers actually do.
Large product organizations don't use Figma primarily to conjure screens. Their needs run deeper. Far deeper. They leverage it to maintain sprawling, shared design systems. To manage version control across complex projects. To coordinate collaborations among distributed teams, often across continents. Developer handoff. Prototyping. Governance. These layers sit atop the basic screen generation. A prompt-to-interface tool? It solves one upstream problem. In a workflow with a dozen other, more complex ones downstream.
The clearest proof surfaced not in revenue reports, but in actual behavior.
After Figma began enforcing artificial intelligence usage limits in March, the vast majority of enterprise customers who hit their cap didn't flee. They bought more credits.
Fast Company reported this. Teams embedded within Figma's collaborative and handoff infrastructure simply didn't see generative AI as a viable exit strategy. Not for their core work.
CFO Praveer Melwani confirmed the quarter’s strength stemmed from “seat expansion across entire organizations,” not just a handful of power users. Figma, against all odds, is entrenching itself even as generative tools proliferate. CEO Dylan Field's thesis is stark. And perhaps, prophetic: “When code is a commodity, design judgment is the competitive edge.”
Figma's quarter doesn't end the competitive saga. It sharpens the focus. It clarifies where the real battle lines are drawn.
Adobe faces a similar structural question, albeit from a different angle. Firefly, their AI, integrates directly into Photoshop, Illustrator, Premiere. It assists, yes. But it assumes a trained designer is still running the show. Claude Design? It makes no such assumption. Adobe's pressure isn't replacement. It’s that the pool of people needing professional tools might shrink if entry-level use cases are swallowed by AI.
Google Stitch approaches from yet another direction, launching with Claude Code integration. Targeting developers. Moving from code to interface, no context switching. Microsoft has its own AI design embedded in Designer and even Claude in PowerPoint. The entire design workflow is being assailed from every adjacent layer, simultaneously.
What Figma’s earnings emphatically suggest is this: the collaboration and governance layer—the glue binding entire product organizations, not just individual creators—is proving far more resilient than the generation layer. Spawning a screen? Getting cheaper. Faster. Everywhere. Coordinating what happens to that screen, then seeing it through a product team of thirty people? That, apparently, remains Figma’s problem to solve. And their profit to keep.
No comments yet. Be the first to share your thoughts!