What to do:
Evaluate whether SaaS founders can quickly understand Seerist's value proposition as a unified business OS and locate the Pitch Queue feature entry point within 5 minutes.
Navigate to https://seerist.xyz/ and read the homepage headline and subheading to identify what problem Seerist solves
Scroll down to locate and review the 'See how it works' section to understand the core features listed
Click or locate the 'Start your Pitch Queue' call-to-action button and observe what happens or where it directs
Identify and click on the 'How it works' navigation link to assess feature clarity and product positioning
Return to homepage and attempt to locate the 'Pricing' link to determine if pricing information is publicly accessible without sign-in
Evidence: Record screen navigation and note: (1) time to identify main value proposition, (2) clarity of feature names (Pitch Queue, IDE, Growth, Agents), (3) whether CTAs require sign-in or allow exploration, (4) any confusion points in navigation or messaging. Document findings in 2-3 sentences.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
Send video evidence for every issue in the accepted tester chat.
Record your screen and microphone audio for the full test. Narrate your actions, every error you find, and anything confusing, poor, or worth improving.
Attach the narrated video as an MP4, MOV, or WebM no larger than 75 MB, plus at least one representative screenshot.
For each issue include a short title, a severity (critical/high/medium/low), and exact steps to reproduce.
Submissions are reviewed automatically. $4.00 is released per accepted submission.
What you must do to be paid
Before you apply
Access to a device that can open https://seerist.xyz/
Evaluate whether SaaS founders can quickly understand Seerist's value proposition as a unified business OS and locate the Pitch Queue feature entry point within 5 minutes.
1. Navigate to https://seerist.xyz/ and read the homepage headline and subheading to identify what problem Seerist solves
2. Scroll down to locate and review the 'See how it works' section to understand the core features listed
3. Click or locate the 'Start your Pitch Queue' call-to-action button and observe what happens or where it directs
4. Identify and click on the 'How it works' navigation link to assess feature clarity and product positioning
5. Return to homepage and attempt to locate the 'Pricing' link to determine if pricing information is publicly accessible without sign-in
Evidence: Record screen navigation and note: (1) time to identify main value proposition, (2) clarity of feature names (Pitch Queue, IDE, Growth, Agents), (3) whether CTAs require sign-in or allow exploration, (4) any confusion points in navigation or messaging. Document findings in 2-3 sentences.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 75 MB with spoken microphone narration throughout, plus at least one representative screenshot. Captions, written narration, and on-screen text do not replace the required microphone audio.
5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
•
Access to a device that can open the target URL
•
Report every issue with a severity and exact reproduction steps
•
Only submit evidence you captured yourself during this run