Figma AI Design Tools at Config 2025: One Platform Targeting Adobe, Canva, and WordPress Simultaneously

On May 7, 2025, roughly three weeks after Figma filed its IPO on the NYSE under the ticker FIG, the company used its annual Config conference to announce four distinct products aimed at four different competitive categories simultaneously. That sequencing is deliberate and worth taking seriously as an analytical frame before evaluating any individual product on its merits.

Four Products, One Event, Four Separate Wars

What Figma Actually Announced at Config 2025

The four announcements map cleanly onto existing competitive territories. Figma Sites targets the design-to-publish space occupied by WordPress, Wix, and more precisely, Webflow. Figma Make is a prompt-to-prototype tool that competes with v0 by Vercel, Cursor AI, and Framer's AI layout engine. Figma Buzz targets the marketing asset production workflow that Canva currently dominates. Figma Draw positions directly against Adobe Illustrator for vector illustration work.

Each of these is a credible product category. Each has established incumbents with significant user bases and workflow lock-in. The unusual thing about Config 2025 is not that Figma is entering any one of these spaces, but that it is entering all four at once, with a coherent structural argument for why they belong together.

Why Simultaneous Multi-Category Expansion Is Unusual

Most software companies expand sequentially. They deepen one category until they have a defensible position, then extend adjacently. Figma's Config 2025 announcements are not sequential. They represent a thesis: that design, content production, code generation, and marketing asset creation share a single source-of-truth problem, and that solving it in one collaboration graph is worth more than solving each problem individually in best-of-breed tools.

The IPO timing reinforces this reading. Companies filing for public markets need a growth story that extends beyond their existing category. Figma's existing category, collaborative interface design, is mature and well-penetrated among its target users. Four new product categories, announced three weeks after the IPO filing, are not coincidental additions to a product roadmap. They are the revenue diversification argument made concrete.

The Platform Consolidation Thesis: What Figma Is Actually Arguing

The Collaboration Graph as Competitive Moat

Figma's structural argument is that the export-import friction tax is real and expensive. A designer builds a component in Figma, exports assets to Canva for marketing variants, hands off specs to a developer who rebuilds the component in code, and publishes to a CMS that has no awareness of the original design system. Each handoff is a potential divergence point. Brand tokens drift. Component states get lost. Localization creates parallel asset trees that nobody fully controls.

If design tokens, brand assets, component libraries, and publishing infrastructure all live in one data model, that divergence problem shrinks considerably. This is the genuine value proposition behind Figma Sites, Buzz, and Draw as a bundle. Individually, each product faces strong incumbents. Together, they describe a workflow where a single source of truth governs everything from initial wireframe to published marketing page.

The Salesforce parallel is instructive here. Salesforce built platform gravity through CRM, then absorbed marketing automation, analytics, and commerce over roughly a decade. Each acquisition or product extension made the core CRM data more valuable because more workflows fed into it. Figma is attempting the same vector through design data, but compressed into a much shorter timeline, which is where execution risk concentrates.

How the Weavy Acquisition Signals Architectural Intent

Figma's $200 million acquisition of Israeli AI startup Weavy received less attention than the product announcements, but it is arguably more architecturally significant. Weavy builds embedded collaboration infrastructure: in-app messaging, activity feeds, notification systems, contextual commenting. These are not features. They are plumbing for a platform that expects multiple stakeholder types (designers, marketers, developers, content editors) to work inside the same environment simultaneously.

This acquisition signals that Figma is not building four separate products that happen to share a brand. It is building a collaboration substrate that each product surface sits on top of. Whether that substrate becomes a genuine competitive moat depends on how deeply it integrates with the data models of each product, and whether the resulting experience is meaningfully better than, say, leaving comments in a shared Notion doc while working across separate specialized tools.

The honest counterargument deserves direct address: platform breadth without depth in each category often produces tools that satisfy no professional fully. A marketing coordinator who needs Canva's template library and a professional illustrator who needs Illustrator's node editing are not going to accept a unified platform that handles both tasks at 70% of the quality of their current tools. Figma's execution challenge is not building four products. It is building four products that each meet professional-grade standards while sharing infrastructure.

