The first people who answer a founder's study are often friends or enthusiastic followers. Their feedback may be useful, but it does not automatically represent the people who experience the problem you want to solve.
For founders recruiting an initial discovery group, define relevance before chasing response volume. A small purposeful sample can answer an early question when its limits remain visible.
What makes a respondent relevant to discovery?
Relevance comes from experience with the problem, workflow or decision being studied. Job title alone may be too broad if only some people in that role perform the task.
Write an eligibility description that a participant can understand without revealing the answer you hope to hear. Avoid screening only for people who already like your proposed solution.
Build a recruitment brief around behaviour
Use a fictional product for coordinating maintenance enquiries. The proposed brief might target people who recently handled those enquiries and can describe the current process.
| Recruitment field | Useful detail |
|---|---|
| Relevant activity | Task the person has actually performed |
| Recency | Period appropriate to the research question |
| Context | Business type or operating constraint that matters |
| Exclusions | Relationships or roles that bias this particular study |
| Participation request | Expected activity, time and recording choice |
The GOV.UK participant recruitment guide provides a primary reference for finding relevant users. Adapt the recruitment process to your audience and approved research arrangements.
Choose channels with visible selection limits
Professional communities, existing contacts and relevant organisations can each provide access to participants. They also shape who is likely to respond. Record the source so later findings are not presented as though respondents were selected randomly from the whole market.
Ask permission before posting a study in a community, and keep invitations concise about purpose and expected effort. Do not promise a product benefit or sales opportunity merely to improve participation.
Keep early findings appropriately scoped
A first group can reveal vocabulary, workflow steps and potential problems to investigate. It cannot by itself establish market size or guarantee demand for a proposed feature.
My StackFlight case study describes a study-and-review product, not a claim that its respondents represent every founder's target audience. The recruitment design remains part of the research responsibility.
Review which relevant people did not participate and whether an important context is missing. Use that gap to plan the next round rather than simply collecting more responses from the easiest channel.
Should we exclude all friends from an early study?
Their experience can be useful when relevant, but record the relationship and avoid treating the sample as representative of an entire audience.
Is a job title enough screening?
Ask about the relevant activity and context, since people with the same title can have different responsibilities.
What should we write before recruiting?
Prepare the research question, eligibility and participation request before a discovery workflow discussion.