Figma commissioned Forrester Consulting to assess Dev Mode using its Total Economic Impact Methodology. The study draws on interviews with four decision makers whose teams use the tool; their input was aggregated into a composite organization with 100–1,000 designers and developers. The research targeted the problems Dev Mode was built to address—inefficient handoff and redundant work—and modeled how teams use it to improve efficiency and time to market.
Measured effects on developer output
Forrester estimates that the tool raises developer output by 20–30% and saves each developer who uses it more than 90 minutes per week. The savings held up in individual reports as well: one company surveyed 200 of its developers and found average savings of 98 minutes per week.
Two years after Dev Mode's launch, the study also puts figures on how faster delivery feeds revenue.
Self-service instead of back-and-forth
Before Dev Mode, developers lost time clarifying design intent or hunting down exact specifications. With inspectable design files, they can pull assets, variables, specs and code snippets directly rather than messaging a designer or waiting for a meeting—a particular pain where time zones don't overlap. A systems designer in the fitness industry described the change as giving developers autonomy: questions go to the file instead of to colleagues, and manual annotation and discussion threads shrink.
Reducing that mental overhead improves the developer experience beyond raw minutes. One developer called the tool non-negotiable, saying, "You cannot take this away from me. I can't work without this."
Staying inside existing tools
Forrester singled out Dev Mode's connections to tools already in developers' daily workflows as a lever for cutting context switching. The Figma for Jira integration links tickets to Dev Mode so developers can update status and comment without breaking flow. Code Connect surfaces production-ready code, removing the need to move between sources of truth. One respondent noted that Code Connect presents the component directly—with a VS Code integration that keeps engineers in their IDEs—instead of requiring them to read design system documentation and then navigate to an internal GitHub repository.
Code Connect also addresses design system adoption. One organization measured $4M in "reuse value" from making its design system easier to use with Dev Mode, with more than $10M expected in 2025. Quality assurance benefited too, since Dev Mode encouraged use of approved code. "We've seen testing savings on average of an 85 to 90% reduction," said a Chief Design Officer at a financial services organization, adding that this made delivering features significantly faster.
Since the research was conducted, Figma launched the Figma MCP server, which flows real-time, design-aware code into AI-assisted development environments and extends Dev Mode's single source of truth so developers can pull assets, specs and components without leaving their editor.
Collaboration outcomes that resist measurement
The handoff is no longer linear; workflows are iterative and increasingly shaped by generative AI, with designers prototyping ideas and developers scoping designs. Forrester found that showing designers how their work lands in code helps them structure and annotate designs for developer efficiency. Time savings translated into revenue impacts, but respondents at the interviewed companies described the relational effects as equally important, calling design and development "wholeheartedly a joint effort" and noting that discussions are "much clearer because they can come together and collaborate."
One company reported moving from "zero code to release" in six to eight months, compared with an old handoff process that "might have taken two or three years."




