Figma Adds a Backend to Its Prototyping Tools, and That Changes What a Website Request Can Look Like

What Figma actually announced

Figma published three announcements on October 15, 2026. The one with the most direct bearing on business owners connects Payload, the open source content framework Figma acquired in 2025, to its prompt-driven build tool, Figma Make. In Figma's description, an app assembled through a prompt no longer arrives as a bare interface: it comes with the surrounding machinery a working site needs, namely somewhere to keep content and submitted information, a way for visitors to sign in, and a back office where staff can maintain what the site shows. Access to the feature is not switched on for everyone at once; Figma says it is reaching accounts gradually over the coming weeks, and the hosting that runs these projects is still a beta that carries no charge today, with the company committing to announce pricing before any charge begins.

The second release, called Specs, is a collaborative container for Markdown that lives on the Figma canvas and references the team's design work. Figma describes it as a place for shared decisions and context that evolves over time, and it is rolling out in open beta on paid plans. The third release moves code layers into open beta, letting teams build prototypes backed by real code side by side on the shared canvas. Figma's own documentation notes that code layers uses AI credits, and a prototype written in code is not evidence that an arbitrary production application is ready to ship.

TechCrunch's independent reporting on the same announcements confirms the release itself. It does not test the reliability, security or business results of these features, and Figma's promotional statements about download growth and adoption are vendor claims that we do not treat as verified outcomes for any other organization.

Why a prototyping tool with a real backend matters to a business owner

A familiar pattern in small organizations is the disconnected website. The marketing pages live in one system, quote requests arrive by email or a form whose responses land in a shared inbox, and the details then get retyped into spreadsheets or a customer record. Nobody owns the flow end to end, and status is hard to see without asking around.

What Figma is building points in a different direction: the prototype, the content, the submitted data and the administrative review screen are assembled from the same prompt and managed in one place. That is a meaningful shift in expectation. When a design tool ships an admin panel, a login and a database as part of the prototyping step, business owners can reasonably start asking their vendors for websites where staff can update service pages themselves and where each incoming request carries a record of who reviewed it and what happened next.

What this means for your business

Detailed In Design could build a service business website around exactly this pattern: staff-editable service pages, a structured quote request form instead of a free form email, a link from each request to the customer record, and a staff review queue that holds an estimate or customer message until a named person approves it. Approved shared requirements and a working prototype would be used to validate the flow before anything goes live. The expected benefit is less repeated entry and clearer ownership and request status. We make no claim about time saved, revenue or accuracy; those depend on your process and staff.

The limitations are real and worth stating. This is a proposed custom build by Detailed In Design, not a shipped product of ours and not a partnership with Figma or Payload. Access to these Figma features is phased, Specs is limited to paid plans during beta, code layers consumes AI credits, and future hosting prices are unannounced. A production system still requires documented access permissions, privacy and retention rules, form validation, backups, error handling, accessibility and security checks, and named human reviewers. Generating a website in a tool does not supply a business operating system, and no automatic connection to a CRM is established by these announcements.

A practical next step

If your website and your request handling live in separate places, the useful first move is not to adopt any particular tool. It is to write down one flow end to end, from the page a visitor reads to the person who answers, and find where details are retyped or lost. If you would like help mapping that flow or building a website with editable content and a reviewed intake queue, our web design work starts with that kind of map, and you can see where to begin at our website.