User Research Before You Hire Anyone

Most founders I work with share a common thought: they need to hire a UX researcher or designer before they can talk to users properly. I don’t know where this has come from — it’s not true.

The conversation usually starts the same way. A founder has an idea, maybe a rough prototype they should validate. Someone told them to 'talk to users', they've heard about design sprints and user interviews and journey mapping, but it all sounds expensive and formal.

So they ask: "Should I hire a researcher first?"

The answer, again, is almost always no. You can do useful research yourself, right now, with the people you already have access to. You just need to know what to look for and how to ask.

The User vs Customer Distinction

Before we get into methods, clarify this: your user might not be your customer.

A user is someone who interacts with your product. A customer is someone who pays for it. Sometimes they're the same person. Often they're not. Don’t conflate the two and build something users love but customers won't fund.

If you're building software for schools, the user might be a teacher or student. The customer is the head teacher or procurement team. This distinction shapes your research. You need to understand what the user needs and what the customer is willing to pay for.

For the purposes of this piece, when I say 'user research', I mean understanding the person who will interact with what you're building. Customer research is adjacent but different.

What User Research Is

User research is not a formal, expensive process requiring trained professionals. At its core, it's structured curiosity about the people you're building for.

You're trying to answer a few fundamental questions: What problem are they experiencing right now? How are they solving it today (even if badly)? What would make a solution worth changing their behaviour for? What would stop them using it, even if it worked?

The goal is to learn whether the problem you think exists really exists, and whether your proposed solution maps to how people work.

Most of the useful research I've done with founders in the last two years has been low-cost and informal. Fifteen-minute Zoom calls, coffee with someone, or even watching someone try to complete a task using their current tools.

Five Research Methods You Can Use This Week

1. The 'Show Me' Conversation

Find someone who fits your target audience. Ask them to show you how they currently solve the problem you're addressing. Don't pitch your idea. Just observe.

You'll see their workflow, the tools they use, where they get stuck and what they've built workarounds for. This is worth more than fifty survey responses.

2. The Five-Person Rule

You don't need hundreds of interviews. In most cases, talking to five people in your target user group will surface 80% of the usability issues and workflow problems.

The key is talking to the right five people. If you're building for care home managers, talk to five care home managers. Not someone whose nan is in a care home.

If all five people describe the same problem in similar terms, you're onto something. If they describe five completely different problems, your audience definition is too broad.

3. The 'Current Solution' Audit

Make a list of every tool, spreadsheet, form, or manual process your target users currently rely on to do the thing your product is supposed to help with.

If they're using three different spreadsheets, a shared Google Doc and a WhatsApp group, that tells you something. The problem is real and there’s a cobbled-together solution that shows you what ‘good enough’ looks like.

Your product needs to be meaningfully better than their Frankenstein setup. If it’s right, they'll feel it in the first week.

4. The Task-Based Test

Once you have wireframes or a rough prototype, ask someone to complete a specific task using it. Do not guide them or explain further.

If they can't complete the task without your help, the design isn't ready yet.

I've seen founders realise in ten minutes that their 'intuitive' interface made no sense to anyone outside their own heads. That realisation is cheap when it happens before you build the thing. Expensive when it happens after launch.

5. The Follow-Up Question

'Why?' is your most powerful research tool. When someone says "I'd use that", ask why. When they say "I wouldn't pay for it", ask why. When they say "We tried something similar before", ask what happened.

People are polite. They'll say nice things about your idea to avoid hurting your feelings. Dig past the politeness. What you're looking for is the moment when they stop being polite and start being honest, usually when you ask them to describe a specific situation or decision.

What Good Research Feels Like

You'll know your research is working when you start hearing the same phrases repeated by different people.

If three separate users say "the problem is we waste time chasing approvals", you've found a real pain point. If every person describes the problem differently, you might be solving five different problems (which means you're solving none of them well).

Good research also makes you uncomfortable. If everyone you speak to validates your idea exactly as you imagined it, you're probably asking leading questions or talking to the wrong people.

The best research I've been part of has included at least one moment where the founder says "I hadn't thought about it that way." That's the signal that you're learning something useful.

When to Hire Professional Help

There are times when you do need a researcher or designer. Usually when you're past the validation stage and into detailed usability work, accessibility requirements or complex user journey mapping.

If you're building a regulated product (health, finance, education), you'll likely need professional UX input earlier. If you're designing for users with specific needs (elderly users, users with disabilities), get expert help.

For early-stage validation and problem discovery? You don't need to hire anyone. You just need to get comfortable having conversations with strangers.

The Research You're Avoiding

Most founders skip user research because it's uncomfortable or inconvenient.

It's easier to build in isolation than to risk hearing "I don't think anyone needs this." It's easier to assume you understand the user than to sit through fifteen minutes of someone struggling with your prototype.

I get it. I've been there. You're emotionally invested in the idea and it feels personal.

But sometimes a few uncomfortable conversations and a hard realisation will save you from six months of building the wrong thing. The earlier you have those conversations, the less attached you'll be to any particular solution.

You don't need a researcher or designer to do useful user research. You need five people who fit your target audience, a list of questions focused on current behaviour (not hypothetical future behaviour), and the discipline to listen more than you talk. Start with 'show me how you do this today'. Progress to 'can you complete this task using my prototype'. Hire professional help when you're refining, not when you're still figuring out if the problem exists.

Want to validate your idea properly before you build? Download the MVP Cost Clarity Toolkit — it includes a user research checklist designed for founders working alone.