Recruit for responsibility, not just a senior title
A CEO, CFO or procurement director may sound like the right participant. But a title alone cannot tell you whether that person has recently dealt with the problem you’re investigating.
If your product concerns supplier onboarding, someone who has led a supplier evaluation may be more useful than a more senior executive who only approves contracts at the end. An operations owner or IT lead might be more relevant than the expected executive.
Define responsibility, experience and company context before recruiting. Services such as User Interviews can help target and screen professional participants. Your team still needs to decide what each interview must establish.
Give each hard-to-recruit role a specific research job
Before booking executive or specialist in-depth interviews, decide what each participant should help establish.
| Responsibility to investigate | Explore with a virtual customer | Recruit someone who can establish |
|---|---|---|
| Procurement: How might supplier selection and onboarding work? | Possible evaluation steps, handoffs, alternatives and concerns. | How a recent supplier review actually unfolded, who participated and what delayed or changed the decision. |
| Finance: What could justify investment? | Possible budget trade-offs, evidence requirements and business risks. | What happened in a comparable approval or rejection, and what financial criteria mattered. |
| Technology: What could make adoption difficult? | Potential integration, security, support and ownership questions. | Which technical reviews occurred in a relevant implementation and who had authority to approve it. |
Treat these as responsibilities, not a fixed three-person buying committee. Add a CEO or another role only if their involvement could materially change your research decision. One participant may cover several responsibilities if their experience supports it.
Each interview now has a purpose beyond collecting another opinion.
Explore the roles inside the same business world
Virtual Customer is built specifically for B2B customer discovery. You define a customer company’s region, industry and size. The platform builds a business world model covering its business environment, market and organizational context. Virtual customer roles operate within that modeled setting, with different goals, responsibilities and areas of knowledge.
For example, keep a medium-sized US manufacturing company and a supplier-management concept constant while exploring procurement, finance and technology perspectives. A virtual procurement leader might raise supplier qualification questions; a CFO might explore the business case; a CTO might consider implementation dependencies. These are possible perspectives, not findings about actual companies.
Talk with each virtual customer by text or voice. Return to the same perspectives when the concept changes. For another region or company size, define a separate context instead of assuming the first still applies.
Keep exploring while recruitment continues
Before interviews: Start with the customer’s existing work, not your proposed feature. Use virtual dialogues to examine competing explanations and identify missing responsibilities. Turn those possibilities into screening criteria and open interview questions.
During customer research: Ask participants to reconstruct recent situations and decisions in their own words. An interview provides firsthand accounts of experience; a simulated perspective does not. Leave room for answers that contradict your earlier hypotheses.
Between rounds: When the product changes, revisit the virtual customers with the new version. Capture which questions still need customer evidence and which new roles may matter. You can explore without a new recruitment round, but decisions about actual experience or behavior still need customer evidence.
Example: the supplier-management concept changes mid-recruitment
Consider a B2B software team developing a supplier-onboarding platform for medium-sized industrial companies in the United States. A conversation with a finance sponsor is booked. Suitable procurement and technical participants are not yet available.
The team explores virtual Head of Procurement, CFO and CTO perspectives in the same modeled business context. It starts by asking how supplier information might move between teams, rather than presenting its solution as the answer.
Then the product team adds automated supplier-risk alerts. It returns to the same virtual customers to explore possible changes in responsibility, review requirements and implementation effort. The team records hypotheses and refines its recruitment criteria.
When the interviews take place, the researchers investigate recent supplier reviews and implementation decisions. Customer accounts may redirect the earlier exploration and inform the next product decision.
Start with the customer role you cannot reach yet
Choose a product decision and define one B2B customer context: industry, region and company size. Create a virtual Head of Procurement and CFO in that context. Ask first about their responsibilities and existing approaches, then introduce your product idea. Return to the same customers when you change the idea.
Write one participant-screening requirement and one unanswered question that needs firsthand customer experience. You now have a more purposeful next interview, and a way to keep exploring while you wait.
For help turning that question into fieldwork, see how to prepare better B2B customer interviews.