Product Design

In scope and depth. The individual UX/UI services design a specific product type against an agreed scenario. Product Design is the full cycle: first we work out how the product is structured and how users move through it, then we design, draw, build the design system and support development. It is the option for products built from scratch or rebuilt entirely.

A Figma file with every screen and its states, a design system with components and rules, an interactive prototype of the key flows, wireframes and a screen map, plus specifications for the development handoff. All source files become your property.

Up to 30 unique screens. A screen is the same as a page on a website: a distinct view the user sees — a dashboard, an order list, a product card, profile settings. Screen states — loading, errors, empty lists — are not counted separately; they are included. For a bigger product, screens are added in blocks of 10.

An understanding of the product and its audience, plus participation in the kick-off workshop. The ideal input is a defined MVP scope or a technical specification; if you have neither, we start with the workshop and fix the scope together. User data, analytics and references speed things up.

Four stages with sign-off after each: information architecture and flows, wireframes of the key screens, a UI concept in two directions, then the design of all screens and the system build. You never get a surprise at the end — every step is approved before the next begins.

No, but they make the work cheaper. If you have already been through Prototyping or MVP Scope Definition, the structural stage shrinks and we move to the visual part sooner. If not, we do it all within this service.

A set of components — buttons, fields, cards, tables — with rules for using them. For you it means faster and cheaper development: engineers assemble screens from ready parts, and new pages after launch do not need a designer for every small thing.

The Figma file is structured for dev mode: specifications, spacing and styles read without extra documents. We hold a kick-off meeting with the development team, and through the first month we answer questions and check the built screens against the layouts.

Two rounds per stage within 7 days of its delivery. A round is one consolidated list of comments that we work through in full. An extra cycle costs $400 and adds 3 business days.

Yes, development is a separate line of our services, and a product designed with us goes into build without a handoff stage. But it is not a condition: with the design system and specifications, any external team can build the product without us.