Existing contacts
Ask customers, former colleagues, classmates, or friends only when they genuinely resemble the intended user. Explain that you need honest reactions, not encouragement.
Early product validation
Find product testers without inventing a crowd.
For an early website, five relevant conversations can be more useful than a hundred vague clicks. Start with people you can actually invite, then ask them to attempt one realistic task.
Create a test taskGefimi does not supply a panel or send invitations for you. It helps turn a product question into a brief you can take to people who plausibly face the problem.
Choose people by context
Recruit for the decision, not the demographic.
Relevant communities
Request permission before posting in a niche group. Say what the product is, who the task is for, how long it takes, and that participation is voluntary.
Professional networks
Use a personal message for a narrow role or workflow. A specific reason for asking is more respectful than a generic call for “testers.”
A small recruitment note
Make the request easy to decline.
- Name the page or product and the situation it is meant for.
- Ask for one concrete task, such as finding a price, explaining the offer, or starting a trial.
- State the expected time and what you will record; do not collect private data you do not need.
- Thank the person, including when they decide not to participate.
What to save
Observations beat a vote count.
Note where a person paused, what they expected before clicking, what words they used, and whether they completed the task unaided.
Separate what you observed from your interpretation. One confusing moment is a signal to investigate, not proof of a universal problem.
Keep the participant’s contact details and consent outside any public notes.