UX research budget benchmarks by ARR and team size

UX research budgets at most product companies are either inherited from a spreadsheet someone built three years ago or set by guesswork. Most teams spend less than they need for the research program to actually change decisions, and few have a principled benchmark to anchor the conversation during annual planning.

The benchmarks below are drawn from industry surveys, research operations community data, and observed patterns across product organizations at different growth stages. They are designed to give you a defensible starting point, not a precise figure.

Why ARR-based benchmarks matter

Most SaaS and digital product companies use ARR as the primary scaling mechanism for headcount and operational budgets. Pegging research spend to ARR gives you a number that scales with your ability to invest and your product’s complexity, and it anchors the conversation with finance in the same language they use for every other function.

The broad benchmark: product-led companies typically invest between 0.5% and 2% of ARR on user research, encompassing recruitment, incentives, tools, and the proportional cost of researcher time. The specific number within that range depends on your product type, your B2B or B2C mix, and how heavily research is embedded in your product development process.

Benchmarks by ARR stage

The table below shows typical annual research operations budgets (excluding researcher salaries) at each ARR stage. These figures reflect out-of-pocket costs for running research, not headcount.

ARR stage	Typical research ops budget	Studies per year	Researcher headcount
Pre-revenue / Seed	$5,000 to $20,000	4 to 8	0 (PM-led)
$1M to $5M ARR	$15,000 to $45,000	8 to 15	0 to 0.5 FTE
$5M to $20M ARR	$40,000 to $100,000	12 to 25	1 FTE
$20M to $50M ARR	$80,000 to $200,000	20 to 40	1 to 3 FTE
$50M to $150M ARR	$150,000 to $400,000	35 to 60	3 to 6 FTE
$150M+ ARR	$300,000 to $1M+	50+	6+ FTE

The budget column covers participant recruitment and incentives, platform subscriptions, analysis tools, and incidental costs like participant gifts. It does not include researcher salary, which typically ranges from $95,000 to $160,000 per year for a mid-senior UX researcher in the US.

Benchmarks by team size

ARR is one axis. Research team headcount is the other. A team of one researcher operates very differently from a team of five, and the operational budget per researcher changes at each stage.

Solo researcher (1 FTE)

A solo researcher at a product company of 30 to 100 people typically manages 15 to 25 studies per year across qualitative and quantitative methods. A realistic annual operations budget for this role is $30,000 to $75,000, structured roughly as follows.

• Participant recruitment and incentives: $18,000 to $45,000
• Recruitment platform: $3,000 to $8,000
• Research repository (Dovetail or similar): $1,500 to $4,000
• Unmoderated testing tool: $1,500 to $3,600
• Survey tool: $500 to $2,400
• Transcription and analysis tools: $600 to $2,000

Teams using AI-moderated interviews for lower-priority studies can compress recruitment and session costs significantly, often running secondary research tracks for $50 to $150 per study instead of $300 to $800 for moderated sessions.

Research team of 2 to 4 FTE

A team of 2 to 4 researchers embedded in a product organization of 100 to 400 people typically runs 30 to 60 studies per year across multiple product lines or squads. Operational budgets in this range tend to sit between $80,000 and $200,000 annually.

This is the stage where recruitment costs scale fastest because teams are running more concurrent projects with different participant profiles. It is also where a managed panel with flexible per-study access becomes more economical than individual outreach or rigid subscription tiers.

Research team of 5 or more FTE

Research organizations of 5 or more full-time researchers typically operate at companies above $50M ARR with mature product development processes. Annual operational budgets at this scale typically run $200,000 to $600,000, though enterprise organizations with global research programs can spend more.

At this scale, the budget conversation shifts from whether to invest to how to allocate across method types, product areas, and geographic markets.

What drives costs up or down

The ARR and headcount benchmarks above are starting points. Several factors push costs higher or lower in practice.

B2B versus B2C professional profiles is the single biggest cost driver. A research program focused on enterprise software buyers with director-level and above participants will cost 3x to 5x more per study than a consumer research program, because professional incentives are higher and recruitment is more complex. See B2B user research: complete playbook for a breakdown of the unique cost dynamics in B2B research.

Study frequency and cadence matters more than individual study costs. Teams running continuous research (weekly or bi-weekly sessions) build a more consistent budget than teams running large quarterly studies, but continuous research requires a platform that can recruit fast and consistently. For the tradeoff between in-house panels and external recruitment platforms, see in-house research operations vs outsourcing: cost comparison.

Method mix changes the cost profile substantially. Moderated interviews are the most expensive per session, unmoderated tests are the most scalable, and surveys are the cheapest per data point but require the most participants to be statistically meaningful. A research program that skews toward AI-moderated and unmoderated methods can run significantly more studies on the same budget.

