The full answer
Good designs often cover the happy path and leave out the states that make a product work: loading, empty, error, permissions, offline, long text and small screens. The first step is a design review that lists those gaps, so they are resolved with you rather than improvised by a developer under deadline.
The second step is working out what the design implies technically. A screen that shows live availability needs a real-time back end; a search bar implies indexing; a login screen implies authentication and account recovery. Creuto turns the Figma file into a scope document with those elements made explicit, which is what the fixed-scope proposal is based on.
In development, components are built to match the design system in Figma, with the same spacing, typography and colour tokens, so the product stays consistent as new screens are added. QA checks the build against the designs on real devices and browsers, including accessibility and performance.
If your designer wants to stay involved, they can review each sprint demo and raise changes through the normal change request process. If you only have partial designs, Creuto's UI/UX team can complete them. Share your Figma file on a discovery call for an initial assessment.