“Small businesses” includes people with very different tasks, budgets and authority. A study aimed at all of them can collect many answers while leaving the founder unsure which workflow to build for first.
For early product discovery, choose an audience narrow enough that its relevant context can be understood. Narrowing the study does not require claiming that everyone outside the group will never become a customer.
What defines a useful early research audience?
Define the activity, circumstance and decision role that matter to the research question. Industry and company size can provide context, but they may not explain who actually performs the task.
For a missed-enquiry product, the initial audience might be people who personally coordinate incoming service requests in a particular operating arrangement. That is more specific than any founder or office employee.
Build an audience hypothesis worksheet
Use the following proposed fields to distinguish relevant boundaries from convenient demographic filters. The example is fictional and does not establish a target market.
| Audience field | Research purpose |
|---|---|
| Task performed | Establishes direct experience |
| Operating context | Explains constraints on the workflow |
| Recent involvement | Supports concrete accounts |
| Decision role | Separates user, approver and buyer |
| Important variation | Identifies cases needed for comparison |
| Excluded context | Makes the study boundary explicit |
Avoid narrowing only to people who already like automation. That selection can hide effective manual workarounds and reasons the proposed product may not fit.
Recruit for the question rather than easy agreement
Use channels where relevant people can be reached appropriately and record how participants were found. Keep the recruitment message clear about the activity and expected effort.
The GOV.UK recruitment guide provides primary context for finding relevant users. The first-respondent guide turns that concern into a founder-facing recruitment brief.
Expand when evidence justifies the next comparison
If the first group reveals a repeated problem, test a meaningful adjacent context rather than simply broadening the invitation to everyone. Compare what changes in the task, consequence or purchasing process.
My StackFlight case study describes study collection and founder review. It does not claim that a platform chooses the right audience or establishes market size for the founder.
Record findings with the audience boundary attached. A useful conclusion can be that a problem appears important in this specific context while remaining uncertain elsewhere. That is a stronger basis for a focused MVP than a broad claim based on unrelated respondents.
Does a narrow audience limit future growth?
It defines the current learning boundary. Future expansion can follow evidence from additional contexts.
Should we recruit only likely buyers?
Choose participants for the research question and distinguish user experience from buying authority rather than treating those roles as identical.
What should we write first?
Describe the task, context and relevant role before a customer discovery discussion.