4.9/5 from 20,000+ builders
For product teams
The whole team edits one thing. The product itself.
Design, product and engineering compose on one screen. The variant and the number point at the same component.
Works with the tools the team already has
Figma
Slack
Trello
GitHub
Google Analytics
Vercel
Airtable
Stripe
Plausible
Claude
The loop
The answer comes back to the same screen.
A variant, a run, a decision. All three land on the component that changed.
plusui.com/projects/pricing
Pricing card
Live testAPro£24Choose plan
BPro£24Start free
Changed
ButtonLabel
Result
A
B
Decision
Keeping B
The team composes on one screen
Design, product and engineering edit the same composition, so nobody has to describe it to anyone else.
A variant belongs to the component
Test the same component with a different value. The variant cannot leave the system.
Button
Choose planStart free
The number names the component
Events are grounded in the design system, so what you read names the thing you changed.
ButtonPricing cardNav
By the numbers
The team counts one set of things.
The parts everyone names the same way, and the people already working from them.
Product teams
Put the whole team in one file.
The design system layer is open, and the Builder is where the team meets it.