How Much Does UI/UX Design Cost?

UI/UX design is sold as a single line on a quote and is actually four separate jobs: finding out what users need, deciding how the thing works, drawing what it looks like, and checking whether any of it landed. Different providers include different subsets, which is why two quotes for "UI/UX" can describe completely different amounts of work.

This breaks the four apart, says what each is worth, and names the cases where skipping one is sensible and the cases where it is expensive.

The Four Things Inside the Quote

Research — finding out what is actually true

Talking to real users, watching them use what exists, reading support tickets, finding where people give up. UX research is the part most often cut, and cutting it is a bet that you already know what the problem is. Sometimes that bet is fine. It is a bad bet when you are building something new, entering an unfamiliar market, or when the team has strong disagreements nobody can settle with evidence.

UX design — deciding how it works

The structure: what screens exist, what order they come in, what each one asks of the person, what happens when something goes wrong. UX design produces flows and wireframes — deliberately plain, because arguing about layout while the structure is unsettled wastes both.

UI design — deciding how it looks

Type, color, spacing, components, states. UI design is the visible part and the one clients imagine when they ask for design. It is also the part that costs least to change later, which is the opposite of what most people assume.

Testing — checking it worked

Putting the thing in front of people before it is built in full. Usability testing with five or six people finds most of what is wrong, and finds it while changing it is still cheap.

What Moves the Number

• Number of distinct screens — a dashboard with twenty views is not a five-page site
• Whether a design system exists, or has to be built from nothing
• Platforms — web only, or web plus mobile app, each with its own conventions
• How much is genuinely new versus a pattern that already exists and works
• Whether research and testing are included or assumed away
• States: loading, empty, error, permission-denied. These are half the real work and they are what gets forgotten in the estimate

Why the Cheap Quote Is Usually UI Only

A low UI/UX quote almost always means somebody will draw screens that look good and nobody will have decided what happens when the form fails, when the list is empty, or when the user arrives from an email rather than the homepage.

You find this out during the build, when developers start asking questions the designs do not answer. Those questions get resolved by whoever is nearest, usually a developer at speed, and the result is the thing you paid a designer to avoid.

The test for a quote is simple: ask whether error states, empty states and edge cases are included. If the answer is vague, the price is for pictures, not for design.

When Research Pays for Itself

Research is the easiest thing to cut and the one whose absence costs most, so it is worth being specific about when to buy it.

Buy it when you are building something that does not exist yet; when you are designing for a job you have never done (a healthcare workflow, a fintech compliance step); when people are abandoning a flow and nobody knows at which step; or when two senior people disagree and the argument has no evidence in it.

Skip it when the pattern is well established and your version is not special — a contact form, a standard checkout, a marketing page. Copying a convention that works is not laziness, it is the correct answer, and users already know how to use it.

The Cost of Not Doing It

Design debt is paid in development hours, not design hours, and development hours are the expensive ones. A flow that was never thought through gets built, then rebuilt. A missing empty state becomes a support ticket. A checkout that loses people costs the same amount every month until somebody fixes it, and nobody notices because there is no alert for revenue that never arrived.

That last one is why conversion-focused UX is usually the easiest UI/UX spend to justify: the thing it improves is already measurable, so the result is visible rather than argued about.

What to Ask Before You Commit

• Which of the four — research, UX, UI, testing — is included, and which is not?
• Are error, empty and loading states part of the deliverable?
• What do developers actually receive, and will they have questions it does not answer?
• Do I get the source files, and can my next designer open them?
• If this is a redesign, what evidence says the current version is the problem?
• What would you measure to tell whether this worked?

The last question separates designers who have shipped from designers who have presented. Someone who has shipped names a number — completion rate, drop-off at a step, support tickets about one screen — and someone who has only presented talks about how it will feel.

If you want the detail on what each part covers, our UI/UX page lists them separately for exactly this reason. And if you are still deciding whether you need design or development first, UI/UX vs web design sets out the difference.