Hiring a UI UX design firm, the three jobs sold under one name and what has to arrive in the design file

A UI UX design firm sells three different things under one name. The first is research, which tells you what to build. The second is interface design, which draws the screens. The third is a design system, which is the set of reusable parts a developer builds from. Most buyers want the second, assume the third is included, and never asked for the first. Decide which of the three you are paying for before you read a single proposal, because a firm that is strong at one of them is often indifferent at the others.

This is a buying decision with real demand behind it. In India, searches for ui ux companies, ui ux design firms and user interface design companies each ran at 480 a month, harvested on 22 October 2026 against Google's India location alone. In the United Kingdom the same three phrases ran at 140, 110 and 40 a month, harvested the same day against the United Kingdom alone. Those are two separate measurements of two separate markets, and neither figure includes the other.

Research, interface design and the design system are three purchases

Research is the work that happens before anybody draws a screen. It covers interviews with the people who will use the thing, a review of what they do today, and a written set of tasks the product has to make easy. The output is a document, not a picture. It is the right first purchase when you are building something new, when an existing product gets support tickets you cannot explain, or when two people in your own company disagree about who the user is.

Interface design is the drawing of screens. It is the part everybody pictures when they hear UI UX. The output is a set of layouts covering every state a screen can be in, which is a longer list than most buyers expect. A single form has an empty state, a filled state, a loading state, a success state, a validation error on one field, a server error on the whole submission, and a version that works on a phone. A design that shows only the happy path hands all seven decisions to a developer who will make them in a hurry.

A design system is the reusable layer. It is a named set of colours, type sizes, spacing steps, buttons, inputs, tables and cards, each defined once and used everywhere. Buying it is worth it when you expect to keep building for a year or more, because it makes the second and third screens far cheaper than the first. Skipping it is reasonable for a short project with a fixed end. What is not reasonable is assuming it came free with the screens, then discovering at handover that every button in the file is drawn by hand and no two are the same size.

What has to arrive in the design file

Name these in the contract as deliverables, not as hopes. A firm that is doing the work properly will have no trouble with the list, and a firm that objects to it is telling you something useful.

• Every screen in every state, including empty, loading, error and success, and including the phone width.
• Colour, type and spacing defined as named values rather than painted on individual shapes, so a developer reads one list instead of measuring pictures.
• A component for each repeated element, used everywhere that element appears.
• Editable source files in the tool you were shown, handed over in your own account rather than shared from theirs.
• Exported assets at the sizes the build needs, with the source artwork for each one.
• A short written note on each flow saying what happens when the user gets it wrong.

The handover detail that costs people the most is account ownership. If the files live in the firm's workspace and you are a guest, your access ends when the relationship does. Open the account in your company's name, invite the firm into it, and the question never arises.

How the work is priced, and the unit that makes quotes comparable

Three pricing units are common and they are not interchangeable. A per screen price is the easiest to compare and the easiest to game, because a screen can be a login box or a reporting dashboard. A day rate is honest about effort and tells you nothing about scope. A fixed project price is comfortable to sign and only works when the deliverable list above is written into it.

The way to get comparable quotes is to supply the scope yourself. Write down the number of distinct screens, the number of states you expect per screen, whether research is in or out, and whether you want a design system. Send the same page to every firm. Quotes that arrive against your scope can be compared. Quotes that arrive against each firm's own interpretation cannot, and the cheapest of them is usually the one that assumed the least.

Ask what a change costs after sign off, and get the answer in the same unit as the quote. A fixed price with uncapped change requests is a day rate wearing a disguise.

The usability test that is worth paying for

A usability test is five to eight people attempting real tasks on a clickable version of the design while somebody watches and says almost nothing. It is cheap, it is fast, and it is the single most useful thing in this category, because it replaces an argument about taste with a recording of somebody failing to find the button.

Insist on two things. First, the tasks have to be written before the test and phrased as goals rather than instructions. Asking somebody to find the pricing page is not a test. Asking them to work out what this would cost their team for a year is. Second, you watch at least two sessions yourself, live. A summary deck removes exactly the detail that changes your mind.

