Key insights

• 29% of research teams work with under $25,000 a year. Large enterprise budgets exist, but they’re not the norm.
• Headcount, not tools, is the biggest cost. Staffing takes 32% of the average research budget, recruitment and incentives 20%, tools and platforms 19%.
• The UX budget floor beats a percentage of ARR. A team testing monthly learns more than one spending a bigger budget on two studies a year.
• Unmoderated testing can cost less per year than a handful of moderated studies. A full year of continuous testing runs $600 to $3,000, about the same as four single moderated sessions at $300 to $800 each.
• Mature UX doesn’t mean testing everything. Spend where uncertainty and risk justify the research, and let low-risk, reversible work ship first.

Somewhere in the next quarter’s planning doc, there’s a line item for research. Maybe it’s a real number. Maybe it’s a placeholder someone will fight for in a meeting. Maybe it doesn’t exist yet, and you’re the person who has to invent it.

The trouble is that nobody publishes the numbers. Ask what a UX budget should look like and you get percentages of R&D from a decade ago, or agency quotes that start at $40,000. Neither helps when you’re a product lead with a redesign shipping in six weeks and no research line at all.

So here are the actual numbers: what teams spend, what each research method costs, what the enterprise platforms charge, and the smallest budget you can still do real UX testing with. That last one matters most, because it’s lower than almost everyone assumes. Two research leaders who scaled real teams, one at the online lottery platform LOTTO24, one running Research and Analytics inside DKB, add the part a spreadsheet alone won’t tell you: how to size the team the budget buys, and how to structure the ask so it survives a leadership meeting.

What teams actually spend on UX research

Most research budgets are small. In the 2025 Research Budget Report from User Interviews, which surveyed 180 people who own or have visibility into a research budget, 29% of teams work with under $25,000 a year. That’s the single largest group.

Here’s the full distribution:

Annual research budget	Share of teams
Under $25,000	29%
$25,000 to $100,000	20%
$100,000 to $500,000	20%
$500,000+	17%

The direction of travel is flat rather than falling. 41% of teams held their budget steady year over year, 35% grew it, and 17% took a cut. So the picture isn’t collapse. It’s stagnation, with teams expected to produce more insight from the same number.

Where the money goes matters as much as how much there is:

• Headcount and staffing: 32%. The biggest slice by far, which means budget conversations are usually salary conversations in disguise.
• Participant recruitment and incentives: 20%. The cost of getting real people in front of your product, and the first thing to get cut when the number tightens.
• Tools and platforms: 19%. Under a fifth of the total, split across the two to five research tools that 58% of teams pay for.

That 19% is worth sitting with. 22.5% of teams named tools as the hardest expense to justify to leadership, because the value only becomes obvious after purchase and implementation. If you’re trying to get a research platform approved, you’re pitching into the least defensible line on the sheet, competing for the smallest slice of it.

One more finding from that report, and it’s the one to bring to your budget meeting: no team that took a significant budget cut reached the highest UX maturity level. Not a low percentage. Zero.

The UX budget floor: the smallest number that still works

The UX budget floor is the smallest annual research spend at which a team can still test continuously, rather than once or twice a year. In 2026, that floor sits under $3,000 a year for a small product team running unmoderated user testing. That’s the number below which research becomes an occasional event, and above which it becomes a habit. A single person testing occasionally can start even lower, around $600 a year, but this section is about a team running tests every week, not just one person checking in monthly, and that needs the extra seats and setups that come with it.

The distinction matters more than the amount. A team with $15,000 that spends it on two big studies in March and October learns twice a year. A team running about three test setups a month for $2,988 a year learns thirty-six times a year, on whatever shipped most recently. The second team catches more, earlier, when changing things is still cheap.

This is why the floor is a more useful planning concept than a percentage of ARR. The benchmarks are real (product-led companies typically invest 0.5% to 2% of ARR in user research), but a percentage tells you what’s normal, not what’s sufficient. The floor tells you whether your budget buys you a cadence or just a moment.

Here’s what the floor looks like by company stage, based on CleverX’s benchmark data:

Stage	Typical annual research budget	Studies per year	Dedicated researchers
Pre-revenue / seed	$5,000 to $20,000	4 to 8	0
$1M to $5M ARR	$15,000 to $45,000	8 to 15	0 to 0.5
$5M to $20M ARR	$40,000 to $100,000	12 to 25	1
$20M to $50M ARR	$80,000 to $200,000	20 to 40	1 to 3
$50M to $150M ARR	$150,000 to $400,000	35 to 60	3 to 6
$150M+ ARR	$300,000 to $1M+	50+	6+

