How to Recruit B2B SaaS Users for UX Research

Recruiting B2B SaaS users for UX research can feel like a project in its own right. The people you need may be busy, hard to reach, or subject to company rules about discussing software. And a participant’s job title rarely tells you whether they actually use the workflow you want to study.

The solution is not simply to send more invitations. Start by defining the decisions your research needs to inform, then recruit people who have direct experience with those decisions or tasks. This guide explains how to do that, from setting criteria to handling incentives and scheduling—without treating a narrow professional audience as if it were easy to access.

Start with the research question, not the job title

“We need more product managers” is not a useful recruiting brief. A product manager may be an administrator, an occasional approver, or someone who has never opened the feature under study. Recruitment should reflect the behavior and context your team needs to understand.

Write down the decision the research will support. For example: “Should we simplify the weekly invoice approval flow, and where do finance reviewers get stuck?” That points to a more specific audience: people who review invoices in the product, how often they do it, and whether they approve or reject them.

Turn the question into observable criteria

Separate essential criteria from useful context. Essential criteria determine whether someone can speak from relevant experience. Context helps you compare different situations without making the audience impossibly narrow.

• Role in the workflow: Does the person create, review, approve, administer, or report on the work?
• Recent experience: Have they completed the task recently enough to describe it accurately?
• Frequency: Is the task daily, monthly, or only triggered by an exception?
• Environment: Do they work in a small company, a regulated organization, or a team with several approval layers?
• Product relationship: Are they a current customer, a former customer, or someone using a competing process?

For the invoice example, an essential criterion might be “personally reviewed at least one invoice in the past month.” Company size could be a useful comparison, but insisting on a particular industry, title, region, and accounting system may make recruitment unnecessarily difficult.

Decide in advance which differences matter. If the study concerns a new admin setting, include administrators. If it concerns everyday task completion, prioritize hands-on users. When both perspectives matter, recruit them as distinct participant groups rather than assuming one person represents both.

Choose a recruitment route that fits your audience

B2B participant sourcing often depends on how close your team is to the people it wants to learn from. Each route has trade-offs. Existing customers are reachable, but may be unusually engaged. A recruiting panel can help find people beyond your customer base, but screening needs to verify real task experience. Your own sales or support teams can make introductions, but their involvement may influence what participants feel safe saying.

Recruit through current customers

Customer success, support, and account teams can identify customers who match a study’s criteria. Give them a short, neutral invitation to forward—not a list of customers to pressure. Ask account owners to avoid selecting only enthusiastic advocates or people who have recently praised the product.

Make the purpose clear: research is intended to improve the product, not assess the customer’s performance or renew a contract. Where possible, let the researcher handle follow-up and scheduling. This reduces the chance that a participant feels obliged to take part because their account manager asked.

Customer recruitment is useful for understanding existing workflows, but it will not tell you how non-customers solve the same problem. If you are evaluating onboarding or switching barriers, include people who are evaluating, have recently rejected, or have recently left the product, where you can reach them appropriately.

Use professional communities and referrals carefully

Industry associations, user groups, and professional communities may help you reach people with specialist experience. First check the community’s rules and ask moderators before posting. Keep the request specific and respectful; a generic “we want feedback” message gives people little reason to respond.

Referrals can be effective when a target role is uncommon. Ask participants to pass along your invitation rather than provide another person’s contact details without permission. Referral chains tend to reproduce the same networks, so they should not be your only source if you need varied company sizes, regions, or working practices.

Consider a specialist recruiting panel

A panel can save time when you need people outside your customer base or with a less common role. It does not remove the need for careful screening. Confirm that the panel can recruit for the actual task, not just a job title, and ask how it verifies eligibility and handles participant data.

Budget for the full cost: sourcing, screening, incentive administration, rescheduling, and any replacement participants. A panel may be a poor fit if your audience is very small, if participants need access to confidential systems, or if the research depends on a long-standing customer relationship.

Write an invitation that respects the participant’s time

A good invitation answers the questions a busy professional is likely to ask: What is this about? Why are you contacting me? How long will it take? What will I be asked to do? Is there an incentive? Will my employer or account team see what I say?

