UX ROI, How to Price a Research Study Before You Run It

Which UX ROI statistics hold up when finance checks them?

Few UX ROI statistics survive a finance review, because most published figures describe design or usability averages, not what one UX research study will return.

Each figure carries an evidence grade, set by its sample, its method and whether it shows causation or only correlation. McKinsey's 2018 report The Business Value of Design tracked 300 publicly listed companies over five years and found 32 percentage points higher revenue growth for companies in the top quartile of the McKinsey Design Index than for industry peers. It measures design practice across whole companies, and it shows correlation.

Jakob Nielsen's 2008 NN/g article Usability ROI Declining, But Still Strong reported an average 83% improvement in the metrics measured after usability redesigns, lower than the firm's earlier survey. Published case studies are self-selected, so failed projects rarely enter the sample. Ronny Kohavi and colleagues' 2009 paper Online Experimentation at Microsoft gives a harsher figure from controlled experiments: roughly a third of the ideas tested improved the key metric they targeted. The authors note a selection effect, since teams send ideas to an experiment when they are less sure of them, and add that this bias is possibly smaller than most people think.

Grade a figure here before you quote it to finance.

Decision value is missing from all three for a structural reason: the counterfactual, the feature that was never built, leaves no metric behind, so analytics cannot show the loss a study prevented. Other ROI figures circulate with no traceable method, including a dollar-return claim attributed to Forrester and percentages in the thousands; ask for the sample, the method and the period, and drop any figure that has none.

No average prices the UX return on investment of your own decision. Our article on what skipping UX research costs a product team lists those costs, and the next section turns them into one number for one decision.

How do you price a study against the cost of being wrong?

To price UX ROI before a research study, multiply the chance of being wrong by the cost of being wrong; that expected opportunity loss caps what the study is worth.

1. Name the decision and its build stake, the build budget that rides on one assumption.
2. Estimate the cost of being wrong, the share of the build stake lost if the assumption fails, since some work survives a change of direction.
3. Estimate the chance of being wrong, the team's honest doubt, as a percentage, that the assumption is false.
4. Multiply the two to get the expected opportunity loss, what the team stands to lose on average by building without evidence.
5. Compare it with the study cost, and fund the study when its price sits well below that loss.

The method comes from decision analysis. Douglas Hubbard's book How to Measure Anything treats measurement as a reduction in uncertainty and pairs the chance of being wrong with the cost of being wrong as expected opportunity loss; the drop in that loss a measurement buys is the expected value of information. A real study removes part of the doubt, not all of it, so the expected opportunity loss is a ceiling on its value.

The quick test is the break-even doubt: the study cost divided by the cost of being wrong. If the team's honest doubt sits above it, fund the study; below it, build, or run a cheaper test. The dial uses the worked example's numbers from the next section.

Doubt is the input teams shade down. In the Microsoft data, about two in three tested ideas failed to improve their target metric, so a team that calls itself 95% sure needs evidence for that 95%. Before you scope a study, ask what evidence sits behind that confidence, because a study aimed at one assumption costs less than a broad one, which lowers the break-even doubt. To match a method to that one assumption, see UX research methods matched to the question they answer.

UX ROI worked example, one feature bet and its study

In this illustrative UX ROI example, a $35,000 study against a $210,000 cost of being wrong breaks even at about 17% doubt, and the team's 35% makes it worth funding.

These figures are illustrative, chosen only to make the arithmetic visible, and none comes from a client project. A field-service app plans to build automatic job scheduling for dispatchers next quarter, a build stake of $300,000. The team judges that 70% of that work would be lost if dispatchers reject automatic schedules, a cost of being wrong of $210,000, and puts its chance of being wrong at 35% because no dispatcher has been interviewed yet.

The proposed study runs 12 dispatcher interviews in 1 user group, 5 contextual inquiry visits and a concept test over 5 weeks for $35,000, an illustrative price inside our published $25,000–$60,000 range, not a quote; the price drivers of a UX research program show what moves a study within it. The contextual inquiry visits mean watching dispatchers at work, a step our process for supply chain products also names, where researchers shadow pickers and dispatchers across shifts.

The expected opportunity loss is 0.35 × $210,000 = $73,500. The break-even doubt is $35,000 ÷ $210,000 = 16.7%, about 17%, well below the team's 35%. The expected return at funding is at most ($73,500 − $35,000) ÷ $35,000 = 110%, a ceiling, because the study will not remove all doubt.

At the readout, the last step of the program, one of three outcomes lands. In the change outcome, dispatchers distrust fully automatic schedules and want suggested slots they approve; the team re-scopes and estimates that $150,000 of planned work is avoided or redirected, a realized return of ($150,000 − $35,000) ÷ $35,000 = 329%.

A study that confirms the plan is not wasted money. In the go outcome the assumption holds and realized decision value is near zero, yet funding was still right, because the study's expected value was positive when the money was approved; like insurance on the build, the study is judged by the risk it covered. In the stop outcome, the problem proves too rare to justify a build, so the whole $210,000 loss is avoided.

Whichever outcome lands, the readout includes a Jobs to be Done (JTBD) opportunity map that ranks the dispatcher jobs by importance and current satisfaction. To reuse the example, swap in your own inputs and keep all three outcomes on the page, so nobody reads the result as a forecast of one.

