How to price UX design work: pricing methods explained

By FastBuySale Newsroom · 9 Nov 2026 · 11m ago

Why UX pricing is tricky

UX design is not just making screens look good. It includes understanding users and business goals, researching behaviour, mapping journeys, designing information architecture, creating wireframes and prototypes, testing with real users and preparing designs for developers. Clients often see only the final screens and underestimate the thinking behind them. Your pricing needs to account for the full process, and your proposals need to explain it clearly. Once clients understand the value of research and testing, they are more comfortable paying for it.

The main pricing methods

| Method | How it works | Best for |

|---|---|---|

| Hourly or day rate | Bill time spent | Workshops, research, embedded work |

| Fixed project fee | One price for defined deliverables | Clear redesigns, app flows |

| Phased pricing | Price each phase separately | Larger, uncertain projects |

| Retainer | Monthly fee for ongoing design support | Product teams with steady needs |

| Value-based | Price linked to business impact | Experienced designers, measurable goals |

Step 1: calculate your minimum rate

Add your target annual income to business costs, such as design software, prototyping and testing tools, hardware, insurance, training and taxes. Divide by realistic billable hours, which are often 50 to 70% of working hours once admin, marketing and learning are included. This is your floor, not necessarily your quoted rate.

Worked example: day rate

Leo wants 70,000 dollars a year and has 14,000 dollars of costs, so he needs 84,000 dollars. He expects 140 billable days a year. His minimum day rate is 84,000 divided by 140, or 600 dollars, which is 75 dollars an hour over an eight hour day. The salary calculator on this site can help.

Step 2: break the project into phases

Typical phases include discovery and stakeholder interviews, user research, analysis and personas or journey maps, information architecture, wireframes, high-fidelity design, prototyping, usability testing, iteration and developer handoff. Estimate time for each, including meetings and feedback.

Worked example: an app onboarding redesign

Leo estimates 2 days for discovery, 3 days for research and analysis, 4 days for wireframes and prototypes, 2 days for testing and 2 days for final design and handoff, totalling 13 days. At 600 dollars a day, that is 7,800 dollars. He adds 10% for project management, or 780 dollars, and quotes 8,580 dollars.

Step 3: present options

Offer two or three options, such as a lean version without formal research, a standard version with five usability tests and a full version with a design system starter. Options help clients choose based on budget while understanding trade-offs.

Step 4: set revision limits

Include a set number of revision rounds for each phase, such as two rounds of wireframe feedback. Explain how extra rounds will be charged.

Value-based pricing in practice

Value-based pricing starts with a conversation about outcomes. If an online shop loses many customers at checkout, and better design could recover even a small share of them, the value of your work may be far greater than your hours. Ask clients about their goals, current metrics and what success would mean for their business. You might then price a project at a level that reflects that value while still being a clear win for the client. This approach requires confidence, trust and reliable measurement, so many designers combine it with a base fee or use it only for selected clients.

Pricing research and testing separately

Research and usability testing are sometimes the first items clients want to cut, yet they often prevent expensive mistakes. Pricing them as separate, clearly explained line items helps clients see their purpose. Include participant recruitment, incentives, session time, analysis and a findings report. If clients decline research, note the risks in your proposal so expectations are clear.

Retainers for product teams

Some startups and product teams need ongoing design help rather than a one-off project. A retainer gives them a set number of days or hours each month, such as six days for design reviews, new feature flows and testing. Retainers provide predictable income for you and predictable costs for them. Define what happens to unused time and how urgent requests are handled.

Design systems and handoff

Creating reusable components, style guides and documentation takes significant time but saves clients money later. Price design system work explicitly rather than hiding it inside screen design. Include developer handoff support, such as answering questions during build, as a defined number of hours.

Common pricing mistakes

Designers often underestimate meetings, feedback rounds and handoff, forget tool and testing costs, accept unlimited revisions or quote a single number without explaining scope. Some never raise rates despite stronger portfolios. Track actual time on each project and compare it with your estimates to improve future quotes.

Payment terms

Ask for a deposit, often 30 to 50%, before starting, with remaining payments tied to phase milestones. Set clear payment deadlines and include a kill fee if a project is cancelled midway.

Researching market rates

Before setting prices, research what UX designers with similar experience charge in your country and in the markets where your clients are based. Freelance marketplaces, design community surveys, job adverts for contract roles and conversations with other designers can give useful ranges. Official labour statistics on digital designers can also show typical salaries, which help you compare employed and freelance income. Remember that freelance rates need to be higher than equivalent salaried hourly pay because you cover your own equipment, software, holidays, sick days, pensions and quiet periods between projects.

Adjusting for client type

A local charity, an early-stage startup and a large financial company may all need UX work, but their budgets, expectations and risks differ greatly. Large organisations often require more meetings, stakeholder reviews, accessibility checks and documentation, which take extra time. Startups may want fast, lean work and may offer equity or deferred payment, which carries risk. Price according to the real effort and the value delivered, and be careful about accepting promises of future payment instead of cash.

Accessibility and compliance work

Many clients now need designs that meet accessibility standards so that people using screen readers, keyboard navigation or larger text can use their products. Accessibility reviews, colour contrast checks and inclusive design work add value and time. Price them explicitly and explain how they reduce legal and reputational risk while improving the experience for all users.

Raising your rates over time

As you build case studies that show measurable improvements, such as increased sign-ups, faster task completion or reduced support requests, you can justify higher rates. Raise prices for new clients first, give existing clients notice and consider moving from hourly billing to project or value-based pricing as your confidence grows.

Writing a clear proposal

A good proposal summarises the problem, the goals, your recommended approach, phases, deliverables, timeline, price, payment schedule, revision limits and what is out of scope. Keeping it concise and visual helps busy decision makers say yes quickly.

Tracking time to improve estimates

Even if you charge fixed fees, track how long each phase actually takes. After several projects, you will know whether discovery usually takes two days or four, how many feedback rounds clients typically request and how long handoff support lasts. This data makes future quotes more accurate and protects your effective hourly rate. If a phase regularly runs over, either raise the price for that phase, tighten scope or improve your process. Sharing this kind of evidence with clients can also help explain why certain phases cost what they do, building trust in your pricing.

Handling budget objections

When a client says your quote is too high, ask what budget they have in mind, then suggest reducing scope rather than lowering your rate. For example, you could test with three users instead of six, or design the main flow first and leave secondary screens for a later phase. This keeps your pricing consistent while still helping the client move forward.

Reader questions

Questions about pricing freelance work? Send them through the Ask page on this site.

Disclaimer

This article is for general information only. No income is guaranteed.

💬 Join the discussion on this article →

More in News · Trending News · Browse local deals