Figma Make and the Anthropic Dependency: The Sleeper Story

What Claude 3.7 Actually Does Inside Figma Make

Figma Make is powered by Claude 3.7, Anthropic's model with strong structured output and code generation capabilities. Users describe an interface or interaction in natural language, and the model generates functional Figma components and prototype flows. The practical experience positions it against v0 by Vercel, which generates React UI from prompts, and Cursor AI, which edits and writes code in a development context.

The differentiation Figma Make is attempting is significant: where v0 generates code and Cursor edits code, Figma Make generates design artifacts that live natively in the Figma collaboration graph. The output is not a React component you then need to hand off to a designer for visual refinement. The output is already in the design tool, already using your existing component library, already connected to your design tokens. That is a genuinely different value proposition from prompt-to-code tools, provided the output fidelity is high enough to be useful in complex UI scenarios.

In practice, prompt-to-UI tools across the board struggle with complex interaction states, responsive behavior, and edge cases in component variants. Figma Make will face the same fidelity ceiling. The question is whether its native integration with the Figma component model gives it an advantage over tools that generate code and require a separate translation step back into design.

The Conflict-of-Interest Architecture No One Is Covering

The underreported story in the Figma Make announcement is the dependency structure it creates. Figma's most critical AI capability layer runs on Anthropic's Claude. Anthropic has been reported, per The Information, to be developing its own design-adjacent capabilities as part of its product roadmap. This means Figma's primary AI infrastructure partner is simultaneously a potential direct competitor in the design tool space.

The structural parallel is AWS building services that compete with startups running on AWS infrastructure. But the design tool market is smaller and more concentrated than cloud infrastructure, which makes the conflict more acute. If Anthropic releases a design tool with deep Claude integration, Figma faces a scenario where its most capable AI partner has a direct incentive to limit or redirect that capability.

For enterprise procurement teams evaluating Figma's IPO risk profile, this dependency is material. Figma could theoretically migrate to Google Vertex AI or access multiple models through a routing layer, but the product is currently built around Claude's specific strengths in structured output generation. Rebuilding that integration on a different model provider is not a trivial engineering task, and the output quality would not be guaranteed to transfer.

This is worth monitoring specifically as a risk factor, not as a reason to dismiss Figma Make. The product may be excellent. The dependency architecture is still a structural vulnerability that belongs in any serious evaluation of the platform's long-term reliability.

Adobe's Actual Vulnerability: Reading the Revenue Story Correctly

Where Adobe Is Genuinely Exposed vs. Where It Still Wins

Adobe reported approximately $23.77 billion in FY2025 revenue, a figure that can obscure where competitive pressure is actually concentrated. The threat from Figma AI design tools is not uniformly distributed across Adobe's product portfolio. It is concentrated in Creative Cloud subscriptions for design and illustration work, specifically among entry-level and mid-market users who are not dependent on Adobe's deeper professional capabilities.

Adobe's durable advantages remain significant in specific domains. Print production and prepress workflows, video editing in Premiere Pro and After Effects, enterprise PDF workflows in Document Cloud, and the depth of Photoshop's compositing capabilities are not threatened by Config 2025 announcements. Professional illustrators working in complex vector environments with Boolean operations, advanced node editing, and production-grade output requirements are not switching to Figma Draw based on what was shown at Config 2025.

The credible threat is at the entry and mid-market level. Junior designers who use Illustrator primarily for basic vector tasks, icon creation, and simple marketing graphics are a realistic migration target if Figma Draw reaches sufficient quality. That is a meaningful portion of Creative Cloud's subscriber base, even if it is not the professional core.

What the Stock Decline Actually Reflects

Adobe's stock decline in the period around Config 2025 reflects investor concern that AI commoditizes the core creative tools value proposition. The logic is straightforward: if a model can generate vector illustrations (Figma Draw) or produce on-brand marketing variants (Figma Buzz), the justification for a $60/month Creative Cloud subscription weakens for users whose needs are not deeply professional.

