How to Recruit User Research Participants (Without a Big Budget)

Author: Inputly

How do you recruit user research participants?

Recruiting is a sequence, not a scramble. Define the behavior you need to observe, write a two minute screener, invite people who already show that behavior, pay for their time, and hand them a booking link. Your own product is the fastest source: pull users who match the question (churned in the last 60 days, used a feature three times), email them personally, and offer one click scheduling. Five or six sessions per round answer most questions.

The order matters. Teams that ask who is willing to talk end up with whoever is friendliest, not whoever is representative. Recruiting is the part of product discovery teams skip, then blame when sessions come back vague.

How many participants do you actually need?

It depends on the question, not the budget.

| Research question | Sessions | Why that number | | --- | --- | --- | | Usability test on one task | 5 | Severe problems repeat by the fifth session | | Concept or pricing test | 8 to 12 | Preferences vary far more than ability | | Churn and win loss | 6 to 10 | You need patterns, not one story |

Run rounds, not one long study: five sessions, fix the top three problems, then five with fresh people to see whether the fix worked.

Where should you find participants?

Rank sources by how close they are to the behavior you are studying.

• Your own user base, filtered by behavior. The default source, and the only one with full history.
• Churned and lost accounts. They owe you nothing and say the most useful things.
• Feature request voters. People who already argued for a change are motivated, and you can see what they asked for in feature voting.
• Communities where your users talk. Contribute for a few weeks, then invite. Never drop a form into a group you have never posted in.

Never recruit colleagues. They know the intended flow and forgive what real users trip over.

How do you write a screener survey?

Keep it under six questions and two minutes of effort.

1. Screen on behavior, not opinion: ask how often in the last 30 days someone did the thing.
2. Put the disqualifying question first, so the wrong people stop early.
3. Add one open text question about the last time they did the task.
4. Mention the incentive and session length before asking for contact details.
5. Log every rejection with a reason, so you can defend the sample.

A screener exists to exclude people, so a small clean panel beats a large messy one. The rules behind a good customer feedback survey apply here too.

What incentives work, and what does not?

| Participant | Incentive | Notes | | --- | --- | --- | | Existing customer | 25 to 50 dollar card or account credit | Credit is cheaper and keeps value in the product | | Churned customer | 50 to 75 | They have no reason to help you | | Specialist or non user | 75 to 150 | Panel rates, paid up front |

Never tie payment to a positive opinion, and pay the same day. For B2B, credit or a donation avoids procurement delays. Reach hard to fill segments through a paid panel.

How do you cut no-shows?

• Send a calendar invite with the meeting link, not a time to confirm later.
• Remind at 24 hours and one hour before.
• Offer two slots, hold one standby participant, and overbook by about 20 percent.
• If someone misses twice, take them off the list and move on.

What mistakes should you avoid?

• Recruiting only power users, who know the product too well to be surprised.
• Explaining what you are building before they describe their own work.
• Using friends and family as a shortcut, which produces polite noise.
• Collecting sessions and never reporting back, which kills the loop you build when closing the feedback loop.

How do you keep a participant pool warm?

• End every session by asking who else you should talk to. Referrals beat panels.
• Rotate people, or six friendly voices become a second opinion department.
• Add a happy to talk to the team checkbox to your in-app feedback widget, and re-invite new users about their onboarding.

Frequently Asked Questions

1. How long should a session be? Thirty to forty five minutes for interviews, twenty for a usability test. Long sessions get declined.
2. Can you recruit from support tickets? Yes, often the best list you have. Reach the user a day after the ticket closes.
3. What if nobody replies? Expect a 5 to 15 percent response rate on cold email. Send fewer, more personal messages.
4. Do you need recording permission? Yes. Ask before recording, and share the summary later.
5. When should you stop recruiting? When a round stops producing new problems, not when the calendar is full.

Store what participants tell you in one place. Create a free Inputly space to collect the requests that come out of every session.