Dylan Field: “Design is increasingly the differentiator” as Figma moves content and hosting into the canvas

Figma spent its biggest conference yet telling you that design is the differentiator and code is cheap. That's the pitch. Underneath it is a bigger move: Figma wants to be the place where specs, content, and shipping all happen, not just where you draw the screens. Let me catch you up on what changed and what it does to your stack.

The deep cut

• One tool wants the whole pipeline, not the canvas. Figma added Payload content and Make hosting so apps ship from inside Figma.
• Content becomes design material, not a handoff. IBM's Noah Trevino got a working content system his team could edit without engineering.
• A shared record beats scattered AI chats. Productboard argues specs drift when each PM feeds a different context to a different tool.

From drawing screens to shipping them

Figma used Config India, its largest international conference with over 30,000 registered, to frame the whole thing. Dylan Field put it plainly: "In a world where code is becoming commoditized, design is increasingly the differentiator." India is now Figma's second largest market by daily active users, and the research there is bullish. 83% of Indian builders say they are more productive, and 77% of non-designers are regularly doing design work.

That last number is the real story for you. Figma is betting the line between designer, PM, and marketer keeps blurring. If non-designers are already in your files, Figma wants to give them more to do there than comment.

Content stops being a handoff

The Payload integration is the clearest sign of the ambition. Payload joined Figma last year, and now it is baked into Figma Make. Prompt an app and you also get a database, file storage, user login, and an admin panel. A marketer edits copy in the panel. A developer extends the open-source framework. Figma hosts it all.

At IBM, lead designer Noah Trevino handed Figma his existing screens and a list of fields, and got back "a content system anyone can manage, with version history built in." Content is no longer the thing you wire up after the design is done. It is raw material you design with from the first prompt.

The tradeoff: hosting is in beta and free for now, with pricing "before it takes effect." You would be moving your content layer and your backend into a tool whose price you cannot see yet.

The record that drift keeps killing

Here is the problem Figma is racing to solve, and Productboard describes it best: every PM has an AI tool, and each one gets different context. One writes specs in Claude, one mocks in Lovable, one sits in Cursor with engineering. "That flexibility works for the individual PM. Across a product organization, it creates inconsistency and drift."

Two PMs ask about the same customer and get different answers. A spec changes in a coding tool and the roadmap never catches up. When an exec asks why a feature shipped the way it did, the reasoning is scattered across private chats and code comments.

The answer both companies land on is a shared record connected by MCP, the open standard that lets AI tools read from and write back to one source. Figma is pushing to be that source for design and content. Productboard wants it for the product record. You cannot have two.

Ops becomes the air traffic control

If one tool runs the pipeline, someone has to run the tool choices. Tom Moorer, Head of Design Ops at Fin, calls the shift "operating to orchestrating." The job used to be building scaffolding for designers. Now it is coordinating people, agents, and tooling so anyone can build.

Moorer is blunt about headcount. "I think we've proven you don't need teams of 10, 20, 30 DPMs now." He wants marketers building websites and legal building its own dashboards, with internal infra that is plug-and-play. That maps exactly onto what Figma is selling. The risk is obvious: if your tooling decides who can build what, your org chart starts to follow your software contract.

And some judgment does not move. As Dilara Cumhur told Design Meets AI, judgment "comes from within your presence, through your emotions, your belief system." The system can hold your context. It cannot hold your taste.

Three questions for your team

• If specs and content move into Figma, what becomes our single source of truth, and who owns writing back to it?
• Payload hosting is free in beta with no pricing yet. What is our exit plan if the number lands wrong?
• Non-designers are already editing in our files. Where do we draw the line between "anyone can build" and work that needs a designer's judgment?