Run the test on the design before the build starts. A finding at the design stage costs a conversation. The same finding after launch costs a sprint.

Accessibility belongs in the specification, not in a polish pass

Accessibility is cheap when it is a requirement on the design and expensive when it is a fix on the build. Contrast, focus order, label text, touch target size and a visible keyboard focus state are all design decisions. None of them can be added later without reopening the file.

Indian buyers selling to government have a published specification to point at rather than an argument to have. The Guidelines for Indian Government Websites and Apps are published at guidelines.india.gov.in, where the current manual is GIGW 3.0, and the same site states that STQC offers a Certified Quality Website certification for GIGW compliant websites. If any part of your buyer base is a government department, naming GIGW 3.0 in the design brief turns accessibility from a preference into an acceptance criterion. Private sector buyers can use the same document as a checklist even where nothing obliges them to.

Ask each firm for one example of a screen they changed because of an accessibility requirement. A firm that treats it as a specification will have a story. A firm that treats it as a plugin will describe a plugin.

Two checks that are specific to paying an Indian design firm

Many good interface design shops in India are small enterprises, and that changes your payment obligations rather than their service. The Government of India's MSME Samadhaan portal states that the MSMED Act 2006 carries provisions on delayed payment to micro and small enterprises in sections 15 to 24, that the buyer is liable to pay compound interest with monthly rests at three times the bank rate notified by the Reserve Bank of India where payment is not made within 45 days of acceptance of the goods or service rendered, and that any micro or small enterprise holding a valid Udyam registration can file. It also records that state governments establish Micro and Small Enterprise Facilitation Councils to settle such disputes. Read on 22 October 2026. The practical effect is simple. Ask whether the firm holds Udyam registration, and if it does, build a payment schedule you can actually meet.

The second check is the assignment of rights. Design work you paid for does not become yours because the invoice is paid. Put a clause in the contract that assigns the work to you on payment, names the files and the exported assets, and says what the firm may show in its own portfolio. Most firms want portfolio rights and most buyers are happy to grant them. Settling it in writing at the start is what stops it becoming a conversation at the end.

Questions buyers ask when they shortlist a UI UX design firm

Is a UI UX firm the same thing as a web design agency?

No, and the difference is what arrives at the end. A web design agency usually designs and builds a website, and the website is the deliverable. A UI UX firm designs the interface and hands the design to developers, who may be your own team. If you want a finished site, you want the agency. If you want screens somebody else will build, you want the design firm.

Can we skip research and go straight to screens?

You can, and it is the right call when you already know the tasks because you have watched people do them. It is the wrong call when the product is new to you, because the designer will then invent the user, and you will be reviewing a guess without knowing it is one.

How many rounds of revision should a proposal include?

Two rounds per stage is the common shape and it works when the review is structured. Collect all feedback from all stakeholders into one document per round. Drip fed comments from five people over three weeks will exhaust any number of revision rounds.

Should the same firm design and build?

One supplier removes the handover argument and reduces your ability to replace either half. Two suppliers create a seam that needs managing and keeps both honest. For a first product, one supplier is usually simpler. For a product you will keep investing in, separating design from build is easier to live with.

What does a design system cost compared with the screens?

Ask for it as a separate line rather than a percentage, because the honest answer depends on how many components your product actually needs. A firm that quotes it as a line item has thought about scope. A firm that folds it into the total has not told you whether it is in there at all.

What an assistant says when somebody asks who should design their product

Ask ChatGPT or Gemini to recommend a UI UX design firm and the answer tends to arrive as a list of names with no statement of which of the three jobs above each one does. That is the same gap this page exists to close, and it matters commercially, because a buyer who takes that list at face value briefs a research shop for screen work or a screen shop for a design system. If your firm does one of the three particularly well, the question worth asking is whether the assistants describe you that way, or whether they describe you as a general supplier of everything. AI Knows Us measures which firms get named on questions like that and which sources the answer was built from. For the cost side of a full website project rather than the interface alone, our breakdown of what a website costs in India platform by platform prices the build the screens turn into.