How it works
A short, honest loop between builders and real users.
For builders
- 1
Describe the product
Name, description, category, the live URL, product stage and any login instructions your testers need.
- 2
Define the target tester
Countries, age range, job role, industry, company size, device, experience level and the software they already use. Add screening questions if you need them.
- 3
Write one realistic task
Something a real customer would try to do. General “what do you think” prompts produce vague feedback.
- 4
Choose your questions
Start from six recommended questions, then edit, reorder, remove or add your own. Each can be a long or short written answer, a 1-5 rating, yes/no or multiple choice.
- 5
Pick the number of testers
3, 5, 10 or 20. The price is shown before you confirm and includes what each tester is paid.
- 6
Review the responses
Read the organized summary or go straight to the raw written answers. Send one follow-up question per response.
For testers
- 1
Build your profile
Age range, country, job role, industry, devices and the tools you use. This is what builders see - never your name or email.
- 2
Accept a matching test
Every card shows the reward, estimated time, required device and how many testers are still needed.
- 3
Do the task first
Open the product, complete the task, then write your feedback based on what actually happened.
- 4
Write specific feedback
Name the exact screen or step where you hesitated and give at least one concrete example. Copy-pasted or AI-generated answers are rejected.
- 5
Get approved and paid
Builders review submissions. Approved work adds to your wallet and your reputation score.
Trust, privacy and safety
- Builders receive profile attributes relevant to the test only. No names, emails or contact details.
- Builders confirm in the wizard that they own the product or are authorised to have it tested.
- Testers agree not to publish or repeat anything confidential they see inside a product.
- Every submission has a quality status: pending, approved, revision requested or rejected. Either side can report a test or a submission for review.
- Organized summaries are labelled as such and always sit next to the original written responses.