UX research when you do not have a big budget

There is a myth that UX research is expensive. People picture a lab, a one way mirror, dozens of participants and a thick report nobody reads. That version exists, and for most products it is overkill. The research that actually changes decisions is usually small, fast and cheap, and a founder with almost no budget can run a meaningful version of it.

The goal of research is not a report. The goal is to be less wrong about your users before you spend money building the wrong thing. Keep that in mind and the budget problem mostly disappears.

Five users will tell you most of what you need

The single most freeing fact in UX research is that you do not need many people. For finding usability problems, testing with five users typically surfaces the large majority of the serious issues. After that you see the same problems repeat.

This changes the economics completely. You are not recruiting hundreds of people. You are finding five who resemble your real users and watching them try to use your product. That is something almost any team can afford in time, if not money.

Watch people, do not just ask them

The cheapest and most valuable thing you can do is sit quietly while someone uses your product and tries to complete a real task. Not a demo. A task. Sign up. Make a booking. Find the price.

What people do and what people say they do are different things. If you only ask opinions, you get polite answers. If you watch, you see the hesitation, the wrong tap, the moment they give up. Those moments are the research.

A few rules keep these sessions honest:

• Give a task, then go quiet. Resist the urge to help or explain.
• Ask them to think aloud, so you hear the confusion as it happens.
• When they get stuck, ask what they expected to happen, not whether they like it.
• Watch where their eyes and their cursor go before they act.

You can run these over a video call, screen shared, in under thirty minutes each. Five of them in an afternoon will teach you more than weeks of internal debate.

Cheap methods that punch above their weight

Beyond watching users, a handful of lightweight techniques give a strong return for very little spend.

• Five second tests: show a screen for five seconds, then ask what the product does and what they would do next. Brutal and clarifying for landing pages.
• Card sorting on sticky notes: hand people your features or pages and ask them to group and name them. This fixes navigation before you build it.
• Hallway testing: grab a colleague from another team, or a friend who fits the audience, and watch them use a rough prototype. Rough is fine. Rough is often better, because people feel free to criticise.
• Reading support tickets and reviews: the cheapest research of all is already sitting in your inbox and your app store listing.

A clickable prototype tested with five people beats a polished build tested with none.

The mistakes that waste good research

Cheap research still gets wasted, usually in the same few ways.

The first is leading the witness. If you ask whether someone likes the new green button, they will say yes to be kind. Ask neutral questions about tasks and expectations, and let the discomfort show itself.

The second is testing too late. Research after launch is damage assessment. Research on a prototype, before code, is where it saves real money. The earlier and rougher, the cheaper the fix.

The third is doing the sessions and ignoring them. We have watched teams nod along to five painful sessions, then build exactly what they had planned. Research only counts if you let it change something. Write down the top three problems you saw and fix them before anything else.

A simple plan you can run this month

If you want a starting point, here is one we give to small teams. Pick one important task in your product. Write a short script that asks five people to complete it. Recruit five people who roughly match your audience, even informally. Watch each one, take notes on where they struggle, and meet for an hour afterward to agree the three biggest problems. Fix those, then repeat on the next task.

That loop costs almost nothing and compounds. Each round makes the product noticeably better and your assumptions noticeably more accurate. Good research is not about budget. It is about the discipline to watch real people and the humility to believe what you see.