Your agency brings the design. How do we ship it?
What design and development should agree on so the delivery respects the Figma files, scope and your client relationship.
In this article
The agency design is the starting point
If your agency has approved screens and a visual direction, there is no need to start again. Development translates that design into a working product for the agreed devices and situations.
In a white-label collaboration, the agency can retain the client relationship while Luby supports development. Introductions, communication and portfolio permission are agreed in advance, not assumed.
We review what a screenshot cannot show
A static screen does not explain a failed form, a longer piece of text or a slow API response. These decisions are part of the delivery too.
- Desktop and mobile layouts, including sizes between them.
- Loading, empty, error and success states.
- Components, fonts, assets and usage rights.
- Interactions, animations and navigation.
- Real content, API documentation and test access.
Agree on a first delivery you can review
Instead of a vague promise to “build the whole website”, define screens, journeys, integrations and acceptance criteria. This makes it possible to review concrete work and separate scope changes from implementation errors.
Timing depends on complexity and what is ready. A landing page and a platform with payments and accounts do not require the same effort just because both begin in Figma.
Feedback needs one source of truth
It helps when the agency consolidates comments and separates approved changes from ideas still under discussion. Referencing the screen, device and expected behaviour makes each point actionable.
Visual reviews sit alongside testing navigation, forms and screen sizes. Looking like the design is not enough if the main journey fails or cannot be used with a keyboard.
Handover includes access and continuity
Before launch, agree who controls the domain, hosting, repository and external services. Define which documentation and access will be delivered and what maintenance sits outside the initial scope.
If screens are missing or the agency needs design support, that can be quoted separately. Implementation should not silently turn into an unbudgeted redesign.
What to send us first
A Figma link, a description of the product and its integrations, the target date and the person coordinating reviews. That is enough to identify open questions and start scoping.
You do not need an internal engineering team to discuss the project. It does help to have clear owners for design, content and approvals.
Let’s bring it back to your project.
Tell us what you need to build