# UX design project cost

The most common reason UX design projects go over budget is not that agencies charge more than expected — it is that the project scope was different from what everyone thought it was at the start. Understanding what drives UX design costs is mostly about learning to scope clearly before you ask for a price.

## What you're paying for

UX design agency engagements typically draw on some combination of four types of work. Each has different cost implications.

**Research.** User interviews, usability testing, surveys, diary studies, contextual inquiry. Research costs are driven primarily by the number of participants, the access required to recruit them (specialist users are harder to recruit), and whether the agency conducts it remotely or in person. A thorough research phase for a complex product may cost as much as the initial design phase that follows it.

**UX and interaction design.** Information architecture, user flows, wireframes, prototypes, interaction specifications. This is the work most people mean when they say "UX design." The cost here is driven by the number of distinct screens, the complexity of the flows between them, the number of user roles, and how many rounds of iteration the project budget includes.

**Visual design.** Visual system, component library, high-fidelity screens. Some agencies treat this as a separate phase; others run it in parallel with interaction design. Projects that include visual design cost more than wireframe-only projects, and projects that include a full design system component library cost significantly more than those that don't.

**Frontend build or design-to-development handoff.** Some UX agencies also write production code (or prototype code). This is not universal — most UX agencies are design-only — but where it is offered, it typically adds the largest cost increment to any engagement.

## What drives the price up or down

Within those four categories, cost is shaped by several factors.

**Scope.** The single most important driver. The number of screens, flows, user roles, and states in a product determines how much time the work takes. Ambiguity about scope at the start of a project is the most common reason a fixed-price project goes over budget or a time-and-materials project runs longer than estimated.

**How well-understood the problem is.** A product where the users, their workflows, and the constraints are well-understood costs less to design than one where those things need to be discovered first. If you are starting with significant uncertainty, budget for research.

**Number of stakeholder reviews.** Every round of stakeholder review and incorporation of feedback takes time. Projects with many internal stakeholders, long approval chains, or frequent direction changes cost more than projects with a focused decision-making structure.

**Timeline.** Faster timelines cost more if they require a larger team or compressed working patterns. Extending a project timeline without changing scope does not necessarily save money — agencies generally price by the work, not the calendar.

**Agency size and location.** Rates vary significantly by agency size, reputation, and geography. Boutique agencies often charge less than large studios, though this varies by specialism. Agencies based in lower-cost locations may charge less while doing comparable-quality work. Neither is a reliable quality signal on its own.

## How to get comparable proposals

If you send the same brief to multiple agencies and ask for a price, you will receive proposals with different scope assumptions. One may include research; another may not. One may include a design system; another may deliver isolated screens. The lowest total price may be the most limited scope, not the best value.

To get genuinely comparable proposals:

**Write a scope document, not just a brief.** A brief describes your problem. A scope document describes what you expect the agency to deliver — specifically, the outputs you need. If you need a component library, say so. If you need usability testing, say so. If you need only wireframes, say that too.

**Ask each agency to price against the same list.** If a proposed scope includes something you don't need, ask them to remove it and reprice. If their proposal omits something you do need, ask them to add it.

**Ask for a breakdown by phase.** A phased proposal lets you understand where the cost sits. If research takes 40% of the budget, you can make an informed decision about whether you need a full research phase or a lighter version.

## Fixed price versus time and materials

Most UX design work is priced either as a fixed-price project (defined scope, fixed total cost) or as time and materials (hourly or daily rates, billed against actual time spent).

Fixed price gives you budget certainty but requires well-defined scope. If the scope changes — because you learned something in research, because a stakeholder changed direction, because a technical constraint emerged — you will typically negotiate a change order.

Time and materials gives you flexibility but requires discipline about how time is used. If your team is likely to change direction frequently, ask for more stakeholder reviews than budgeted, or introduce scope without formal process, a time-and-materials engagement can exceed its estimate significantly.

There is no universally better model. The right choice depends on how well you understand the scope and how stable your internal decision-making is.

## What to verify before accepting a proposal

Before accepting any proposal, check the following:

**Team composition.** Who specifically is delivering the work? A principal-level designer supported by a junior team is a different value than the same price for a senior team throughout.

**Revision rounds.** How many rounds of revisions are included? What is out of scope?

**Deliverable format.** What file formats will you receive? Figma files, exported assets, a component library in a specific format — this affects how useful the work is once the engagement ends.

**Handoff support.** Is developer handoff included? If so, what does that look like in practice?

**Intellectual property.** Who owns the work product once the engagement is complete?

A proposal that is clear on all of those points costs the same as one that isn't — but it protects you from surprises.