Notice what happens at the top of that table. A seed-stage company runs four to eight studies a year with zero researchers. Every one of those studies has to be something a product person can run without a research background. Which is fine, because most of them are.

Budget the question before the method

A surprisingly expensive habit is funding research by method instead of by question. “We need a user test” sounds like a plan, but a user test is a method, not a problem statement, and it’s easy to fund the wrong one.

At LOTTO24, Team Lead UX Elodie Lombard describes deliberately moving stakeholders away from requesting a specific method and toward naming the gap instead: "What don’t we know, and what evidence would actually close that gap."

Research then decides whether that means a user test, a focus group, a diary study, an interview, or something else entirely. She walks through the shift on UX Heroes episode 99.

Don’t fund methods. Fund unanswered questions

A broad discovery study is overkill for “can people find this button.” Five task-based sessions won’t tell you why customers quietly churn after a month.

Elodie Lombard calls the work that happens before any method gets picked “Messy Discovery”: the unglamorous stretch of defining the problem properly, understanding what customers actually need, and checking whether the original idea is even the right one to build. It rarely fits neatly into a delivery plan, and it’s the first thing that disappears when every UX hour is already booked for the next feature. The budget line can still say “UX.” What it’s actually funding, at that point, is execution.

Size the team the budget actually buys

A budget number doesn’t mean much without a team shape attached to it.

When LOTTO24 expanded from its core lottery brokerage into several new in-house products, Elodies’s team had to define a minimum viable team for launching each one. On the product side, that came out to one product manager, one UX designer, and two engineers. Every user-facing team got UX capacity as part of that core group. Teams with very little user-facing surface got half a designer instead of a full one.

Budget UX headcount to how much user-facing decision-making a team actually does, not a flat allocation across every team.

The catch showed up fast. A team with exactly one UX hire needs that person to run a quick user test, develop the concept, and ship the UI, because there’s nobody else to hand any of it to. Elodie describes this as ending up hunting for “unicorns,” designers expected to be strong across the entire process at once, which isn’t really a hiring strategy so much as what happens when one headcount has to cover three jobs. Underfunding a capability doesn’t remove the work. It concentrates it into one increasingly unrealistic role.

Give core products a baseline, and let one-off asks bring their own budget

DKB’s Research and Analytics lead, Konrad Maruschewski, runs into a related structuring problem from the leadership side rather than the hiring side.

His team, internally known as “Curiosity” after he retired the original “Research as a Service” framing, splits its funding into two buckets.

• Core products get a standing baseline budget: continuous research and measurement that doesn’t need re-approval every time a team wants five more sessions.
• Anything outside that, an unusual ask, a one-off accessibility study, a hard-to-recruit audience, needs the requesting team to bring budget of its own. Maruschewski goes into the structure on UX Heroes episode 101.

A baseline budget protects the research cadence around the product that matters most. A per-request budget stops every five-user study from turning into a fresh negotiation.

What UX research actually costs, method by method

The cost gap between research methods is enormous, and it has almost nothing to do with insight quality. It’s mostly a function of whether a human has to be in the room.

Method	Typical cost per study
AI-moderated session	$50 to $150
Unmoderated user testing (annual line item)	$600 to $3,000
Moderated session	$300 to $800
Consumer participant incentive	$25 to $75 per hour
B2B professional participant incentive	$75 to $300 per hour

The line to focus on is the second one. Unmoderated user testing runs $600 to $3,000 as a full annual line item, not per study. That’s the entire year of continuous testing for less than the cost of four moderated sessions with B2B participants.

Unmoderated user testing is the format where someone completes a task on your product on their own, records their screen, and talks out loud while doing it. You watch it back later. Nobody schedules a call, nobody moderates, and nobody has to be awake at the same time as anyone else.

It’s the cheapest method per insight, and for most product questions (“can people find this, do they understand what it does, where do they get stuck”) it’s also the right one.

If you want the fuller picture on formats and their trade-offs, our guide to free usability testing tools covers what you can get done at zero cost first.

How to run real UX testing on under $3,000 a year

You can run continuous user testing, with real people, for a fraction of an enterprise contract. Here’s the actual arithmetic, using Userbrain’s current pricing.

There’s no permanent free plan, but every plan starts with the same trial: 30 days, 2 panel testers, plus 5 sessions with your own users, no credit card required. After that:

Plan	Price	Panel testers	Test setups	Seats	Best for
Starter	$49/month	3/month	1/month	2	A solo, steady monthly testing habit
Plus	$249/month	10/month	3/month	4	A small team testing continuously
Flex	$1,100/year	30 to 300/year, plus additional testers on demand	Unlimited	Unlimited	Larger teams, higher volume

Prices as of September 2026, in USD. Starter and Plus are billed monthly; Flex is billed annually. Check the pricing page for current plans.

