BETA
Join the waitlist From chosen variant to pull request.
Pick the variant. Build writes it in your repo with tests and a preview, behind a flag. Your engineers review it like any other PR.
Design and code on one canvas
The screen and its code sit next to each other. Change one and the other follows.
Screens on your design system
Design generates on your components and tokens, sized to content, so the code uses what you already have.
Code in your repo
Build opens a pull request in your codebase, with tests and a preview link. No export step.
Preview before merge
Every PR has a preview the whole team can open, comment on and approve.
Built for the hand-off
Figma in, Figma out
Attach frames as context or send generated screens back to Figma.
Your stack, your conventions
Build reads the repo and follows its patterns, components and tests.
Flags by default
Every change ships dark behind a flag so review and rollout are separate decisions.
Traceable to the why
Each PR links back to the hypothesis and the evidence that started it.
Start from a prompt.
“Implement variant B behind a feature flag, with tests and a preview.”
Run this when my batch opens →“Redesign this checkout step on our design system. Three variants, sized to content.”
Run this when my batch opens →Questions, answered.
Which repos and stacks are supported?
GitHub and GitLab. Build works in the language and framework your repo already uses.
Who reviews the PR?
Your engineers, in your normal review flow. Scopeout never merges on its own.
Can we bring our own designs?
Yes. Attach Figma frames or screenshots and Build implements them.
Stop running the business. Start directing it.
Join the waitlist
ScoutPrivate beta. We onboard teams in small batches. Or contact us.