At Builder, we’re transforming our workflows with Fusion, enabling product management, design, support, and go-to-market team members to tackle complex projects that previously would have required engineering resources or been deprioritized in the backlog.
Through interviews with our own Fusion power users, we've gathered insights on how different departments are leveraging Fusion, its impact on their work, and tips for other organizations considering adoption.
50%
of frontend PRs are now Fusion-generated
0
handoff friction with PMs and designers
80%
acceptance rate for PRs authored by product managers and designers
* For context, the average full-time developer ships between 0.5 - 5 PRs per week
Share this page
Link copied to clipboard!
The Engineering team at Builder uses Fusion to accelerate UI development, turn Figma designs into code, eliminate the blank-screen paralysis, and maintain code quality standards while shipping features faster. Engineers leverage Fusion through their preferred workflows including CLI, VS Code extension, BuilderBot in GitHub, or the desktop app, enabling them to stay in their development environment while benefiting from AI assistance.
Main Fusion use cases
Turning Figma designs into UI features in minutes
Engineers use Fusion’s design-to-code CLI to convert Figma designs from product designers into complete UI features with Fusion rather than starting from scratch. One Engineer, Ben Murray, described the impact: "I save double the time and triple the headache" with Fusion. When building the new Space Insights dashboard, he imported the Figma design and had all components in the right position with proper text, and correctly-designed charting package in one shot. "As an engineer, the biggest hurdle is zero to one. When you're staring at a white screen in your browser and you're like, 'Oh my gosh, I don't know where to start.' This completely eliminates all those steps and I can easily iterate from there."
Collaborative prototyping and handoffs
Engineers seamlessly receive and iterate on prototypes from product managers. Nicholas, a frontend engineer, explains: "Adam, one of our product managers, will create a branch on Fusion with a prototype of something. Then, he will give me a link to that project. I can check it out and test it right away without having to do all the setup." This completely eliminates the traditional friction of PM-to-engineer handoffs.
PR review automation with BuilderBot
When non-engineers submit PRs, engineers use BuilderBot to make code improvements directly rather than leaving comments that authors wouldn't understand. Kyle Fowler, Head of Engineering, explains the workflow: "Non-engineers often don't know what they're producing other than that it gave them what they wanted in the UI. Being able to use BuilderBot to ask it to make those changes instead of leaving comments means the authors don't get confused by technical feedback." For example, before instituting a Builder Rule to handle dark mode variables, Fusion initially hard-coded CSS values instead of using dark mode variables. Using BuilderBot, engineers could simply tell it to update the code to use the proper CSS variables. "It's a nice interaction pattern between non-engineers making changes and engineers reviewing changes. We end up in a good place much faster than if the engineer actually had to get into a back and forth with the PM or designer."
Rapid visual changes and polish
Engineers make UI adjustments more efficiently by visually selecting elements rather than having to describe them or send screenshots to their AI code editor like Cursor. Nicholas notes: "You can switch from interact to design, select just the element you want to change and be like, 'I want this to be exactly like this,' as compared to Cursor where you have to take a screenshot and paste it there. I trust something that I click and say 'edit that' more than AI having to figure it out with a screenshot."
Team impact
Week-long UI projects now take hours
Engineers can iterate immediately on a working foundation rather than spending days getting the first mockup done, eliminating the dreaded blank-screen paralysis.
50% of frontend PRs are now Fusion-generated
The engineering team has dramatically accelerated feature velocity, with all new UI features in recent months built using Fusion.
Zero handoff friction with PMs and designers
Engineers receive working prototypes via a simple link, review them immediately, and use BuilderBot to refine code without lengthy back-and-forth communication.
PR-ready code from day one
Builder Rules and automated PR reviews ensure AI-generated code meets engineering standards without slowing down deployment, keeping quality high at speed.
Top tips from the Engineering team
Create comprehensive .builderrules
Ben emphasizes starting with Builder rules to save significant time: "If you give it examples, even tiny ones, it'll be eight times better." His rules are surprisingly simple but effective: "Always use MUI components when possible, always use colors from appState.theme.colors like appState.theme.colors.textPrimary." This ensures PR-ready code from the start.
Don't expect perfection, be explicit
Kyle's advice for working with AI: "Don't communicate with it like you're communicating with a human. It is a task-oriented product. Leave out ambiguity. Don't assume anything. Be explicit. If it acts like it doesn't know something, it probably doesn't."
Think of it as onboarding a new engineer
Frame your interaction with Fusion like training a new team member. As Kyle explains: "If you were onboarding a new engineer to the team, what information would you give them to make them successful? That's what you're doing here."
Start small and iterate
Following the advice from other teams, engineers recommend beginning with small, incremental changes rather than massive features all at once. This helps the team adapt to the new workflow and understand how to handle AI-generated code effectively.
Leverage existing workflows
Most engineers use Fusion through their local development environment via CLI or VS Code extension rather than the web interface, allowing them to maintain their existing workflows while adding AI capabilities.
Turn Figma into code in minutes
Looking to kill blank-screen paralysis and double your frontend velocity?