Figma Make
Figma's native design-to-code AI with deep design-system context (Make Kits, Make Attachments) and enterprise governance, now extending from prototyping into shipping.
Dimension breakdown
Score · confidenceFigma's native design-to-code AI with deep design-system context (Make Kits, Make Attachments) and enterprise governance, now extending from prototyping into shipping. May 20 launched Figma's own canvas design agent; May 28 launched a Make local-code beta — connect a production Git repo, an AI coding agent reads the code architecture and applies your visual edits, then you commit and open a PR without a terminal (two-way GitHub, governed by your CI + code review).
Q1 2026 financials confirm Market-Leader viability: $333M revenue (+46%), NDR 139% (2-yr high), FCF margin 27%, ~690K paid customers (+54%), guidance raised. Differentiates on design fidelity and ecosystem maturity vs v0/Bolt, but Bolt/Replit win on framework flexibility.
under active competitive disruption — Anthropic's Claude Design (launched Apr 17, Opus 4.7) directly attacks Make's design-system-context differentiator; FIG stock is down ~85% from its post-IPO peak and layoffs continued through Apr 2026.
Reliability complaints persist (GitHub-push 502s, duplicate files forced to main, error loops, OOM on long chats). Khan v.
Figma AI-training-consent class action (filed Nov 21, 2025) remains undismissed; AI-credit/billing complaints persist; local-code feature is a closed, Mac-only beta.
Use cases
Not yet assessed — this section fills in as ACES research covers the tool.
Risk flags
Pricing volatility
enterpriseTemporaryFrequent pricing changes causing budget unpredictability
Caps Enterprise / Compliance at 60
Removed when — 12 months of pricing stability with no user complaints about billing surprises
Reliability complaints
trustTemporaryWidespread reliability complaints (breaks often, unreliable output)
Caps Autonomy at 60
Removed when — 90+ days of improved reliability with community acknowledgment
Status rationale
Assessed sustained. Figma's enterprise platform provides strong Band-4 governance for design-to-code workflows, and Q1 2026 financials confirm Market-Leader viability (revenue +46% to $333M, NDR 139%, FCF margin 27%, ~690K paid customers, guidance raised, AI-credit monetization beating targets).
The May 20 canvas design agent and the May 28 Make local-code/PR workflow materially strengthen autonomy, integration, and interface and begin to close the prior production-code-export gap (export ZIP now includes package.json + vite.config.ts). Not yet Validated because: the headline local-code/two-way-GitHub capability is a closed, Mac-only beta (not GA); reliability complaints are active and recurring (newly applied reliability-complaints cap, Autonomy ≤ 12); pricing-volatility cap stays applied (Compliance ≤ 12 — AI-credit/billing complaints persist, PAYG still rolling out, no 12 months of pricing stability); Khan v.
Figma AI-training-consent class action remains undismissed; and the category is under sharp competitive disruption from Anthropic's Claude Design (which reads codebase + design files at onboarding, eroding Make's design-system-context differentiator) against a backdrop of an ~85% stock decline and continued layoffs. React+Tailwind+Radix lock-in still limits framework reach vs Bolt/Replit.
Config 2026 (June 23-25) is the next major catalyst.
Movement triggers
Upgrade toward Validated if: (1) the Make local-code / two-way-GitHub workflow reaches GA across platforms (currently closed, Mac-only beta) with named enterprise production references on the shipping path; (2) reliability complaints stabilize for 90+ days (GitHub-push 502s, duplicate-file/main-branch behavior, error loops, OOM resolved) — removes the reliability-complaints cap (Autonomy ≤ 12) and clears the way past 12; (3) billing complaints stabilize for 12+ months as AI-credit add-ons + PAYG broadly adopt and overage bugs are fixed — removes pricing-volatility cap (Compliance ≤ 12); (4) Khan v. Figma dismissed or settled with no material adverse finding on training consent; (5) Make demonstrably holds design-system mindshare against Claude Design.
Downgrade/cap if: class-action adverse ruling implicating training opt-out; AI-credit/billing complaints escalate causing measurable enterprise churn; second pricing restructure within 12 months; Claude Design or Bolt/v0 demonstrate measurable Make user exodus (community-exodus cap); reliability regressions worsen or development stalls amid layoffs.
Risks & limitations
Pricing Volatility
ModerateRadar cap: pricing-volatility
Reliability Complaints
ModerateRadar cap: reliability-complaints
Integration surface
Not yet assessed — this section fills in as ACES research covers the tool.
Adoption & benchmarks
Not yet assessed — this section fills in as ACES research covers the tool.
Spotted something wrong or missing here? Suggest a change →
Per-source contributions
Click any dimension to see the underlying sources and citations.
More in this category