Keep the description accurate without revealing so much that it coaches participants toward a preferred answer. For example, “We’re studying how finance teams review and resolve invoice exceptions” is clearer and less leading than “Help us prove our new approval dashboard saves time.”

State the expected duration, format, and any preparation. If someone must bring a laptop, use a demo account, or show a typical workflow, say so before they book. Offer a range of meeting times and an easy way to decline. Avoid implying that taking part is a condition of receiving support or maintaining a customer relationship.

Government guidance on recruiting participants for user research recommends planning recruitment around the users and research needs, rather than treating participant sourcing as an afterthought. That is a useful principle for B2B work too: decide what experience qualifies someone before inviting them.

Screen for experience without making the form a burden

A screener should establish whether a person fits the study, not collect a complete profile of their company. Ask only what you need to decide eligibility and organize sessions. A short form is usually more respectful and easier to complete than a detailed questionnaire full of questions you may never use.

Use behavior-based questions

Ask about recent actions rather than asking people to label themselves as “power users” or “decision-makers.” Those terms mean different things across organizations and can invite optimistic answers.

• “When did you last review or approve an invoice?”
• “Which parts of that process did you personally complete?”
• “About how often does this happen in a typical month?”
• “Do you use software to do this, or another method?”

For a prototype test, you may need a different screener than for contextual inquiry. Someone who can describe the current process may be suitable for an interview; a usability test may require the participant to be the person who actually performs the task. Match the screening questions to the method. If you are deciding between methods, see our guide to user interviews versus surveys.

Check answers consistently

Use the same eligibility rules for everyone. If a participant’s answer is ambiguous, ask a neutral follow-up rather than interpreting it to fill a quota. Watch for contradictions, but do not assume that a polished job title proves relevant experience.

Keep screening information separate from research notes where practical, and limit access to people who need it. If you are collecting names, work emails, or details about someone’s role, explain why and how you will use them. The UK Information Commissioner’s Office outlines how research involving personal information can fall under data protection requirements; consult its guidance on research and data protection and your organization’s privacy or legal team for the rules that apply to your situation.

Plan for incentives, permissions, and confidentiality

An incentive recognizes the participant’s time; it is not a reward for positive feedback. Choose an amount and format that suit the length and burden of the session, your audience, and local norms. A short remote task and a half-day onsite observation have different costs to the participant. If you cannot offer cash, consider an approved alternative, but check whether the participant’s employer allows them to accept it.

In some organizations, employees cannot accept personal payments or gifts from vendors. Offer an option that can be paid to a company, donated, or declined, if your process supports it. Do not ask participants to bypass their employer’s policies. Make the incentive terms clear before the session, including whether it is provided for attendance or completion.

Confidentiality matters especially when participants discuss internal processes, customer data, or a product under development. Tell them what will be recorded, who will see the material, how quotes may be used, and whether the session will be shared internally. Avoid asking people to expose sensitive customer or company information. Use a prototype or sanitized examples when real data is not necessary.

Consent is not just a box to tick. Give participants enough information to make a voluntary choice, and explain that they can pause or stop. The AAPOR Code of Professional Ethics and Practices emphasizes voluntary participation and responsible handling of research information; those principles are relevant even when a UX study is not a formal survey.

Schedule around real working conditions

Scheduling is a common source of drop-off. B2B participants may need approval from a manager, have customer-facing calendars, or work across time zones. Offer several slots and avoid expecting someone to find a quiet hour at short notice. For remote sessions, tell them whether they need video, screen sharing, or access to a particular device.

Send a concise confirmation and a reminder with the meeting link, duration, incentive details, and any setup instructions. If the session involves a work system, make clear that participants should not share credentials or confidential records. Prepare a fallback task or demo environment in case access is blocked.

Build some flexibility into recruitment. A scheduled participant may cancel because of a deadline or a customer issue. Keep a small reserve of eligible people when timing allows, but do not invite far more participants than you can reasonably compensate and schedule. If a session is missed, follow up politely once; repeated pressure is not worth the damage to trust.

