Pricing and quotation guide
UI UX design cost
The cost of UI and UX design depends less on the number of screens than on how much needs to be understood and tested. A small set of screens for a simple task with known users is a modest job; a complex web app with several user roles, unclear needs and many edge cases takes far longer, even if the screen count is similar. Research and testing, prototype fidelity, whether a reusable design system is built, how thoroughly accessibility is checked and how much support developers get during build all change the price. Comparing quotes means comparing what each includes, not only the headline figure.
This guide explains the cost drivers, typical scopes, pricing models and how to judge value. No prices are given, because they depend on scope and provider; LetGetGrow sets out the cost for your project in a custom quotation.
Illustrative diagram
What drives UI and UX cost
- Complexity of tasks
- Roles, rules and edge cases.
- Research and testing
- Interviews, test rounds, analysis.
- Screens and states
- Each screen has empty, error and loading states.
- Fidelity
- Wireframes, clickable prototypes or polished UI.
- Design system
- Reusable components and documentation.
- Handoff and support
- Annotations and help during build.
Costs paid to third parties (separate from our fees)
- Participant incentives
- Research or testing tool licences
- Design tool seats for your team
Ask whether the quote covers every state of each screen or only the main view.
Scopes compared
| Scope | What it covers | Relative cost |
|---|---|---|
| Screen refresh | Visual update of existing flows | Lower |
| Feature design | One flow researched, prototyped and tested | Moderate |
| Product design | Several flows, roles and a component library | Higher |
| Ongoing design support | Regular design time alongside development | Varies by time |
Pricing models
Fixed project fee
Suits you when
- Clear, limited scope
Watch out for
- What counts as a change
Phased fees
Suits you when
- Uncertain needs
Watch out for
- Each phase's deliverables
Time-based or retainer
Suits you when
- Ongoing product work
Watch out for
- Reporting on time spent
Screens hide states
A single screen in a quote may hide several designs: what it looks like empty, while loading, with an error, with too much data, for different user roles and at mobile width. Quotes that count only the main view can lead to gaps at handoff. Ask how states are counted.
Research and testing
Research and testing take time to plan, run and analyse, and may involve paying participants. Small, repeated tests with a few comparable users can find many problems; distinct user groups need people from each. Cutting testing saves money now but moves the risk into development and launch.
Example: phasing a product redesign
Illustrative example — not a client case study
Situation: A start-up wants its whole product redesigned but has a limited budget.
- Phase one covers interviews and flows for the two most important tasks.
- Phase two prototypes and tests those flows; phase three designs the UI and core components.
- Other areas reuse the components later, at lower cost.
What this shows: Spending followed evidence, and components reduced later costs. This example is illustrative.
Design systems
Building reusable components adds cost at the start but can make later screens quicker to design and build. For a small site it may not be worth it; for a growing product it often is. Ask whether components are part of the quote.
Comparing quotes
List for each quote: research, testing rounds, flows, wireframes, prototype fidelity, screens and states, components, accessibility checks, handoff, developer support, revision rounds and file ownership.
Keeping costs down
Prioritise the most important tasks, reuse existing components where they work, provide research you already have and make decisions quickly.
Judging value
Good value shows in fewer surprises during build, fewer support questions after launch and users completing key tasks more easily, measured against an agreed baseline.
Accessibility in the budget
Designing to WCAG 2.2 criteria such as contrast, visible focus and target size costs little when planned from the start, and much more when retrofitted after build. Ask the designer which criteria they check during design and whether that work is included in the fee. A separate accessibility audit of the built product, if needed, is usually priced on its own.
Support during build
Questions tend to arise once development starts: a state that was not designed, a component that behaves differently on mobile, a rule nobody mentioned. Agree how much designer time is included for developer support, and the rate for extra time, so build does not stall or developers fill gaps alone.
Files and tools
Check which design tool the files will be in and whether your team needs its own seats to open and edit them. Tool licences are separate from the design fee.
Questions about UI UX design cost
What affects UI and UX cost most?
Complexity, research and testing, states and handoff.
Is screen count a good guide?
Only partly; states and complexity matter more.
Is research worth paying for?
It moves risk out of development and launch.
Should we build a design system?
For growing products, often; for small sites, maybe not.
How can we spend less?
Prioritise key tasks and share existing research.
How do we judge value?
Smoother build, fewer support questions, easier key tasks.
Sources referenced
Platform features, guidance and rules change. We check the current versions before committing to an approach. This page is general information, not legal advice.
- Nielsen Norman Group: Why you only need to test with 5 users (opens in a new tab) — reviewed 2026-11-03
Request a Custom Quote
Ask about UI UX design cost
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.