Adobe Firefly is Adobe's generative AI answer, but it faces a structural constraint that Figma does not. Adobe must protect existing revenue while introducing AI capabilities that could cannibalize that revenue. Figma has no legacy Creative Cloud pricing to defend. It can price AI features aggressively as part of a platform expansion play because it is not protecting a $23 billion revenue base. That asymmetry matters more than any individual feature comparison.

Figma Buzz vs. Canva: A More Interesting Fight Than It Looks

Why Canva's Moat Is Stickier Than Adobe's in This Context

Canva's user base skews heavily toward non-designers: marketing coordinators, social media managers, small business owners, and communications teams who never used Figma and have no existing workflow investment in the platform. These users do not experience the export-import friction tax that Figma Buzz is designed to eliminate, because they never had assets in Figma to begin with.

This makes Canva's moat structurally different from Adobe's. Adobe's professional users might switch if a better tool emerges. Canva's non-designer users have no reason to migrate to a design-first platform unless the new tool is dramatically simpler than their current workflow. Figma Buzz is not simpler than Canva for someone who has never opened Figma. It is only simpler for someone who already lives in Figma and wants to stop exporting assets to a separate platform.

The Marketing Team Workflow Problem

Figma Buzz's genuine competitive advantage is contextual: if your brand assets, design system, and component library already live in Figma, generating on-brand marketing variants without an export step is a real workflow improvement. This makes Buzz primarily a retention and upsell play for existing Figma customers, not a Canva acquisition play. That distinction matters significantly for evaluating market share claims that may emerge from Figma's investor communications.

Marketing teams that use tools like Make or Clay for connected workflow automation already have sophisticated asset production pipelines that pull from multiple sources. For these teams, the relevant question is not Buzz vs. Canva in isolation, but whether Figma's platform integrates cleanly with the automation infrastructure they have already built. A tool that generates on-brand assets but cannot push them to a CMS, a social scheduler, or a campaign management platform through an API is solving only part of the problem.

Canva's recent enterprise push, including Canva for Teams and Canva Enterprise, means the competition is bidirectional. Canva is moving toward Figma's core territory with design system features and brand kit management. Figma is moving toward Canva's territory with Buzz. Both companies are converging on the same enterprise marketing workflow problem from opposite directions.

Figma Sites and the CMS Question

What 'AI Website Builder with CMS' Actually Means Technically

WordPress powers a substantial portion of the web not because of its design tools but because of its plugin ecosystem, SEO infrastructure, and hosting portability. Figma Sites does not address any of these structural advantages. Comparing Figma Sites to WordPress is a category error that makes Figma look more threatening than it is to WordPress's actual user base.

The more accurate competitive frame is Figma Sites vs. Webflow. Both target designers who want to publish without writing code. Both have CMS capabilities. Webflow has a multi-year head start with mature hosting infrastructure, a CMS layer that supports structured content modeling, and a developer community that has built significant workflow tooling around it. Figma Sites' genuine advantage is zero-friction publishing for teams already in Figma: a prototype becomes a live site without a handoff step, which is a real pain point for landing pages, portfolio sites, and marketing microsites.

The Webflow Comparison Is More Instructive Than the WordPress One

The CMS component of Figma Sites is the critical unknown. Enterprise content workflows require structured content modeling, localization support, API access for headless delivery, and editorial workflows with role-based permissions. Whether Figma Sites supports these capabilities at launch or positions them as future additions matters significantly for evaluating who the product actually serves today.

Figma's Weavy acquisition suggests they are building toward multi-stakeholder content workflows rather than just designer-to-publish pipelines. Embedded collaboration infrastructure is more relevant to a CMS use case than to a simple static site publisher. But infrastructure intent and shipped product capability are different things, and the gap between them is where enterprise evaluations get stuck.

Breadth as Strategy vs. Breadth as Distraction: The Execution Risk Framework

Historical Precedents for Multi-Category Platform Expansion

Platform consolidation plays succeed when the shared data model genuinely improves each use case. They fail when each product is a thin wrapper around a shared brand that provides no cross-product benefit. Microsoft's expansion from Office to Teams to Power Automate succeeded in large part because each product made the others more useful: documents became collaborative, collaboration became automatable, automation fed back into documents. The reinforcing logic was real.