Recruit enough people to answer the question—not to fill a quota

There is no universal participant count for B2B research. The right number depends on the method, the diversity of workflows, the risk of the decision, and whether you are looking for patterns or measuring a defined outcome. A focused usability study of one task needs a different plan from research comparing several industries and buyer roles.

For exploratory work, begin with a manageable group representing the most important user types, review what you learn, and recruit more if meaningful gaps remain. For a quantitative survey, plan around the question, sampling approach, and precision you need; do not treat a handful of responses as representative of a market. This is one reason to keep interviews and surveys distinct in the research plan rather than using participant count as a substitute for method choice.

Make a simple recruitment matrix before outreach. For example, a billing workflow study might include daily operators, occasional approvers, and administrators. Add company size or region only if the research question depends on those differences. A matrix helps reveal when one group is missing and prevents the easiest-to-reach customer segment from silently becoming the entire sample.

When time is tight, prioritize the research decision and be explicit about what the sample cannot tell you. A small study can uncover usability problems in a workflow; it cannot establish how common those problems are across all customers. For help making a research plan with limited capacity, see how to plan UX research when your team has no dedicated researcher.

Common recruitment mistakes to avoid

• Recruiting by seniority alone. A buyer may not be a daily user, and a daily user may not control purchasing. Define which perspective the study needs.
• Using only enthusiastic customers. Advocates can provide valuable feedback, but their experience may not reflect people who struggle, disengage, or leave.
• Over-screening. Every extra criterion shrinks the pool. Keep only requirements tied to the research question.
• Letting sales or support sit in without a plan. Their presence can change what participants say. If their input is needed, explain their role and consider having the researcher conduct the session alone.
• Promising anonymity carelessly. In a small professional market, a role, company size, and distinctive quote may identify someone. Promise confidentiality only to the extent you can protect it.
• Treating recruitment as separate from research quality. If the right people cannot be found, revisit the question, method, or scope before lowering the criteria without discussion.

A practical recruitment checklist

1. Write the decision the study will inform and the user behavior you need to understand.
2. Define essential eligibility criteria, plus any contextual differences worth comparing.
3. Choose the sourcing route—or mix of routes—and note its likely bias.
4. Prepare a plain-language invitation and a short behavior-based screener.
5. Confirm incentive rules, consent, recording, privacy, and confidentiality with the right internal partners.
6. Offer accessible scheduling and clear session instructions, then track attendance and gaps in the sample.
7. Review whether the participants you recruited can actually support the conclusions you plan to make.

Good B2B recruitment is less about finding a perfect representative and more about making thoughtful, transparent choices. Be specific about the work people do, reduce the effort required to take part, and state the limits of what your sample can tell you. That gives a product team evidence it can use without asking participants to carry the burden of a poorly defined study.

Frequently asked questions

How do I recruit B2B users if my company has very few customers?

Look beyond the customer list: professional communities, referrals, former customers, and specialist panels may help. Keep the criteria tied to the workflow rather than your product, and be transparent about why you are speaking with people who are not customers. If you can only recruit a small group, treat the findings as exploratory rather than representative.

Should I recruit decision-makers or people who use the software every day?

Recruit the people whose perspective matches the question. Study task usability with hands-on users; study purchasing, governance, or rollout decisions with buyers and administrators. If the product decision depends on both, include both roles and analyze their needs separately.

How much should I pay B2B research participants?

There is no single appropriate amount. Consider session length, preparation, disruption to work, local expectations, and any employer restrictions. Explain the incentive before booking and make clear whether it is for attendance rather than favorable feedback.

Can I use customer success managers to recruit participants?

Yes, they can identify customers who may fit, but give them a neutral invitation to forward and let participants respond directly to the research team. Avoid having account owners select only advocates or implying that participation affects service or renewal.

How can I protect confidential company information during a session?

Tell participants what will be recorded and who will see it. Ask them not to share credentials, customer records, or information they are not authorized to disclose. Use a demo account or sanitized examples when possible, and follow your organization’s privacy and retention policies.