How to recruit beyond your existing customer base

Your current customers can explain important parts of the experience you have already created. They cannot, by themselves, explain every reason someone never adopted it, left it, or solved the same problem another way.

Recruit beyond the customer base when the decision requires those missing perspectives. Begin with the question, then identify which experience groups could answer it. An indiscriminate mix of customers and strangers is no more useful than speaking only with loyal users.

The worked example here is hypothetical: a team building staff-scheduling software wants to understand why some multi-location retailers continue to coordinate schedules through spreadsheets and messages. The sample design is illustrative, not a claim about retail businesses.

Choose the comparison that serves the decision

If you are improving an existing scheduling screen, current users with relevant tasks may be the appropriate participants. If you are investigating why suitable businesses do not adopt the product, include people who handle the task through other means.

GOV.UK’s guidance on user needs includes actual and likely users and the ways they currently accomplish their goals. That is a useful boundary: recruit around the work, not simply around whether a person has an account. Read the user-needs guidance.

Write the missing perspective as a sentence. “We have not heard from managers who considered changing their scheduling process but continued with their existing approach” gives recruitment a specific job.

Avoid treating anyone unfamiliar with your product as a potential customer. They still need a relevant task and context. A retailer with a stable schedule at one small location may be informative, but it may not match a study focused on frequent changes across several sites.

Build an experience coverage matrix

Use relationship to the product as one dimension, then add the behavior or situation that matters to the research.

The last group may overlap the others. A store supervisor affected by a scheduling decision could be part of an organization that uses the product without controlling its purchase.

Keep such overlaps in the record rather than forcing everyone into a single marketing label. Your analysis may need both the account relationship and the participant’s operating role.

Keep one anchor task comparable across groups

For the scheduling example, ask each relevant participant about a recent change to a staff schedule: what triggered it, who acted, how the information moved, and how completion was confirmed.

That common event makes the accounts easier to compare. Current users can describe the task in your product; nonusers can describe a spreadsheet, another service, or a manual arrangement. Do not require all groups to discuss your interface before you understand their own process.

Use group-specific questions afterward. Former users may describe what changed over time. Evaluators can explain their comparison. People who never evaluated the product can discuss how they discover or select tools, if that is part of the question.

Do not manufacture a single satisfaction ranking from these different experiences. Someone cannot meaningfully rate a workflow they have never used.

Recruit through more than one doorway

Current-user invitations may come through an appropriate research opt-in or an established contact route. Former users and nonusers may require professional communities, relevant organizations, introductions, or targeted people search.

GOV.UK notes that recruitment methods, session times, locations, and activities can affect who is included. Using different approaches can help reduce those blind spots. Read the recruitment bias guidance.

Track how each participant entered the study. If every nonuser came through one partner, their apparent agreement may reflect a shared context. That does not invalidate their accounts, but it limits the comparison you can make.

Keep participation voluntary and respect existing communication preferences. Do not contact a former customer through a new channel to circumvent their request not to be contacted. Where direct outreach is unsuitable, a permitted public invitation or another recruitment route may be more appropriate.

Acknowledge compensation plainly when offered. It should not depend on whether the participant likes the product or supplies the conclusion the team wants.

Prioritize gaps instead of filling equal quotas

Equal numbers in every group can look tidy without serving the decision. Choose coverage based on the uncertainty, the differences you need to examine, and the evidence already available.

In the fictional scheduling study, the team might already understand current users’ workflows but have little knowledge of businesses that considered changing and decided against it. The next recruitment effort could focus there while retaining current-user evidence as context.

That choice does not make the result representative of all retailers. It creates a purposeful comparison. If you need a population estimate, design a separate study appropriate to that claim.

Write an allocation note before recruiting:

“Our main gap is [experience]. We need to compare it with [reference context] because [decision]. We are not prioritizing [group] in this round because [reason]. We will revisit the plan if [new evidence or missing coverage].”

This makes the sample design discussable and helps a colleague recognize when convenience is replacing the intended comparison.

Report the achieved coverage alongside the findings

At the end, record whom you actually reached. Distinguish completed sessions, people who declined, unresolved eligibility, and groups you could not recruit. Preserve the reasons when known without guessing why someone remained silent.

Compare findings within relevant contexts before contrasting entire groups. A difference between current users and nonusers may reflect company structure, responsibility, task frequency, or another condition—not merely adoption status.

Look for counterexamples. A nonuser may describe an effective existing process; a current user may report a serious gap. Both can refine the boundaries of the product’s value.

The final recommendation should state which perspectives support it and which remain absent. Expanding recruitment is useful when it changes what the team can understand, rather than simply increasing the number of names in the study.