Great testers get their feedback approved consistently — which means more credits and a better reputation. Here's a detailed guide with examples.
1. Narrate your thought process
This is the single most important thing you can do. Think out loud — constantly. Say what you expect to find, what you're looking for, and what confuses you. This gives founders a window into a real user's mind.
Do: "I'm looking for pricing, but I don't see it in the nav. Let me check... oh, it's under 'Plans.' That's not where I expected it. I would have looked for 'Pricing' or 'Cost.'"
Don't: (silence while clicking around) — the founder sees you clicking but has no idea what you're thinking.
Do: "Okay, so this says 'Grow faster.' I'm not sure what that means — is this a marketing tool? A productivity app? Let me scroll down and see if there's more info..."
Don't: "Looks good." — this tells the founder nothing.
2. Be specific
Vague feedback isn't actionable. Specific feedback is gold.
Bad: "This is confusing."
Good: "I'm not sure if this is a product or a service. The headline says 'grow faster' but I don't know what the product actually is. Is it software? A course? A consulting service?"
Bad: "I don't like the design."
Good: "The hero image is really dark and the text on top of it is hard to read. I had to squint to see the headline. A lighter image or a text overlay would help."
Bad: "The sign-up was hard."
Good: "The sign-up form asked for my phone number, but there was no explanation of why you need it. I almost didn't complete it because I wasn't sure if I'd get marketing calls. Adding a note like 'we'll only text you about your account' would make me more comfortable."
3. Be honest, not harsh
You don't need to be mean to be honest. Founders are real people who've put real work into their sites.
Honest & constructive: "I didn't understand what this page was about. The headline is vague and I couldn't tell what the product does until I scrolled to the third section."
Just harsh: "This is garbage. I have no idea what you're selling."
Both convey the same information, but the first helps the founder understand the problem, while the second just makes them defensive.
4. Share expectations vs. reality
One of the most useful things you can tell a founder is what you expected vs. what you found. This gap is where the best insights live.
Example: "When I saw 'Pricing' in the nav, I expected a simple table with 3 tiers. Instead, I found a custom calculator that asked me a bunch of questions. That was unexpected — I wasn't prepared to answer questions, I just wanted to see the numbers. I'd suggest offering a simple pricing table first, with the calculator as an option."
5. Point out what works, too
Don't just report problems. Tell founders what's working so they don't accidentally change it.
Example: "The testimonial section was really effective — seeing real names and photos made me trust the product more. The social proof near the sign-up button also gave me confidence."
6. Stay on task
Answer the questions asked. If you have unrelated thoughts, save them for the wrap-up questions. Tangents reduce the quality and focus of your feedback.
If the test asks about the homepage clarity, don't spend 5 minutes critiquing the blog footer. Stay focused on what the founder asked.
7. Don't rush
A 3-minute thoughtful test is worth more than a 30-second skim. Take the time to genuinely engage with the site, try the tasks, and form real opinions.
Creators can see how long you spent. Very short responses are often rejected because they indicate you didn't take the test seriously.
8. Check your tech before you start
Before you begin recording:
- ✅ Close other tabs and notifications — you don't want a Slack pop-up in your recording.
- ✅ Test your microphone — make sure it's picking up your voice clearly.
- ✅ Check your screen — make sure the right tab will be recorded.
- ✅ Use a supported browser (Chrome or Firefox recommended).
- ✅ Make sure you have a quiet environment.
Technical issues can invalidate your response, so it's worth taking 30 seconds to check.
9. Watch the "do" vs. "don't" examples
| Situation | Don't | Do |
|---|---|---|
| Homepage first impression | "Looks nice." | "The hero says 'Transform your business' but I'm not sure what the product is. Is it software? A service? I'd like to see a clearer value proposition." |
| Navigation | "The nav is fine." | "I expected to find 'Pricing' in the main nav, but it's under 'Resources.' That's not where I'd look for it." |
| Sign-up flow | "It worked." | "The sign-up form asked for my company size, but I didn't see why that's needed. I almost abandoned because it felt like too much info for a free trial." |
| Overall impression | "It's good." | "The design feels modern and clean, which built trust. But I'm still not sure what the product does after 30 seconds of scrolling." |
Quick pre-submit checklist
- ✅ Did I narrate my thought process throughout?
- ✅ Did I answer every question with specific, actionable detail?
- ✅ Did I share expectations vs. reality where relevant?
- ✅ Did I mention what's working, not just what's broken?
- ✅ Did I spend enough time to give thoughtful feedback?
- ✅ Is my audio clear and my screen visible?
If you can check all these boxes, your feedback will almost certainly be approved.