What goes on a one-page UX ROI case for leadership?

A one-page UX ROI business case needs five lines, decision, stake, doubt, study and rule, showing leadership the cost of being wrong and what each finding does to the plan.

The page is a funding document, not a case study. Executives and other stakeholders asked to invest in UX research can check every figure on it, because each one comes from your own plan.

1. Decision. What will be built, when, and who decides.
2. Stake. The build stake and the cost of being wrong, with the share of work you expect to survive a change.
3. Doubt. The chance of being wrong and the evidence behind it, or the absence of evidence.
4. Study. Method, participants, weeks and price.
5. Rule. The decision rule: which finding stops, changes or confirms the build, written before fieldwork.

The Rule line does the most work. A decision rule written before the first interview, such as "if fewer than X of 12 dispatchers accept automatic schedules, re-scope to suggested slots; if the problem shows up in fewer than Y of 5 visits, stop", makes the return measurable later and keeps the readout from being read to fit the plan. X and Y are the team's call. Keep the page to those lines and a sign-off, short enough for the executive suite to read in one sitting.

A Study line that reads "to be confirmed" invites a no. A fixed-scope proposal replaces the placeholder with a defined scope, so draft the other four lines first and bring them to whoever scopes the study.

How do you measure UX ROI after the study?

Measure UX ROI after a UX research study with a decision log recording, per finding, the decision changed, the avoided cost or target metric, the attribution share and measurement window.

Decision value is counted at the readout, when the team records the build money it redirected. Improvement value waits until the changed design ships and its measurement window closes, because a time lag separates a decision from the metric it moves. Pick the one or two metrics the decision should move, such as task success rate, time on task, support tickets, churn rate or Net Promoter Score (NPS), and take a baseline before the change. Base any pre-launch projection on the study's findings, competitor benchmarks or past projects, and label it as one.

Attribution share is the part of a metric change the study can claim, agreed before launch, because pricing, marketing and other releases move the same metric. In the Parents Connect product revamp, research into what parents need from a community came first and the forum was designed from there; the case study reports 45% more forum participation among parents. That result belongs to the whole revamp, research and design together, so a decision log would credit the research with the direction it set, not with the percentage.

The log records each finding against the decision it changed and the evidence that will show its return.

To report UX research ROI across several studies, total the decision log each quarter and keep decision value and improvement value on separate lines, so a strong launch does not hide a study that changed nothing. Open the log at your next readout and test each finding against the decision rule from your one-page business case.

When does a UX research study have a negative ROI?

A UX research study earns a negative UX ROI when its price exceeds the expected opportunity loss: a small build stake, a reversible change, low doubt or a known answer.

• A small build stake. When the cost of being wrong is close to the study cost, the break-even doubt nears 100%, so no honest doubt clears it.
• A change you can reverse on live traffic. A/B testing measures a variant's result on real users directly, so a wrong version costs a rollback, not a rebuild.
• Low doubt with evidence behind it. When an earlier study already tested the assumption, the honest doubt falls below the break-even doubt.
• An answer already in the research repository. Searching tagged findings costs hours, not a program, which is reuse value paying out.

Is the ROI of UX declining? Yes, in Jakob Nielsen's view. In his 2025 UX Tigers essay Declining ROI From UX Design Work, he argues that returns from UX design work have fallen since about 2020, because the low-hanging fruit of terrible usability has long since been picked. Read that as a reason to aim studies at uncertain, expensive decisions.

When price is the only problem, shrink the study before you skip it. A narrower study, such as the 8–10 user interviews we suggest for a startup, lowers the study cost and the break-even doubt with it, so run the sum again at the smaller price.

Who owns the UX ROI case, and when does outside help pay?

The decision's product owner builds the UX ROI business case, since only they know the build stake and doubt; a UX research partner pays when the study outgrows your team.

A researcher can run the arithmetic, but the stake comes from the build plan and the doubt from the people who wrote it, so the owner signs the business case. Outside help pays when the study, not the sum, is the hard part, and three of the five lines show it:

• The Doubt line rests on users nobody on the team can reach. If the study never hears from the people able to prove the assumption wrong, the chance of being wrong stays where it was; recruiting is its own step in our program, 3–6 days before fieldwork.
• The Study line combines methods your team cannot run together. Interviews, field visits and a concept test feeding one decision rule have to become one answer at the readout, and that synthesis needs someone who has run all three.
• The Rule line belongs to a sponsor who also wrote the plan. When the person setting X and Y wants the build, leadership discounts the readout, and a team that did not write the plan keeps the decision rule credible.

Our UX research program runs 4–8 weeks at $25,000–$60,000, with 10–15 interviews per user group, and ends in a 90-minute readout. If no decision is framed yet, a UX consulting engagement gives senior guidance in 2–3 weeks for $5,000–$15,000.

The same scheduling build can flip on doubt alone. At 35% doubt it justifies the $35,000 study; at 10% doubt the expected opportunity loss falls to 0.10 × $210,000 = $21,000, below the study price, so the team builds or runs a cheaper test. Price the next build on your roadmap the same way, and if its Study line still has no scope, bring the decision and the budget riding on it to a scoping call. Every project begins with a free consultation and a fixed-scope proposal.

FAQs