What enterprise UX agencies charge: how engagements are priced
An agency’s hourly rate tells you little about what a project will cost. The total depends on three things: how the engagement is priced, which phases it includes, and who works on it. This page explains each one, so you can compare proposals from agencies in five of our rankings on equal terms. Every agency’s hourly range and minimum engagement is listed in the table below.
Five ways agencies price enterprise work
Fixed price per phase. The agency commits to a defined output, such as a research report or a set of designed flows, for an agreed fee. It suits work that can be specified in advance. The agency carries the risk of underestimating, and its price includes a margin for that risk.
Time and materials. You pay for hours worked, usually against a monthly estimate. It suits work where the problem is still being defined. The risk moves to you, so it only works when someone on your side reviews progress and scope every week.
Phased commitment. A short, fixed-price first phase, followed by a separate decision on the rest. It’s the most common structure in enterprise work because it lets both sides learn before committing the larger budget.
Retainer. A reserved number of days each month, usually with the same designers. It suits products that ship continuously. It suits one-off projects poorly, because it buys time rather than a defined result.
Embedded designers. The agency places designers inside your team, working to your processes and priorities. You get extra capacity but not design direction, so it works best when you already have a design lead.
Where the budget goes, phase by phase
A full engagement usually moves through the phases below. Proposals differ most in which ones they include and how deeply, so check each against what you actually need.
Discovery and research. Interviews, observation and analysis of how people currently do the work. It produces the evidence every later decision depends on. Cutting it saves money only until the first design is built for the wrong workflow.
Structure and flows. Information architecture, navigation and the main task flows, usually as wireframes. This is where the product’s logic is fixed, and changes here are cheap compared to changes after visual design.
Interface design. High-fidelity screens, including the states people rarely see in a portfolio: empty, loading, error and permission-restricted views. Ask how many states the proposal covers, not just how many screens.
Usability testing. Sessions with real users on prototypes before build. Some proposals include it, some add it as an option, and some leave it out without saying so.
Design system. Reusable components with documented rules. It costs more upfront and pays back when several teams build into the same product.
Handoff and build support. Specifications, component documentation and a designer available to answer engineering questions during development. Without it, engineers fill the gaps themselves, and the shipped product drifts from the design.
Post-launch review. Checking how the released product performs against the original goals. It’s the phase most often cut and the one that shows whether the rest worked.
Who you are paying for
Most agencies quote a blended rate: one hourly figure averaged across everyone on the project. Two proposals with the same blended rate can buy very different teams. A typical enterprise team may include a design lead, a researcher, one or more interface designers, a content designer, an accessibility specialist and a project manager.
Ask for the team as named roles with a percentage of time for each. A design lead at a small share of the project and a design lead running it day to day are different engagements, even at the same price.
How to write a brief that gets comparable quotes
Quotes vary most when the brief leaves agencies to guess. A brief that produces comparable numbers covers:
- Users: who uses the product and how many distinct roles there are.
- Scope: which parts of the product are in scope and which are not.
- Existing assets: research, analytics, a design system or brand guidelines the agency can build on.
- Constraints: technical limits, regulations or accessibility standards the product must meet.
- Timing: fixed dates, and the reason behind each one.
- Decision-making: who approves work on your side and how quickly.
Send the same brief to every agency. If one asks questions the others didn’t, share the answer with all of them.
Reading a quote: what to check
- A line for research, with the number of users involved. “Discovery” alone can mean anything from stakeholder workshops to weeks of fieldwork.
- Named roles and time, not just “a senior team.”
- What engineers receive at the end, described as documents and components, not just “design files.”
- The payment schedule. Payments tied to milestones give you natural points to review or stop.
- Assumptions. Good proposals state what they assumed about your systems, data and availability. Missing assumptions usually return later as change requests.
Costs outside the agency’s invoice
The agency fee is only part of the cost of a UX project. Budget for these as well:
- Your team’s time. Subject-matter experts, stakeholders and approvers will spend time in workshops and reviews.
- User recruitment and incentives, if the agency does not include them.
- Tools and licences for design, prototyping or testing software your team will keep using.
- An independent accessibility audit, if customers or regulators require one.
- Engineering. Building the design usually costs more than designing it, and the quality of the handoff affects how much more.