Recruitment speed requirements affect cost. Recruiting 8 B2B participants in 5 business days typically costs more than recruiting the same profile over 3 weeks, because faster recruitment requires a larger active panel with automated matching. Platforms with large verified panels handle this more efficiently than those relying on organic outreach.

How to calculate your target budget

If you are building a research budget from scratch, start with study count, not with a percentage.

1. List the major product initiatives for the next 12 months and identify which ones require research input.
2. Map each initiative to a method type: discovery interview, concept test, usability study, survey, or diary study.
3. Estimate participant count and sessions per study based on method.
4. Multiply by your expected cost per participant given your audience profile (B2B vs B2C, seniority, specialization).
5. Add 20 to 25% for ad hoc and reactive research that will come up mid-year.
6. Add tool subscriptions and platform costs on top.

This bottom-up number is usually more defensible in budget conversations than a percentage, because it connects research investment directly to product decisions rather than to an abstract benchmark.

For the full cost breakdown by study type and method, see user research budget planning: costs, allocation and ROI.

Making the case to stakeholders

The hardest part of the research budget conversation is not calculating the number. It is convincing stakeholders that the investment has a measurable return.

The most effective framing is cost of wrong decisions, not value of research. Most product teams can identify one decision in the past year that required significant rework because user assumptions were wrong. Estimating the engineering, design, and opportunity cost of that rework and comparing it to the cost of one well-designed discovery study makes the ROI case concrete and credible.

Nielsen Norman Group research has consistently shown that usability improvements driven by research reduce support costs, increase conversion, and reduce rework. For a methodology-based approach to quantifying the return on research, see research ROI: how to measure and prove user research value.

External resources like the Nielsen Norman Group’s research on UX ROI and the Research Operations Community’s practitioner surveys provide industry-level data that supports internal budget proposals.

Scaling research without scaling headcount proportionally

One constraint product teams consistently underestimate is that research capacity does not scale linearly with budget. Hiring a second researcher doubles capacity on paper, but coordination overhead, documentation requirements, and stakeholder management absorb a meaningful portion of that capacity.

The teams that get the most out of a fixed budget tend to invest in three areas before adding headcount: a recruitment platform that removes the coordination burden from the researcher, an AI-moderated interview option for lower-stakes research that would otherwise not happen at all, and a research repository that prevents insights from being lost between quarters.

CleverX covers all three. The platform provides access to an 8 million-plus verified panel across 150 countries, AI Interview Agents for autonomous moderated sessions, and integrated session recording and analysis tools, all on a credit-based model with no annual commitment. For teams at the $5M to $50M ARR stage in particular, this means a solo researcher can run a research program that would otherwise require two or three people.

For guidance on building the operational infrastructure that makes a research program scale, see how to build a research operations practice from scratch.

Frequently asked questions

What percentage of ARR should product teams spend on UX research?

Most product-led companies spend between 0.5% and 2% of ARR on user research, including tools, recruitment, incentives, and researcher time. Early-stage teams under $5M ARR typically invest $10,000 to $40,000 per year. Series B and beyond teams with $20M+ ARR commonly budget $100,000 to $500,000 annually across a dedicated research function.

How much should a startup with no revenue spend on UX research?

Pre-revenue and seed-stage startups should plan for $5,000 to $20,000 per year in out-of-pocket research costs, primarily covering participant incentives and a lightweight platform subscription. Many early-stage teams offset costs by running no-incentive founder interviews, using free tools like Google Forms, and leaning on panels with pay-per-session pricing to avoid annual contracts.

What is a realistic research budget for a one-person UX research team?

A solo researcher at a mid-size company typically operates with $25,000 to $75,000 in annual research ops budget, separate from their salary. This covers participant incentives for 8 to 12 studies per year, a recruitment platform, a research repository, and one or two unmoderated testing tool subscriptions. Teams that use AI-moderated interviews for lower-priority studies stretch this budget to cover 20 or more studies per year.

How does B2B vs B2C affect UX research budget requirements?

B2B research costs significantly more per study because professional participants command higher incentives ($75 to $300 per hour versus $25 to $75 for consumers), recruitment is more complex, and study counts per year are lower but each study is higher stakes. A B2B product team running 10 studies per year typically spends 2x to 4x more per study than a B2C team running the same number.

What drives the biggest cost in a UX research budget?

Participant incentives and recruitment fees are the largest variable cost, typically accounting for 40% to 65% of the total research ops budget. Tool subscriptions are the next largest category at 20% to 35%. Researcher salary and benefits are not typically counted in the operational budget but represent the single largest investment when factoring total cost of a research function.

When should a product team hire a dedicated UX researcher versus using a platform?

Most product teams should consider a dedicated researcher once they are running more than 6 to 8 studies per year and have a product team of 5 or more. Before that threshold, a research platform like CleverX lets PMs and designers run studies independently, keeping costs variable and aligned to actual research volume rather than committed headcount.