Plus is the one that matches the budget floor described above: three test setups a month is enough to run a real cadence, and four seats mean the whole core team from the LOTTO24 example earlier, product manager, designer, and two engineers, can watch sessions and review findings together. Starter works if it’s genuinely one person running a small, steady testing habit; it caps out at one test setup a month, which isn’t enough for a team cadence.

A few things make that number achievable rather than theoretical:

• Participant costs are already in the price. The 20% of budget that usually goes to recruitment and incentives is bundled in. You pick demographics, devices, and screening criteria from a pool of 180,000+ qualified testers across 17 countries, and the tester payment is included.
• You don’t need a researcher on staff to get findings. AI insights surface the patterns across sessions, generate time-stamped clips of the moments that matter, and produce a shareable report automatically. The 32% of budget that normally goes to headcount isn’t a prerequisite for getting started.
• Nothing waits on scheduling. 85.42% of tests complete within four hours and 97.43% within 24 hours, so a test you set up on Tuesday morning is something you’re watching Tuesday afternoon.
• You can invite your own users on top of that. Flex bundles 100 invite-your-own-tester sessions a year at no extra cost per session; check the pricing page for the exact allowance on Starter and Plus.

For more tactics on stretching a small budget, our post on affordable ways to improve UX on a limited budget goes deeper on the process side.

How to defend a small UX budget

The reason tools are the hardest expense to justify is that most people pitch them as tools. Reframe the ask around avoided cost and the conversation changes.

• Price the redesign you’re trying to avoid. A homepage or checkout rebuild costs engineering weeks. A month of Plus, enough for a real round of testing before the sprint commitment, costs $249. Say both numbers out loud in the same sentence.
• Tie the number to a decision, not a period. “$2,988 a year for research” invites a debate about whether research is worth it. “$249 a month so we stop guessing on checkout” invites a decision about checkout.
• Use the maturity finding. Zero teams that took significant research cuts reached the highest UX maturity level. That’s a defensible line when someone proposes trimming the research budget to fund something else.
• Show a clip, not a slide. The fastest way to protect a research budget is to put a 40-second recording of a real person failing to complete a task in front of the people who control it. Nobody argues with the video.
• Start with the people already curious, not the whole company. Maruschewski describes real resistance when DKB began testing products the bank had shipped for years: teams worried a test would only prove their existing work was bad. Instead of asking for a mandate, he found two or three stakeholders open to experimenting and used small “lighthouse” projects to show what research actually changes, before asking for anything bigger.
• Price the sprint you’d otherwise spend guessing. Maruschewski’s team builds click dummies and tests them within hours, before any engineering time gets committed. A prototype you can change this afternoon is cheap to be wrong about. A feature that’s already through two or three sprints is not. As he puts it: “It’s better to fail with us in a UX test than out there with real customers.”

Our post on the ROI of user testing has the longer version of this argument if you need to build a case in writing.

What UX budgets look like in 2027

The near-term outlook is better than the last two years suggested. Forrester’s 2027 budget planning research found that 55% of customer experience leaders expect spending growth of 5% or more in 2027, up from 39% a year earlier. Across the wider picture, 82% of technology decision-makers and 91% of marketers expect budget increases.

Two things about that recovery are worth planning for.

First, the money is arriving with strings attached. IDC projects that 60% of Global 2000 CMOs will be measured on customer-value outcomes by 2027, which means UX budgets get tied to retention and revenue metrics rather than usability scores. Research that can show its work against a business number will be easier to fund than research that reports findings.

Second, headcount isn’t coming back the way budget is. Nielsen Norman Group’s State of UX 2026 describes team sizes stabilising rather than expanding, with responsibilities compressing across fewer roles. The practical read: more product people will be running their own research in 2027, not fewer. Budget that assumes a specialist will do it is budget planned for a team structure that’s going away.

Which is an argument for setting your floor now rather than waiting for the increase. A testing habit that already exists is much easier to fund than one that has to be proposed.

The number that matters is the cadence

The UX budget question usually gets asked as “how much.” It’s the wrong question. A team with a large budget and an annual research cycle learns slowly. A team at the floor with a monthly cadence learns constantly, on the thing they shipped last week, while it’s still cheap to change.

29% of research teams work with under $25,000 a year. That’s not a reason to test less. It’s a reason to pick the format that gets a real person, thinking out loud, in front of the thing you built, on a plan that starts at $49 a month.

Set the floor. Then never go below it.

Userbrain lets you test with real users on any budget, starting with a 30-day free trial. Set up a test in minutes, pick from 180,000+ testers, and let AI insights do the analysis while you get on with shipping. Start your free trial →