David Brooks
Figma's stock is down 35% in 2026 and shed another 8.8% the day Google Stitch was announced. I've been tracking this space for over a decade, and that kind of market reaction doesn't happen by accident. When a company with Google's distribution ships a free AI design tool with native multi-screen generation, the industry recalibrates — whether it's ready to or not.
Here's my take: Google Stitch isn't a research demo. It's a calculated move to commoditize UI design tooling at exactly the moment when Figma is most vulnerable. And the $13,200 question is already on every CFO's desk.
The $13,200 Problem
Start with the number driving this conversation: a team of 20 pays $13,200/year for Figma Organization. Google Stitch's Experimental tier costs zero. That delta is so stark that even if Stitch delivers 60% of Figma's functionality, the budget conversation changes immediately.
The elephant in the room is that Figma has been raising prices into a market where AI-generated UI is getting dramatically better. That's not a defensible long-term position. The Adobe acquisition collapsed at $20 billion — a number that looked rational in 2022 and appears increasingly questionable as Figma trades at $23.60 against an $85 IPO price.
For US enterprise teams, this isn't just a pricing story. It's a vendor lock-in calculation that just got significantly more complicated.
What Google Stitch Actually Does
Stitch is built around Galileo AI integration — not bolted on top as an afterthought, but native to the canvas from day one. The practical implications are real: describe a user flow in plain language and Stitch generates coherent multi-screen designs with consistent component logic. Export that to HTML, CSS, or React. Connect it to your MCP-based agent pipeline for automated design tasks.
The "vibe design" framing isn't marketing fluff — it accurately describes the interaction model. You specify intent and context, the system produces screens that cohere across the full flow. Is it perfect? No. Is the improvement trajectory obvious? Absolutely.
What matters technically is the MCP integration. Teams already running agent-based development workflows can slot Stitch in as a native node rather than maintaining a separate tool silo. The SDK availability from launch also signals intent clearly: this is infrastructure with an API surface designed to embed in broader pipelines, not a closed product. That's a fundamentally different product philosophy than Figma's historically walled-garden approach — and it matters for how enterprise teams evaluate long-term dependency risk.
The Google Platform Advantage
Here's context that matters more for US enterprise teams than it might initially appear: Stitch is shipping with Google Workspace integration built in. Design artifacts become natively shareable within the same ecosystem where your team already writes docs, runs standups, and manages calendars — without the export-and-link workflow that Figma requires.
Figma's strength has always been its role as neutral ground between design and development. Google is betting that "neutral ground" loses its value when one platform controls the entire collaboration stack. For organizations already deep in Google Workspace — a significant portion of US mid-market and enterprise — the adoption friction drops substantially.
I've seen this movie before. Google ships a tight Workspace integration, enterprise adoption follows the path of least resistance over 18-24 months. Anyone who watched Google Docs quietly displace Microsoft Office inside mid-market companies between 2012 and 2016 knows exactly how this plays out.
The Experimental Tier: Free Isn't Free
Let's be real about the limitations, because the 50 generations/month ceiling on the Experimental tier is more restrictive than it sounds. A medium-complexity project with normal iteration velocity will burn through that limit in under a week.
This is a deliberate product decision, not a technical constraint. Google is seeding adoption and building dependency before announcing enterprise pricing — which hasn't been published yet. Based on Google's playbook with Workspace, Maps Platform, and Firebase, expect a genuinely useful free tier for small teams and a per-seat model that recovers revenue from organizations that would have otherwise paid for Figma Organization.
The honest evaluation for teams looking at Stitch today: you're getting access to pre-GA software with a usage ceiling that will force a pricing decision within 12-18 months. That timeline needs to factor into your adoption planning and your vendor negotiation leverage with Figma.
Should Enterprise Teams Panic?
No. But complacency is equally wrong. The switching costs from Figma are real and non-trivial: design tokens, component libraries, plugin ecosystem, handoff workflows, developer integrations. You don't migrate a mature design system in a sprint.
The actual risk isn't that your existing team switches tomorrow. It's that new projects start in Stitch. Three years from now, Figma's installed base looks stable on paper while all new greenfield work flows to Google. That's how platform displacement works in enterprise — gradually, then suddenly.
Teams on Figma Professional (not Organization) face a different calculus. You're not staring at $13,200/year, so the urgency is lower. Watch Q3 2026 when Google will likely announce enterprise pricing — that's when the real TCO comparison becomes possible and the decision gets concrete.
The Verdict
Google Stitch is the most credible pricing threat to Figma since Figma ended Sketch's reign. The stock reaction is rational market behavior, not panic. The question isn't whether Stitch will pressure Figma's pricing power — it already is — but whether Google has the product discipline to execute past the Labs phase.
If you ask me directly: Figma needs more than AI feature additions. It needs a structural response — a genuine free tier, an open-source core, something that changes the cost comparison at the enterprise level. What it cannot afford is letting Google own the "free AI design tool" positioning while sitting at $13,200/year for a 20-person team.
Startups and small teams: put Stitch in your stack now, before enterprise pricing arrives. Figma Organization customers: don't migrate yet, but start that evaluation before Q3 forces the decision. The market has already placed its bet — and it's not betting on the status quo.
