Figma is becoming a suite
Figma is expanding beyond a single design canvas into a suite that includes sites, AI-assisted build tools, slides and more, which raises classic platform questions. That breadth can lower switching costs if objects and workflows remain coherent, but it also creates new failure modes—broken exports, asset fidelity issues and permission seams—that PMs must guard against (intellectia.ai). The practical test for product teams is whether adding features reduces friction across the user journey or simply increases surface area and support burden (intellectia.ai).
Figma used to be the place where a product team drew the interface. By April 2026, its own pricing page lists Figma Design, Figma Make, Figma Draw, Figma Sites, Development Mode, FigJam, Figma Slides, and Figma Buzz in one product lineup. (figma.com) That shift happened fast. At Config in June 2024, Figma launched Figma Slides, a redesigned interface, new artificial intelligence features, and major updates to Development Mode, then added another wave of products at Config on May 7, 2025. (figma.com, figma.com) The clearest sign of the new strategy is Figma Sites. Figma said in May 2025 that Sites lets teams design, build, and publish websites inside the same workflow instead of handing mockups to another tool and rebuilding them there. (figma.com) Then there is Figma Make. Figma’s home page now describes it as a prompt-to-code tool that turns ideas into working outputs inside the same product family, which pushes Figma closer to the part of the stack where software actually gets built. (figma.com) Slides fills another gap that used to send teams elsewhere. When Figma introduced Figma Slides in June 2024, it added speaker notes, slide transitions, and presentation tools so designers could stay in Figma instead of exporting work into PowerPoint or Google Slides. (figma.com) Development Mode ties the suite to engineers. Figma says Development Mode now brings design context into Visual Studio Code, Cursor, Windsurf, and Claude, so the handoff step starts to look less like passing a file and more like working from one shared source. (figma.com) This is the classic software suite play. If the same button, color token, and page layout can move from design file to website to slide deck to code view without being recreated, leaving Figma gets harder because the cost is no longer one file export but an entire workflow rewrite. (figma.com, figma.com) The risk is that every new room in the house adds another door that can jam. Figma’s own help center says some products such as Figma Sites and Figma Buzz are still in beta, which usually means teams should expect rough edges in publishing limits, permissions, and feature coverage. (figma.com, figma.com) Billing shows the same tension between convenience and complexity. Figma now sells different seat types such as Full, Development, and Collaboration seats, and says it does not offer standalone products, which makes adoption simpler for Figma but can make access rules and cost control more complicated for customers. (figma.com, figma.com) So the real test is not whether Figma can launch more tabs. The real test is whether a marketing page made in Figma Sites, a product review deck built in Figma Slides, and an engineer’s work in Development Mode all stay faithful to the same underlying objects instead of creating three slightly different versions of the truth. (figma.com, figma.com, figma.com)