Figma's shared data model, comprising components, design tokens, brand assets, and the collaboration graph, is a credible foundation for Sites, Buzz, and Draw. The question is whether Figma Make's code generation output integrates cleanly with this model or produces orphaned artifacts that live outside the design system. If Make generates components that do not inherit from the existing token structure, it creates a new divergence problem rather than solving the existing one.

The counter-model worth considering is how tools like n8n and Cursor AI have built strong user bases by going deep in a single workflow rather than broad across many. Cursor AI, scored 8.2/10 by the TopReviewed AI panel, succeeded by making the code editing experience genuinely better for developers who live in that workflow. Figma is betting the opposite thesis: that breadth with a coherent shared data model beats depth in any single category. The historical evidence for this thesis is mixed.

What Figma Needs to Get Right in the Next 18 Months

The IPO timing creates a specific execution risk. Public market pressure to show revenue growth in new categories may force premature feature releases or pricing decisions that undermine product quality. Four products launched simultaneously at a conference are not four products at parity with their respective incumbents. The gap between announcement and professional-grade execution is where the real evaluation happens.

Specific capabilities to watch: Figma Sites' CMS depth and API access, Figma Make's output fidelity in complex multi-state UI scenarios, Figma Buzz's brand consistency controls for enterprise brand systems, and whether Figma Draw supports the vector operations professionals actually need, including Boolean operations, node-level editing, and pen tool precision comparable to Illustrator. These are not minor polish items. They are the threshold requirements for professional adoption in each category.

Product	Primary Competitor	Figma's Claimed Advantage	Key Execution Risk
Figma Sites	Webflow, WordPress	Zero-friction prototype-to-publish	CMS depth and enterprise content modeling
Figma Make	v0 by Vercel, Cursor AI, Framer	Native design artifact output vs. code output	Anthropic dependency; complex UI fidelity
Figma Buzz	Canva	On-brand variants from existing design system	Non-designer UX; API integration with marketing stack
Figma Draw	Adobe Illustrator	Integrated with design workflow, no export needed	Professional vector tooling depth

What This Means for Teams Evaluating Their Design Stack in 2025

Who Should Pay Attention to Config 2025 Right Now

Teams already on Figma with significant design system investment are the clearest immediate beneficiaries. Figma Sites and Figma Buzz have near-zero switching cost for these teams because the assets they need are already in the platform. If either product works as described, the workflow benefit is immediate. The evaluation criteria are simple: does Sites support your CMS requirements, and does Buzz generate assets that actually conform to your brand system without manual correction?

The Anthropic conflict-of-interest angle is worth monitoring specifically for enterprise procurement teams. If Anthropic launches a competing design tool with deep Claude integration, Figma's AI capabilities in Make could degrade, be restricted, or become a negotiating chip in a competitive dynamic that Figma does not fully control. Enterprise contracts that depend on Figma Make's AI output quality should include contingency evaluation of alternative model providers, including what a migration to Google Vertex AI would require.

Who Should Wait for Version 2 of Each Product

Teams currently on Adobe Creative Cloud for professional illustration and vector work should treat Figma Draw as a product to watch rather than a migration trigger. The professional-grade vector tooling evidence is not yet available, and switching costs in production illustration workflows are high. Wait for independent assessments of Boolean operation behavior, node editing precision, and output quality at print resolution before making a stack decision.

Teams on WordPress with complex content workflows, including multi-author publishing, localization, plugin-dependent functionality, and established SEO infrastructure, should not consider Figma Sites a replacement at this stage. The CMS and hosting infrastructure gap is too wide, and the plugin ecosystem advantage WordPress holds is not addressed by anything announced at Config 2025.

If your team currently uses Figma and exports assets to Canva for marketing production, Figma Buzz is the single highest-ROI thing to evaluate from Config 2025. The use case is narrow, the friction it eliminates is real, and the evaluation cost is low because your assets are already in the platform. That is the concrete starting point, not the platform consolidation thesis as a whole.