Most design handovers fail quietly. The screens are beautiful, the engineer opens Figma, and three quarters of the states they need are missing — empty, loading, error, long name, no permission. The design was a picture of the product working. Here is the other kind.
UI/UX design covers research, information architecture, user flows, wireframes, interface design and a reusable design system. Its job is to reduce the number of decisions made during engineering. A design engagement for a product typically runs four to eight weeks.
Enough to surface most serious usability problems, which is why we never wait for a big study.
Default, empty, loading and error — designed, not left to the engineer at 6pm.
Because the majority of Indian traffic is a phone, and desktop-first designs degrade badly.
One source of truth, so the eleventh screen does not invent a twelfth grey.
Research summary and problem statement
IA map and user flows
Wireframe set
Figma design system
Full design file and prototype
Tested designs and a QA report
The design looked finished. Then engineering asked what happens when the list is empty, when the name is forty characters, when the network drops halfway, when the user has read-only access. None of it was drawn, so all of it got decided in code, inconsistently, by four different people.
Design does a different job depending on what the product is trying to do. Aesthetics are the smallest part of all of them.
Onboarding that drops most trial users before they reach the feature that would have convinced them.
A flow designed backwards from the activation moment, with the first session choreographed rather than assumed.
Filters and search designed for the catalogue's structure rather than for how customers actually look for things.
Research-led navigation and product pages built around the decisions a buyer is really making.
A tool the team works around because it fits the database rather than the job, so the shadow spreadsheet survives.
Flows designed by watching the work, with the common path fast and the exceptions possible.
Forms that are legally complete and humanly impossible, abandoned two-thirds of the way through.
Progressive disclosure, saved progress, plain-language help at the field that confuses people.
Interfaces designed for the clinic's workflow and used, under stress, by patients who have never seen them before.
Accessible, high-contrast, plain-language design tested with actual patients rather than with staff.
Every screen designed from scratch, so the product looks like four products and the team is slow.
A small design system first, then screens assembled from it — faster to design and far faster to build.
A design system is usually sold as a consistency benefit. That undersells it. Its real return is in decisions not made twice.
When spacing, type and components are defined, an engineer implements rather than interprets. That is where the speed comes from — not from typing faster.
Changing a button in a system is one change. Changing a button in forty hand-drawn screens is forty changes and at least one you will miss.
A documented system is how a new designer or a new agency picks up your product without redesigning it out of habit.
Contrast ratios, focus states, touch targets and text sizing decided once at the component level, rather than argued about per screen and forgotten under deadline.
Interviews with real users, a look at what your analytics and support tickets already say, and a competitive teardown that is honest about what competitors do well.
Navigation, hierarchy and naming — what things are called, which is a design decision people consistently underestimate.
The paths through the product, including the ones where something goes wrong, which is where most of the real design work lives.
Structure before styling, so the argument about what goes on the page happens before anyone has fallen in love with a colour.
Every screen, mobile and desktop, with the four states each — default, empty, loading, error.
Type scale, colour tokens, spacing, components and usage notes, built in Figma so engineering can mirror it in code.
A clickable prototype tested with five people from the target audience, with the findings written down and prioritised.
We review the built product against the design and file the differences. Handover without this is an assumption, not a process.
Every tool on this list is one we have shipped and still maintain for a paying client. Nothing here is aspirational — if it is not in production somewhere, it is not on the page.
A short list, because the tools matter far less than whether the states got drawn.
Design, prototype, system and handover in one file the client keeps access to permanently.
The design system expressed as the tokens the front end actually uses, so the two cannot drift.
The component library built alongside the design system, so a component exists in both places or in neither.
Most design handovers fail quietly. The screens look finished, the engineer opens the file, and three quarters of the states they need are missing — empty, loading, error, long name, no permission. The design was a picture of the product working.
Research, information architecture, user flows, wireframes, interface design and a reusable design system. Its job is to reduce the number of decisions made during engineering — that is where the speed comes from, not from designers working faster.
Sold as a consistency benefit, which undersells it. Its real return is decisions not made twice: when spacing, type and components are defined, an engineer implements rather than interprets. Changing a button in a system is one change; changing it across forty hand-drawn screens is forty changes and at least one you miss.
Start with tokens — type scale, colour, spacing, radius — then the eight or nine components used on every screen. What to build first and what wastes a month is set out in design system development.
On commercial pages, clarity beats decoration and message match beats layout. If the ad promised 2BHK flats in New Town from a certain price, the H1 should say close to that — every gap between promise and page is a moment where some visitors leave. The structure that works is in conversion-focused web design.
Five people will surface most serious usability problems, which is why we never wait for a large study. Interviews in English, Hindi or Bengali, sessions recorded, findings written down and prioritised rather than mentioned in a call and forgotten.
We design what we build, and design what other people build. Either way the handover includes specs, every state, and a design QA pass afterwards — because the gap between the file and the shipped product is where the quality actually goes. See Web Development and Mobile Apps.
Every stage ends in something you can hold — a document, a build, a live account. If a stage cannot name its output, it is a meeting, not a stage.
Interviews, analytics review and a competitive teardown, ending in a written point of view rather than a mood board.
Navigation, naming and the paths through the product, agreed before anything is styled.
Structure for every key screen, reviewed fast and cheaply while changes still cost nothing.
Type, colour, spacing and the components the product needs — built before the screens that use them.
Every screen in every state, assembled from the system, then made clickable.
Five-user usability round, revisions, then handover with specs and a design QA pass after the build.
Everything here is part of the engagement at no extra cost. We do not itemise them on an invoice and we do not withhold them if you leave.
Real people from your target market, on real phones, with findings written up and prioritised. Included rather than sold as research.
Default, empty, loading and error — designed, not left to an engineer at 6pm. This is where most handovers quietly fall apart.
We review what was built against what was designed and file the differences, even when someone else built it.
Full access to the source, the components and the system. No view-only handover.
Contrast, focus states and touch targets decided once at component level rather than argued about per screen and skipped under deadline.
Longer answers to the questions people ask before they hire anyone for ui/ux & product design.
Built by us, free, no signup, nothing uploaded to a server. Take them whether or not you ever become a client.
Website design is scoped on the number of unique templates. Product design — with research, a design system and every screen in every state — is scoped on flows and user roles rather than screen count. An embedded designer is monthly. All of them include the Figma source and a design QA pass after the build.
Tell us what you have now and what you are trying to reach. We will audit it and tell you what we would do, what it would cost and whether you need us at all. The audit is free and yours to keep.